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

11–20 of 109 posts

Re: The Epic Stack

#11

Post by doctor_eval »

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.

Couldn’t agree more. Tailwind css is great, but TailwindUI is where the wins are.

I love using it and despite being crap at design, I’ve managed to put some stuff together that I think is not half bad. (And I remain mighty impressed with their business plan, too!)

Re: The Epic Stack

#12

Post by julianeon »

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 hacker, or follow people who do, then this deserves your consideration too, as Dodds is essentially coming from that background.

Re: The Epic Stack

#13

Post by shanebellone »

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…

"I would give it serious consideration"

There are 18 components listed. This stack is thick.

Re: The Epic Stack

#14

Post by madeofpalk »

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…

Tailwind exists at a different part of the... stack. Tailwind is not a component library, it's a styling language as an alternative to CSS.

Re: The Epic Stack

#15

Post by jatins »

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

Re: The Epic Stack

#16

Post by woile »

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?

Re: The Epic Stack

#18

Post by have_faith »

Nothing against most of the individual tech chooses but this is a phat stack. I can’t imagine using something with so much stuff baked in, is it pluggable in any way? I guess the whole point is it’s not.

Re: The Epic Stack

#19

Post by TN1ck »

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.

Re: The Epic Stack

#20

Post by ohthatsnotright »

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.

It also does code generation into its own module, so good luck with hoisting in a monorepo where you want multiple independent prisma schemas. MikroORM[1] is a much better alternative to Prisma in my opinion but any ORM carries some form of baggage.

[1] https://mikro-orm.io/

Post reply on HN