It’s also just not actually true though. It’s not considered good practice to bundle your web components when publishing to npm for this exact reason. That’s something that should happen inside the final app itself where the components get used so you only have one instance of Lit for example if you are using that.

Lit is also totally web standards compliant to be fair.

Ok.

Here’s the top comment from the Reddit post that was linked

> Hey folks! Kevin, product manager on Flutter and Dart here.

> The layoffs were decided AT LEAST a couple of layers above our team and affected a LOT of teams. (I think I can say that). Lots of good folks got bad news and lots of great projects lost people. Flutter and Dart were not affected any more or less that others. It was a tough day...tough week.

Can you comprehend that?

That’s not actually correct I don’t know where you got that from. This is from this year and was built on top of a wider rewrite of their JS interop using new language features to make it essentially a zero cost abstraction.

Dart has had browser support and DOM APIs before but never had the same APIs you have in the web platform before.

I think I had it confused with dart:html, which looks almost the same. I don't see a big difference in the example code.

They dropped that “client side” framing a while back thankfully. It’s considered a general purpose language at this point.

One of the postgresql client packages (posgres) is roughly 8 years old. That's how "client side" it ever was...

This looks like nightmare fuel.

Lit.dev has been nothing but great for me. Strong recommendation.

I used on a project 6~mo ago and struggled quite a bit to get some basic things to work. Iirc it was related to event handling on nested elements in a component. I believe I felt quite forced to make lots of very tiny components, which made the "try it out" phase quite frustrating.

Do you have any recommended learning resources on building with Lit?

I don’t know if you actually read the article or not but just to be clear that was not the argument that was made.

It’s not just “not new” it’s considered to be actively worse than all of its peers in terms of things like performance and complexity, it’s actively a very questionable choice in a greenfield project in 2023.

I did, and the fixation on React’s age struck me. Was it the core premise? No. Was it a central theme? Yes.

I agree with you, there was definitely a fixation. The implication is that React doesn't do things the new and better way just because it's old, rather than a deliberate decision.

Goes back to writing SQL

No, the core theme was technical debt. Technical debt happens to be (typically) a function of time.

Just as an FYI your information is a bit out of date. They rewrote their entire graphics pipeline a while back to solve exactly this.

This is what it looks like now in terms of performance if you want a demo https://flutter.gskinner.com/wonderous/

I had high hopes for this new renderer, but it’s still not good enough. There’s a single frame lag when scrolling, it might not be noticeable to some people, but I do notice and it’s very annoying. There’s an issue opened: https://github.com/flutter/flutter/issues/110431

I’m actively trying to move more and more of my stuff into Dart these days it’s actually an amazing language to work with.

What do you find amazing about it?