Earlier quoted context omitted.
Even there, aren’t Facebook and Etsy using it, at least?
And WordPress, Yahoo, Salesforce, Adobe, eBay and on and on. You'll have a hard time finding any tech company that doesn't use it to some extent.
Ask HN: What's your favorite way of getting a web app up quickly in 2018?
441–450 of 569 posts
Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?
#442Earlier quoted context omitted.
How far do you make it writing a web app in rust or go without pulling in external packages, then? Or a front-end using only javascript and html?
In Rust, it’s pretty quick. You could write a server yourself, but it would take a lot of work. It’s trivial with a package though.
Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?
#443Earlier quoted context omitted.
You seem to know a lot about what everyone else's motives are :) There's nothing less "vanilla" or "standard" with python/go/RoR/whatever vs. PHP. It just so happens that you know PHP well, so, by all means, YOU should use that.
One can put together a set of (Fast)CGI scripts in almost any language, given environment variables and some IPC is supported (IDK what IPC FastCGI uses exactly, bug CGI is envvars). Same goes with exposing a custom socket server. I guess people associate languages with frameworks and that's why they think these things are not possible in them. Or they like the style intermingling of 4 programming languages, which is…
Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?
#444The easiest thing to do is Heroku. They've really nailed it down and the +$2/month for their basic instance is easily worth it if you don't want to spend the time getting everything setup. Automation requires infrastructure and infrastructure is cheap only if you know how to set it up. I run ~3 side projects using Heroku to host a Django project with a GraphQL API talking to Heroku Postgres and Netlify the host the R…
Sorry What did you mean by $+2? I see $7 for their hobby instance..?
Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?
#445I think Dokku solves a bunch of your pain points: https://github.com/dokku/dokku
If you're into that, or have CPU/RAM requirements that would be prohibitively expensive on Heroku then give it a try (I run it for a couple things on a cheap but powerful dedicated machine). If you're just doing something simple it's probably not worth it, just get a hobby dyno and go that route.
Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?
#446Earlier quoted context omitted.
>No cutting edge incomplete frameworks So what, you rewrite a templating engine every time you want to make an application that outputs user data? Or are you reliant on making damn sure you always call htmlentities every time you echo something to prevent XSS? Are you sure you've not slipped up anywhere? What about CSRF? Do you write your own filtering mechanism every time you make a web app to check for the existenc…
The other side of the coin is whether you do a full security audit of every framework and dependency graph before you use it? When you write your own code you know there is nothing hidden.
Frameworks are much better at handling most security needs.
Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?
#447Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?
#448Full-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…
I'm curious to hear more about this. I'm someone who's used Elm at work, and on the side is interested in Lisp.
Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?
#449Rust + Diesel + Tokio.io + Postgres. I don't do web frontend (just apps and bots), and this stack took a LOT of time to get used to, but now I enjoy full static typing, perfect ORM-ish abstraction level (Diesel is kind of unique in that regard), built-in integration testing so it's compatible with SQL migrations and functions in Postgres and pretty good perfomance.