They wrote
Feel free to fork the project under a
(yes, the sentence ends with the 'a')
The ZUDoom GitHub project description says
UZDoom is a feature centric port for all Doom engine games, based on ZDoom, adding an advanced renderer, powerful scripting capabilities, and forked under a
It ending with 'forked under a' is probably a reference to that comment? lol, nice reference joke, but I hope they change it after a while, because as a description it's quite confusing.
Unless you open it in Excel. In which case bad things will happen no matter what you have in the CSV…
These changes will apply to operations like cloning repositories over HTTPS, anonymously interacting with our REST APIs, and downloading files from raw.githubusercontent.com.
Test date 2019, and it only lands now. No wonder it's being labeled a catastrophic failure. /s
In what way is it cleaner than Markdown?
[table]
[tr][th]Header 1;;Header 2;;Header 3[/th][/tr]
That looks like replicating HTML with additional complexity.
Markdown is good because it's simple and text-based. It has a simple syntax. Looking at Marksafe looks like you have to learn more syntax than Markdown and more than HTML.
I can see that additional syntax can make it more concise than HTML. But intuitively I wouldn't conciseness at the cost of additional complexity cleaner.
this project was created due to wanting to give control of communication and data back to the people
The "giving control of communication" goal seems to contradict the "viewer automatically shares without a choice" and the dependence on good-intent node owners not moderating their node content.
If a node owner hosts a community, what prevents them from moderating that community?
More specifically answering your question of is it worth learning:
It's very interesting because it's very different to other shells.
In your own description you added a bunch of considerations, requirements of following specific practices, having specific knowledge, and a ton of environmental requirements.
For simple scripts or duck tape schedules all of that is fine. For anything else, I would be at least mindful if not skeptical of bash being a good tool for the job.
Bash is installed on all linux systems. I would not be very concerned about some dependencies like sqlite, if that is what you're using. But very concerned about others, like jq, which is an additional tool and requirement where you or others will eventually struggle with diffuse dependencies or managing a managed environment.
Even if you query sqlite or whatever tool with the command line query tool, you have to be aware that getting a value like that into bash means you lose a lot of typing and structure information. That's fine if you get only one or very few values. But I would have strong aversions when it goes beyond that.
You seem to be familiar with Bash syntax. But others may not be. It's not a simple syntax to get into and intuitively understand without mistakes. There's too many alternatives of if-ing and comparing values. It ends up as magic. In your example, if you read code, you may guess that :- means fallback, but it's not necessarily obvious. And certainly not other magic flags and operators.
As an anecdote, I guess the most complex thing I have done with Bash was scripting a deployment and starting test-runs onto a distributed system (and I think collecting results? I don't remember). Bash was available and copying and starting processes via ssh was simple and robust enough. Notably, the scope and env requirements were very limited.
I like that even here on Lemmy, with inline code format, colors.ini is not being colored but color.ini is. Great symbolism for your issue.
The Nobara Project, to put it simply, is a modified version of Fedora Linux with user-friendly fixes added to it. Fedora is a very good workstation OS, however, anything involving any kind of 3rd party or proprietary packages is usually absent from a fresh install. A typical point and click user can often struggle with how to get a lot of things working beyond the basic browser and office documents that come with the OS without having to take extra time to search documentation. Some of the important things that are missing from Fedora, especially with regards to gaming include WINE dependencies, obs-studio, 3rd party codec packages such as those for gstreamer, 3rd party drivers such as NVIDIA drivers, and even small package fixes here and there.
If only this post title had received descriptive text too
Tailwind is an example of those frameworks fighting against/crossing the native web technologies referenced further up with the links to webdev posts.
The idea of shifting CSS declaration into the DOM element class attribute seems flawed to me. You lose what CSS provides natively.