3 ms·

Well, some things are enabled by more involved software architectures that would not have been realistically achievable back then. Turbo Pascal was limited to o

Well, 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 ago
But it compiled instantaneously. So "compile" was simply the command used to "jump to next error".
badsectoracula 7y ago
TBH 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 ago
  It 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 ago
    I 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 ago
      I 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?

Certhas 7y ago

But it compiled instantaneously. So "compile" was simply the command used to "jump to next error".

badsectoracula 7y ago

TBH 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 ago
It 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 ago
  I 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 ago
    I 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?