5 ms·

I agree with everything you've said here, but I'd like to add something about startup time. If it takes you 5s to start up your server, that's a lot of time yo

by raylu 13y ago

I agree with everything you've said here, but I'd like to add something about startup time. If it takes you 5s to start up your server, that's a lot of time you've added to each development iteration. Make a change, restart the server, wait 5s, see if it works/check debug output.

jbverschoor 13y ago
Ruby or Python are even worse (slow / big) than java these days. I'm a ruby guy btw..
- henk53 13y ago
  Java is not that bad at all these days. For years now every iteration of Java EE has become lighter (with respect to the programming model and the startup time of servers).
henk53 13y ago
JBoss EAP 6.0.1 does a cold start in 1.5 seconds on my 2.93Ghz i7. TomEE is some 2 seconds. If even that's too much, there's JRebel which does full hot reloading of pretty much every piece of code you change.
cunac 13y ago
typically you don't stop/start server during development cycle, hot deployment works 99% of cases
- deleted 13y ago
  [deleted]
cmircea 13y ago
This is business as usual for me with ASP.NET. IIS Express has to start, then the app to load, then to initialize, then to compile the views. And don't get me started on the Azure Compute Emulator.
exabrial 13y ago
If you're continuously restarting, you're doing it wrong. That argument became invalid about 4 years ago I think around the time Eclipse Helios was released. Now-a-days, starting a Tomcat or TomEE JVM in debug mode with Eclipse gives you the ability to hot swap probably 95% of your changes. It doesn't supporting adding completely new functions or changing declared fields. JRebel does support this though. As a matter of fact, if you're in a stack frame and you pause the execution pointer with a breakpoint, you can completely change the code of the function and the JVM will discard the current stack frame and then restart the functional call. Essentially, you can rewrite your code, while it's executing, without losing your stack.
threeseed 13y ago
Make a change, restart the server, wait 5s, see if it works/check debug output. Look at JRebel, Play or Nailgun. Most of us aren't waiting 5 seconds before checking output. We just refresh the browser.

by raylu 13y ago

jbverschoor 13y ago

Ruby or Python are even worse (slow / big) than java these days. I'm a ruby guy btw..

henk53 13y ago
Java is not that bad at all these days. For years now every iteration of Java EE has become lighter (with respect to the programming model and the startup time of servers).

henk53 13y ago

JBoss EAP 6.0.1 does a cold start in 1.5 seconds on my 2.93Ghz i7. TomEE is some 2 seconds. If even that's too much, there's JRebel which does full hot reloading of pretty much every piece of code you change.

cunac 13y ago

typically you don't stop/start server during development cycle, hot deployment works 99% of cases

deleted 13y ago
[deleted]

cmircea 13y ago

This is business as usual for me with ASP.NET. IIS Express has to start, then the app to load, then to initialize, then to compile the views. And don't get me started on the Azure Compute Emulator.

exabrial 13y ago

If you're continuously restarting, you're doing it wrong. That argument became invalid about 4 years ago I think around the time Eclipse Helios was released. Now-a-days, starting a Tomcat or TomEE JVM in debug mode with Eclipse gives you the ability to hot swap probably 95% of your changes. It doesn't supporting adding completely new functions or changing declared fields. JRebel does support this though. As a matter of fact, if you're in a stack frame and you pause the execution pointer with a breakpoint, you can completely change the code of the function and the JVM will discard the current stack frame and then restart the functional call. Essentially, you can rewrite your code, while it's executing, without losing your stack.

threeseed 13y ago

Make a change, restart the server, wait 5s, see if it works/check debug output. Look at JRebel, Play or Nailgun. Most of us aren't waiting 5 seconds before checking output. We just refresh the browser.