I'm totally aware of the benefits of encapsulation, but the way java does it seems so unnecessarily boilerplatey (C# is better, functional programming makes encapsulation even simpler, but that's a different paradigm...)
I like how Rust approaches this via the module system and crates (you have pub for the public interface, pub(crate) for crate/lib wide access and no modifier for being only allowed to access in the current module and submodules of that module)
My condolences, haha (I'm honestly not a big Java lover ^^).
Yeah but why do I have to use an IDE to generate getters and setters in the first place? It just adds up to more mental overhead, because my brain has to process this boilerplate somehow, even if my IDE can generate it (I know it's simple code, but it's even simpler to not have that boilerplate code at all).
Yeah the way you need to maintain two codebases: one for types and one for actual logic is annoying.
Also nix is purely functional (which is necessary, for more information read the Nix Pills), Typescript is not, so unless it's only a purely functional subset or severely limits Nix (in the form of abstractions, after skimming over it, I think this is the case), it will run into issues...
The curse of OOP (java style...).
I mean why do you need to write getter and setter methods. I have wondered at the beginning of university 10 years ago, and am still wondering why you would need something like that...
At this point, I think it's almost mainstream, and it's still growing fast (and it's getting better, rust-analyzer is really awesome these days, I was there at the beginning, no comparison to today...))
I may be biased, but I think it'll be the next big main language probably leaving other very popular ones behind it in the coming decade (Entry barrier and ease of use got much better over the last couple years, and the future sounds exciting with stuff like this)
Nah the old official reddit code is entirely out of date, writing up something like the original official reddit clone, is not too hard, and I would rather rewrite it (in Rust obviously ^^).
Hubzilla is certainly an interesting and ambitious project (though a PHP codebase repels me a little bit, TBH). Need to check it out further. Zot also sounds interesting. Looks a little bit like a swiss-army-knife sandbox-toolkit of federated social networks.
misunderstanding was
I think here's a misunderstanding too :). With quickly I mean closing without getting feedback, or without providing a good reason why the issue is closed (without being obviously resolved), not the dates (which I think are only relevant, when actually awaiting a response). I have seen this over the repo a few times, good writeups often explaining some behavior etc. and then bam closed, either as duplicate (although it's not (example)), or "not as planned" etc. I think this is not good behavior for an open source project (I'm around the block for a few years contributing and maintaining OSS, for reference...). Especially as this is a real community project and not some random opinionated application (well depending on how you define it, could be true to lemmy, but I don't think it is...)
I rather let an issue open than close it, "just to have fewer open issues". I can close it anytime, and if someone searches for that issue sees it closed while it isn't resolved, it just creates confusion...
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...)
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...
Sure I'm totally in for something new, maybe even more in a wiki based style (i.e. collecting knowledge) or a mix of all kinds of things (like StackExchange etc.). But I don't think that the concerns you have, have much to do with the platform and more with the users using the platform. The communities I'm mostly on, are civil and objective/less emotionally driven. This topic is (as the title already implies) a little bit the exception...
It has Properties (basically syntax sugar...)