Live data from Hacker News

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

news.ycombinator.com

511–520 of 569 posts

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

#511

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…

[deleted]

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

#514
post #123

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

> As an example I once ported an Elm project to Clojurescript and it was a 4x reduction in lines. 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.

I think it is much easier to get real-world nontrivial work done in Clojurescript compared to Elm.

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

#515
post #186

Earlier quoted context omitted.

How is this setting things up "quickly" when OP is asking to limit complexity? You're suggesting: 1. Server side in Go 2. Cross-compiling it 3. sftp'ing and restarting the service everytime 4. postgres 5. ansible 6. Makefiles 7. Webpack 8. Babel 9. React

Writing web servers in Go is extremely easy. https://golang.org/doc/articles/wiki/ Cross-compiling with Go is done by setting two environment variables. That's it. This is not like the mess of C++ cross-compiling. In LiteIDE it is simply a matter of choosing Linux from a drop-down: https://www.wut.de/pics/screenshot/e-505ww-07-pide-000.png SFTP is not exactly hard. Nor is `nohup ./server &`. From 5 on I agree though…

yeah, I use straight HTML wherever possible. But for some things it isn't possible, or suitable. I'd love a simpler client-side environment. Any suggestions welcome... I'm looking at Vue.js now, recommended from comments here.

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

#516
post #390

Earlier quoted context omitted.

PHP isn't dead, and it will never be dead, but as a long time and continuing professional Perl developer myself, let me tell you that you're better off just accepting that your language of choice isn't in vogue anymore. It's not all bad once you're on the ass-end of history. I'm sure you can easily identify a few negatives being the language de jour bring (such as lots of shitty programmers joining the community all…

Perl 5 is pulling me like a superstrong magnet. I haven't had time to read the basics and things like choosing the correct sigil + accessor trim me up, but still, it has many niceties. To begin with, you can have a statement "use v5.x;" and be done with which interpreter problem: it can tell you it needs sth. different, and does not fail because you have python3 to be 3.x, but the script needs 3.x+y, or you have the…

Well said!

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

#517
post #290

Earlier quoted context omitted.

Isn't NodeJS the Javascript of backend?

+1 for NodeJS, seriously no offence to PHP folks, but Nodejs or Python is not much different from PHP in terms of developer productivity.

The reference implementation of PHP, Zend, is objectively not good (blocking I/O) and encourages server side templating, which is basically something you can perfectly do in the client and serve on a CDN at much lower cost (orders of magnitude lower, for processing, memory and transfer).

That being said, doing server side templating in node.js is even worse since it usually wrecks the entire event loop with long lived CPU-bound operations flushing your server performance doing the toilet.

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

#518

Earlier quoted context omitted.

Writing web servers in Go is extremely easy. https://golang.org/doc/articles/wiki/ Cross-compiling with Go is done by setting two environment variables. That's it. This is not like the mess of C++ cross-compiling. In LiteIDE it is simply a matter of choosing Linux from a drop-down: https://www.wut.de/pics/screenshot/e-505ww-07-pide-000.png SFTP is not exactly hard. Nor is `nohup ./server &`. From 5 on I agree though…

yeah, I use straight HTML wherever possible. But for some things it isn't possible, or suitable. I'd love a simpler client-side environment. Any suggestions welcome... I'm looking at Vue.js now, recommended from comments here.

I've enjoyed using Elm for client side development.

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

#520
post #486
post #442

Earlier quoted context omitted.

Steve, what is Rust's equivalent to Go's cross-compilation-- plain old cargo build?

$ cargo build --target=TARGET a list of default targets-- $ rustc --print target-list aarch64-linux-android aarch64-unknown-cloudabi aarch64-unknown-freebsd aarch64-unknown-fuchsia aarch64-unknown-linux-gnu aarch64-unknown-linux-musl arm-linux-androideabi arm-unknown-linux-gnueabi arm-unknown-linux-gnueabihf arm-unknown-linux-musleabi arm-unknown-linux-musleabihf armv4t-unknown-linux-gnueabi armv5te-unknown-linux-gnu…

Thank you
Post reply on HN