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

Ask HN: What web stack would you use for startup, and why?

news.ycombinator.com

Post reply on HN
Print view View original

41–45 of 45 posts

Re: Ask HN: What web stack would you use for startup, and why?

#41

Post by jmarchello »

john_the_writer wrote: post #6

Rails (front and back) Turbo handles live updates For authentication, I'd use the devise gem, and plan for OAuth later. I'd use Pundit for authorisation. I'd use sendgrid for email and stripe for payment. I'd host on FlyIO; though I'd consider Heroku as 50$ a month would likely cover most needs, and it's super simple. All up blog would take about an hour. Then it's about style, and for that I'd go with w3schools css.…

Came here to say this. Rails is by far the best option for a startup. For starters you can focus on business-level design rather than building a bunch of plumbing.

Also, the framework lends itself to small teams extremely well. A single developer on Rails can outperform entire teams on other technologies.

Re: Ask HN: What web stack would you use for startup, and why?

#42

Post by whodev »

capl wrote: post #40
whodev wrote: post #39

I've started using what I've dubbed the HAG (HTMX, AlpineJS, Go) stack for my "startup". It's really simple and easy to get into. I do try to minimize the use of third party packages/modules to reduce my attack surface. For the rest of your questions, - Auth: Auth0. Simple to get started, and depending on your plan you can enable SSO for business clients. - Frontend: Plain ol' HTML, CSS, and minimal JS. This is where…

Cool! I haven't heard of Turso until now but it looks great. Why choose it over Planetscale, though? I've been looking at HTMX + Go for some time but I just don't know if it's worth it over React which I already know. Is it really more productive, or is it simply a ideology/hype thing? I'm also a Go fan because it values simplicity, which I think we should all strive for, so the HTMX + Go combo appeals to me, even th…

To be honest, while I have heard of Planetscale I never really looked into it. It does seem really interesting, but as you can probably gather from my answer I'm really into simplicity and ease of use. And since Turso is powered by LibSQL (SQLite fork) it is dead simple to use. Their pricing is also very predictable which and with a generous free tier.

HTMX + Go is such a great combo for those who don't necessarily enjoy JS/TS. I just want a good user experience and also a good dev experience. And for me, HTMX + Go is that. I can create reactive websites while working in my preferred language. I'm also shipping minimal amount of data to the user so and using as little CPU and memory as I can.

Re: Ask HN: What web stack would you use for startup, and why?

#43

Post by capl »

whodev wrote: post #42
capl wrote: post #40

Earlier quoted context omitted.

Cool! I haven't heard of Turso until now but it looks great. Why choose it over Planetscale, though? I've been looking at HTMX + Go for some time but I just don't know if it's worth it over React which I already know. Is it really more productive, or is it simply a ideology/hype thing? I'm also a Go fan because it values simplicity, which I think we should all strive for, so the HTMX + Go combo appeals to me, even th…

To be honest, while I have heard of Planetscale I never really looked into it. It does seem really interesting, but as you can probably gather from my answer I'm really into simplicity and ease of use. And since Turso is powered by LibSQL (SQLite fork) it is dead simple to use. Their pricing is also very predictable which and with a generous free tier. HTMX + Go is such a great combo for those who don't necessarily e…

Fair enough! I'll try out Go + HTMX this weekend if I get the time

Re: Ask HN: What web stack would you use for startup, and why?

#44

Post by capl »

onetoo wrote: post #10
capl wrote: post #7

Earlier quoted context omitted.

Yeah I've been looking at Blazor for some time, and the .NET 8 updates are great, but I just don't know if I like the .razor DSL and the fact that things are either SignalR (latency) or .NET runtime in the shape of WASM (huge bundle, literally the kitchen sink). The biggest upsides to Blazor is that, as you said, greatly simplify development as you basically have only one code base to think about with Blazor Server,…

Blazor Server isn't inherently latency riddled. Blazor Wasm isn't necessarily slow to initial load with .NET 8. IIRC the compiler is also really good at trimming the Wasm bundle when publishing in Release mode. The neat thing about the new stuff in .NET 8 is that you can choose the interactivity at the component level, so if some component really sucks when used with Server interactivity, you can take the extra time…

Hey again. Tested .NET 8 and blazor again, and it wins… I mean it wins by so much that I now default to using .NET and C# for any task web related. Having components be SSR’d by default and then using SignalR later on by interactivity demand fixed by biggest criticism which was initial load overhead.

Also I’ve experimented with azure since it’s of course very well integrated with the .NET environment, and I think I’ll use that too instead of digital ocean which I’ve defaulted to before. I thought azure was too expensive, but re-evaluating now, it is actually very generous by giving free tiers which lets you launch without paying a dime.

Re: Ask HN: What web stack would you use for startup, and why?

#45

Post by askarhussain »

ttymck wrote: post #35
onetoo wrote: post #4

Full .NET stack. - Self-hosted identity management, "ASP.NET Core Identity", using new scaffolding from .NET 8 - Blazor, using the "Auto" mode from .NET 8: Default to SSR, autopromote to Server mode for live updating components - EF Core for DB handling The idea is to focus on keeping things simple and easy for the developer. The most annoying part about the stack is the way Microsoft names things. Keeping the render…

I just want to note how much time would be lost to confusion on my team, if we had to differentiate between "Server Side Rendering" and "Server mode"... .NET is such a cluster of poor naming choices

I ended up moving things to the standalone WASM app just for this same reason. This confusion gets worst if you have different layouts for different aspects of your app, and who knows where things should be placed appropriately. All of a sudden some of the components won't become responsive at all...only to realize that it's pre-rendered.

In some cases, even the SSR gets you a quick time to first bite, clicking on a link that takes you to a WASM-rendered page freezes things for a bit while WASM and other files were getting downloaded.

The experience turned into a bit of a mess and I ended up moving things back to WASM and so far a smooth ride since then. There's potential with the Blazor Web App approach, only if Microsoft put some heads into revamping that experience a bit better.

Post reply on HN