Ignoring prices, Mac is definitely the second best option after Linux for Linux-y development flows. None of my issues were huge, but still enough to ask for a Linux laptop for a replacement.
Sure, if you just use Linux for dev, with a Windows hypervisor, you won't notice the difference.
We devs also have a serious issue of performance blindness, because generally work and test on pretty beefy machines. Windows 11 is undeniably heavier on the system than Linux, and Mac hardware flies anyway. If your dev machine is beefy enough, you won't really notice though.
It obviously depends on the environment, but if I am supposed to develop tools that, in theory, can fuck up everything, then I also need access to everything (on my machine). There's no point in testing, if the elevated access rights on the server suddenly surface a fuckton of extra bugs.
Heck, I need admin just for the basics of installing developer tools and opening web ports.
They tried to lock our stuff down once. After a couple of days of absolutely zero work being done because all our tooling was missing, and the poor IT guy had to somehow learn how to install every tool we needed and taking forever, we just got sudo rights.
Cool, and then there's NEVER any problems with different paths? With back and forward slashes? With the limit on path length? With missing permissions on the file system requiring weird workarounds?
Most importantly, your server is likely not Windows, yet you test on Windows, and that's never ever been a serious source of issues?
And don't say WSL. That's like saying the fix to using Windows is to use Linux, but fiddlier. Not to mention you still get issues with the mounted file system.
This really depends on the project. For example, if you're creating a CRUD web app for managing some kind of data, the main tough decisions involve system and data architecture. After that, most other work is straight forward menial work. It doesn't take a genius to validate a gajillion text fields for a specific min and max length, map them to the correct field in the API, validate on the server again, and write them to the correct database field.
I agree that AI might screw companies over in the long run, when there's no more juniors that can become seniors. That doesn't apply to this case at all.
You do have to consider that this is an opensource developer creating something free in his free time. The app is also not life or death. Meaning, his quality standards are UNDERSTANDABLY not as high as if he was working for money on a banks money system.
In the end, all of the complainers are welcome to do the work themselves. That way, he won't have to use AI at all.
No, vibe coding explicitly requires NEVER looking at the actual code. I can give claude a ticket, it creates a plan. I review that plan, maybe change some things. Then claude does the thing. I review the code, then tell claude to fix X. Then I test, then I tell claude to create a commit.
There we have claude creating a commit without any of it being vibe coded
From his perspective, he's investing his free time and likely money into a project for people that are 99% of the time just leechers, as in they never contribute back and only complain.
Now he has a tool that he feels helps him deal with all that FREE labor is doing for everyone, and the very same people now want to tell him how to do his FREE labor he does for them.
I completely understand being pissed off by that.
Can you point to the justifying? If your argument is "AI bad because water usage", then you have to actually demonstrate it's a problem, and that you've always cared about water usage.
In the post they very EXPLICITLY state that there are many real issues with AI, just that water is the worst of them.
Do you know how psy-op for a movement works? Simple, you start focussing the movement on obviously false or irrelevant topics. That way, nothing useful gets accomplished, and the movement looks like a joke to anyone with a brain.
Are you a secret pro AI agent?
Cool, and the people that wanted to thing they produced at the price they produced it at? They'll just chill and completely change their ways? Your people riot and kill people, what makes you think the "other" group wouldn't too?
Any policy change has to be accepted and lived by the people, at the end of the day.
To be clear, we can do both eating the rich AND educating about and changing our negative consumptive habits.
All of that just seems like special pleading, and has no moral basis at all. "It's my culture" is morally equivalent to "I've always done it this way", tradition is just "My parents have always done it this way". I hope I don't have to bring any examples to demonstrate how often "culture" was horrendously immoral.
In the end, going vegan does require some amount of effort, at least initially. Guess what? If someone has gotten used to using LLMs for many parts of their live, it would ALSO require some amount of effort to replace it. You might say that veganism requires more effort atm, which I could agree with. But that begs the question: If AI lives long enough, will it suddenly become totally fine, simply because it's just as integrated into daily life as meat eating is?
Finally, "they need to eat food" is to veganism as "I need to learn" is to LLMs. In both cases there's better alternatives.
What exactly are we talking about? Doing Windows related development on Windows is roughly as decent as doing Linux related development is on Linux (or Mac).
It's just that because like 90% of servers are Linux, 90% of development benefits far more from being developed on a Linux-y system.
For example, the Windows filesystem is very different. Over and over I've had issues with permissions being different, with paths being inconsistent (this happens esp. with WSL) and with limits on path length.
You can develop on Windows, but having the test env closer to the real env takes care of so many little headaches.