Ancestors

Written by Ben on 2024-08-15 at 15:06

@slightlyoff Loving the blog post series, and excited to share with others when I get back to work in a few weeks.

One thing I struggle with, having been working with large SPAs since I left Twitter in 2017, is… what stack is a good choice these days? We’ve had so much investment in SPA tech that it feels like the MPA world is still using similar answers to the last time I was doing that.

I admittedly haven’t spent much time with WebC, but it feels still very rough whenever I read about them

=> More informations about this toot | More toots from sangster@macaw.social

Written by Ben on 2024-08-15 at 15:10

@slightlyoff and even then, the only SSR story for that is Lit, perpetually in beta. A huge amount of it ends up being client rendered without that, which is more complicated to sell to people (since people who know React ask why that’s different)

=> More informations about this toot | More toots from sangster@macaw.social

Written by Ben on 2024-08-15 at 15:11

@slightlyoff many years of React usage has also caused significant amounts of atrophy for a lot of folks when it comes to web platform fundamentals, like the brain rot that causes developers to add click handlers to submit buttons in forms and manually doing all of the steps the browser does for them

=> More informations about this toot | More toots from sangster@macaw.social

Written by Ben on 2024-08-15 at 15:13

@slightlyoff but if I wanted to build Etsy (for example) today, I’m not sure what stack would even be right. My instinct would be to look for Rust or Elixir (extremely fast/stable multithreaded backends with strong types), but I’m not sure where else to look

=> More informations about this toot | More toots from sangster@macaw.social

Written by Ben on 2024-08-15 at 15:14

@slightlyoff but there’s currently no way to server-render web components in those languages, afaik, so it’s “fast backend without WebC SSR” or “some node server with Lit”?

=> More informations about this toot | More toots from sangster@macaw.social

Written by Alex Russell on 2024-08-15 at 15:19

@sangster The shared templating language thing is a classic bun fight. Teams in this position need to do the Web Components + SSR (yes, likely Node) thing, or be happy with the idea that they'll end up with their own system for outputting Declarative Shadow DOM for everything that needs to be progressively enhanced, and that they'll be building those templates in their server-side language too.

Google's dependence on SOY should be a warning, not a life goal.

=> More informations about this toot | More toots from slightlyoff@toot.cafe

Written by Ben on 2024-08-15 at 15:26

@slightlyoff yeah, that’s a good point — trying for “shared templating” between the two definitely makes things a lot harder. Once you accept that some concerns are better on the server and some in the client with some overlap that has to be maintained, maybe you find serenity.

=> More informations about this toot | More toots from sangster@macaw.social

Written by sayrer on 2024-08-15 at 17:49

@sangster @slightlyoff the only thing I'd add is that the server templating is nicer when relatively smart. The Go “html/template" package is a good example, but there are lots of others. The docs for that “Security Model" are good. https://pkg.go.dev/html/template#hdr-Security_Model

=> More informations about this toot | More toots from sayrer@mastodon.social

Written by Ben on 2024-08-15 at 18:49

@sayrer @slightlyoff yeah, I am in general a fan of server templating, especially when it’s smarter than mustache. For all that I was excited as heck when Twitter started migrating from Scala-rendered “thin” client to a React “fat” client, I dearly miss the Scala these days. It was a far better tool than I gave it credit, even if it had to carry the load of a very old frontend.

=> More informations about this toot | More toots from sangster@macaw.social

Written by Ben on 2024-08-15 at 18:51

@sayrer @slightlyoff I’m not in the job market, but after being in a frontend-but-mostly-Preact architect role for a while, I’m trying to figure out what I want my next stack to even look like. Don’t want to eventually start looking for jobs and only try to figure it out then.

=> More informations about this toot | More toots from sangster@macaw.social

Written by sayrer on 2024-08-15 at 19:17

@sangster @slightlyoff Scala wasn't so bad, it was fast. It was just that the memory-per-socket was too high (maybe better now, idk). I know for sure that Apple runs Rust for iCloud etc, but maybe Swift would be good too, and there's a whole Swift-Linux thing going on that I don't follow. I did a Go thing, and it totally fucking worked, but I just do not like that language.

=> More informations about this toot | More toots from sayrer@mastodon.social

Toot

Written by sayrer on 2024-08-15 at 19:35

@sangster @slightlyoff as it happens, someone just wrote this, which probably sounds familiar: https://mastodon.social/@jawnsy/112966152364902922

=> More informations about this toot | More toots from sayrer@mastodon.social

Descendants