It's interesting to see UK-based influencers all citing these weak studies (internet surveys) about how social media is not so bad for children, or bemoaning the huge loss for children whose access to educational videos will be cut.
While the financial motive is clear, they must all believe it to an extent, because social media made their careers and changed their lives.
The reality is that the vast majority of kids aren't interested in learning video editing or movie directing, they are mindlessly consuming AI-generated videos and similar content served to them. 30-second videos on random facts sprinkled here and there aren't education.
Not that I think this ban will help, but downplaying the harm to children is a bit too much coming from people with ties to these platforms, like the author of this article.
> ...while far off from feature parity with the most popular production browsers today...
What a way to phrase it!
You know, I found a bicycle in the trash. It doesn't work great yet, but I can walk it down a hill. While far off from the level of the most popular supercars today, I think we have made impressive progress going down the hill.
Yep, every SLA I've ever seen only offers credit. The idea that providers are incentivized to fudge uptime % due to SLAs makes no sense to me. Reputation and marketing maybe, but not SLAs.
The compensation is peanuts. $137 off a $10,000 bill for 10 hours of downtime, or 98.68% uptime in a month, is well within the profit margins.
The mod_pagespeed filter "prioritize_critical_css" was released exactly 12 years ago in early May 2013. At least 3 more popular critical css tools were released the following year, integrating with Grunt, Gulp, and later Webpack.
It's a bit like the <center> tag. A codebase that's littered with stuff like "InlineStack" is harder to work with and parse because the resulting div soup still requires extra styling, which is now both markup and CSS.
React was literally first created in ML out of the author's dislike of MVC, who preferred functional programming and immutability[0]. For a long time, react aspired for its future to be in ReasonML.
Hooks came as no surprise to anyone who paid attention, as the recommended way to write components since at least 2016 was in the stateless functional style whenever possible, and many of us used recompose[1] to simulate hooks long before their introduction.
Russia invaded in 2014 and the conflict stabilized (but didn't stop) in 2015.
In the meantime, the Syrian civil war was raging on.
Similarly, if we ignore all the events in the prelude to WW2, the world was a very peaceful place. According to Hoover, Roosevelt was a threat to world peace, not Hitler.
I'm not implying anything with the analogy, I'm only trying to illustrate that the world was not peaceful between 2016 and 2020, despite the president's efforts.
Perhaps if we had gotten 2 consecutive terms, it might have provided more long term stability.
If seeing how common `eslint-disable-next-line react-hooks/exhaustive-deps` is any indication, people just don't bother with best practices. Not to mention the majority of people I interview or hire don't know anything about CSS performance, they learn on the job. They'll happily add 1000 box shadows in a view if it's in the design.
Also OP is looking to move an existing React UI to Svelte, why not try Preact first instead of an entire rewrite? Or even Inferno or million.dev? If they did and they're insufficient, I don't even believe the browser's DOM is the right technology for that UI then.
Here's a utility to convert exported Aegis JSON to a Keepass 2 or KeepassXC database if anyone's interested
https://github.com/GeKorm/atk (binaries in the releases page)
Result: Zoom out, show 10 places with ratings starting from 1.5, among them a nail shop and a government building. If I'm lucky, it will also show the 4.7 star pizza place 2 blocks away, for which I needed directions.
The client can track its own error rate to the service, but it would need information from a server to get the overall health of the service, which is what the author probably means. Furthermore the load balancer can add a Retry-After header to have more control over the client's retries.
It's confusingly presented in the video, but they already work in the near infrared, up to ~900nm. They're used with IR illuminators and lasers all the time.
There are tubes that work on a wider spectrum, like the Photonis 4G tubes from UV to IR 350-1100nm. But I found them dimmer than the L3Harris in the video.
My comment is in agreement with yours! I'm just expanding on how absurd it is to struggle with merge because GP didn't know about a simple --abort, and how common it is even with senior devs.
And yeah I too find a mix of GUI and CLI works great.
While the financial motive is clear, they must all believe it to an extent, because social media made their careers and changed their lives.
The reality is that the vast majority of kids aren't interested in learning video editing or movie directing, they are mindlessly consuming AI-generated videos and similar content served to them. 30-second videos on random facts sprinkled here and there aren't education.
Not that I think this ban will help, but downplaying the harm to children is a bit too much coming from people with ties to these platforms, like the author of this article.