Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

You probably don't need a single-page app

journal.plausible.io

Post reply on HN
Print view View original

1–10 of 522 posts

Re: You probably don't need a single-page app

#2

Post by ttty »

Normally you'll always need to add something interactive, therefore js. To do that with server side rendering you'll couple the client side to the server side.

For example the server has to send a tag with a class name that the client also is aware of that.

Therefore you have 1 component, where half is on server side and half of on client side, which in my opinion is not maintainable.

Re: You probably don't need a single-page app

#3

Post by nkozyra »

While I've long been more comfortable with server rendered pages, I feel like we're oversaturated with this sentiment. I don't think it matters all that much.

The message is build with what accomplishes your goals and works with your team's skills.

The notion that SPAs are only good for certain types of applications or organizations doesn't make much sense to me.

Building server-generated web sites works faster for me because I'm still more comfortable with it. SPAs make concessions but so do server generated apps.

Re: You probably don't need a single-page app

#4

Post by hskaw »

ttty wrote: post #2

Normally you'll always need to add something interactive, therefore js. To do that with server side rendering you'll couple the client side to the server side. For example the server has to send a tag with a class name that the client also is aware of that. Therefore you have 1 component, where half is on server side and half of on client side, which in my opinion is not maintainable.

This is unrelated to the article. Many webpages, like HN, use JS but are not SPAs.

Re: You probably don't need a single-page app

#5

Post by nkozyra »

ttty wrote: post #2

Normally you'll always need to add something interactive, therefore js. To do that with server side rendering you'll couple the client side to the server side. For example the server has to send a tag with a class name that the client also is aware of that. Therefore you have 1 component, where half is on server side and half of on client side, which in my opinion is not maintainable.

You can get surprisingly far without Javascript, imo. Interactivity means a lot of different things, do you won't always need to have coordinating front and back ends

Re: You probably don't need a single-page app

#7

Post by sigfubar »

nkozyra wrote: post #3

While I've long been more comfortable with server rendered pages, I feel like we're oversaturated with this sentiment. I don't think it matters all that much. The message is build with what accomplishes your goals and works with your team's skills. The notion that SPAs are only good for certain types of applications or organizations doesn't make much sense to me. Building server-generated web sites works faster for m…

> The message is build with what accomplishes your goals and works with your team's skills.

Unfortunately most teams cannot be trusted to pick the right tool for each job without overcomplicating the planned implementation. Ego and the yearning to do “cool stuff” conspire to derail projects that could have been built without fuss using simpler tools.

Re: You probably don't need a single-page app

#8

Post by tyingq »

I'm more interested in the future of "you probably don't need a native app".

It feels like browsers are closing the gap pretty well with things like IndexedDB, offline features, WASM, etc. Still a ways off, but seems like it's getting there.

I do worry, though, that it's not really in Apple's or Google's best interest to move that along.

Post reply on HN