121–130 of 187 posts
So that might be Phoenix/Elixir one day, F# the next, and Go or Kotlin another. For front-end I typically use Vue, often in the same repo as the backend with 'git push' deployments.
Rails. Nothing really beats it for the combination of * Getting something up and running quickly. Something that does what you want. * Iterating quickly on the thing you're building. Need a library (gem)? There's very likely a pretty good one. * Building the thing in a fairly clean way (tests, code organization) in a way that's not too bureaucratic and tedious. * Friendly community of people. I've done some playing a…
I’m at least a bit amused that you have a whole comment about how nice rails is without mentioning ruby ;-)
In my opinion, it's Clojure(script). I simply just don't have as much fun with other languages anymore. Clojure let me write some of the most elegant code I have ever written, and knowing certain nooks and crannies of Clojure lets me pull off some...interesting stuff.
Could you say more about what/how you're using them? Like, frameworks, libs, practices (testing), editor, repls, etc.
The stack for my project is:
Backend:
Redis (no relational DB needed for my use case)
Clojure:
Carmine - (redis interop)
Reitit - Nice API definition and routing
Malli - Nice schema validation and coercion
Timbre - Logging without known RCE vulnerability ;)
Frontend:
Clojurescript
Figwheel - CLJS compiling and hot-reloading in browser. Would probably use ShadowCLJS these days though.
Rum - It's a simple wrapper around react, with Hiccup-style list syntax for HTML. Though in a do-over I'd probably try Reagent since it seems to have a bigger ecosystem of wrapped react libraries, but I really like Rum best. That said, it's also not that hard to use native JS React components with Rum.
All of the libraries and idioms in this stack guide the design to push side effects out to the edges of the program - this makes testing easier in a lot of cases. E.g., for a web request you can craft a test request, or pretty-print a literal request object and paste it into your code, then pass it to your API in Reitit without an http-server attached, and get back the result object, and assert that it matches the desired output. Clojure's mutability make it pretty simple to stub or mock calls to storage, or to create a fixture to use a test database.
Earlier quoted context omitted.
+1 phoenix/elixir is such a joy to use. A big emphasis on developer happiness, extremely powerful (with a broader set of strengths than Rails imo), and the actor model is much easier for me to reason/think about because it cleanly separates logic and is designed to fail and recover cleanly.
> broader set of strengths than Rails imo What are those, in your experience? The BEAM platform is certainly better for concurrent work where you might be holding open something like a web socket. But other stuff...? I'm a pretty happy Erlang programmer and feel like I 'get' the functional programming aspect of things, but to me ActiveRecord just feels like such a great fit for DB work in that it makes the simple thi…
As others have mentioned, this is highly personal. My own favorite stack is Elixir and/or full-stack Clojure.
Can you give some details about what you use with Clojure? I was looking at Fulcro.
Previously I've used compojure and all that.
I've only done the data/backend stuff, so I've personally never seriously used cljs, and my companies would use a regular reactjs frontend.
But Clojure is definitely a joy and if I had to make a frontend I'd probably reach for something like reagent.
Go. Lower your pitchforks and hear me out: 1. Sensible defaults, can go very with just the stdlib: no choice paralysis between frameworks, mental overhead of setting up a project or ecosystem fragments to pick from. Just start with a main.go with net/http, add things along as you need them. 2. No ecosystem churn, whatever you write now will be idiomatic Go and build without issues for years to come. 3. Enough of a ty…
Take Rails 7 with Turbo. Start with the Jumpstart Pro template. You’ll feel like a god. https://jumpstartrails.com/ Finally, all of the boilerplate and over-engineered components are gone. You’re finally free to solve the just business problems. And you’ll be fighting integration issues a whole lot less. I have no idea why any saas based startup, whether it’s one person or VC backed, would start with anything less. T…
From: https://jumpstartrails.com/pricing > Pricing Plans > Simple, straightforward pricing to get your online business up and running > Rails Single Site - Build one application with Jumpstart Pro - $249 /year > Rails Unlimited - Build unlimited apps with Jumpstart Pro - $749 /year Might be useful to be aware of the commercial nature of the project, not that it's a bad thing in of itself, just not accessible to every…
You will only get in life what you ask for.
They may say no, but you owe it to yourself to try.
pleasure == productivity ruby on rails is still awesome. But since you might have to work with react anyways...nextjs is a second. On the mobile side - Flutter is unparalleled. No seriously - im a react guy. And Dart is weird. But Flutter is seriously the Ruby on Rails of the mobile world.
Earlier quoted context omitted.
I’m at least a bit amused that you have a whole comment about how nice rails is without mentioning ruby ;-)
To me it's just sort of a given that Ruby is pleasant to work with. Otherwise Rails wouldn't be. If Rails itself were unpleasant, though, merely being in Ruby wouldn't be enough to make up for that.