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

Ask HN: What's your go-to stack for prototyping web applications and MVPs?

news.ycombinator.com

Post reply on HN
Print view View original

11–20 of 30 posts

Re: Ask HN: What's your go-to stack for prototyping web applications and MVPs?

#12

Post by billconan »

JohnnySpaghetti wrote: post #11
billconan wrote: post #10

For web, I wrote my own http server with c++. For desktop app I use c++/Qt. For app I use ios/swift.

Do you use any front-end libraries for your web projects?

I don't use front-end lib that much.

I usually purchase a template from themeforest. I care more about the design, whatever the theme I purchase use, I just modify it from there.

Re: Ask HN: What's your go-to stack for prototyping web applications and MVPs?

#14

Post by adnanh »

I love Ruby and for the quick web MVPs I use sinatra + sequel.

I try to avoid JavaScript if possible... Setting up the JavaScript build/transpile system, installing dependencies, fighting the dependency version hell drains all the hype and productivity from my soul...

Re: Ask HN: What's your go-to stack for prototyping web applications and MVPs?

#15

Post by JohnnySpaghetti »

billconan wrote: post #12
JohnnySpaghetti wrote: post #11

Earlier quoted context omitted.

Do you use any front-end libraries for your web projects?

I don't use front-end lib that much. I usually purchase a template from themeforest. I care more about the design, whatever the theme I purchase use, I just modify it from there.

Thanks for your answer.

I'm curious about what kind of projects you do with a C++ web server. Could you talk a bit about them?

Re: Ask HN: What's your go-to stack for prototyping web applications and MVPs?

#16

Post by JohnnySpaghetti »

adnanh wrote: post #14

I love Ruby and for the quick web MVPs I use sinatra + sequel. I try to avoid JavaScript if possible... Setting up the JavaScript build/transpile system, installing dependencies, fighting the dependency version hell drains all the hype and productivity from my soul...

I agree that dealing with the front-end can be a drain sometimes, but unfortunately it's necessary for many types of MVPs that require a rich UI.

Do you have any such MVPs or projects you could share?

Re: Ask HN: What's your go-to stack for prototyping web applications and MVPs?

#17

Post by dzink »

Go(Lang) backend + plain html, jquery and gulp on the frontend. After doing Rails for a while, I was tired of the slowness and layers upon layers of abstraction. Go is simple in comparison - the language philosophy helps you keep everything close to where it's executing. No assumptions. I've borrowed some lessons from Rails in structuring my code (models are separate, api for controller logic, views are static pages that interact with the Api through JSON). The performance of my sites is so incredibly delightfully fast now, that I would never go back. Almost all of my server calls return back in microseconds. I'm rewriting all of my sites in Go now.

Re: Ask HN: What's your go-to stack for prototyping web applications and MVPs?

#18

Post by pesfandiar »

Backend: Node.js+Exress. Although I'm recently looking into serverless options (e.g. using AWS Lambda, etc.)

Frontend: Bootstrap for looks and CSS sanity. Knockout for data binding; it's a mature framework that works fine for small- to medium-sized web apps. If I'm to learn something new, I'd go for Vue.js, whose concepts look very much like Knockout and it benefits from virtual DOM rendering.

Re: Ask HN: What's your go-to stack for prototyping web applications and MVPs?

#19

Post by sharmi »

I use django. For starters, I use bootstrap and jquery for frontend but once the project matures and is here to stay, I shift to plain CSS. I also use plain javascript (for now the total LOC is <900) but may shift to some other lib when complexity increases.

Re: Ask HN: What's your go-to stack for prototyping web applications and MVPs?

#20

Post by iends »

dzink wrote: post #17

Go(Lang) backend + plain html, jquery and gulp on the frontend. After doing Rails for a while, I was tired of the slowness and layers upon layers of abstraction. Go is simple in comparison - the language philosophy helps you keep everything close to where it's executing. No assumptions. I've borrowed some lessons from Rails in structuring my code (models are separate, api for controller logic, views are static pages…

Working with a database in Go has been painful for me. Have you found this is the case in your projects?
Post reply on HN