Off course, we don't use light in the vacuum to move data from the memory to the CPU, in a straight line, we use electricity through copper wires that needs to trace big hooks to avoid electronic components in the motherboard. To solve this problem, the CPU uses cache.
-
-
Well, this is a tricky question. I'll say, don't think on webpages only, but in products that were created using web technologies:
@SlackHQ ,@code,@discord,@AtomEditor and anything created with@electronjs. Also, you can run Webassembly in@nodejs in the backend. -
One very specific example: Casino Games. The most important thing for a casino game that provide games on smartphones is to have the player in the game for as long as possible. Most of them uses HTML5 canvas to develop games. A game uses 50% less battery means 2x money.
- 1 more reply
New conversation -
-
-
I would say web apps would benefit from better resource management and less bloat, less so SIMD or any more involved optimizations. Honestly though, with some web apps I can't even tell what could possibly be the bottleneck given how simple they are yet they are still slow!
-
Something I tried to show in the thread, is that SIMD and Multithread performance gains are nothing compared with the performance you have if you code your programs with CPU cache efficiency in mind.
- 1 more reply
New conversation -
-
-
Couldn't agree more, games. And webgl applications.
-
Which are extremely niche problems in the webdev ecosystem and generally not created by "frontend developers."
End of conversation
New conversation -
-
-
I didn’t understand one of these words
@TimSweeneyEpic, a word that I do understand is triosThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.