31–40 of 80 posts
> ah yes, the famous XSS coming from your own backend API calls… Author does not seem to understand the concept of XSS. Of course your own API could return user-provided data to trigger XSS attacks. Entering alert(1); in a messenger to see whether its rendered value is escaped correctly is a famous example.
Reading that entire thing was a struggle. Really feels like _everyone_ is wrong here. Yes the current state of FE development is overly dogmatic and cultish. But it always has been. On the other hand the frameworks and build systems are solving actual problems, they're not there for looks. 5-7 second skeleton loaders are there because backend systems are slow, not because of the front end application. You can say "oh…
there is no way any competently written back end system takes 5-7 seconds for any reason whatsoever. A middling back end system with median complexity is doing 10-100K requests per second per server and is near-perfectly horizontally scalable.
Earlier quoted context omitted.
there is no way any competently written back end system takes 5-7 seconds for any reason whatsoever. A middling back end system with median complexity is doing 10-100K requests per second per server and is near-perfectly horizontally scalable.
I cannot fathom how you arrived at that conclusion - there are so many systems that need to display the results of complex data queries where caching or precomputing the results does not make sense - waiting several seconds for results would be normal in those cases.
Earlier quoted context omitted.
there is no way any competently written back end system takes 5-7 seconds for any reason whatsoever. A middling back end system with median complexity is doing 10-100K requests per second per server and is near-perfectly horizontally scalable.
If you serve data from a DC in California to the west coast of Australia it will take 10 seconds of just network transfer time. Sometimes data has a high degree of cardinality and cannot be cached. Some companies cannot afford to, or for other reasons cannot, have regional instances of their compute surfaces. This is just one common scenario, there are many others. > A middling back end system with median complexity…
What? Is this a typo or do you think that’s true?
Earlier quoted context omitted.
there is no way any competently written back end system takes 5-7 seconds for any reason whatsoever. A middling back end system with median complexity is doing 10-100K requests per second per server and is near-perfectly horizontally scalable.
If you serve data from a DC in California to the west coast of Australia it will take 10 seconds of just network transfer time. Sometimes data has a high degree of cardinality and cannot be cached. Some companies cannot afford to, or for other reasons cannot, have regional instances of their compute surfaces. This is just one common scenario, there are many others. > A middling back end system with median complexity…
Where did you get that calculation? Looks way way off
Earlier quoted context omitted.
> The problem with FE is that they seem to be wannabe nodejs BE devs instead of the W3C experts they should be What are the best resources for someone interested in being a W3C expert? (Aside from just slogging through https://www.w3.org/TR/ )
MDN is one of the best resources imo https://developer.mozilla.org/ Generally more practical than W3C.
Reading that entire thing was a struggle. Really feels like _everyone_ is wrong here. Yes the current state of FE development is overly dogmatic and cultish. But it always has been. On the other hand the frameworks and build systems are solving actual problems, they're not there for looks. 5-7 second skeleton loaders are there because backend systems are slow, not because of the front end application. You can say "oh…
there is no way any competently written back end system takes 5-7 seconds for any reason whatsoever. A middling back end system with median complexity is doing 10-100K requests per second per server and is near-perfectly horizontally scalable.
Earlier quoted context omitted.
there is no way any competently written back end system takes 5-7 seconds for any reason whatsoever. A middling back end system with median complexity is doing 10-100K requests per second per server and is near-perfectly horizontally scalable.
If you serve data from a DC in California to the west coast of Australia it will take 10 seconds of just network transfer time. Sometimes data has a high degree of cardinality and cannot be cached. Some companies cannot afford to, or for other reasons cannot, have regional instances of their compute surfaces. This is just one common scenario, there are many others. > A middling back end system with median complexity…
Earlier quoted context omitted.
there is no way any competently written back end system takes 5-7 seconds for any reason whatsoever. A middling back end system with median complexity is doing 10-100K requests per second per server and is near-perfectly horizontally scalable.
Not everyone has the luxury to work with competently written backend systems.
Even a backend roughly cobbled together in PHP4 with Varnish running on top of it would considerably outperform some of the stuff that is accepted as 'good enough' today.
Reading that entire thing was a struggle. Really feels like _everyone_ is wrong here. Yes the current state of FE development is overly dogmatic and cultish. But it always has been. On the other hand the frameworks and build systems are solving actual problems, they're not there for looks. 5-7 second skeleton loaders are there because backend systems are slow, not because of the front end application. You can say "oh…
there is no way any competently written back end system takes 5-7 seconds for any reason whatsoever. A middling back end system with median complexity is doing 10-100K requests per second per server and is near-perfectly horizontally scalable.