![](https://lemmygrad.ml/pictrs/image/292b778f-4b03-4532-907a-885b1239728b.webp)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
I use .NET for my job. My team shifted to a lot of frontend work with react for about a year when the lastest .NET was .NET 5. Barely a year later after not touching it the latest version was .NET 7. Ridiculous.
(he/him)
Terminally online insomniac code monkey from burgerland. Deeply unserious person.
I use .NET for my job. My team shifted to a lot of frontend work with react for about a year when the lastest .NET was .NET 5. Barely a year later after not touching it the latest version was .NET 7. Ridiculous.
I never knew the initial commit was on Valentine’s Day. Also, very based how the very first commit is just the AGPL-3 license.
Its small size is due to having few dependencies and not having a lot of code itself. It also helps that I use different dependencies depending on whether or not it is compiled to target WASM. The library I use for WASM, gloo-net, is a thin WASM wrapper around the browser’s fetch API, which should keep the binary smaller when sent to the browser.
It’s a coincidence that you mention that. One of my main motivations for making this was to have something that would be easy to use with the leptos UI.
If you try emacs again, try evil mode. It adds vi bindings.
Your hate for America and capitalism has distorted your world view. I’d prefer to live in a world of opportunity rather than a world of schadenfreude.
“I reject reality and substitute my own.”
That’s a dictatorship of the bourgeoisie for you.
I think this is a good idea. My main question is: how could this reading club work? With a reading club for a book, you can have participants read a certain number of pages or chapters and discuss those readings regularly over some time frame. There’s a sort of progress from beginning to end that keeps all the participants on the same page (pun unintended). How could that be adapted for reading source code and documentation?
I write rust on a meh computer alot and have never had compile times be that bad (at least not for debug). The target dir is massive though.
Depends on what you consider taking down. The fact that the project is FOSS means anyone who wants to can fork the code, so it would be hard to eliminate one’s ability to get the source code even if the main repos got taken down and the maintainers are detained or killed.
As to whether they can control the fediverse in a way that allows them to invent reality like they do with mainstream platforms, I could see them trying to compromise admin teams for individual instances. However, unlike mainstream social media, our eggs aren’t all in one basket so to speak. They won’t be able infect the entire platform like they can do with big tech.
That sounds like a good idea generally, but it’s hard to say more without specific feature ideas in mind.
This seems like a big change that also requires a lot of brainstorming to flesh out. It sounds like it would best be made as an RFC for now.
I’m personally annoyed with how the default UI shows messages and mostly work on the frontend, so changing that is definitely on my agenda.
Bomber for me.
There was some discussion among the maintainers months ago regarding holding a contest for a new logo, but it never came up again. I think it would be a good idea.
I’m personally working a full time job in addition to this. However, I spend a lot of my free time contributing because if the only software I worked on was the corpo shit at my dayjob that ends up being cancelled before it reaches production half the time, I’d go insane.
I’ve found the people pretty good. I find it’s easier to get a sense of community on here than it is on big tech platforms.
Joy, but also panic.
Users can already block entire instances, so progress has been made on this front.
I’m curious how we’d go about automatic mod kicking. Instance admins are already able to remove and appoint mods to communities. What would a sensible trigger for auto-removing mods be?
I’ve been wanting to change how the existing admin options are organized on the admin page for awhile now to be easier to understand. As for improvements beyond that, I’m open to suggestions from instance admins for improvements.
Regarding your last point, even if an offending user is registered on another instance, banning them will prevent them from bothering users on your instance.
It’s been way too long since I last saw a Dolan meme in the wild.