It's the snappiest browser at the moment and I love its render as text function and automatic ad blocking on mobile. I've made a permanent switch on mobile, but I tend to miss the Chrome dev tools whenever I use it on a computer.
It's also wonderful that the browser is truly privacy conscious.
There is a lot of land in the world. And definitely have the capacity to build the supply chains. It's just that it's slow and expensive while oil, gas and nuclear is fast and cheap.
We need policy changes. Or in a very ideal world, fusion.
It's startling how quickly this happened. Even ten years ago it wasn't true. Many people have not updated their priors yet and still think nuclear is a realistic option. At this point, nuclear is a long shot, which is why I refer to SMRs as HMRs, "Hail Mary Reactors".
And to elaborate on the other side of the argument: JSX creates plain JavaScript objects instead of exposing an "almost-JS" templating language. Additionally you get an enormous amount of flexibility. For some types of apps that is very important.
I'm not certain I would call Vue.js templates as an 'almost-JS' templating language. It is pure html. A browser could render it without any js backing it up.
I can't speak for many other template specs, but I believe Angular.js was just pure html, as well, using custom properties to perform the binding between the html and the backing js, which is very similar to what Vue.js does, in that aspect at least.
> I still write and think in SQL, but don't have to write queries as strings.
Why is that a benefit though? Why would I rather learn some custom query builder-specific DSL when SQL is at least mostly standardized pretty much everywhere. The use of template strings in JS can get rid of all the problems of just plain string concatenation for SQL (e.g. it can prevent SQL injection, enable safe dynamic queries, etc.)