philm

joined 1 year ago
[–] philm 2 points 1 year ago

Not without a super fancy type system that has to be still found. I think the key issue is cyclic data-structures (e.g. doubly-linked list). The language somehow needs to have strong/weak pointers and automatically determining them is a very complex research question...

[–] philm 8 points 1 year ago* (last edited 1 year 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)

[–] philm 5 points 1 year ago (1 children)

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

[–] philm 3 points 1 year ago (1 children)

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?

[–] philm 4 points 1 year ago (3 children)

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)

[–] philm 2 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] philm 2 points 1 year ago

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

[–] philm 2 points 1 year 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...)

[–] philm 4 points 1 year ago (1 children)

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

[–] philm 2 points 1 year ago (1 children)

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

[–] philm 3 points 1 year ago (3 children)

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

[–] philm 2 points 1 year ago

Yeah lemmy-ui doesn't escape/sanitizes properly...

view more: ‹ prev next ›