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

Ask HN: What's your favorite way of getting a web app up quickly in 2018?

news.ycombinator.com

Post reply on HN
Print view View original

561–569 of 569 posts

Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?

#561

Post by regulation_d »

trcollinson wrote: post #545
regulation_d wrote: post #538

Earlier quoted context omitted.

For my load balancer heartbeat checks, I'm returning responses in 200µs.

That’s a highly unrealistic real world scenario. I’d like to see a page under load with actual queries. Heartbeat checks are far from actual real world examples of much of anything.

I guess my point was: that’s the baseline. It’s an order of magnitude faster the 20ms your saying is unlikely. That leaves a lot of headroom for hitting the db and things done. The api I’m working on isn’t currently being hit super hard, but for most of my endpoints 25ms is pretty average.

Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?

#564

Post by alfredallan1 »

Larrikin wrote: post #469
alfredallan1 wrote: post #399

Earlier quoted context omitted.

I’m curious: once one has written a CRUD app, why can’t they use that as the boilerplate for other CRUDs they need to write? Replace the bits specific to each individual app. If the program is designed in a sufficiently modular fashion, shouldn’t this be doable?

That assumes you're allowed to use the code you wrote in a previous project in your new project.

Eh, are you perhaps hinting at that horrible lawsuit where Oracle sued Google(?) for a lot of money for copying about 9(?) lines of code that was basically a looping routine?

That notwithstanding, I was asking about code that could be considered “boilerplate”, not things that could be considered proprietary business logic. So the code to do a login, or check for cookies, or get something from a db, or anything of that sort should be broadly reusable (for a general CRUD app).

Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?

#565

Post by meain »

The simplest way that I find to get an webapp running is by using [parcel](https://github.com/parcel-bundler/parcel) for bundling the frontend and using a python [flask](http://flask.pocoo.org/) server for backend. I don't think it could get any simpler than this. Now if I have a database, I usually go with mongodb along with pymongo.

Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?

#566

Post by vorg »

antoaravinth wrote: post #173
nooyurrsdey wrote: post #63

For some reason people seem to constant doubt Ruby-ists and Rails Devs. I completely get that other languages have huge benefits over Ruby. Golang being compiled or Java running anywhere, etc... And ruby is slow, totally understood. But if youre talking about getting a functioning webapp up and running quickly ... no way anyone is beating a Rails dev in setting one up. The piping and scaffolding are all built in and…

On a side note, if someone asks me to prototype anything on Java world, will pick Grails. Getting a webpage up and running in Grails is so easy.

Which version of Grails was that? If you mean version 3, why is virtually no-one starting new projects in it, or upgraded from v.2 ? Grails 3 looks like nothing more than a wrapper around Spring Boot, so why not just use that? If you're talking about version 2, why has its plugin ecosystem died?

Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?

#567

Post by catchmeifyoucan »

iopuy wrote: post #214
catchmeifyoucan wrote: post #196

Angular, host on S3 and serverless backend with AWS Lambda. Build a client, write your routes and your good to go. Also scales really well.

how do you handle authentication?

You can do signed cookies, validate in your lambda function the credentials, and then return a signed cookie. A little dirty, but quick and enough to lock-down

Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?

#568

Post by tiangolo »

I created a project generator to solve that for my use cases: https://github.com/tiangolo/full-stack

It allows me (and the teams I work with) to go from clean Linux to web app 5 - 10 min while keeping best practices and allowing the system to scale.

It's all based on Docker and Docker in Swarm mode clusters (setup included in docs) Backend with Python Flask Interactive docs with Swagger/OpenAPI HTTPS automatic handling with Let's encrypt handled by Traefik Asynchronous tasks with Celery Front end with a modern SPA (Angular, React, Vue) Relational DB with Postgres, although I'm also using a modified version with CouchDB (I'll create a project generator with that later) CI/CD intergraded And more stuff...

Re: Ask HN: What's your favorite way of getting a web app up quickly in 2018?

#569

Post by kristopolous »

lol768 wrote: post #300
kristopolous wrote: post #168

Vanilla php + html5up + sqlite3. Everyone else here is trying to be stylish and fancy. Your customers don't care what language it's in or whether the code is beautiful. No cutting edge incomplete frameworks, convoluted tooling, piles of inaccurate documentation to read, inexplicable cryptic error messages with a bunch of incorrect solutions on stack overflow, or other incompetently over engineered bullshit. Just go a…

>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…

Most of the higher level code like that is written by incompetent people who make amateur hour mistakes and only release overengineered under documented slow broken code that is never supported and gets deprecated in a week.

I'm constantly shocked and amazed at the beginner mistakes riddled throughout these hip cool kid frameworks. And the dependencies of that code, and their dependencies, and the build system, and the management of the build system. It's a 5,000 hour a week job fixing all that and someone else will just go in and break it again.

So no, don't tell me to stop my life and fix everyone's mistakes. This is why there's 10 person teams to build an ecommerce site these days. This used to be a weekend project before all these slick stylish tools took up everyone's time.

Most people are incompetent and the more complexity you have, the greater your chances of getting crap code tearing your system apart

Why would I use something as a core piece of infrastructure written by people I'd never even consider hiring in a million years?

All too often you're standing on the shoulders of people tripping over their own shoelaces.

No thank you.

Post reply on HN