Kiss of death for Gitlab? A temporary bump in profits while being technically assimilated by Google due to a significant portion of profits being directly dependent on Google? Now people who don't want to contribute to Microsoft training data sets on Github and escaped to Gitlab will be forced to contribute to Google's training data or forced to migrate elsewhere.
I was involved with some deep React apps that utilized all kinds of advanced patterns and I simply don't see the need for most apps I see around. React is neat if you have thousands of concurrent updates coming in all the time where dependency graph is a killer. But only a few companies need it - why then force this on all frontend devs by default? It's like with big data - let's push everything to Hadoop/Spark when our SQL database fits into 20MB etc.
Maybe you can consider that on HN you are talking to experts who in their lives experienced dozens different UI paradigms and frameworks including deep experience with React, its ecosystem, its benefits and its warts. I am pointing out that the problem of "how can I scale this UI" is experienced by a very small percentage of apps. For Meta or Uber it makes sense as they need to coordinate overlapping real-time feeds where dependency graph is insane; why should however most apps bother jumping on this paradigm? There are complex yet performant apps like draw.io that never touched anything reactive and aren't missing it in the slightest.
Agreed, Apple practices are atrocious and Framework seems like a better deal. But it looks like they scavenged unsold displays made for Microsoft Surface and can't source other ones with the same aspect ratio/size but better anywhere.
There is no framework. Just simple JS calls and bindings to HTML with somebody defining REST or GraphQL backend. And some eye candy CSS. The point is that with ES7+ JS can be finally readable and not a spaghetti code monster so anyone can easily understand and extend any code.
That might be true but React has the same issue with larger teams and everyone using a different part of it; the pace of development drops rapidly and apps become complex monsters for little reason.
It's easy to make your own SPA using div display: none/block, so is routing. Global store is also pretty easy to do including update events. Async/await makes backend calls super simple, one could still use promises for a few more advanced cases as well, or even go full Saga pattern. Why is a framework needed these days?
How many apps actually benefit from reactivity, i.e. 1,000 people can post to a feed realtime and the app fetches data from 200 other backend services? I believe for vast majority apps, a basic HTML/JS/CSS is all one needs. It's fairly trivial to make your own SPA in ES7.
Isn't it easier just to learn ES7, use async/await whenever possible, learn how to do div display=none/block, read some CSS tutorials and forget about learning any JS framework?
Yeah, writing a thesis on it right now; this + adapters give so many options to play with and Meta was nice to give me access to their research models.
...or maybe it's just market segmentation to give PC plebs inferior tech? You seem to be proud of being what some marketing exec views as an unimportant low-margin value segment only good for getting rid of old stuff.
Most people use 2x scaling at that resolution and that helps predominantly the text quality as a single "superpixel" is made out of 4 pixels and many more subpixels.
My ASUS ZenBook has 3300x2200 at 13" and it's the best display I've ever had. Can't downgrade once I got used to it, at 2x pixel density it's basically 1650x1100 but with much nicer pixels. Looks stunning in Linux.
That's fine, for folks like you Framework should offer the current display. For folks like me they could offer the 3300x2200 option. They offer options on everything but display for some reason.
That seems more like Intel gatekeeping high-end for themselves via some shady background deals with laptop manufacturers. There is no reason why an 8-core Ryzen with Radeon GPU would be limited to these crappy 1080p resolutions.
Calorie deficit doesn't work. One has to switch body to burning fat and eating any carbs prevents it due to keeping carb metabolism pathway instead of fat-burning one, switching body to starvation mode, depression and major muscle loss. The fastest way to lose fat weight is electrolyte fasting with no food (1lb/0.5kg weight loss a day). This method works for very determined fairly healthy folks but most aren't those; it's also super important to drink a lot during this fasting and break the fast by taking high-dose thiamine. Carnivore diet (meat/fish/quality fat) gives similar results due to activating the same metabolic pathway while keeping eating but the rate of weight loss is more like 2lb/1kg a week and not feeling hungry at all.
As much as I like the idea, they don't address their main weakness - low resolution display. They are like a 720p phone - 2256x1504 is somewhat precise but one can clearly see the pixels and switching to 2x mode makes everything huge. Older ASUS ZenBook could do 3300x2200 at the same size for about the same money.
Switching to carnivore diet gives you 2lb/1kg weight loss a week without any exercise and any feeling of hunger or weakness (assuming you are overweight).