"Googling a lot while coding" is not even remotely close to vibe coding, please don't gaslight yourself into that.
When you read up on things, you know what you're looking for. You read a potential solution (e.g. part of a documentation, an example, someone else's solution, a solution to a similar problem), you think about it and transfer that to your own problem, with your own code, with your own thoughts.
Using AI support is totally fine too - it's a smarter code completion, nothing more. It might spit out something wrong, something partial, something good. You might ignore it as with the regular completion. In the end, it's still you thinking about it, modifying it until it works, and doing your thing.
"Vibe coding" is basically saying tech jesus take the wheel. And it might go well for someone who cannot code, who managed to create their small game or some website. It will go horribly wrong for any project handling user data, sensitive data, or something that needs to be maintained after. We've had more than enough examples of that.
It's not about being dumb and expecting stuff for free but a general anger towards subscription based models. Fair models exist and are possible, but are a collateral of the general hate.
Then, free alternatives exist, and believe it or not, some people do not have a tiny monthly fee they could spare or do not want to pay for something that a free alternative exists.
Why are we giving this person their stage again? How probable is it that the instance admins of the like 15 instances they have accounts on will all collectively ban him?
It's just your average nazi spammer on the internet. You've read that "bio" this person has. Even if they get banned, they'll come back just on principle. Just block him like any sane person would do, leave him shadow banned like that with his nazi friends, and call it a day.
So, you mean using a proprietary vendor to operate something binds you to that vendor?
Congratulations, you've just discovered vendor lock-in.
"Obfuscating the environment" is also an absolutely unhinged claim, what even is that supposed to mean?
And again, Automattic is NOT in the right. What Automattic did was break license terms, attempt to extort, steal code, and light their whole brand, company, ecosystem and community on fire. Matt spit in the faces of his open source community (and open source in general), and every single person dependent on WordPress losing their job because of the shift he's causing will be blood on his hands personally.
Even if WP Engine was questionably morally or ethically, they did play by the laws and the license terms.
Matt went on a mental breakdown and additionally to his unethical behavior broke several laws on that journey, which is exactly why he is losing the lawsuit. Matt and Automattic are NOT in the right.
I'd laugh my ass off if WP Engine would lead a hard fork called WP Core. If any WP Engine folks read this, feel free to use the name, I won't sue, I promise.
It really depends what you're doing.
If it's really "only" blogging I've seen a lot of blogs using Ghost. Hugo is more of a "simpler" static site generator.
That whole blog post is so full of salt, that it really hurts to read.
Still going on about the "imbalance of the contributions", well that's open source for you - you don't get to control who contributes how much, all you can do is ask nicely, and provide a good experience for contributors. Acting like a lunatic does not do that.
legal attacks started by WP Engine
Of course they did after the witch-hunt and the absolutely illegal, unethical and plain ridiculous behavior of Automattic. The counter they did, the whole ACF takeover and the slandering are a lawsuit handed on a plate.
The way "community" is quoted in that article for those who dared to disagree.
This legal action diverts significant time and energy that could otherwise be directed toward supporting WordPress’s growth and health.
Yeah, as a developer I also hate when lawsuits are stopping me from working. He had no problem letting go of nearly 10% of his staff with their "alignment offer" to get rid of people who again dared to disagree, but the legal action is diverting resources now.
But the whole "Focused on the Future" paragraph is going full mask off:
Before, they said that resources will be reallocated to "for-profit projects within Automattic", and
We will redirect our energy toward projects that can fortify WordPress for the long term
It's only a matter of time another hostile takeover will take place, and Matt will attempt to go full for-profit on WordPress itself.
We’re excited to return to active contributions to WordPress core, Gutenberg, Playground, Openverse, and WordPress.org when the legal attacks have stopped.
Full on extortion. Stop the lawsuit or we won't contribute.
Honestly, if I'd be dependent on WordPress for my work, I'd not sleep well and start going into something else right fucking now. How are people that stupid, childish and entitled getting into such positions.
WordPress.org statement threatens possible shutdown for all of 2025 – Computerworld
Matt never ceases to amaze with his smoothbrain decisions.
The amount of effort this moron puts into his weird personal vendetta against WP engine, even after the court told him that he has nothing, which was actually his last chance to end this kinda gracefully, could've been used for so much better things.
And he's not only successfully kicking himself in the balls, he's willing to throw so many years of community and project time and effort under the bus for it.
Go on Matt, keep telling how much you're only doing this for WordPress.
"Googling a lot while coding" is not even remotely close to vibe coding, please don't gaslight yourself into that.
When you read up on things, you know what you're looking for. You read a potential solution (e.g. part of a documentation, an example, someone else's solution, a solution to a similar problem), you think about it and transfer that to your own problem, with your own code, with your own thoughts.
Using AI support is totally fine too - it's a smarter code completion, nothing more. It might spit out something wrong, something partial, something good. You might ignore it as with the regular completion. In the end, it's still you thinking about it, modifying it until it works, and doing your thing.
"Vibe coding" is basically saying tech jesus take the wheel. And it might go well for someone who cannot code, who managed to create their small game or some website. It will go horribly wrong for any project handling user data, sensitive data, or something that needs to be maintained after. We've had more than enough examples of that.