MeteorJS (Node) + React for https://eddtor.com/editor, really quick (1 month from idea to launch), more recently going for Go full stack (server side + template/html package for front-end). After staying on the bleeding edge of Javascript ecosystem for about three years, I missed the simplicity of a reliable server-side language + the battle tested JQuery (I know, right?!) plug-ins.
Ask HN: What's your favorite way of getting a web app up quickly in 2018?
151–160 of 569 posts
Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?
#152Earlier quoted context omitted.
I’d say the slowness of Ruby is really over exaggerated. For most web applications it’s good enough, and the speed of development (how fast you can ship) almost always outweighs any costs from it being slow. You can always replace the endpoints that are slow with something written in a more performant language like Golang or Erlang later. I’ve worked on all sorts of applications from corporate CRUD to mobile billing…
I think the rise of Mastodon is really pouring some hot water on that meme. Lots of really small VPSs are running some fairly big instances. Although I'm only personally using one of them, it's very fast, and the general view is that isn't unusual. I get that it won't hit Twitter scale but that matches the majority of "how do I build a prototype" use cases.
"Twitter scale" wasn't so much a Ruby/Rails problem as it was an RDBMS (write-many + read-many = road to fail) and writing their own in-house message queue problem. Starling performed worse than just about everything else out there (and their Scala replacement Kestrel isn't much better).
One really insipid blog post and thousands of mindless followers later and the damage to Rails has been done.
That's not to say Rails doesn't/didn't have other issues -- it did. It's just telling that Twitter is the first example people reach for instead of anything else.
Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?
#153Full-stack Clojure with Clojurescript front-end is about the fastest workflow I’ve ever used. The front-end part in particular with Reagent (a Clojurescript React library) is a very quick workflow compared to all front-end alternatives. There are perhaps more valid options for server, but even still, having the same language in both browser and server is very convenient both for reduction in cognitive dissonance and…
Does Clojurescript support stuff like hot code reloading? And does Clojure have any good framework for an actor system implementation?
Because I've been interesting to get an excuse and try Clojure out and what you're saying is really interesting.
Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?
#154Web2py (Python framework) includes an Ubuntu (and other) setup scripts plus a Fabric fab file for one command deploys that works pretty well. Web2py comes with a bootstrap welcome app that gives you user mgmt, authentication, admin and DB access with about a click.
Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?
#155React, Express, Postgress, Nginx all in Docker containers managed with Docker Machine on a Digital Ocean box. It may not be the most simple/quick solution, but with some copy/pasting I can get something up rather quick and it's super flexible. Need OCR? Add a Tesseract container. Need a fileserver? Etc.
Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?
#156I like flask and I also like to use boilerplate or skeleton projects. These are projects that have a fair amount of infrastructure set up (testing, views, user accounts, even admin stuff). There are a lot of them set up on github with varying degrees of added features. I’ve begun to maintain my own for the sake of saving time.
The only challenge is setting up the appropriate infrastructure for deployment. Fabric works well for that.
Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?
#157The fastest way to get a web app running, for free is Rails + github + Heroku, imo. It's very fast to scaffold a new app, with diverse options you'd want (react/vue/other stuff). Host it on github, create a heroku app and push it.
What do you mean host it on github in the context of using Heroku, which would be your host? How is github involved?
I think the parent meant publish the repo on GitHub as you are unlikely to accidently nuke the code like you would if you were experimenting on Heroku.
Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?
#158Earlier quoted context omitted.
It blows my mind that there still isn't a polished ORM for the node.js / Express ecosystem.
> ORM for the node.js / Express ecosystem Coming from Python world, it's probably for the best that nobody is using ORMs.
Can you expand on your logic here? Is this because Python ORMs have gotten too bloated?
Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?
#159I'm surprised nobody is talking about Express for the back end. Maybe it's because I hail from the front end world, but I'm already so comfortable in javascript I'm faster in it than if I had to learn anything else. For the front end, I like Vue because it's just react with less boilerplate.
It blows my mind that there still isn't a polished ORM for the node.js / Express ecosystem.
Have a look at http://loopback.io
Express with scaffolding and connectors to memory, MongoDb, MySql, MsSql and other.
Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?
#160Earlier quoted context omitted.
I think the rise of Mastodon is really pouring some hot water on that meme. Lots of really small VPSs are running some fairly big instances. Although I'm only personally using one of them, it's very fast, and the general view is that isn't unusual. I get that it won't hit Twitter scale but that matches the majority of "how do I build a prototype" use cases.
"Twitter scale" wasn't so much a Ruby/Rails problem as it was an RDBMS (write-many + read-many = road to fail) and writing their own in-house message queue problem. Starling performed worse than just about everything else out there (and their Scala replacement Kestrel isn't much better). One really insipid blog post and thousands of mindless followers later and the damage to Rails has been done. That's not to say Rai…
Agreed. I've been working mostly in Ruby since 2006, over hundreds or thousands of apps, depending on how you count, and I have only worked on 2 apps that actually had scaling problems with Ruby. The rest were 100% improperly designed or scaled databases.
Twitter is certainly of a scale that I would not be using Ruby on the primary load points. But even billion dollar companies don't often reach that scale.