As someone just learning Go, the current behaviour is really unexpected. I’m happy that they are changing it.
As someone just learning Go, the current behaviour is really unexpected. I’m happy that they are changing it.
Because it’s unintentionally funny even though not a dad joke and people might be seeing this on their all feeds without noticing the community name. It made me expel air out of both my nostrils at the same time.
The Google Play Store uses a technique called delta patching to calculate the diff server side and avoid transferring parts of the app that haven’t changed since your original installation.
This is understandably not perfect because they want to avoid load on their servers and also the extra processing on your device to “unpack” it. So what you have is a happy medium between sending the entire app again and sending strictly the diff.
React and Vue already have lots of libraries, components, and know-how. You can also move from CSR to SSR and back depending on your requirements.
That’s exactly how we got Javascript on the backend in the first place. I remember when this was the new “weird” thing.
That’s true, and you can also combine multiple errors to have a single catch block or handle each error separately. The perfect dataset for this comparison will need to be written. Code golf data is good enough for a non-academic fun analysis like this one.
I think code golf is a great dataset for this kind of analysis specifically because they are artificial and people are paying attention to the number of characters used. Leetcode solutions might be a better option though.
In real world projects there are too many confounding factors. People aren’t implementing servers in brainfuck or websites in C. Even rewrites of a project into another language have more/fewer features. So it’s an apples to oranges comparison.
My mileage has indeed varied.
It’s the same with Python support.
Yeah. Build machines should never have had internet access. Any dependencies your product uses should be downloaded once and then cached in your own artifactory. If you don’t, what you deploy in production could be different from what you tested in staging. That can allow attacks like this to happen much more easily.
It doesn’t look half-bad but i would rather have roughly the same firefox interface on every OS than have it customized for gnome as it appears here.
Even when running an instance for yourself, you’re not really safe. The threat to your privacy goes from being a third party in control of your data to your own operational inexperience.
I tried to host my own personal Lemmy instance and ran into a lot of issues hosting it. On the one hand you want to be safe by restricting unnecessary access, but on the other hand you have no idea why federation doesn’t work, or the postfix-relay docker cannot send an email, or why you cannot ssh into your own host, so you want to just allow everything and just get it to work somehow. In the end, unless you are already an expert at this stuff, trying to host your personal instance safely is a tall task.
It’s also going to be very costly. Especially for an image sharing website like Pixelfed.
Maybe there is a market for self-service managed hosts like we have with Wordpress blogs.
Hi, I’m Dr. Mordecai Tutu on this glorious day.
You know, saying that everyone except caucasians are “people of color” itself reeks of inherent racism.
Racism is quite common in the world. It always has been. It’s just that in most of our history our out-groups were still local so racism didn’t manifest.
Right now we’re at a point in the human journey where we see people of different races quite often, but we don’t interact often enough that it is no longer relevant for anyone. It’s improving.
Posted in /c/technology 😬
Well, using ai-generated answers to train their own ai would bring down the quality of answers and worse quality means lesser money. Don’t you want them to make any money??!!
You missed a /s marker