Without the "some" qualifier my quote totally loses meaning.
In the same message you managed to twist my words, lack reading comprehension, jump to conclusions and do a personal attack.
Since you're new here, I recommend reading this: https://news.ycombinator.com/newsguidelines.html , especially this part: "Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith."
Yeah. I feel it's more of a "ticking all the boxes" situation than anything.
For example: I worked with Rails from 2009-2024 and I haven't come across a single Rails project in the wild that didn't have the queue du jour installed: sideqik+redis, delayed-job before, etc. And then since it's there, people just end up using.
The craziest to me was someone saying “we are using AI in daily processes, now we need to automate”.
But of course to some asshole non-technical people it meant asking for their vibe coded bullshit to be merged into production without review and fighting about it.
> The worker-owned businesses that are more effective will do a better job of concentrating wealth though, as they don't have to pay investors back dividends or participate in stock buybacks.
That’s only close to possible if we start with the assumption that all businesses are billion dollar businesses.
This is also unrelated with the possibility to bootstrap a business without money.
Bingo. Bullshit work grows to accommodate productivity gains.
Is it easier to implement a design now? Then let’s redesign every quarter.
Is it easier to refactor the whole codebase? Then let’s rewrite in whatever new hotness.
This is not different from web frameworks 10-20 years ago. Is it easier to make a website using Rails? If so, why did I see an explosion in devs-per-project after I started using Rails? Because of the BS.
Yep, this is why experiences and ratings of models vary so wildly.
I recently migrated a very large web app to Tailwind and Opus kept screwing up over and over, refactoring and changing the design, the more complex the component became.
I ended up asking Haiku to do it and it managed to do everything correctly, pretty much without intervention.
It's either a problem to have this released or not. Google doesn't seem to care this is in an official repo.
> its also speculation to suggest that's the only reason he was fired
That's the reason given by Google.
The implication here is that Google is lying about this whole thing for ass-covering reasons.
People here are up in arms because someone potentially misrepresented a tool that Google itself doesn't even care to remove, while Google HR and legal are possibly lying to damage someone's livelihood.
This is clearly something done in official capacity, during working hours, with the knowledge and support of his manager, who announced the CLI.
It says "This is not an officially supported Google product" because it's a DevRel sample/experiment, just like dozens of other Google repositories made by Google employees as part of their job.
I browse HN at work in-between GH Actions runs, compiling and Claude thinking, so no time for videos.