Web Components are bad. Lit in particular is one giant memory leak. No tooling exists for making use of server-rendered Shadow DOM, which means users pay CPU cycles for client-side rendering.
I don't think that could be written down and published today.
“I liken starting one’s computing career with Unix, say as an under-
graduate, to being born in East Africa. It is intolerably hot, your
body is covered with lice and flies, you are malnourished and you
suffer from numerous curable diseases. But, as far as young East
Africans can tell, this is simply the natural condition and they live
within it. By the time they find out differently, it is too late. They
already think that the writing of shell scripts is a natural act.”
— Ken Pier, Xerox PARC
Good people solving some interesting problems. Lots of secret, unannounced, greenfield stuff to work on. Hit me up and I will personally refer you.
Here's the original post from LinkedIn:
"I’m looking for amazing people to join an exciting new AWS cloud product that is part of the Amazon Connect family in New York City (domestic relocation available). If you are interested in building a high-quality and scalable SaaS offering using the latest AWS infrastructure from inside AWS, and having a blast with a fun and talented team, I would love to hear from you. Some of the open positions are linked below. Watch this Andy Jassy video if you want to learn about Amazon Connect and its impact for customers: https://lnkd.in/eq6sXe8M.
I wonder if some sites are using JavaScript to handle language, but they don’t want to use navigator.language since below IE 11 doesn’t support it. In this case, it might make sense to fall back to location.
This is incorrect. The File System Access API 100% does contain a showOpenFilePicker API. As it says in the blog post, they’ve just begun this process by beginning with the private origin portion of the API, but they’ll be adding the other portions later.
Everything here is still true: https://dev.to/richharris/why-i-don-t-use-web-components-2ci...