Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Epic Stack

epicweb.dev

Post reply on HN
Print view View original

21–30 of 109 posts

Re: The Epic Stack

#21

Post by _heimdall »

jatins wrote: post #15

"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.

I really do appreciate Prisma's developer experience though. Recently I've been testing out Prisma for migrations and Kysely as the actual ORM.

Prisma is generating the Kysely type definitions automatically so it is still pretty hands off without the production overhead of prisma server/client.

Re: The Epic Stack

#22

Post by macNchz »

> It’s time to just ship

With “just shipping” as the stated goal, I am a big believer in using the tools you know, even if they’re not absolutely perfect or new or sexy enough to blog about.

Using things you know like the back of your hand will smooth over innumerable little snags that you’d run into if everything were new to you, and let you focus on the actual problem your software is supposed to solve. I can get a toy app live in an hour with the tools I know best, but I’m confident there’s at least one thing in this stack that I’d get stuck on for half a day, just because it’s unfamiliar.

Working with a team? Everyone throws their best-known tools in the pot and one person is directly responsible for selecting among them.

Re: The Epic Stack

#23

Post by mvf4z7 »

woile wrote: post #16

How's remix compared to nextjs? NextJs is quite well established, does Remix offer something better on top? Under which circumstances one would choose remix over nextjs?

I think one of those circumstances is when you previously worked for the company behind Remix. He is probably just really comfortable with the framework, so it makes sense for him to use it.

https://www.linkedin.com/in/kentcdodds/

Re: The Epic Stack

#24

Post by _heimdall »

TN1ck wrote: post #19

Had to laugh when I clicked on LiteFS and saw: > LiteFS is currently in beta and is not recommended for production use yet. Kind of JS dev in a nutshell, always bleeding edge.

Yeah I got a kick out of that one too. I like what LiteFS is going for but it's interesting to see in a stack focused on minimizing dependencies and avoiding painful updates.

Re: The Epic Stack

#25

Post by _heimdall »

julianeon wrote: post #12

I would describe myself as someone 'in the trenches' of web dev as a consultant and I wanted to say that I respect this more knowing it's from Kent C. Dodds. I considered buying his React course, though I haven't, but I respect his knowledge and opinions; and for what it's worth, if Kent C. Dodds considers this to be an excellent stack, I would give it serious consideration. If you consider yourself to be an indie ha…

100% agree, I've always been impressed by what the projects and courses Kent puts out. I'd love to hear a podcast episode with him really diving into the choices behind everything in this stack.

Re: The Epic Stack

#26

Post by tobr »

Looking 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.

Re: The Epic Stack

#27

Post by maxcan »

tmorton wrote: post #8
solatic wrote: post #4

I have mixed opinions seeing Tailwind on that list. If you're not a designer, it takes a non-trivial amount of time to add the utility classes you need to get something that looks passable. Quite simply, it gives you too much control over something that just doesn't matter for an MVP. There are great component libraries out there (I'm a fan of Chakra) that give you sane defaults so that you can get something off the…

That's the niche for https://tailwindui.com - which is how the Tailwind creators make money. If you're convinced by the overall Tailwind philosophy, it's a steal at the price they charge.

Personally I feel like TailwindUI is a missed opportunity.

Their opposition to abstracted utility classes means that anything you want to do has incredibly long, unreadable classes. Its quite a bit of work to abstract away the bits that you want.

https://daisyui.com is my absolute sweet spot for abstraction. Its a bit limited, especially compared to TwUI and flowbite but its developer experience is a joy.

Re: The Epic Stack

#28

Post by _heimdall »

listenallyall wrote: post #9
solatic wrote: post #4

I have mixed opinions seeing Tailwind on that list. If you're not a designer, it takes a non-trivial amount of time to add the utility classes you need to get something that looks passable. Quite simply, it gives you too much control over something that just doesn't matter for an MVP. There are great component libraries out there (I'm a fan of Chakra) that give you sane defaults so that you can get something off the…

Disagree -- tailwind is likely the fastest way to get a barely-passable design. (Certainly faster than using an external component library then realizing ones you need are only available under the paid, "premium" collection). And to say that design "just doesn't matter" while you're in fundraising mode, i think is also incorrect. You don't need perfect design, but it has to look pretty decent. It's in people's nature…

OpenProps is on par with the developer experience of Tailwind in my opinion. The choice between the two more comes down to preference, class names as inline styles or a collection of Css variables
Post reply on HN