That requires a complete picture and all possible use cases from the start. Initially when a language is new and hardly used there are much to benefit from flexibility and trying new concepts. Then as the language matures, a more formal process is needed to ensure stability. There is a reason these discussions comes now, since rust is in a very stable phase.

As someone that have worked in software for 30 years, and deplying complicated software, shared libraries is a misstake. You think you get the benefit of size and easy security upgrades, but due to deployment hell you end up using docker and now your deployment actually added a whole OS in size and you need to do security upgrades for this OS instead of just your application. I use rust for some software now, and I build it with musl, and is struck by how small things get in relation to the regular deployment, and it feels like magic that I no longer get glibc incompatibility issues.

I actually asked chatGPT about a specific issue I had and solved a while back. It was one of these issues where it looked like a simple naive solution would be sufficient, but due to different conditions that fails, you have to go with a more complex solution. So, I asked about this to see what it would answer. And it went with the simpler solution, but with some adjustments. The code also didn't compile. But it looked interesting enough, for me to question my self. Maybe it was just me that failed the simpler solution, so I actually tried to fix the compile errors to see if I could get it working. But the more I tried to fix its code the more obvious it got that it didn't have a clue about what it was doing. However, due to the confidence and ability to make things look plausible, it sent me on a wild goose chase. And this is why I am not using LLM for programming. They are basically overconfident junior devs, that likes mansplaining.

I suggest an alternative title to this post: AWS employee is mad since Redis change license to prevent them from leaching

Didn't they switch to a license with stronger mechanisms to keep the source available? SSPL, is basically AGPL but have even stronger protection from large corperations to use the code in their data centers without contributing the changes back. This is basically a move to prevent AWS/Google/Microsoft/et al, from leaching on the contributors work without giving anything back.

Or am I reading this wrong?

EDIT: Note, that the Mastodon account is to an AWS employee.... so for him, this might be bad, since it no longer allows them to have their own internal fork without contributing back. Now, they will need to use a real for and maintain that them selves without leaching on the redis contributors.

If you think this is bad, then you should make sure to use copyleft licenses.

EDIT: Just read the details, and it seems that this is just what they did. SSPL is like AGPL with a stronger SAAS is distribution claus. That might not be valid, according to the OpenSource definition, but unless you are planning to modify the code and provide it as SAAS I think this is no a problem.

For Linux it is a huge difference. AMD and Intel have great open source drivers, while Nvidia have binary drivers with a lot of issues.

I'm free to choose any laptop I want for work. This means, that for me, the GPU and other processors are free. It turns out that I still avoid Nvidia like the plague. I don't care if it is free, if the drivers are horrible.

The hostility towards custom ROM in general, is what forced me to root. Initially I used LineageOs without root. However, that got me in to issues with various apps, due to not passing safety net. So now I use magisk to hide that I use a custom ROM. So, they basically forced me to root.

They explain a bit more about what that means here: https://kagifeedback.org/d/2808-reconsider-your-partnership-with-brave/75

TL;DR They use multiple sources for search results besides their own indexer, the most obvious one is Google. To lessen dependence on one single search provider they have been adding other sources, one of them is now Brave. That is the whole thing.

On Dec 26, Kagi started including search results from Brave search index, after we previously added Mojeek and Yandex earlier in the year. Brave has a public search api and we currently implemented it for about 10% of queries as a first test (same as any other API we use, there is no mutual development or anything of the sorts). This was announced in our Dec 28 public changelog. Approximately a week later on Jan 5 after several posts on social media about ‘Brave partnership’ the situation escalated.]

So, if you do not like to use Google in the first place, I don't really understand why lessening the dependence on google would be a bad thing?

I found that a homicidal lane assist, have a really good effect on my alertness. Before lane assist I could relax and almost doze of, but with lane assist I don't dare to relax for a second since I know it will try to murder me the first chance it gets. So, I guess that is why people say lane assist prevents accidents.

What?!? Pictures Under Glass turns out not to be the most desired solution for controling your car? Who could have guessed? /s