mhoad

Are there any other topics in that list that look particularly confusing to you about their purpose? Any reason why this would be the odd one out

This isn’t actually true. Here is a recently released report from Estonia’s foreign intelligence service that talks about that among other topics https://raport.valisluureamet.ee/2023/assets/WEB_VLA_ENG-rap...

It’s really 100% ok to not comment on things you don’t actually know anything about.

Of course they do. Just look at how that entire system is set up. It’s very clearly a for profit driven industry first and foremost and a healthcare system in a very distant second place.

It’s a British Virgin Islands registered company run by a Russian billionaire who lives in Dubai.

This might not be clear if you don’t normally have any interaction with this kind of “policy” friendly language but it’s making a point that it’s falling into the hands of particularly authoritarian governments who use it to target political enemies, journalists and human rights types and that they certainly didn’t have that capability domestically until someone packaged it up and sold it to them.

They seem to be acknowledging some parallels to this kind of scenario as to the nuclear proliferation problem and that many governments aren’t ok with irresponsible sellers who will put these things in the hands of anyone with money.

This is in some places a little bit specific to Lit but mostly not and walks you through that shift in mental models from start to finish that tends to trip people up a lot coming to Web Components https://youtu.be/Xt7blcyuw5s

FWIW if you are interested in Web Components I would say Lit is hands down the best entry point I’ve come across. Strong recommendation and nullifies most of the common complaints you tend to hear associated with them.

It’s pretty universally described as extremely ugly to the point where the most common request for years is people asking how to build component classes in CSS in order to move it out of the HTML.

I also used to feel like the comment you were replying to. About two years ago I decided to try and lean in heavily towards “modern” CSS and honestly things have gotten so much better the past few years.

I also leaned in heavily to the component model with Web Components which was another huge win for my experience with CSS.

I actively enjoy it now rather than dread it. Catching up wasn’t too difficult and if someone else is in the same boat I would recommend the investment.

Web Components use of the shadow DOM is designed for this very use case.

I never have to worry about clashes or getting too cute with my naming conventions. You can just use a h1 selector and not think about it.

Seems you’re not alone. This was ripped out of Google’s Stadia platform I believe but might be wrong https://github.com/google/hierarchical-state-machine.dart

I’m not saying it wasn’t helpful, we did learn a lot about UI development for the web but we learned a lot of new things that don’t work well too and a bunch of those things are very React specific these days.

Furthermore compared to more modern takes on the problem and the evolution of the platform itself it’s probably not what you should be stating projects with these days without a good reason (I.e it’s no longer an obvious default choice)

The entire need and premise for virtual DOM stands out as a pretty big example for me here. Made a lot of sense at the time but is an actively bad choice in 2023.

Similar argument on things like their synthetic events approach where you now have to pay a runtime cost now to just implement something in a worse fashion and much slower language that the browser already provides for you.

I do feel as though a lot of the initial conditions that existed around the time of React’s release are mostly no longer relevant and many of the assumptions that it was built around are no longer true.

It never cared much about the gaps that started to develop between “the React way” and the underlying web platform and now it’s off in its own weird self contained ecosystem and doesn’t play particularly well with anything else.

It also is one of those frameworks that starts forcing you to extend the same broken abstractions further and further into the rest of your stack up into your backends and data models. That isn’t a healthy sign at all.

As a big Dart fan I would say it’s actually in no small part to how the core language team works. Really good mix of thoughtfulness and pragmatism.

That story was what first got me interested in the field of security. This is truly the perfect ending to that story for me. Genuine chefs kiss.

It’s actually not a huge deal in practice.

I just put together a content style website using nothing but web components and used a base class to put my global styles into and just inherited my various components from it.

Was also really easy to factor out shareable styles like various page layouts using a similar technique.

That just left me with doing small targeted tweaks where I would override things with custom properties along the way as needed plus any component specific styles.

Was probably the cleanest approach I’ve had in as long as I could remember. Plus it was delivering me a perfect 100 score in Lighthouse too for what it’s worth. Would recommend.

How is it different from window.localStorage.setItem('user-id', 'user123');

I look at it like so:

Local Storage: Key Value

IndexedDB: Structured Document Database

OPFS: BYO File Format

But all operate under the same restrictions and set of considerations.

Was… the richest.

https://fortune.com/2023/03/02/elon-musk-bernard-arnault-wor...

Reading the article, everything in there actually sound quite reasonable and good for users.

This sounds a lot like a “you” problem.

When Alex did this post live at a conference once it was even better I thought https://youtu.be/somze2DW7vs

Lit-Html is a templating library similar to say Mustache or something like that but I would argue much more expressive. You can see a demo of how it looks here https://www.npmjs.com/package/lit-html

Lit is another library that is made up of a couple of things one of which is lit-html but is closer to a React or Vue by way of comparison.

Some noticeable differences between it and other view layer libraries include the fact that it was written by a team who are arguably much closer to actual browsers engineers and it uses native Web Components. The side-effect of this is that it’s incredibly fast and lightweight. I tend to think of it as the 5kb developer experience enhancement that takes Web Components as a primitive and makes them an actual pleasure to work with.

There are also a series of enhancement packages that are also totally opt in if you want more out of the box like internationalisation, client side routing etc.

If you go to lit.dev the documentation is actually pretty great and it’s probably the easiest way to get started.

There is a JavaScript/TypeScript toggle on all the code samples, just click that and you’re all set.

Flutter web is in the process of moving to a new rendering pipeline that is C++ compiled to WASM and backed by WebGPU.

I don’t think they are going to have troubles performance wise for long.

This is actually an interesting read I came across by someone from their team recently which poses some hypothetical directions they could take things in the future depending on how the web platform evolves over time.

https://docs.google.com/document/d/1peUSMsvFGvqD5yKh3GprskLC...

Certainly glad the US would never do anything so backwards and silly.

https://www.washingtonpost.com/education/2023/01/31/florida-...

Probably this one https://rive.app/

Meta also announced a $40B stock buy back this week. These excuses about needing to save costs reek of bullshit.

https://www.cnbc.com/amp/2023/02/01/facebook-parent-meta-ann...

Under the settings screen there is a software licenses section. In there.

The plan AFAIK is to make it the default everywhere but they are just rolling out each platform in some kind of prioritised order.