Did the last AI bubble even pop? Why would I expect this one, arguably more groundbreaking wave of changes to "pop"?

for snapshot tests it seems better to diff a data representation such as some yaml string, than to diff UIs

The whole UI seems better for LLMs to consume and also displays nicely in-editor for humans. Test failures become failing screenshot tests essentially, which are really comfortable changes to review.

"displays nicely in-editor" is the whole point of yaml. The snapshots in the article are just yaml with additional useless ASCII characters

Yaml is just a serialization of some intermediate representation. The expect test output in the article is a full-fidelity (minus color) rendering of the UI. I would argue that the final app UI is both easier to read for humans and covers more code. As an example, a naive yaml test would likely not capture positions of all of the elements in the app and so you’d be able to silently introduce positioning bugs. On the flip side, if the yaml does include positioning information then it’s now substantially harder to read than the UI test and the signal from the test is compromised because readers will have a harder time understanding and be more likely to ignore.

sorry both of the things you said are false, why are they stated so confidently?

because being confidently incorrect is a thing?

vanila javascript would not be far off, just replace the tags with function calls. In early versions of react, there were people who wrote code like that. For some reason web devs since collectively agreed that the xml syntax is essential to web technologies

I think mostly people like to have logical component with all the code in one place and not have to think about structuring css/html/js separately. Many people like react for jsx (surprisingly, because initially there was a lot of push back even in early react adoption).

Then they took it to the next level with things like styled-component. Virtual DOM is just an implementation detail and overrated to the success of React.

Any future web framework that solves that component thing and allow people to just write code instead of "web code", they'll win.

(I am aware that the web veterans don't like that view)

not just de facto standard and not just in the US, it's a logical way to intepret the laws, in many western countries. The laws should streamline and welcome people who have already established connection and contributed to the success of America. It makes no sense for people to have to leave the country to apply for permanent resident, and be treated like all those to-be immigrants who have never lived in America.

> The laws should streamline and welcome people who have already established connection and contributed to the success of America

The law should do what it was designed to do. The H1 system reflects a compromise between people who wanted skilled workers and those who didn’t want foreigners becoming permanent residents. So the compromise was a temporary worker program where most people would go home afterwards.

The law should be interpreted to give effect to that compromise. Your approach of streamlining immigration wipes away that compromise.

they still need to file for permanent residency and you can still reject them.

If the laws need to "wipe away that compromise", better just disqualify them from filing in the first place.

It makes no sense to deport some of the people that you're going to give permanent residency to, while you're giving permanent residency to them.

Isn't kotlin a more modern choice coming from java, that's designed propperly instead a series of bolted on decisions?

I see their name mentiod everywere along with Aider, presumably for being among the first agents, but I've never met anyone that actually uses them.

The author was pretty clear about his motivation on the language. It's to make it more sustainable for them to maintain bun (instead of directly making bun safer), but the former can and often will result in the latter.

"basic permission model" used to be the only thing Deno had going for, and the keyword is "basic". They pivot pretty late to become a drop-in replacement for nodejs (using the term drop-in loosely here).

Bun has a pragmatic approach from the beginning for being a all-in-one toolset (not just a runtime) and node's replacement. They also has gradual adoption paths such as using bun only as package manager and/or test runner.