This. I wouldn't be surprised if people give up after a while of searching and migrating to alternatives to each service that started using or selling data for AI training.
Scope hoisting is the technique used there (it's in the title of your link) to simplify tree shaking a.k.a dead code elimination. Also yeah it's unlikely to be what's happening in that bug due to Google using Closure compiler.
Agree, it's like they made no effort to make hydration easier. Even the router doesn't have the route info on the first render on the client, I had to pass it with getServerSideProps, that's ridiculous.
If you have to re-engineer all your code to avoid content shift, why bother using a mega-framework like Next in the first place?
Also the point of SSR and hydration is to improve performance and page loads, if you have a ton of work to do again on the client that's very small actual performance gains, but that's not so much of a surprise considering Next is one of the heaviest frameworks out there (in bundle size)
This. Same happened with npm starting to offer new features (like lockfiles) only after yarn had them. History has shown competition is only way to make them move.
> This video debunks 4 dangerously misleading scientific papers, all with a Google co-author, that denigrate the urgent need for massive audits and investments in security and ethics. Terrifyingly, the scientific community has scientifically validated and massively propagated what appears to be intentional disinformation.
French researcher and youtuber Lê Nguyên Hoang tries in this video essay to demonstrate that the ML research community is plagued by unfounded claims of algorithms being privacy-preserving, and lack of accountability over ethical concerns.
This video seems to be the continuation of papers co-authored by Lê:
Basically because MDX mixes JSX and markdown, you need knowledge of JSX/JS (which non-devs might not have), and tooling dedicated to build, parse it and so on.
Markdoc is more of a "separation of concerns" approach.
From MS' point of view I doubt it is worth thr squeeze. You have to consider that the average user and their grandma make very little revenue for them. They buy a license with their computer and that's mostly it.
Pro users, companies are a big part of the Windows revenue and for them, backwards-compatibilty is the biggest sales point.
I agree this is super bad and confusing for many users, but the majority of them probably never go past the latest design Win10 screens.
It's very easy in japan to find a "baito" job, that is low skill, part time and paid at the hour and with no benefits. People like the "freeters" cumulate several of these jobs to earn a decent monthly wage. The problem is of course that there is no security of employment, very little rights and as I said no benefits like pension. Housing is still doable as the market is not too high tension, but it's pretty much impossible for them to get a loan for anything. Raising children and sending them to higher education is pretty much not feasible.
I guess for US people it's pretty similar to the fast-food workers earning less than livable wage.
I may be wrong as I don't have the rules under the hand but iirc Apple's rules state that the in-app purchases prices must be set as to not push users to go pay outside the app. So raising your price may result in a takedown of your app, meaning you have to eat the 30% if you want to stay on the store.
So much this. Bad plugins and outdated versions, cheap hosting with outdated PHP versions, cheap development with bad code quality. WordPress imho is not made to last without regular maintenance.
Vivaldi browser supports it out of the box, and vertical is even the default iirc. It's thank to it I got used to vertical tabs and I cannot go back.
While it has the drawback of making tabs hoarding easier, just having some tabs open for documentation, GitHub, test pages, quickly brings me to a point where horizontal tabs' title are irrelevant and I have to guess tabs by their favicon.
On top of that, most screens are 16:9 and we're reading almost exclusively vertical websites and horizontal tabs take up vertical screen space.
"Silly" is a strong word. I imagine one of the points would be that a native app has direct access to your filesystem so you'd rather have users be cautious with it?
But I agree that having in native apps the UI patterns people are used to seeing in webapps is simpler for the majority of users.
Haskell is and has always been primarily a research language. It just has some popularity outside the academia. This is something everybody investing into Haskell knows (or should know).