Comment on Your server owner is now banned from participating on lemmy's Github
philm@programming.dev 11 months agodespite what Rust cultists will undoubtedly soon come to tell me
And here I am :)
There’s a lot of reasons to go with Rust (and least of all performance), especially as web-backend. Top-notch libraries/ecosystem (I work extensively with all kinds of programming languages and most others suck in one way or the other). At this point I dare to say that it has the best ecosystem in this regards. Also a static type-system only being exceeded by Haskell (when talking about general purpose languages, that are actually in use), which makes projects maintainable by a lot of people, especially relevant for an open source project. There’s a reason why a lot of high quality projects are either rewriting or starting in Rust or are thinking to switch to… Etc. don’t want to throw more Rust evangalism at you, since there’s a lot to just google and learn…
Anyway, there were a few changes lately that made federated lemmy better (with the last release especially), the initial bugs I accept. But I agree, they aren’t veterans from the valley with multiple years of experience, just a bunch of idealists that had an idea and were persistent enough for years to implement it, I certainly have respect for that. What I don’t like, is that they are moderating a little bit too much, not being mostly community focused (among others, to avoid forks). But bringing a federated link aggregator like lemmy to the place where it currently is, at least takes quite a bit of time… So a fork (if really necessary) sounds like the most likely way forward…
interolivary@beehaw.org 11 months ago
I seriously doubt Rust has the best ecosystem for web backend development, and I seriously doubt anybody claiming that knows what they’re talking about
philm@programming.dev 11 months ago
Sure you can doubt me as much as you want (and this is probably a healthy attitude). I tend to educate myself, and learn from experience (and that I dare to say, I do have…). As you may have guessed, I really recommend looking into it, there’s so many good design decisions with Rust (and the ecosystem). As a starting point/library: axum would be the web-framework I’d recommend to use (as it uses Rust quite idiomatically). And for e.g. service communication via grpc, tonic is quite nice. As database abstraction layer the last time I have used sqlx which was quite convenient to use. (So far with a “classic” web-stack). And rust-analyzer is probably the best language server I have used (and felt the fast development over the time (with “successful” switch of the maintainer), which speaks for itself as well…).
Btw. it also really depends on what you actually mean with “web backend development”. I.e. “just” writing a web-server that takes connections via HTTP or something deeper the stack…
ericjmorey@programming.dev 10 months ago
I like your attitude and approach to this conversation. Thanks for not escalating into a useless argument and making the discussion educational.
kmaismith@lemm.ee 11 months ago
I mean, “best” is infinitely subjective. I would be inclined to think any anyone who says “php is the best backend software ecosystem for web” doesn’t care much about programming and really only are really in the business of making money. Rust is at the creative forefront right now, it makes sense a bunch of pissed off people chose rust to make a reddit clone, it would be challenging to draw passionate engineers to a php or java project; it gives a way to draw more helpful attention (which they are as we now see squandering)
philm@programming.dev 11 months ago
Yeah best is probably not the “best” wording and a little bit provocative, but it’s the “best” ecosystem I have found so far (and I squabbled around with like ~10+ programming languages, often at a deeper level). I’m mostly talking out of a development-experience + quality of software standpoint.
I’m very happy to be proven wrong, or be given a different direction (but C# or JS/TS are definitely not the languages/ecosystem I want to be confronted with, or even maintain systems in it…)