I get that peeps are coming from VSCode and I support competition with MS’s EEE of software dev.
But, like, bloat and corporate capture were always the trade offs with VSCode … you all knew that right?
A little bit of computing and a little bit of neuroscience.
he/him/they
I get that peeps are coming from VSCode and I support competition with MS’s EEE of software dev.
But, like, bloat and corporate capture were always the trade offs with VSCode … you all knew that right?
Unfortunately it’s unlikely to come soon as mastodon is a while away from implementing groups and are doing it their own incompatible way.
This tag process works though and I’m happy the lemmy devs implemented it.
Spread the word.
I don’t believe so. I’m pretty sure I’ve checked it, but I could be wrong.
It makes sense though as hashtags are a different mechanism from follows and boosts.
You could do a quick test with the test community and the test hashtag.
@hrefna @tschenkel @astrojuanlu @programming
Yea … it seems that things like this are part of Julia’s problem …
that for many the “two language problem” is actually the “two language solution” that’s working just fine and as intended, or as you say, well enough to make an ecosystem jump seem too costly.
Yea I remember reading about some deeper issues with the language (Dan Luu was quite dark on it I think) and that more or less turned me off. At the time I would have had to have been amongst some dedicated users urging me on to consider adoption.
In general, how much more performant would you say Rust is or can be than Julia? Any good resources on this?
What’s interesting about this take is that it targets the whole “two language” thing and implies that it might be a fool’s errand.
Problem with that logic is that python was essentially “reborn” at some point 2010-2012.
That’s when scipy, pandas and notebooks all came together, and with early pandas putting python on the map more than some (cough - Guido - cough) are willing to admit.
Of course the maturity of the ecosystem by then is part of it … but also pushing through the python 3 situation wasn’t trivial and likely speaks to the momentum the science stack brought to the ecosystem.
@tschenkel @astrojuanlu @programming
I’d suppose part of the problem might be that there’s a somewhat hidden 3rd category of user that “feels” whatever added complexity there is in a two-language lang like julialang and has no real need for performant “product” code.
And that lack of adoption amongst this cohort and your first enforces lang separation.
I may be off base with whether there’s a usability trade off, but I’d bet there’s at least the perception of one.
Yea. The basic idea feels like something that’s kinda been forgotten in the wake of big-social’s long dominance and vanilla-ification of online activity.
I even once asked the dev of a popular mastodon app who was expressing interesting in making a lemmy app too … “why not just add lemmy compatibility to the mastodon app”.
Their response was that they couldn’t see what that would look like or how it would work.
It’s all just text messages … I don’t think this is hard!
A useful lens I find is whether a social media system is good at creating, facilitating and hosting genuine communities.
Alt-social right now is struggling with this I think and, IMO, has plenty of room to grow in this regard.
The difficulty though is that it requires more features in our platforms, some likely non-trivial. That’s a big ask for an open non-profit ecosystem.
An effective means of aggregating multiple parts into a unified view could alleviate this.
Personally, I’m there with you I think. I only use default web-UIs on all fediverse platforms I’ve used, and advocate for that.
But should multi-protocol systems and multi-platform clients become normalised, I think this goes beyond “to app or not to app”. What I’m talking about could likely just be a web-app.
The issue is more around aggregation and creating something “greater than the sum of its parts” out of open alt-social.
@fediverse
Probably not original at all. But I suspect there’s something to framing it around “improving the quality of internet discourse” through the emergent dynamics of a federation … especially in comparison to monolithic big-social.
It also repositions the internet as a broader resource to be used effectively.
And instills independent and contentiously incompatible instances along with widely connected federation as desirable positives for social media and the internet in general.
2/2
A tricky part here is that the community still needs to be followed at least once on your instance for the content to come through. *I think*
So if a community isn’t coming through, I’d recommend these steps:
* Search for the community and follow it like any other user.
* Add it to a specific/bespoke list, then remove that list from home (a setting available on each list). This removes “the firehose” from your home feed.
* Follow the corresponding tag as you would any other
2/2
@mick_collins @Subversivo @fediverse @fediversenews
I’m not familiar enough (or at all) with C#, but AFAICT, it could make an instance more stable, as firefish and misskey have struggled with handling a decent amount of users and C# could be a faster system for the server.
Also, a re-write sometimes is a good thing. And, developers have different preferences for languages, so having a C# project around enables C# devs to more easily contribute to the fedi.
@eldereko
> he plugins are still very few compared to other mature editors. also, it’s not quite as configurable as Sublime
AFAIU, it doesn’t have a plugin runtime, which is fairly glaring to me (but maybe not for devs these days).
This is what triggered my “is it hype” thought, as I’ve seen people say it does but it’s in rust or something.
And I feel like many fail to realise how hard it is to build a new editor with everything we take for granted these days.
Fediverse & typst similarly.