4 ms·

Any time I read anything about any web-adjacent technology I'm incredibly thankful that I don't work anywhere near that industry. Embedded can be complex, but

Any time I read anything about any web-adjacent technology I'm incredibly thankful that I don't work anywhere near that industry. Embedded can be complex, but web stuff is just a Lovecraftian nightmare in comparison

milesvp 2y ago
I have stared into the abyss and seen the eyes of cthulu. I am much happier writing embedded drivers than I was trying to make sense of why previous devs thought it was a good idea to move bounded tunable server side api calls to the client, allowing it to effectively write arbitrary sql calls across multiple databases.
- qudat 2y ago
  Iteration speed is significantly fast on the client. Perf is an afterthought — for better or worse
  - swyx 2y ago
    spoken like someone who doesnt deploy clients at discord scale? the 200 backend nodes surely update significantly faster than the hundreds of millions of clients.
- artursapek 2y ago
  Sounds like a fun time lol
- bdcravens 2y ago
  Fortunately the web is starting (very slowly) to return to sanity, pushing back towards the simpler server-rendered pattern with Javascript being relegated to specific use cases.
  - Aeolun 2y ago
    I really like the client rendered UI part. It’s a lot more efficient than sending the whole page again every time.
    - gonzo41 2y ago
      But you can cache the whole server side page and the cost is once. Whereas if you have the client side do the render then every client wears the cost.
      - iknowstuff 2y ago
        You usually can't because of users who are signed in needing slightly different pages etc.
        bdcravens 2y ago
        While not as fast as a purely client cached page, the server can selectively cache content, even when some bits of the page are dynamic.
      - asynchronous 2y ago
        We can also cache some of the dynamic JavaScript, depending on the scenario but your point stands.
      - bdcravens 2y ago
        Which becomes a far more important issue when dealing with bandwidth or CPU constrained devices, or artificially imposed constraints due to data usage costs.
      - Aeolun 2y ago
        That’s your generation that happens once. The browser still needs to render it. Sure, rendering it on the client may cost the client a bit more, but the client generally has the computational power to spare.
    - bdcravens 2y ago

milesvp 2y ago

I have stared into the abyss and seen the eyes of cthulu. I am much happier writing embedded drivers than I was trying to make sense of why previous devs thought it was a good idea to move bounded tunable server side api calls to the client, allowing it to effectively write arbitrary sql calls across multiple databases.

qudat 2y ago
Iteration speed is significantly fast on the client. Perf is an afterthought — for better or worse
- swyx 2y ago
  spoken like someone who doesnt deploy clients at discord scale? the 200 backend nodes surely update significantly faster than the hundreds of millions of clients.
artursapek 2y ago
Sounds like a fun time lol
bdcravens 2y ago
Fortunately the web is starting (very slowly) to return to sanity, pushing back towards the simpler server-rendered pattern with Javascript being relegated to specific use cases.
- Aeolun 2y ago
  I really like the client rendered UI part. It’s a lot more efficient than sending the whole page again every time.
  - gonzo41 2y ago
    But you can cache the whole server side page and the cost is once. Whereas if you have the client side do the render then every client wears the cost.
    - iknowstuff 2y ago
      You usually can't because of users who are signed in needing slightly different pages etc.
      - bdcravens 2y ago
        While not as fast as a purely client cached page, the server can selectively cache content, even when some bits of the page are dynamic.
    - asynchronous 2y ago
      We can also cache some of the dynamic JavaScript, depending on the scenario but your point stands.
    - bdcravens 2y ago
      Which becomes a far more important issue when dealing with bandwidth or CPU constrained devices, or artificially imposed constraints due to data usage costs.
    - Aeolun 2y ago
      That’s your generation that happens once. The browser still needs to render it. Sure, rendering it on the client may cost the client a bit more, but the client generally has the computational power to spare.
  - bdcravens 2y ago