It's going to be quite a while until open source models catch up. And, as long as Anthropic maintains the perception that Opus is even slightly better than the best OSS models, they'll still be the preferred tool for professional developers.
Even if the best OSS model is only 1% worse than Claude, do you want to risk your codebase on it? When you're working through a tough bug in your code, and an OSS model just isn't grokking it, wouldn't it be only natural to want to cast it away and say "I should only be using the very best tools, dammit! My time is too valuable!"
That said, I agree with your point about SWEs modifying their workflows to avoid lock-in. That's a good idea, no matter what.
Your point about Firefox not handling the Microsoft teams meeting is interesting as I have found that google meet video calls do not work well or at all on Firefox the last time I checked. my best guess is that this is Google trying to entrench their browser.
I get the sentiment, but I much prefer this to the alternative, which is rank and file employees getting laid off. It’s much better to have accountability that starts at the top and then trickles down. Too often it feels like workers are the only ones who suffer from the bad decisions of executive leadership.
The problem is that many devices instantly spill over to the secondary Pi-Hole. And rogue devices bypass the primary altogether once they begin to get blocked for a short period of time. Having a secondary without blocking nearly negates the benefit of having the primary pi-hole, for the devices that it matters for most.
How convenient! Turns out they don’t give the slightest damn about “Responsible AI” in the first place. It’s nice to roll out news like this while everyone else is distracted.
Would you mind sharing which automated tasks offered the highest ROI, and some information about how you run them all (i.e., do you use cloud services, or an always on RPi that you run the scripts on)? Also, which libraries have you used for scraping?
Don't you think it'd be rather hard to go without the tactile feedback provided by our keyboards? I can imagine people getting really lazy with their keystrokes when performing them with a glove in midair or on a table, making it hard to interpret the input.
Even if the best OSS model is only 1% worse than Claude, do you want to risk your codebase on it? When you're working through a tough bug in your code, and an OSS model just isn't grokking it, wouldn't it be only natural to want to cast it away and say "I should only be using the very best tools, dammit! My time is too valuable!"
That said, I agree with your point about SWEs modifying their workflows to avoid lock-in. That's a good idea, no matter what.