4 ms·
Since many of the problems we have today to solve were solved in the '80s and '90s with tiny tools such as Turbo Pascal, we can conclude that faster hardware an
by DeathArrow 7y ago
Since many of the problems we have today to solve were solved in the '80s and '90s with tiny tools such as Turbo Pascal, we can conclude that faster hardware and lots of memory are allowing us to bloat the software by using layers upon layers of abstraction, SOLID and DDD principles, virtualizations inside virtualizations inside virtualizations, emulators running on emulators, totally inefficient interpreters.
Using Python with its Global Interpreter Lock seems like a total antipattern when it comes to use resources wisely.
- gmueckl 7y agoWell, some things are enabled by more involved software architectures that would not have been realistically achievable back then. Turbo Pascal was limited to only showing the first error it encountered when compiling your program. It did move the cursor to the location of the suspected error. It wouldn't have been able to generate error markers in th e background while you type. Autocompletion would not have been realistically achievable either. That doesn't mean that lots of programs aren't bloated by overly complicated internal designs. Sometimes this is a concession to the development team structure. Sometimes this is incompetence. It is hard for me to tell from the outside.
- Certhas 7y agoBut it compiled instantaneously. So "compile" was simply the command used to "jump to next error".
- badsectoracula 7y agoTBH in practice i never found showing more than one error useful since way more often than not these errors are either related or the first error also causes the other errors. I only find it useful when the compilation process is very slow, but i try to avoid slow compilers whenever possible and always just recompile whenever i fix the first error. Most IDEs move your cursor to the error position so the build key also acts as a "move to next error" key :-P.
- gmueckl 7y agoIt depends on the language you are using. Sometimes it can be useful to see more than the first error message to understand the problem. I find all the squiggly lines and annotations that Resharper adds to the code quite helpful. These are a kind of low key way of indicating minor issues with the code. I find that appropriate for things like coding style violations because they often aren't an immediate concern because I want to get things working first. But they are a good reminder of the open cleanup work once that is done.
- badsectoracula 7y agoI think it depends on more than just the language... i find the squiggly lines very distracting and brings me a bit of anxiety, like someone being over my shoulder looking at my code and going "hey, you forgot a semicolon over there" and i'm like "YES I KNOW, i just noticed something else that i want to edit a few lines above, i'll fix it, leave me alone" :-P.
- gmueckl 7y agoI don't have any problems with that at all. I confess that I have a kind of a disconnect with people like you who seem to be easily distracted by this. I don't understand it. I am not thinking that you are wrong or anything like that - it's on me. This is mostly my confusion talking right now. Sometimes I wonder whether this is somehow related to a quest for clean/simplified (or, as some might say, dumbed down) user experiences in other situations. Also, is this in general more of a thing in America compared to the rest of the world?
- badsectoracula 7y agoYeap, but note that modern hardware also allows simplifying the code considerably, thus making it easier to avoid bugs. As an example, Turbo Pascal used to have an addon called "Turbo Toolbox for Databases" (or something like that) that described using a simple database API to handle the customers of a dentist (that was an example) stored as B+ Tree indexed records on disk. This added a lot of complexity which was necessary due to the memory and disk limitations of the time. Nowadays, the same "database" in Free Pascal can be achieved with a simple "array of TCustomer" type that keeps everything in memory and is loaded/written to disk with a couple of lines of code. Computers are so fast that unless you have every single citizen of a European country as a customer, you can simply perform linear searches directly in RAM without touching the disk. If anything this approach would also be much faster than if the Turbo Toolbox approach was used on a modern PC. Of course a lot of software is very inefficient but TBH i do not ever expect this to change since people will always value features and convenience above performance - even when they do not use said features themselves.