Perhaps surprising: I agree with @slightlylate that the discussion we're having about web performance isn't helping us move forward as a community.
Show this thread
-
We're over-focused on benchmarking "hello world" minimal thresholds, with very little focus on what we can do as a larger community to systemically reduce the cost of abstractions?
Show this thread
The "hello world" focus is a big problem. Too many popular backend benchmarks will, for example, never require looking at request headers -- thus favoring a framework which implements `headers.get` as an on demand string search, even though that will hurt real world use cases
-
-
I suspect we're talking about opposite sides of web tech though. :)
-
The problems exist in both places, but are much much more acute on the client side.
- 1 more reply
New conversation -
-
-
This goes so far as so penalize frameworks for constant-time verification algorithms, or even having on-by-default cookie signature verification at all.
-
And on the server side, the "slow frameworks" have a few milliseconds of overhead, while people report "requests per second", which produces much much bigger apparent differences.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.