I thought I'd run through this just because I like Remix. It confirmed my prejudices against Fly. I've never gotten an app to deploy on Fly on the first try. There's always some error that I've got to debug and fix. I can't imagine recommending Fly as easy. Contrast to Vercel where everything just seems to work on the first try.
The Epic Stack
61–70 of 109 posts
Re: The Epic Stack
#62Without fail, every article from Kent C. Dodds shows what appears to be total inexperience despite claims of the contrary. The advice is, at this point, almost meme worthy. There's an infamous post from 2021 (that he may have been roasted for here): https://kentcdodds.com/blog/how-i-built-a-modern-website-in-... Almost every single piece of advice is wildly overcomplicated and ridiculous. I do like some of the techno…
I was convinced that he was going to sell this "Stack" for an exorbitant amount like some other Javascript influencers have done in the past. Thankfully this seems to be free at least.
I think you still have to be careful about folks selling training courses (or consulting services) to make sure that they aren't also glorifying complexity, even if they aren't trying to sell a product (or library or framework).
Re: The Epic Stack
#63Looking at the logo wall, happily surprised that it doesn’t include React! …then looking a bit closer to discover that once again, I’m running in to a React dev who assumes that everyone assumes that everyone uses React, thus you don’t even need to mention that a boilerplate built on React is built on React.
Isn’t Remix filling that role in his logo wall?
Re: The Epic Stack
#64We already have multiple "Epic Stacks". They are Rails, Laravel, Phoenix and Django. They give you everything listed straight out of the box and you don't have to deal with the trash that is the JS ecosystem. That's what makes them Epic :)
Re: The Epic Stack
#65Without fail, every article from Kent C. Dodds shows what appears to be total inexperience despite claims of the contrary. The advice is, at this point, almost meme worthy. There's an infamous post from 2021 (that he may have been roasted for here): https://kentcdodds.com/blog/how-i-built-a-modern-website-in-... Almost every single piece of advice is wildly overcomplicated and ridiculous. I do like some of the techno…
[flagged]
Re: The Epic Stack
#66Looking at the logo wall, happily surprised that it doesn’t include React! …then looking a bit closer to discover that once again, I’m running in to a React dev who assumes that everyone assumes that everyone uses React, thus you don’t even need to mention that a boilerplate built on React is built on React.
Curious what alternative you believe is a better option for building applications in this day and age... Angular is basically dead and Vue abstracts too much (imo), unless you think vanilla JS is the way?
Personally, Svelte when I get to choose. But that’s not really what my comment is about.
Re: The Epic Stack
#67Without fail, every article from Kent C. Dodds shows what appears to be total inexperience despite claims of the contrary. The advice is, at this point, almost meme worthy. There's an infamous post from 2021 (that he may have been roasted for here): https://kentcdodds.com/blog/how-i-built-a-modern-website-in-... Almost every single piece of advice is wildly overcomplicated and ridiculous. I do like some of the techno…
It's not just him and is more of a general issue with frontend "thought leadership". Most of them went into it when they were relatively early in their career. There's no 1:1 relationship between years of experience and skill/knowledge of course, but if you pick any random FE influencer on Twitter, chances are they have less experience in the field than the staff engineer in your team. Unfortunately, it shows.
They do have a lot of good advice, and I don't want to throw the baby with the bathwater. But they do get it wrong pretty often, and it does waste hundreds or thousands of hours having to go internally in an engineering org telling people "No, it's not because you read it on the internet that it's true".
A much older equivalent example was how back in the days in the Microsoft world everyone would say you HAD to use stored procedures for performance and security, ignoring prepared statements, so a lot of big companies had internal onboarding classes that always started with debunking it. Kent added a ton of confusion and did a lot of disservice to the unit testing space (the library is good, the philosophy lacks a lot of nuance), some other folks are creating a lot of chaos around SPAs/client vs SSR (they started adding nuance to that more recently), and so on and so forth.
It's part of why the JS ecosystem keeps restarting from scratch over and over instead of building on top and creating vertical innovation. We get there eventually, but it's so much slower than it needs to be.
Re: The Epic Stack
#68Earlier quoted context omitted.
I was convinced that he was going to sell this "Stack" for an exorbitant amount like some other Javascript influencers have done in the past. Thankfully this seems to be free at least.
I think you still have to be careful about folks selling training courses (or consulting services) to make sure that they aren't also glorifying complexity, even if they aren't trying to sell a product (or library or framework).
"You're wrong about the way you do unit test! Everything everyone is telling you is wrong! Fortunately, you can get my course that will clarify everything I just confused you about!!"
Re: The Epic Stack
#69Looking at the logo wall, happily surprised that it doesn’t include React! …then looking a bit closer to discover that once again, I’m running in to a React dev who assumes that everyone assumes that everyone uses React, thus you don’t even need to mention that a boilerplate built on React is built on React.
To be fair, they're not assuming anything, and Remix is like the first thing in the list, which is one of the major React frameworks right now. The name is not as descriptive obviously but its like someone saying SvelteKit and not mentioning Svelte proper.
Re: The Epic Stack
#70"It's time to just ship" Lists 10 tools to start with. Also, had the displeasure of using Prisma a while back. Extremely slow type generation, and complex to work with its client-server architecture. When your library requires a separate process you know you messed up. If you want to just ship, pick up Next.js, or whatever you already know and add dependencies when you need them. Let thought leaders thought lead.
Interesting. Have you tried https://github.com/kysely-org/kysely ? I know Prisma is an ORM and kysely is a "type-safe typescript SQL query builder" but I just wanted to know if you had the opportunity to try it and your opinion about it. I'm searching for SQL typescript tooling for my next project.
Have you tried Slonik (https://github.com/gajus/slonik)? It won't generate types from queries automatically, but it encourages writing SQL vs. a query builder and allows type annotations of queries with Zod. Query results are validated at runtime to ensure the queries are typed correctly.