4 ms·
And so does Rails and Sinatra in Ruby land. I have encountered very few development servers that lacked hot-reloading in decades. Many such stacks will even in
by berkes 5y ago
And so does Rails and Sinatra in Ruby land.
I have encountered very few development servers that lacked hot-reloading in decades. Many such stacks will even inject some JS or headers to automatically refresh the browser for you on detected changes.
I think OP may have an outdated or skewed experience of web-development stacks. Where PHP through apache+mod_php had "instant code refresh" back in early 2000s, and other stacks (Beans, CGI, etc) required a manual reboot everytime you'd want to check your changes in a browser. But this hasn't been true since Rails was released in 2004~5.
Ironically the most difficult one I recently encoutered was a PHP-FPM with APC, that required a "manually" restart of nginx and php-fpm in the right order after every code change. But this really is not suited as "development" server, as shown in this anecdotal issue.
- thraxil 5y ago> and other stacks (Beans, CGI, etc) required a manual reboot Hey, now! Don't go lumping CGI in with those. :) CGI had the same "instant code refresh" as PHP since before PHP even existed. It even had a better "shared nothing" approach since you were guaranteed to start an entirely new process for every request.
- berkes 5y agoSorry. CGI is a bit unfair. I recall it refreshed fine with Perl, but CGI wrapping compiled languages (I did some C webdev back then) was a bit more involved. It's vague, but IIRC, that had more to do with the compiler than the CGI, indeed.
- thraxil 5y agoFair. My main experience with CGI was bash, Perl, and Python so I tend to think of compiled languages in a completely different context.