3 ms·
I was part of a team at a job about 20 years ago that ported an existing C codebase over to (then new) Java. Once we got everything working, a co-worker who wa
by commandlinefan 3y ago
I was part of a team at a job about 20 years ago that ported an existing C codebase over to (then new) Java. Once we got everything working, a co-worker who was very familiar with the old C codebase remarked that with C it took a lot longer to get things working the first time, but once they were working, they stayed working whereas with Java you could get things working pretty quick, but you'd start to see problems when you actually put load on it.
- gavinhoward 3y agoAuthor here. This is my experience, though I started in Java and transitioned to C. My C code also does not need to be updated for language changes and such.
- canadianfella 3y ago[dead]
- conor- 3y agoHow do you feel about Go if you've ever worked with it? It seems like it was intended to solve exactly those types of pain points associated with maintaining Java programs
- gavinhoward 3y agoGo is fine, but I'm not really a fan.
- jakogut 3y agoI'm not the person you responded to, but my biggest complaint with Go is binary size. It makes it rather unusable for low level programs on resource constrained systems.