I think Sam Altman is an asshole and I prefer to spend my money elsewhere.
Frontier models being commoditize is inevitable. OpenAI thinks they're still competing on technology, and not user experience and market reputation otherwise they'd understand the continuous negative PR generated by Altman's chaos is going to cost them everything.
You listed common items you think may be counterfeits, and all your effort in checking, but fail to mention av single time you _actually_ ran into a counterfeit. I'm sure if it occurred you'd happily mention it since it would do wonders in reinforcing the paranoia.
No. Why the hell would I use Angular 1.x style directives in 2026? For the simple contact form and todo apps, why would I even use client side scripting? Go away.
A private business can 100% refuse service to you. Examples with regards to "delegation":
- If you come in using a form of non-cash payment that doesn't belong to you.
- If you're purchasing a car, and are filling out paperwork under someone else's name. FYI, you can buy cars on Amazon.com.
- If you attempt to pick-up a pre-order or an item earmarked for someone else.
...
Of course some businesses are more or less restrictive base on fraud chance, yada yada, but you get the idea. You're not being oppressed. Go shop elsewhere.
What is the regular API? How do you express all the integrations needed in this API? Who provides the integrations? Answering these questions lead you back to something like an MCP, which is an API contract that can be as generic or as specific as needed. Wasting context window to understand and re-implement each integration is why MCPs exist.
All the security issues are orthogonal, and occur regardless if invoking this API occurs via code or natural language.
_Telling the browser how you want the DOM manipulated_ isn't the expensive part. You can do this just fine with Javascript. The browser _actually redrawing after applying the DOM changes_ is the expensive part and won't be any cheaper if the signal originated from WASM.
It's winning by default because _there is nothing materially better_. React was _materially_ better than Ember, Angular, plain JQuery, etc. at the time.
Front-end engineers have no issues adopting new frameworks. See the common complaints about the speed front-end stacks change vs. say Spring MVC or Rails.
A more interesting examination is what is the impact of agentic AI tools being able to write better, more idiomatic code in React vs. Svelte because there's more of it. The human side is less of a barrier here.
I took a workshop class and was told to setup a track saw. The course didn't bother explaining how to utilize it properly or protect yourself. I ended up losing a finger. I truly hate Stanley Tools with a passion and if I ever need to use another track saw, I'll use someone else.
> You're getting a billion applicants because people are desperate and there are tons of CS grads, not because you're the greatest company on earth
How does this change the point? They would still like the best candidate out of that pool, not any warm body, since they have limited positions.
What is your approach to hiring and evaluating talent knowing the large number of applicants and how easy it is to _talk about software development_ vs. _actually developing software_, and how expensive and difficult it is to deal with a bad hire, even in America.
The biggest funders of basic research are those with the most resources. This is your insight? I don't think anyone disagrees. Then you conflate correlation with causation and move it to _monopolies_ fund basic research. Bravo.
As a long time Kagi user, the thing I miss the most is Google Maps integration for search results. It's nice to search for a restaurant or an address, see results for it, and with one click open up Google Maps to see how to get there and nearby attractions. Google Maps is such a large moat for Google, especially in locations that Apple Maps (the only real alternative) has poor coverage.
Outside of that use case, I enjoy using Kagi and recommend it to most people.
Consider what companies are launching these days and the talent they need to do it. It's AI companies, it's hardware, it's hard science. It's fewer Uber for pet grooming. There's less appetite for investing in the latter companies and _normal_ software developers are less useful for the former. Yes, ZIRP has contributed, but there are wider economic and social issues that are above my pay grade at play.
The safest space continues to be distributed systems and systems programming in general IMO. You'll still find work at hyperscalers. You'll still find work in the new spaces. Until AI can operate these systems, there'll be a spot for us bit janitors for a little while longer.
> Seize or terminate their patents and copyrights. Issue arrest warrants for criminal evasion. Compulsory licensing of x86 to a European design firm immunized by EU law.
My eyes rolled so far back I hurt myself.
Please provide some examples of where the EU has been able to do a fraction of what you listed to large, US based firms in the past.
Looking at the future, if you want a trade war and an excuse for the new US administration to completely neglect NATO obligations this is a great start.
> Because the harsh truth is that none of those things are actually big issues that would justify learning slightly different syntax.
That's partially the cost, but the other cost is building this into existing tool chains and deployment mechanisms. Getting buyin from teams, ensuring _everyone_ learns the syntax.
And the unstated fear: The code it generates, is it actually good? Am I going to have silly issues down the road that are hard to debug and require diving into generated code to see some concurrency issue?