Live data from Hacker News

The Epic Stack

epicweb.dev

1–10 of 109 posts

Re: The Epic Stack

#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 ground, while not focusing on something that doesn't matter at the MVP stage.

Maybe Tailwind + Radix makes more sense after you raise funding...?

Re: The Epic Stack

#5
post #2

Subjectively epic, objectively complex.

I was a little surprised by the list of tools and services included after first reading the principles for the stack (limit third-party services and only include the most common use cases)

Re: The Epic Stack

#6
The benefits of naming stacks like LAMP and MEAN/MERN was coupling technologies that intrinsically work well together, where swapping out one would meaningfully change the whole system. LAMP without PHP would be unrecognisable, MEAN without MongoDB would feel completely different to develop for.

There’s almost nothing about the Epic stack from what I can see that wouldn’t feel roughly the same if replaced. Swap Tailwind for a different CSS framework and… it’s basically the same. Use a different validation library and it’s still the same. There are pairings within the list that complement each other relatively well, but none that are make or break in the same way as LAMP/MEAN/etc.

These stacks were useful in understanding values in an acronym, but here that requires a full blog post to lay out principles making it less memorable and, I suspect, less impactful as a result.

Re: The Epic Stack

#8
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.

Re: The Epic Stack

#9
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 to be turned off by ugly/obsolete looking web pages.

Re: The Epic Stack

#10

The benefits of naming stacks like LAMP and MEAN/MERN was coupling technologies that intrinsically work well together, where swapping out one would meaningfully change the whole system. LAMP without PHP would be unrecognisable, MEAN without MongoDB would feel completely different to develop for. There’s almost nothing about the Epic stack from what I can see that wouldn’t feel roughly the same if replaced. Swap Tailw…

The name "Stack" here means a starter template for the Remix framework e.g. Remix Stacks https://remix.run/docs/en/main/pages/stacks
Post reply on HN