Timeline for Rush to client-side in web development
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 27, 2012 at 6:10 | comment | added | Bruno Schäpper | I chose to accept this answer, because it is the most complete one. All the others have good points, but this is the most conclusive. Thanks everyone! | |
| Aug 27, 2012 at 6:09 | vote | accept | Bruno Schäpper | ||
| Aug 26, 2012 at 0:12 | comment | added | Jack Stone | Yes Sir, server-side frameworks promise the same benefits, yes. What needs to be known is that there are additional benefits, found unexpectedly, in emerging technology. It is at the lowest level (c) in the io. The threads wait. In JS it has a callback. It does not wait. So there is an io optimization at the lowest level. This realization is now, quietly, adopted in a large way by Microsoft. Which is why their OS is JS. Final point, this yields optimization and meta optimizations - at all levels. Because the language is flexible. A simple-invisible thing. Not known. Hope that helps. | |
| Aug 25, 2012 at 7:24 | comment | added | Bruno Schäpper | Great answer! But server-side frameworks promise the same benefits, don't they? | |
| Aug 25, 2012 at 6:50 | history | edited | Jack Stone | CC BY-SA 3.0 | deleted 1 characters in body |
| Aug 25, 2012 at 6:43 | history | edited | Jack Stone | CC BY-SA 3.0 | added 261 characters in body |
| Aug 25, 2012 at 6:38 | history | edited | Jack Stone | CC BY-SA 3.0 | added 261 characters in body |
| Aug 25, 2012 at 6:33 | history | edited | Jack Stone | CC BY-SA 3.0 | added 261 characters in body |
| Aug 25, 2012 at 6:24 | history | answered | Jack Stone | CC BY-SA 3.0 |