Women and gay men get horny all the time as well. So why not forbid men from taking off their shirts in hot weather?

Witch is fine. Why not conjure a big curse to the people who came up with IPv6 addresses? Let them have piss in their blood and rotten teeth for the rest of their lives.

It’s not a simple matter of choice. Most people aren’t invested into open source, they just want to get by and do their mundane things. Most people aren’t even aware of all the privacy stuff or abusive practices of big business, it’s usually some more outspoken tech savvy person that decides to expose what the big corps are doing. So using open source is not a choice, like you would be just choosing your preferred cereal brand, but both a technical and political act. And most people are just into the system, they aren’t aware of all malicious things around them.

Not only that, but also when companies feel threatened, they start imposing new technical and legal restrictions to make using OSS harder. Since they have more control over the whole production supply chain of devices, they have more cost effective options and even partnership with hardware vendors to make using OSS very hard or impossible.

I won’t be surprised if AI ends up so expensive that they will cost more than actual developers. But as experience has shown, C-Suites prefer expensive and bloated tech than providing developers autonomy, good salaries and good career plans. They see us just as rebellious cogs in the machine.

They already pissed people off, using OSS code for training AI models without people’s consent.

One more of those revolutionary functional languages that fade over the course of 5 years?

Fuck capitalism. Nuff said…

Yup, can confirm. We had a wrapper to a C++ library using JNI, so whenever this library crashed so did the entire JVM.

I am not anti-AI or something like it and I use AI on a daily basis. If you work on a domain where there’s plenty code written for it or documentation, AI acts like a very efficient search tool. It does not replace traditional documentation or stack overflow, but it significantly reduces the time I take searching for specific syntax, or an example of how to use a library, or how to use a specific feature or parameter of a library. Occasionally it gives me bad advice as well, such as doing something that results in low performance, low security, but then I can check the actual documentation and code to see the details. For code reviews, I think it’s only partially useful, while sometimes it spits something useful, most of the time it spits out bad or irrelevant advice that ends up polluting the code review screen for actual human devs trying to review the code. However, even with all the gains, which is kind of a mixed bag, I think it’s very unlikely AI will increase speed 10 fold. At best, it will be like a 25% improvement at best, and only specific to some times in the project lifecycle, and most of the gains only happen when you are dealing with generating boilerplate code and adding non business-specific functionality. Most of the time I had to maintain existing code, debug existing functionality and fix some security flaws, AI didn’t help me at all.

How to tell someone you don’t know how compression algorithms work, without telling them directly.

2050: people still wondering how to center a div because html and CSS is a nightmare.