Ask HN: What's your go-to stack for prototyping web applications and MVPs?
20 points| JohnnySpaghetti | 9 years ago | reply
My current go-to stack is Rails + Ember.js. I understand it's a bit dated so I'm considering learning something new.
Thus, I'm wondering what you guys use, or what you'd recommend learning.
Thanks!
[+] [-] bharani_m|9 years ago|reply
I have now deployed two applications using Elixir. One is a simple blog and the other is the side-project that I am currently working on called Email This [1]. Overall, I've been very happy with Elixir. The learning curve is not too steep and the docs are very exhaustive.
For my next project, I am planning on trying Go. There were many great resources shared in this post on HN today [2].
[1] https://www.emailthis.me
[2] https://news.ycombinator.com/item?id=13612941
[+] [-] JohnnySpaghetti|9 years ago|reply
Is there anything you missed from Rails when you did your project based on Elixir/Phoenix?
What are you using on the front-end for both projects? Do you currently have a go-to front-end framework/library?
Email This looks great. What are your plans (if any) to monetize it?
[+] [-] gt2|9 years ago|reply
edit: added Phoenix, the framework name
[+] [-] pesfandiar|9 years ago|reply
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.
[+] [-] mod|9 years ago|reply
I'm on the cusp of starting a new project and some configuration problems have left me looking elsewhere. I used to work with Django a lot, and I may go that route, but I also think a full-javascript stack could be good for me professionally.
Alternatively, I'd love to try a clojure backend but frankly I'm a bit afraid of it--I tried maybe 18 months ago and I had a bad go of things. I've read lately that some of the problems I had have been remedied (most importantly better stack traces) and so I might just give that a go.
No matter what backend I choose, I'm going to build out a React/Redux front-end. I'm working with that on the job and I could use a little more time with it to become more comfortable. Also, I really think it's a good paradigm and that it's going to stick.
Anyway, lots of fun choices out there. If your efficiency isn't a top priority, I'd urge you to pick a language that looks fun. For me, Clojure is that option.
[+] [-] _m8fo|9 years ago|reply
[+] [-] JohnnySpaghetti|9 years ago|reply
[+] [-] RUG3Y|9 years ago|reply
[+] [-] sharmi|9 years ago|reply
[+] [-] adnanh|9 years ago|reply
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...
[+] [-] JohnnySpaghetti|9 years ago|reply
Do you have any such MVPs or projects you could share?
[+] [-] dzink|9 years ago|reply
[+] [-] iends|9 years ago|reply
[+] [-] madamelic|9 years ago|reply
Don't do it. It is quick and somewhat easy but just horrible. I need to stop being lazy...
[+] [-] whostolemyhat|9 years ago|reply
[+] [-] unknown|9 years ago|reply
[deleted]
[+] [-] patrickgordon|9 years ago|reply
I use the `create-react-app` which means no build config at the trade off of some nice-to-haves (CSS modules >_<)
[+] [-] sprobertson|9 years ago|reply
[+] [-] billconan|9 years ago|reply
For desktop app I use c++/Qt.
For app I use ios/swift.
[+] [-] JohnnySpaghetti|9 years ago|reply
[+] [-] jfajobi|9 years ago|reply
[+] [-] miguelrochefort|9 years ago|reply