Linked by theuserbl on Sun 10th Jul 2011 18:48 UTC
Permalink for comment 480239
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
Linked by Thom Holwerda on 04/15/13 22:44 UTC
More Features »
Sponsored Links



Member since:
2005-11-13
Well, we've got perl apps that run side-by-side along with the java ones, and never have any trouble with those. It's only once the 'legacy' perl code gets rewritten to java (I assume because of java's multi-threading capabilities) does the trouble begin.
But who knows, you guys may be right. I don't work on the dev team - I'm just the grunt that gets paged at 3am every time one of those f**king apps decides to go on strike. So, I just call 'em like I see 'em. I've seen so many badly written apps in java, both on the server and desktop, yet it always seems to be the developers' fault every time this happens. Maybe other languages make it just as incredibly easy as java to write apps that run like dogshit. *shrug*
Edited 2011-07-11 05:31 UTC