3 ms·

I clicked on the the castle-engine.io link out of curiosity and then went to the Hello World example, and was greeted by this line: {$mode objfpc}{$H+}{$J-}

I clicked on the the castle-engine.io link out of curiosity and then went to the Hello World example, and was greeted by this line: {$mode objfpc}{$H+}{$J-} // Just use this line in all modern sources That screams "lots of old cruft". Poking around the rest of that tutorial, I see crufty things like inheritance, manual freeing of memory, and a whole section on CORBA. I can't speak to why Pascal died, but I would guess that historical baggage is the thing that's preventing a revival.

KronisLV 5y ago
In many ways, that's the price you pay for long term backwards compatibility. After all, JavaScript didn't remove the function(){} syntax either when the arrow syntax was introduced. Moreso, React hasn't remove class based components either as of yet, even though we have hooks and function components now. I actually find myself wishing that Java 8+ hadn't removed so much of the standard library without backwards compatible ways to reintroduce the logic, since now the transition from 8 to newer releases is a massive pain, especially because of migrating a 1M SLoC enterprise app is no small feat. So yes, Pascal has baggage but it's not always a bad thing.