3 ms·
Which is nonsense, because: 1. I have never seen a framework that didn't go to great lengths to update to new changes quickly in development 2. Which means yo
by eevee 13y ago
Which is nonsense, because:
1. I have never seen a framework that didn't go to great lengths to update to new changes quickly in development
2. Which means you lose resources between requests, unless you stuff them into the interpreter/httpd itself. And anyway this is only a problem for PHP, where by default everything runs in the top-level namespace, versus in separate functions.
3. That's a funny way to spin "no concurrency", but you can get that in any language by just not deploying it threaded.
- m3mnoch 13y agoblink blink um. have you used java?
- eevee 13y agonope
- Terr_ 13y agoWhat, you mean with "hot deployment" of your changes?
- eloisant 13y agoWell, even in Play Framework 1.0 in 2009 there was hot reloading. Edit a file, refresh your browser => it's there.
- Moru 13y agoOn the Atari ST you didn't even have to hit reload, the webpage reloaded automatically as soon as you saved your file. No need to alt-tab even, just keep webpage open next to your editor. Now get off my lawn.