3 ms·
Because JavaScript developers are too busy fighting over whether it should be rendered on the client or server or both
by whalesalad 2y ago
Because JavaScript developers are too busy fighting over whether it should be rendered on the client or server or both
- rezonant 2y agoNot sure that's true, the answer is "it depends". Is your app a content website? Does it have interactive features? Is it a tool that has no state? Does it have tons of transient state? Do you depend on SEO for this thing? Do you need it to work offline? It's far too easy to think of the web as "the thing that feeds you text articles while you are actively connected to the Internet" and lose sight of the fact that as time goes on more and more software use cases are moving to it whether you like it or not. If it was not the preferred way to receive software as a user, software made using non-web stacks would have an immediate advantage over web stack ones. Obviously the opposite is true.
- switch007 2y agoThey're too busy replacing packages because the sole maintainer and contributor of each package found a new shiny thing to work on/need a new project with lots of emojis in the README to enhance their Personal Brand And every time, management just congratulate them for keeping "up to date"
- the_third_wave 2y agoIt'll end up somewhere in the middle: cloud rendering. Come try out our new service at Https://cloudrenderfish.frog.ly and be amazed at the insane benefits of offloading your render tasks to our experts.