You get access to more APIs specific to the native platform, the looks and feel is far better (I can easily see when an app isn't a native iOS app - e.g., Liquid Glass is awesome), and the tool ecosystem (e.g., Xcode is specifically built for Apple Apps).
Why? All big and even medium tech companies have dev offices in EU and India. As example since it's much easier to deal with visas say in Ireland a lot of hiring was shifted to Irish offices.
I do want to follow up to my own comment here, and just mention that I realize that capital's entire point is to get us to blame each other instead of capital (e.g., American software vs Indian|Chinese|etc software).
The moral of the story is that two things can be true at the same time: A lot of H1Bs are rightfully thrilled at the opportunity to work for decent US companies and make decent money to provide for their family. While a lot of American engineers are rightfully wary of the knock-on effects of hiring workers who can be cheaper and more 'malleable' (in a manner of speaking).
1/ Employment provides training and experience. If the h1bs are given access to the jobs (training and experience), then is it the American's fault that they are no longer considered "best"?
2/ h1b increases labor supply, not the demand. More supply, means lower wages for everyone.
1/ Training is only effective if you can fill the function of the job and learn from it. Many software engineering jobs people claim are stolen by H1B hires are filled by human beings more likely to meet the bar. Many American candidates just don’t. Filling a software role is hard.
2/ Demand for software is not static. Good software drives demand for more engineers in many cases, intra or extra-company. There is probably a non zero rate of wage suppression per marginal h1b currently. But an American economy with no h1b employees could feasibly have a much lower average sde salary. It is not an Econ 101 problem.
1/ Training goes all the way down the pipeline to colleges. If x% of students are foreign, then Americans didn't have the opportunity to get the education.
Again... the skill issue falls apart when you consider teams at tech companies having 1 non-American national origin or caste. I'm very skeptical that, between two foreign candidates with the same U.S. education and experience but different national origins, the fact that the candidate whose nationality matches the current team composition is selected can be explained purely as a matter of skill.
2/ Great, lets train up more American engineers to push the demand higher.
People are not as capable as you think they are and software engineering (well) is actually difficult. You cannot just push more people in. People are not fungible.
There is truth to your statement, but high salaries and demand encourage locally capable people to enter the industry.
Consider growth of CS graduates in the past 5 years or the number of people that transitioned into tech (like myself).
In 2026, this signal is not as clear: with the uncertainty of tech, increased output with less labor due to AI, and growing competition amongst workers (citizen or otherwise). We may see a shift in studies to other fields.
For B2B SaaS apps, you'll notice that the panels and navs (top navigation, bottom navigation, left-navigation, etc) are much smaller (which is a slightly more 'modern' look) - e.g., OpenAI/Claude dashboards. In general components are more uniform/standard, fonts are smaller. Again, this is just what I've noticed for specifically B2B SaaS apps. If you ask Claude Design to build you one - you'll see exactly what I'm referring to.
I honestly don't mind it. For these B2B SaaS apps its nice to have some site consistency. It almost reminds me of a a new "Bootstrap" way of doing things.
I've always ran into an issue running arbitrary processes - whether it be for serious production work, or just toy scripts. So many choices with so many dependencies, featuring so many foot-guns. So I decided to take a stab at solving the problem. Would love any feedback or contributors :)
SystemG - An agent-friendly general process composer.
I understand the source is thehindu.com - but I'm assuming there's no way we can get that title updated? "Government orders..." sort've misleadingly implies something that "Indian government orders..." does not.
Great point. Devs have relatively no incentive to be more productive for their orgs, and all the incentive to be more productive on their own personal work. The AI benefit to devs is real, just not for large enterprises IMO outside of automating clerical/mundane work.
> Devs have relatively no incentive to be more productive for their orgs, and all the incentive to be more productive on their own personal work.
AI definitely supercharges the side project myth, but I think we’re going to see waves of developers quitting or losing their jobs because they’re chasing dreams of running a side code project that isn’t going to turn into a business.
The incentive to be more productive at work is that they get to keep their job and not be replaced by a cheaper junior. I think we’re in for a reckoning across the industry as companies realize that there’s little difference between a lazy senior armed with Claude and a halfway motivated junior who has aspirations of growing into something more. The latter costs less and might grow into a better dev.
A bit of meta: Claude Design -> Claude Code or Codex.
IMO Claude Code almost feels like a hack for getting web-ish products off the ground. It does such a great job of making the UI mockups interactive and providing a great "base" that the agents can use. Once you get that "base" the way you want in Claude Design, export it, then literally just tell your agent "Hey, the exported design project is /at/this/path - read it and implement it". No it's seriously been that simple - either agent can handle it. From there, you can A/B test to see which agent you prefer. The better agent is going to depend on your project and your prompting.
nice. I just got a free monthly gift from gpt, codex for now. looks like people also like visuals nowadays and go for the claude vibe, which honestly makes for better optimizing and iterating fast I think. getting a plan to also see how it feels working with agents, just imagining how tech will improve by next year.
thanks good luck !
My final answer on this is that we just can't say anything affirmative because all of our projects/codebases are completely different. I've gone back and forth on the "codex vs claude" being better, and while I'm currently of the believe that Claude is superior, I understand that might be the case for _my_ particular set of projects and _my_ personal way of interacting with the model.
Meh, seems he's using arbitrary metrics to make arbitrary claims (which is fine). But to just state that "Life is so much better in 2026 than in 1926 for Americans" is obviously a pretty nebulous statement. It's like saying "Beaches in 2026 are so much better than beaches in 1926". Sure you could cherry-pick some metrics to make the case, and someone else could cherry-pick metrics to make the opposite case. Sort've a "talking just to hear yourself talk" kind've thing.
> But to just state that "Life is so much better in 2026 than in 1926 for Americans" is obviously a pretty nebulous statement.
Given that there was no antibiotics in 1926, no chemotherapy or radiation therapy for cancer, no public pensions (so good luck getting old), hardly any indoor plumbing (even by 1940 it was about half), I think life is much better now that one hundred years ago.
What were infant mortality rates in 1926? Maternal mortality? Average life span? How many years did people live after retirement?
Can you list the ways in which you think life was better in 1926?
And to say life is better now is not to say it's perfect or to deny that improvements can still be made.
AC existed but was barely used until at least a decade or two later (window units invented in the 30s and full-home central AC in the 50s).
One of the current social media trends is Europeans discovering what the US is actually like, having come here for the World Cup. A lot of them have apparently never experienced AC before and it's one of the major focuses in these clips for how life-changing it is.
reply