7 comments

[ 3.4 ms ] story [ 25.4 ms ] thread
I believe they are also moving their front end to another Google project too https://lit.dev/ not sure where they are on that.

As a side note to the original post, I wish gRPC-web was better supported or alternatively that WebTransport gets standardised quickly. I would love to be able to using gRPC in web apps, it’s such a pleasant experience relative to passing JSON back and forth.

I'm re-acquainting myself with front end development, and the question I've been asking myself is, what toolkit or framework should I begin with for building my own projects? Lit seems like an excellent candidate for that, thanks for sharing.
What's your goal? If its eventual employability in the FE world, Typescript and React dominate job boards. If it's just using cool stuff, sure, do Lit.

If you want exposure to a lot of modern stuff, Next.js is also a great candidate – it makes it pretty simple to use typically finicky stuff like SSR.

I’ve followed the Lit project for a while and would strongly recommend it as as an amazing option that is currently only at a tiny fraction of its real potential currently.

As far as I know this is what the YouTube is moving to as well along with a lot of other major name platforms.

This is a bold thing to say right now but I’m confident Lit is going to eat Reacts lunch in the next 2 years.

They are currently in the very early planning stages of expanding it into a full blown application framework. I’m very curious to see where it lands but I have very high hopes in the meantime.

What do folks use to monitor gRPC in production? Every time we think about making the switch, we come up to the lack of protocol documentation and monitoring. Or I missed something obvious which can definitely be the case.
Is this solely due to HTTP/2 support, or are there other good reasons for gRPC?