161–170 of 569 posts
deployed on aws or lightsail
Earlier quoted context omitted.
> 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?
I'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.
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…
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.
https://github.com/bhauman/lein-figwheel
has that out of the box. As for an actor model implementation, there is pulsar:
http://docs.paralleluniverse.co/pulsar/
Which has erlang-like actors, though some might suggest that core.async and its channel implementation provides everything you might need an actor for, YMMV.
I'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.
- JS-Data - https://github.com/js-data/js-data
SQL:
- Sequelize - https://github.com/sequelize/sequelize
- Bookshelf - https://github.com/bookshelf/bookshelf
- Objection - https://github.com/Vincit/objection.js
- TypeORM - https://github.com/typeorm/typeorm
NoSQL:
- Mongoose - https://github.com/Automattic/mongoose
- Thinky - https://github.com/neumino/thinky
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 as vanilla, basic, and standard as possible.
True speed comes when you don't have to deal with other people's bugs and poorly designed mistakes.
Don't rely on code written by flocks of people you'd never hire in a million years.
Earlier quoted context omitted.
I second this; Go + React.js (Vue.js in my case) I talked about it just a couple of hours ago [1]. [1] https://news.ycombinator.com/item?id=17215658
How do you handle server side rendering? This is one of the reasons I chose to go full Node+React.
The run part became easy the last few years: Dockerize all the things, run them on AWS ECS with Fargate (and add whatever else you might need, e.g. ELB, S3, SQS, ...), no servers to setup or maintain.
The built part, that actually became harder... You need to figure out the best tools for whatever problem you're trying to solve, and the list of tools keeps growing. I default to very conservative standards, because I'm familiar and productive with them: Java (Spring Boot), Vue.js and PostGRES, with sometimes a bit of Node or Python and some ElasticSearch or DynamoDB thrown in the mix.