Well,
I have the same questions and been overwhelmed by the same amount of uninformative threads spawning every day so what I did is install one system with systemd in production on non critical system. My experience has been a good one so far and the systemd designs decisions (which people have been complaining a lot about) have not impacted my life as it's user.
Another thing to consider, and most haters/fanboys forget, is that it might be the right/wrong option for YOU on YOUR context and it just might not be for another person or on another context.
Try to create a decontaminated area around the bad code where you have tests, good new code and, specially, confidence on the new stuff you're building.
Every time you have to touch the old codebase, try creating new code that replicate the old behavior.
If you absolutely need to change the old code be sure to at least cover the affected area with many functional tests BEFORE you change anything. That safety net will make you fell relaxed and confident on your changes.
Most developers really love greenfield projects but renewing an old one could be just as rewarding.
If you want some hardcore insight on how to handle that, read 'Working Effectively with Legacy Code' from Michael Feathers.
http://www.amazon.com/Working-...
I agree that "The" Football World Cup, (The one with the right, round, ball), isn't crack the net, but unmesured data flux will ocurr and some nodes will be considerably slow.
Slashdot Mirror
You are on the surface of the Earth, which it's where you've started. - focus on the question, not on the solution.
Well, I have the same questions and been overwhelmed by the same amount of uninformative threads spawning every day so what I did is install one system with systemd in production on non critical system. My experience has been a good one so far and the systemd designs decisions (which people have been complaining a lot about) have not impacted my life as it's user. Another thing to consider, and most haters/fanboys forget, is that it might be the right/wrong option for YOU on YOUR context and it just might not be for another person or on another context.
River Raid
That's the only application for that that I can think right now. :p
Try to create a decontaminated area around the bad code where you have tests, good new code and, specially, confidence on the new stuff you're building. Every time you have to touch the old codebase, try creating new code that replicate the old behavior. If you absolutely need to change the old code be sure to at least cover the affected area with many functional tests BEFORE you change anything. That safety net will make you fell relaxed and confident on your changes. Most developers really love greenfield projects but renewing an old one could be just as rewarding. If you want some hardcore insight on how to handle that, read 'Working Effectively with Legacy Code' from Michael Feathers. http://www.amazon.com/Working-...
Well,
remember 9/11?
Text only page in NYT?
I agree that "The" Football World Cup, (The one with the right, round, ball), isn't crack the net, but unmesured data flux will ocurr and some nodes will be considerably slow.
But these are sensacionalist news anyway.
[]'s jc