this post was submitted on 12 Feb 2026
46 points (100.0% liked)
libre
10167 readers
28 users here now
Welcome to libre
A comm dedicated to the fight for free software with an anti-capitalist perspective.
The struggle for libre computing cannot be disentangled from other forms of socialist reform. One must be willing to reject proprietary software as fiercely as they would reject capitalism. Luckily, we are not alone.
Resources
- Free Software, Free Society provides an excellent primer in the origins and theory around free software and the GNU Project, the pioneers of the Free Software Movement.
- Switch to GNU/Linux! If you're still using Windows in
$CURRENT_YEAR, take Linux Mint for a spin. If you're ready to take the plunge, flock to Fedora! If you're a computer hobbyist and love DIY, use Arch, Gentoo, Guix or the many, many offerings out there.
- Those on Apple Silicon Macs can consult Asahi Linux for available options.
Rules
- Be on topic: Posts should be about free software and other hacktivst struggles. Topics about general tech news should be in the technology comm or programming comm. That doesn't mean all posts have to be serious though, memes are welcome!
- Avoid using misleading terms/speading misinformation: Here's a great article about what those words are. In short, try to avoid parroting common Techbro lingo and topics.
- Avoid being confrontational: People are in different stages of liberating their computing, focus on informing rather than accusing. Debatebro nonsense is not tolerated.
- All site-wide rules still apply
Artwork
- Xenia was meant to be an alternative to Tux and was created (licensed under CC0) by Alan Mackey in 1996.
- Comm icon (of Xenia the Linux mascot) was originally created by @ioletsgo
- Comm banner is a close up of "Dorlotons Degooglisons" by David Revoy (CC-BY 4.0) for Framasoft
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
python being the home for AI is the cherry on the shit cake. Every time I'm forced to interact with python my mental faculties are degraded beyond repair
I've spent too many decades with C and its cousins to wrap my brain around Python. These days I'm pretty much just using Go, with a little C++ for microcontroller-powered projects.
If you read the thread, there's a large amount of pushback. Overall I'd say the community is neutral on AI with most people actively hating it when people use it for actually submitting PRs or drafting PEPs.
Also I don't think the language itself has much to do with AI since they still don't allow core devs to use AI.
it's more that I loathe that Python has boomed in popularity off the back of AI because I've grown to find it more annoying to hse than anything else.
A lot of the reason for AI being so heavily coupled with Python probably comes from Tensorflow when Google was starting to push AI for image classification stuff years ago. And that was more to do with Python being popular for mathematical programming and visualization over closed-source crap like R.
I just really like it as a glue language. It's super easy to build tooling in it that's easy for users and developers to use. I will say, without the addition and rapid expansion of the typing system it would be really awful to use.
Never had a slicker auto-documentation experience than with Python code that's properly hinted. Those hints are also specifically part of the code too. They aren't resolved at runtime any more either, which means you can use them to store doc/build code that runs separately from your main code.
My best experience with this was using annotations (in a similar way to pydantic) to model out a complicated schema. Wrote something that traversed the dataspace and generated hinted code, then I implemented the hint classes and was able to use them to rebuild the original schema. With the nice side effect that the objects could now be used to lint and interaction with the database and implement all the program logic.
I dunno, I hear a lot of people complaining, but the Python data model is just really slick to use in all my experience and I always find myself coming back to it the second I have to build an API that has to touch more than one thing.