philm @ philm @programming.dev

帖子

0

评论

179

加入于

2 yr. ago

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)

Fingers crossed, that you're right. If I can't watch youtube without ads, I'm mostly done with it (which would be a loss for me TBH, since there's a lot of good informational content there...)

Btw. do you know the technical reason why it's still working with Firefox? Does it have to do with this new anti-adblock-API that was recently introduced in Chrome and Safari?

I have already wondered, why it's still working for me :). Good to know, then it's finally settled, I will stay on Firefox. I hope it will continue to work with adblockers there... (Google has way to much "stake" in Mozilla)

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...

Mastodon - not a link aggregator, tree-threaded, kbin hmm PHP (yuk) and mostly one contributor and by far not as feature rich as lemmy. The rest similarly as Mastodon is not close to reddit as lemmy is.

And yes ActivityPub grows with multiple projects, but I mean specifically something like lemmy or kbin and something that can be a reddit replacement of sorts. There's a little bit more happening than just ActivityPub behind the scenes btw. And it's still no small feat to have a platform like Mastodon or lemmy (I think those two are the mostly the forerunners by now). Sure it's not super complex, but the amount of features are often underestimated by a lot of people (as far as I can read here and often somewhere else, so why is there no real alternative to lemmy yet...?)

Really? Is it necessary to ban people about making a valid argument. I know and also don't like people asking a low effort "What's the status of this" (and would totally get why such a thing would be marked off-topic, but a ban over something like this is still to harsh IMHO, they will learn, that such questions are not well-received over just the marking it as off-topic).

But the comment discussed here has a valid concern (quickly closing issues that don't have satisfactory solution yet, without getting feedback).

A better reaction would be to just ask, whether the issue at hand is still relevant, having [these] alternatives at hand etc.

And yet, I don't know of a better project. Growing, maintained projects will usually get better over time (take major refactors, when being modular, rewritten parts of it etc.). But yeah growing needs to have a healthy and friendly Community Code of Conduct, and that I am more concerned of...

Well yeah the second comment didn't really had to be, but hey it's certainly not really reason enough to ban someone from the repo. The first comment I think is totally ok (as well as marking it off-topic, but optimally with an answer, probably marked as off-topic as well). Just keep an issue (it's not a PR) open, until the issue is resolved in one way or the other i.e. either solved reasonably via a third-party client (with links to it) or directly in the repo, asking the community (when it's not obvious that the issue is resolved), whether this is resolved, wait for reactions, and close it after some time based on that. Banning someone, or quickly closing or not reopening after a carefully written argument, that the issue is not solved etc. is just childish behaviour, especially for a community focused project (I'm watching a few lemmy issues on GH).

despite 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...

installer

You mean the "new" installer GUI? I never used it TBH, I always did partitioning (and everything else) via CLI, not sure about that. But NixOS (gnome version) has GParted and all other kinds of partitioning tools on board, so just partition it as you think it's best and then generate a config via nixos-generate-config as described in the manual. One tip, when going down that rabbit hole (when you're committing at least): Start with Nix flakes right away. Checkout all kinds of dotfiles in github of other users (and on github there are a lot of configurations that can be source of inspiration).

OCI images and CI/CD to buid the image

Actually since I just had a similar issue at work. I fought a little bit with the traditional Docker pipeline, and then discovered this: https://mitchellh.com/writing/nix-with-dockerfiles, which not only solved my problem much faster, but is also more efficient, since only the actual dependencies of the package are in there (and it can be really reproducible). So you can actually combine the best pieces of each technologies (Docker - sandboxing/containerizing, Nix - packaging and configuration).

Btw. Nix is rapidly growing (since flakes mostly), so I think a slow shift towards Nix is happening already.

But I agree, migrating traditional dotfiles to Nix+home-manager takes time. I did it incrementally (I used activation scripts to link directly to the old config files, and slowly converted the old config to Nix.

lack of btrfs support was disappointing

NixOS supports Btrfs

AFAIK NixOS supports every filesystem, that other linux distros support, and often with easier/better configuration, e.g. I'm using ZFS, which seems to be easier to setup on NixOS than on most other distros.

Yes, it certainly invites you to tinker and experiment with the system without having to fear a broken state. I got multiple forks for different applications (e.g. helix-editor with a few merged PRs), and configured the system in a detail not comparable to any previous distros I was on. Really like how I can e.g. carelessly switch between different desktop environments (without VM)...

Yes, if you've found your distro, I also don't see a point in switching, there's more important stuff than learning how to install and setup your distro everytime you hop. I only hopped, when I wanted to have a clean install because my previous was kinda broken (dirty state over time), and/or wanted to have more control, or try a different desktop-environment. I have now found a distro (NixOS) where I can have all of that at the same time (so no point in hopping anymore for me too).

I have hopped rather rarely. I think my journey started with Debian -> (all kinds of flavors of) Ubuntu -> Arch -> NixOS.

Maybe I missed a few (started with linux at probably ~2005). I've stayed on each of these for a few years, I think I switched between Ubuntu flavors a little bit more frequently. Stayed on Arch the longest for ~7 years. And I think I have basically settled now since 3 1/2 years on NixOS without plan to hop any further distros (unless there comes a distro comparable to NixOS that has less quirks and is generally nicer to use (e.g. tooling, strong, strict static typing etc.)).

NixOS is quite different than other distros (which IMO are all very similar) but does package-management+system-configuration basically how it should be done (in hindsight). It's a rather steep learning curve in the beginning, but it only gets better over time, since your system continuously improves, compared to different distros that accumulate dirty state over time and in one way or the other break after some time. This was often the reason why I hopped on a different distro, since I wanted a clean fresh install, which I get with something like Impermanence+tmpfs on root after each reboot.