191–200 of 569 posts
1) Spring Boot on Google App Engine free tier 2) Managed Postgres on GCP/AWS 3) Frontend framework of the day, like React or Vue. 4) Take 1-2 hours in the beginning to set up ci/cd (like Circle) to make things 10x more convenient.
Can you expand more on what you do here?
Django, Docker and AWS ECS and ELB. Absolutely worth the effort to learn how to build a Docker image and put together bash scripts to push the image and update an ECS service. We have a base project which includes nginx and uwsgi set up to simply serve the Django app and static files on port 80. Having an ECS Docker cluster with spare capacity greatly assists getting new projects up and running quickly, especially if…
Earlier quoted context omitted.
I find Ruby’s stdlib a pleasure to use.
How many web apps can you name that don’t rely on any external gems? Packaging that mess is a pain in every scripting language.
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.
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…
Ok. But that does not mean that you have to use the worst thing that is out there. Why not Python?
Build a client, write your routes and your good to go. Also scales really well.
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…
There are some great choices for the server side too. Plus libraries for pretty much every DB. When something is missing, there's definitely a fallback option in Java.
Plus you get hot-reloading on both sides (e.g. boot-reload and ring-reload). And the ability to bundle everything into one neat jar file so the only dependency for deployment is Java.
Here's a getting started project that I found helpful: https://github.com/oakes/full-stack-boot-example
Earlier quoted context omitted.
It's best to pick a project and try to build it, rather than learn things from the outside. In isolation, Ruby can be annoying to learn because it's syntactic sugar seems unnecessary. In context of an app, though, it's great. The sugar makes sense. Rails has a bit of a learning curve, but that learning curve is well rationalized. To borrow a Steve Jobs-ism: you're starting on the 10th floor, when everyone else is sta…
What are the best resources to learn Ruby/Rails these days?
Earlier quoted context omitted.
Ok. But that does not mean that you have to use the worst thing that is out there. Why not Python?
it's worse to you, not the client. client actuality doesn't care and PHP is legacy I guess?