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

471–480 of 569 posts

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

#471

Post by friedman23 »

alter_eco123 wrote: post #371
friedman23 wrote: post #284

Earlier quoted context omitted.

Haha, your comment reeks of inexperience. The thing you have namely not experienced is the pain of having to port an entire service to a different language because SQLAlchemy is as slow as a snail. But yes, keep on using your ORMs because using a query builder is too hard. I'm sure your significant experience building services that will at most ever handle 2 QPS is very important to the software engineering world.

For what it's worth, if SQLAlchemy (or any other ORM) is slow, it's probably not because of "serialization" and "deserialization" (of whatever you had in mind), but because the database is queried in a (really, really) inefficient way. It's also unclear how that's related to whether you're working in an async environment or not. He was probably thinking about stuff like that.

One of the biggest bottlenecks for us was creating these massive nested Python objects.

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

#473

Post by lol768 »

Mikushi wrote: post #438
sethammons wrote: post #406

Earlier quoted context omitted.

If it is open to the public, your train wreck cannot be open to common vulnerabilities like sql injection. Full stop. You can avoid unit or integration tests, not complete features, or cut any corner you want aside from basic security.

Don't presume anyone writing PHP is a trainwreck. With PHP7+ you can write modern applications that are perfectly secure, as much as anything you'd write with any other scripting language.

> Don't presume anyone writing PHP is a trainwreck.

I'm unsure anyone here is disputing this - my original comment said as much:

> Can you write secure code in PHP? Absolutely. But it's more effort and easier to get wrong.

It's undeniably more work to get right, though. As an example, if I create a new django app "the CSRF middleware is activated by default in the MIDDLEWARE setting" - you're safe by default.

I mean, even as a basic DiD measure PHP could use SameSite cookies by default for its sessions - but does it?

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

#474

Post by qqqwww »

bo1024 wrote: post #57

I have trouble understanding where all this demand for webapps come from. As a browser of the web, the only webapps I use are Google's email, maps, and docs. What are all these webapps for and why doesn't HTML (maybe with a touch of javascript) suffice?

I think you are underestimating what is a web app. Think about any website that requires a password - that is a web app because presumably it will do some personalization. Any content serving site is at least backed by a content management system which is a web app.

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

#475

Post by [deleted] »

cutler wrote: post #467
TezlaOil wrote: post #462

Earlier quoted context omitted.

8.90 EUR per month is about $130 a year, so still an order of magnitude more expensive than cheap PHP hosting.

I was just going for a figure similar to the $10/month cited. You can get a 2GB RAM VPS at Hetzner for as little as 2.50 Euros per month.

[deleted]

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

#476

Post by TezlaOil »

cutler wrote: post #467
TezlaOil wrote: post #462

Earlier quoted context omitted.

8.90 EUR per month is about $130 a year, so still an order of magnitude more expensive than cheap PHP hosting.

I was just going for a figure similar to the $10/month cited. You can get a 2GB RAM VPS at Hetzner for as little as 2.50 Euros per month.

The cited price was $10/year, not $10/month. That's a huge difference.

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

#477

Post by callekabo »

swyx wrote: post #452
callekabo wrote: post #318

Not having a server at all is the easiest. I run my front ends on S3 / CloudFront. Backend is run on Lambdas, with state stored in DynamoDB/SimpleDB (can't wait for serverless Aurora though!). create-react-app and aws-amplify gets you really far in a hurry. I then normally use react-redux, @redux-offline/redux-offline, react-router-dom, and flow-bin. Examples: - https://gitlab.com/kabo/synchronize-swatches - https://…

as a frontend dev new to this stuff - how do you keep your lambdas secure? literally anyone can see your secrets? I'm gonna go through your code, thanks for sharing, just wanted to ask in case you have a big picture insight about how serverless auth/security is best done. this stuff freaks me out because i know nothing about it.

I'm afraid I don't follow. What secrets are you referring to? Secrets in the code running on the lambda can't be seen by anyone. If you mean secrets to invoke the lambda I usually have lambdas be completely open (no auth required) or have users log in with cognito and use aws-sdk invoke the lambda, which takes care of auth for me.

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

#478

Post by spicyusername »

marcus_holmes wrote: post #13

I write the server-side in Go, cross-compile to a Linux binary, and set that up as a service on a vanilla Ubuntu box (usually Digital Ocean). Deploying a new version is a matter of sftp'ing the new binary (and any templates, images, etc) over the top of the old one and restarting the service. If I need a database then I use Postgres, and the setup for that can be a pain, so I get it documented/scripted using Ansible.…

%s/react/vuejs/

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

#479

Post by throw2016 »

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…

Let's be frank. This is a place for marketing the newest thing where skepticism and scrutiny is not welcome and likely to be dismissed as 'grey beards' and 'people scared of change'.

So there is never any scrutiny, no experienced person is going to expose themselves to ridicule so all the problems are discovered years later only for a new one to take its place.

Ruby for instance has huge deployment problems, why the hell do you need a build environment on deployment and expose end users to installing hundreds of gems that may need to be compiled and can fail anytime? Same with the wild lands of NPM. It's as if people have endless time to go down all the rabbit holes.

On the other hand Facebook, Wikipedia, Wordpress, Slack and some of the most scalable sites online today use PHP. Yet according to the the hivemind PHP is somehow a disaster, and the next over-engineered complexity is the panacea. This is just not credible.

Unless there can be a way to apply scrutiny during the hype phase the cycle of over-engineering, needless complexity and offloading bad engineering on end users is going to continue.

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

#480

Post by ramy_d »

buvanshak wrote: post #252
ramy_d wrote: post #195

Earlier quoted context omitted.

it's worse to you, not the client. client actuality doesn't care and PHP is legacy I guess?

If the client does not not care, why suffer by using something that is worse for you? I mean, you might as well use something that you like. I don't get the logic here. Another thing is that, if it it worse for you, it is automatically worse for the client. I am not sure why it is so hard to see. if your tool is bad, then your work ll suffer, and thus the client. So it is worse for them also..

liking php is unfathomable
Post reply on HN