I think the more useful part is the parts that checks a ticket, fixes a bug, then opens the PR automatically. Whether you get an email or a phone text or call from a voice agent is ... somewhat secondary, im.
Having got back in to some WP in the last year, the big thing that struck me compared to other framework/environments is... no... build step, or even plugin/module install step. Files are just there in the document root, accessible by default - the logic files are invokable and the asset files are reachable. Most other php frameworks will install a plugin/module outside the document root then have some sort of publish/install step that will copy assets to be publicly accessible as needed. No plugin logic files would be invokable directly from a URL. That one change would make a big difference, imo, but seeing so much of the last 15-20 years of WP involves helper functions to assumed paths, and default assumptions about assets and logic living in the same paths... I'm not sure the ecosystem could adapt or support an alternative approach at this stage. Might be wrong. It's taken me a while to put my finger on why the current situation encourages less-secure-by-default systems, and this is probably the biggest thing I've landed on. There are other issues, but these issues all help contribute to WP popularity in the first place...
One thing I don't see mentioned enough with the whole "the consumers paid these tariffs! we should get refunds!"... We "paid" not just in higher prices, but in many layoffs, reduction in working hours, skipped bonuses and raises. Companies that get 'refunds' will have an opportunity to use that money to rehire and repay workers. I'm cynical enough to think that will happen in large measures across the whole country, but I'm hopeful enough to want to see it happen nonetheless.
Delayed refunds won't even start to repair the damage done by bankruptcies triggered by high tariffs, the snowballed cost of tariffs impacting multiple steps in the supply chain, the emotional toll on families and communities having to deal with less money and rising prices. But rehiring and getting some regions and communities back to work might be a step in the right direction.
EXCEPT WE NOW HAVE A 15% GLOBAL TARIFF ONGOING. And a lunatic administration that will fight tooth and nail for years to keep this going as long as possible.
> Companies that get 'refunds' will have an opportunity to use that money to rehire and repay workers.
Why on Earth do you expect a single-time payment with no strings attached to make companies think some market is profitable so they should invest in it?
Unsure where you got that from? If a company that has had to lay off staff and reduce hours because of increase in expenses because of tariffs, then they get a chunk of money back, trying to 'get back' to where you were before - headcount, wages, etc - might be on your mind, and might be possible with a one-time refund of ideally a sizeable portion of your tax. However... we still have extremely high tariffs in place so the effects of higher input prices are still ongoing (and ramped up in some cases).
If our tariff structure went back to, say, October 2024, and companies who'd paid some inordinate tax - forcing layoffs and reductions - got a chunk of that back - and the taxes went back to what they were - there'd likely be some return to hiring and raises as before. But we can't get back to that any time soon with an administration hellbent on extracting as much from us via tariffs as possible.
The reason companies invest is not because they have money.
And edit because I explained it badly:
That means that yes, getting the tariffs back can make them hire, because there may be more people wanting to buy things. Sending them the tariffs money will do absolutely nothing.
But even the first part isn't guaranteed, because you can't rollback the economy, things don't return to where they were, they go into some other place.
I read that as combined, up to this point in time. You have 20 engineers? If you haven't spent at least $20k up to this point, you've not explored or experienced enough of the ins and outs to know how best to optimize the use of these tools.
I didn't read that as you need to be spending $1k/day per engineer. That is an insane number.
EDIT: re-reading... it's ambiguous to me. But perhaps they mean per day, every day. This will only hasten the elimination of human developers, which I presume is the point.
> No, there is Github Copilot, the AI agent tool that also has autocomplete, and a chat UI.
When it came out, Github Copilot was an autocomplete tool. That's it. That may be what the OP was originally using. That's what I used... 2 years ago. That they change the capabilities but don't change the name, yet change names on services that don't change capabilities further illustrates the OP's point, I would say.
To be fair, Github Copilot (itself a horrible name) has followed the same arc as Cursor, from AI-enhanced editor with smart autocomplete, to more of an IDE that now supports agentic "vibe coding" and "vibe editing" as well.
I do agree that conceptually there is a big difference between an editor, even with smart autocomplete, and an agentic coding tool, as typified by Claude Code and other CLI tools, where there is not necessarily any editor involved at all.
Thanks... 2 years felt a bit too recent. I think I was trialing copilot in late 2022, and then got turned on to ... codeium/windsurf in late 2023. The years are merging together now. :/
That's silly. Gmail is a wildly different product than it was when it launched, but I guess it doesn't count since the name is the same?
Microsoft may or may not have a "problem" with naming, but if you're going to criticize a product, it's always a good starting place to know what you're criticizing.
It was absolutely under version control and there was a full test suite. The guy that wrote it is easily in the top 3 smartest human beings I've ever met and an incredibly talented developer. Unfortunately a lot of his stuff required being at the same level on the IQ bell curve, which meant it was functionally unmaintainable by anyone else. If you're familiar with the Story of Mel, it was kinda like that.
reply