4 ms·

Yes, it is definitely a combination of things you could use. Calling it a "stack" makes it sounds like it's a good combination though. If you find yourself usi

Yes, it is definitely a combination of things you could use. Calling it a "stack" makes it sounds like it's a good combination though. If you find yourself using a library as quick fix to avoid learning or investing time into something, your end result will be forever limited by that. Real systems have hundreds or thousands of parts and they are always eventually complex, so complexity and the underlying tech cannot be avoided for long. Think twice before building a house of cards, that's the wrong kind of stack.

happytiger 3y ago
Real systems don’t become “stacks” just because of their complexity. In fact there is no merit whatsoever in complexity unless it serves a great good! Complexity can definitely be reduced and maintenance complexity is the real killer in software these days — both in price, wasted resources and stunted careers. Simple means supportable, and we should encourage more people to explore systems that “just work” even if they sacrifice some elegance. This may not be it, and your point about not confusing simplicity with progress is valid as heck, but there are good reasons to explore this stuff and I love seeing new combinations like this on HN.
williamcotton 3y ago
There’s nothing in OPs architecture that dictates a descent into spaghetti code. It looks very similar to a Flask (Python), Sinatra (Ruby) or Express (JavaScript) server-side application. It is very straightforward to use a traditional MVC-with-HTTP-verbs architecture. These end up being way cleaner than whatever happens when you split up the backend and front end into separate coupled applications. The downside has always been that your website seems a bit sluggish when doing full page reloads… but that’s where edge compute comes into play and it starts to feel as snappy as a server-side rendered web app feels when running locally.
rmilejczz 3y ago
I don’t really understand this perspective whatsoever. It sounds like you’re saying we shouldn’t rely on abstractions? Isn’t react a quick fix to avoid learning or investing in virtual dom management? Real systems are built upon abstractions

happytiger 3y ago

Real systems don’t become “stacks” just because of their complexity. In fact there is no merit whatsoever in complexity unless it serves a great good! Complexity can definitely be reduced and maintenance complexity is the real killer in software these days — both in price, wasted resources and stunted careers. Simple means supportable, and we should encourage more people to explore systems that “just work” even if they sacrifice some elegance. This may not be it, and your point about not confusing simplicity with progress is valid as heck, but there are good reasons to explore this stuff and I love seeing new combinations like this on HN.

williamcotton 3y ago

There’s nothing in OPs architecture that dictates a descent into spaghetti code. It looks very similar to a Flask (Python), Sinatra (Ruby) or Express (JavaScript) server-side application. It is very straightforward to use a traditional MVC-with-HTTP-verbs architecture. These end up being way cleaner than whatever happens when you split up the backend and front end into separate coupled applications. The downside has always been that your website seems a bit sluggish when doing full page reloads… but that’s where edge compute comes into play and it starts to feel as snappy as a server-side rendered web app feels when running locally.

rmilejczz 3y ago

I don’t really understand this perspective whatsoever. It sounds like you’re saying we shouldn’t rely on abstractions? Isn’t react a quick fix to avoid learning or investing in virtual dom management? Real systems are built upon abstractions