

Right, so expanding our code for better readability vs trying to make a super dense one liner.
Using human readable vars and not excessive short hand.


Right, so expanding our code for better readability vs trying to make a super dense one liner.
Using human readable vars and not excessive short hand.


Fair point. My point still stands on it breaking the black box test. Where the input can wildly effect the logic that creates the output.


Zen of python (PEP 20):
Beautiful is better than ugly. Explicit is better than implicit. Simple is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than dense. Readability counts. Special cases aren’t special enough to break the rules. Although practicality beats purity. Errors should never pass silently. Unless explicitly silenced. In the face of ambiguity, refuse the temptation to guess. There should be one-- and preferably only one --obvious way to do it. Although that way may not be obvious at first unless you’re Dutch. Now is better than never. Although never is often better than right now. If the implementation is hard to explain, it’s a bad idea. If the implementation is easy to explain, it may be a good idea. Namespaces are one honking great idea – let’s do more of those!


The rule I see is functions should be fairly atomic and almost obvious what they do in context of the code.
At least for my small brain that’s how I like it. I can understand some complex abstractions but rembering that actually this function behaves in three different ways depending on what flag is set is awful. It means you could look at one example and be totally wrong in another. Ideally you could guess the functions purpose even in a black box setting based on inputs outputs and the name should then make it obvious.
They could call around asking for pro bono. The firms wright off the costs as charity, but they could still get some in legal fees from the opposition if they win. Tbh though i pay for legal insurance because i hate fraudsters like this, not it helps someone screwed after the fact.
I sue out of spite tbh. Make the bastards fight for it at least


Right! I am so excited to see SUSE, Fedora, KDE, GNOME, Mozzilla, the free desktop foundation, GNU, the linux kernel group and i imagine many more all have stand alone git forges for many of their projects. If I could hit any git forge and explore and interact with all of these groups at once PLUS independent projects would be amazing to me.
Also large orgs like governments also could more meaningfully engage with othet orgs and sub orgs


That’s where digital twin engineering HOPES to bridge the gap.
There is definitely a contium of how long it takes to build and test changes where increasly abstract design makes more and more sense vs the send it model


Dang I wish did more with the Mimic3 project. They have SSML support which just seems like an awesome way to address the mono voice issue in tts for books to me.


I do it with k3s right now on fedora. I like it personally.
Nice thing if you use k8s settings up persistent net storage with something like longhorn is an option too.


Harvester cluster my everything. I really want to play around with having my servers being stationary, a togo cluster (laptops, and UPS in a suit case), and PC all in the same cluster.
Right now they are all segmented rke2 clusters, but Harvester should make running vms way easier too.


Distrobox. Building weird projects is nicer when I can start from a fresh system each time.


Any open projects you could point to on the subject or articles about the government efforts? I would love to learn more on that!


Gamejams! They always look like a blast especially if your goal is just getting something started.


Exactly I fully expect Russia to continue cutting edge early 2000s os development
Lmao. It is more barebones but yeah “feature: none” is a real jab
On one hand I love this, but also I think your right. ‘partners: alice bob’ in make file doesn’t work right?


Gitlab is actively working integrating AP and ForgeFed into it. ForgeJo has been working on ForgeFed.
I can’t wait tbh. I want to follow a project and comment on releases. @ a projects issues to create an issue in that project community.
Also can’t wait to have one big searchable open source forge. Random git project. Gnome. Free desktop. Mozilla. GNU. KDE. Fedora. OpenSuse.
All searchable, cross forkable, cross referencable, etc.
I will argue for standardization/normalization here though. If the change isn’t significant enough or fundamentally needed to achieve something that need or REALLY want, why does it matter if it does catch on?
Like I would rather people make 100 useful things, than polish/refactor/tweak things a 100 times causing everyone to have to learn a 100 new UX changes (yes we are users of the frameworks and languages, though are just different UIs and how we use it is our UX)