4 ms·
"resulted in developers that don't even possess this type of thinking anymore." The good old days weren't. What it resulted in on average was developers who ju
by jerf 10y ago
"resulted in developers that don't even possess this type of thinking anymore."
The good old days weren't. What it resulted in on average was developers who just bashed on their manual allocation until it "seemed to work", not glorious hand-constructed shimmering perfect crystals.
At least now the code that "seems to work" usually does, and is memory-safe now, so yes, it's an improvement. If you still want to be careful and do it by hand in such a language, they're still there, and there's even better options arising.
- mschaef 10y ago> At least now the code that "seems to work" usually does, Some of that may come down to better hardware. It's possible to be incredibly naive with today's hardware and still get results that would've taken high level engineering 20 years ago. Edit: This is down-modded, but it's fundamentally good news. Increases in our capacity to do productive work with these machines come from both software and hardware improvements. Not sure what else you'd expect.
- sgift 10y ago> Edit: This is down-modded, but it's fundamentally good news. Increases in our capacity to do productive work with these machines come from both software and hardware improvements. Not sure what else you'd expect. The downvotes are probably from the realization that this is good and sad news at the same time. On the one side, it is good news because many software projects wouldn't have been realized if you couldn't be that naive, on the other side who knows what would be possible with a bit more "discipline" (for lack of a better word)
- kpil 10y agoI think you could leak a little 20 years ago too, or use unnecessary amounts of memory - in most cases. It's just a few applications and parts of applications that really are resource constrained and critical enough to really matter...
- mcguire 10y agoCertainly. All those Unix-style filter programs had little need to be too careful since they didn't run for long. On the other hand, anyone know if the leak in the X server ever got fixed? IIRC, it was small enough that it was only a problem running the server for months on a resource constrained machine.
- mcguire 10y agoThe power of a notation is not in what it lets you think about, but in what it lets you not think about.
- mschaef 10y agoAgreed... the notational convenience of GC is easy to overlook but important. Particularly when anonymous closures, etc get involved, it's very useful to not have to save off a reference and pass it around to the point where it can be manually freed.
- pbh101 10y agoAlso, many more tasks are now economically feasible whereas before, the high fixed upfront cost of programming would have made them never done. In other words, we're making more programs now to do more more-trivial things because the cost of doing so is lower, and that's more or less a good thing.
- gopalv 10y ago> At least now the code that "seems to work" usually does, and is memory-safe now, so yes, it's an improvement. The most significant part of that statement comes from accepting contributions into your project. Java has made it much saner to just look at a patch and LGTM +1, over any work I've ever done in C/asm. Trust in the careful handling of memory by a stranger has been replaced by trust in the system to complain if they don't ... which has made for bigger and wider communities of strangers sending each other patches.