Earlier quoted context omitted.
This is largely why I built Nodewood [1]. Every time I wanted to start a new project, almost always a SaaS idea, I'd skip over the "boring stuff" like building user management, subscription management, teams, admin, all that, to get to the meat of the business logic, to make sure I had a valid idea. But I still needed all that stuff eventually, so I'd have to lose time later building it all in! So I decided to just b…
Just an FYI, your styling doesn't seem to be responsive on an iPhone X
Build your own web framework
71–80 of 155 posts
Re: Build your own web framework
#72Re: Build your own web framework
#73The commenter's proposed solution was WASM. Wasm doesn't solve the issues in this post. What does this post talk about:
- serving content from the edge (wasm doesn't do anything there) - asset optimization (wasm doesn't help)
- pre-rendering complex pages to static HTML+css (wasm doesn't help)
More broadly, minimizing network trips, pre-fetching data, etc. etc. these are all things where Wasm won't help any more or less than JS.
Re: Build your own web framework
#74Earlier quoted context omitted.
This is an "um ackshually" reply. Nobody used LiveWire and it died a swift death. And don't "um ackshually" me about saying "nobody." You know what I mean.
Classic asp also supports JavaScript, it is old and wide spread in the bowels of legacy sites. I thought of node as a victory for async more than anything else.
In terms of server-side development? Async is rather useless on the server side. Can't generate a web page or JSON blob with the results of a database query until you actually get those results from the database. I can see the application for something like websockets but I presume most Node sites aren't using those.
I figured its success was due to V8 being reasonably fast, plus a generation of front-end-centric developers coming along who had learned to use JS quite heavily on the front end and didn't realize or didn't care that better options already existed on the back end.
Re: Build your own web framework
#75Earlier quoted context omitted.
React can be used as a templating library server-side in a node environment (like handlebars). It's a bit heavy for the task but it works.
A huge benefit React (and anything else that uses JSX) has over text-based templating is that you can strictly lint/typecheck JSX because ultimately it's just syntactic sugar over plain JS.
Vue templates are typechecked for example.
Re: Build your own web framework
#76React made me like frontend for the first time since I was writing html by hand with maybe some PHP. Next has made me love full stack again, I just wish the api server was express by default.
Re: Build your own web framework
#77I’m glad that I’m living in a much faster and simpler world, but I fear, for end users and developers alike, that it is an ever shrinking one.
I really can’t understand the appeal of what, to my eyes, amount to endless layers of needless complexity.
I wish articles such as this one were more common:
https://alexcabal.com/posts/standard-ebooks-and-classic-web-...
This is the web I want and love.
Re: Build your own web framework
#78Re: Build your own web framework
#79Earlier quoted context omitted.
Its pretty hard to trust a lot of the eng content on the web right now; so much blogspam, self promo stuff from frankly underqualified people who are trying to build up a profile to get hired. Somehow I still don't feel that way about StackOverflow. Google and random results though... yikes.
Until now I had not found an eloquent way to express that emotion, but you come close. Somewhere around the time node got very popular, I started to notice a lot of impeccably branded (is that the right word? trendy maybe?) websites with tutorials that used all the right buzzwords to get me interested. Once I'd step through the content, it'd be very low quality. Despite the smooth lines and round edges, a lot of them…
Re: Build your own web framework
#80This is too funny. I predicted that when I entered this post the first comment would be HN people bemoaning complexity. And indeed it was. The commenter's proposed solution was WASM. Wasm doesn't solve the issues in this post. What does this post talk about: - serving content from the edge (wasm doesn't do anything there) - asset optimization (wasm doesn't help) - pre-rendering complex pages to static HTML+css (wasm…