4 ms·

Kent seems like a nice guy, but every piece of his writing seems to be a massive beginner trap. Experienced developers are not setting up brand new projects li

Kent seems like a nice guy, but every piece of his writing seems to be a massive beginner trap. Experienced developers are not setting up brand new projects like this because it's massive overkill at the jump, but newbie devs who don't know better might try to.

noahtallen 3y ago
I don’t know if I agree. For a toy project, sure, you don’t need anything at all except a static file host. However, many experienced devs aren’t going to sacrifice tools they know improve codebases when working on new projects at work, or starting something they think could turn into something bigger. It’s so much easier to have some of these tools available from the start, especially if this requires no extra work to setup (which seems to be the point of this anyways). IMO that includes linting/formatting, type safety, unit tests, observability with a dashboard and analytics, and at least very basic CI/CD. Things that I’d find hard to give up working in other code bases :) Obviously there is going to be a huge amount of bike-shedding about what to use for X or if it’s useful; it’s basically impossible to avoid in this community. So I don’t know if that really detracts from the concept of having a stack with some solid defaults out of the box. Personally, I might avoid the database/auth/payments related stuff at first, since that feels more subjective. However, tools like typescript, eslint, and prettier are practically industry standards. It is still a pain in the ass to get a lot of the basics set up for different projects, so it’s nice to see some opinionated approaches to automating this. Compare to other languages like Rust, and the test runner, formatter, linter, dependency manager, and type safety are all built into the language tool chain. It’s so pleasant to not have to do any work to set that up, and I wish JS was more like that.
0xblinq 3y ago
Well, the business is to sell courses and consulting once you make a mess. It’s understandable.

noahtallen 3y ago

I don’t know if I agree. For a toy project, sure, you don’t need anything at all except a static file host. However, many experienced devs aren’t going to sacrifice tools they know improve codebases when working on new projects at work, or starting something they think could turn into something bigger. It’s so much easier to have some of these tools available from the start, especially if this requires no extra work to setup (which seems to be the point of this anyways). IMO that includes linting/formatting, type safety, unit tests, observability with a dashboard and analytics, and at least very basic CI/CD. Things that I’d find hard to give up working in other code bases :) Obviously there is going to be a huge amount of bike-shedding about what to use for X or if it’s useful; it’s basically impossible to avoid in this community. So I don’t know if that really detracts from the concept of having a stack with some solid defaults out of the box. Personally, I might avoid the database/auth/payments related stuff at first, since that feels more subjective. However, tools like typescript, eslint, and prettier are practically industry standards. It is still a pain in the ass to get a lot of the basics set up for different projects, so it’s nice to see some opinionated approaches to automating this. Compare to other languages like Rust, and the test runner, formatter, linter, dependency manager, and type safety are all built into the language tool chain. It’s so pleasant to not have to do any work to set that up, and I wish JS was more like that.

0xblinq 3y ago

Well, the business is to sell courses and consulting once you make a mess. It’s understandable.