Comment by MisterKent | Hacker News Reader

Comment by MisterKent | Hacker News Reader

Parent Full thread

In the web framework world, libraries are moving from a react component style of authoring to an older knockout based model. This means, instead of rendering an entire block of HTMl on each render pass, just a minimal subset will be rerendered, as the variable is bound to specific DOM elements. This effort started with Knockout, fell out of favor, and saw a resurgence with the success of SolidJS. Svelte has started moving in this direction. It's my opinion that React's compiler will eventually serve the same purpose to allow their giant user base to get the same benefits.

In the web performance space, there's some interesting stuff happening in origin trails around shared dictionary compression. It has been tried and failed before but the latest iteration/spec hopefully improved those shortfalls that made them unusable. Also, ZSTD compression has taken the crown from brotli.

Metas new AR glasses seem to be approaching the ideal hardware, IMO it's still searching for its killer app. Microsoft exited the AR space by killing hololens.

Startup space is dying right now, with very low VC risk tolerance / interest. Some funds have returned money to investors rather than risk it in investing.

Still seeing new auth companies joining the party, whether they are focusing on SSO, customer identity and access management, or authorization. Most are open source, some are SaaS.

Tech meetups seem to be coming back. People want to chat in person. Finding space to meet and sponsors is still not easy, but the demand from the community is there.

Rails continues to deliver a best-in-class batteries included solution for standing up web apps. I see some new folks being pulled into the community; some who enjoy it so much they participate even though their day jobs use some other stack.

As someone else mentioned downstream, IaC is still happening and getting pushed further and further. Whether you are talking about the more standard TF/OpenTofu IaC or some of the newer declarative environment options (I've chatted with the nitric folks), defining infrastructure as software gives you so much power that it seems to be unstoppable.

I am aware, at least a bit, of the Hotwire/liveview/Laravel turbo idea of just streaming DOM diffs instead of full pages, and how that is becoming a real force to reckon for SPAs.

Agreed! The pitch is great. Deliver twice as much by writing half as many apps as your competitors to deliver the same features. Let your competitors write a server app and a client app, and keep them in sync, while you. just. don't.

Do you have some examples of complex SPA-like apps written in this tech? I find it hard seeing how you would implement interactive components this way. They recommend Stimulus for extra JS, but then, what is the benefit over SPAs?

What I can see is that it could be a nice solution for SPAs that should never have been SPAs in the first place, i.e. mostly static pages with JS navigation used for reasons of fashion.

https://dev.37signals.com/page-refreshes-with-morphing-demo/

I'm not being snarky. What apps must be SPA's and why? I'm personally questioning where that line really should be.

not OP, but here's a nice example with Elixir Liveview: https://fly.io/blog/livebeats/

It has a tutorial, also a demo and some videos.

When I think knockout, I think more about the MVVM method of 2 way data binding, which creates some of the most complicated and difficult to debug apps I've ever worked on - is that the same thing, or is that just in how they're authoring views?

Reply on news.ycombinator.com