Hacker News Reader

Comment by nvllsvm | Hacker News Reader

So what would you recommend instead?

Probably something like Lit.dev seems exceptionally well positioned to stay aligned with the platform and give the same developer experience and a much faster user experience.

Literally everything that runs in the browser is "aligned with the platform" since there's nothing but the platform that is running in the browser.

Meanwhile, "the aligned with platform" lit.dev is busy reinventing React, but poorly:

- uses non-standard syntax like `<div ?hidden=xxx .value=yyy .@click=zzz`

- special functions of the form "this particular function call even though it looks like a regular function call will actually throw an exception if used outside a very specific place inside a string". See "built-in directives"

- as a part of the mess that is Web Components in general is now busy reinventing React Context

and so on and so forth.

But yeah, sure, "more aligned something something"

You seem kind of confused about what people are referring to here and I don’t know if it’s out of ignorance or partisanship but I mean using options that don’t have to reimplement entire core parts of the web platform that already exist but in JavaScript and in a way that doesn’t work with anything else.

I’m making the argument that would be a bad choice to make in 2022 but totally understand why it made sense a decade ago.

> You seem kind of confused about what people are referring to here and I don’t know if it’s out of ignorance or partisanship

Ah yes. Go directly for ad hominem attacks without ever telling what exactly you mean. That will definitely help you win an argument.

> I mean using options that don’t have to reimplement entire core parts of the web platform that already exist

Again: what the hell are you talking about.

Reply on news.ycombinator.com