3 ms·

That's a strong argument against using front-end frameworks and other things that require you to run a build on your front-end code. There are plenty of option

That's a strong argument against using front-end frameworks and other things that require you to run a build on your front-end code. There are plenty of options to build fast, modern front ends without having to deal with any of that. And you're right about IDEs too. Given the choice between a full-blown VS.NET + ReSharper versus VSCode + $1,000 in my pocket, it's just no contest. No matter your bill rate, you still break even in single digit hours of productivity gain. As a solo entrepreneur, it's even more of a no brainer, since it's my free time that I'm gaining by working with better tools.

nnq 8y ago
> a strong argument against [...] things that require you to run a build on your front-end code Not really, if it's your own code that requires a build step, then you control that build step and the tools and all and you can have nice auto-reload and fully working source maps and integration with all your other tools... Do whatever exotic build and transpilation makes you more productive when developing your application's code. But libraries and frameworks... it's not OK to have a large part of the ecosystem dependent on such build tools and at the same time have no usable tooling standardization to easily implement something as basic as "jump to implementation in original source".