4 ms·
I'd say this is the typical case for most languages, especially if they try to compile the entire codebase and only report errors at the end. Take TypeScript,
by ljm 3y ago
I'd say this is the typical case for most languages, especially if they try to compile the entire codebase and only report errors at the end.
Take TypeScript, for example: if you bugger up a type definition or function call in one file, you'll have to wade through the errors of everything depending on it. Oftentimes you can go from 30 errors to just 2 or 3 with one simple change.
The alternative is they fail at the first error but you don't get the root cause and end up fixing shit one by one if the problem isn't obvious.
Especially with a new project in an unfamiliar language - start small and compile small, incremental changes. You won't end up with something you can't fix, which can't be said for installing dozens of dependencies up front and hoping for the best.