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.
TortoiseGit.
Through settings, I move the Show Log to the top context menu level, and it's my entry point to every Git operation.
I see a history tree to see and immediately understand commit and branch relationships and states. I can commit, show changes, diff, rebase interactive or not, push, fetch, switch, create branches and tags, squash and split commits, commit chunk-wise through "restet after commit", … And everything from a repo overview.
/edit: To add; other clients I tried never reached what I want from a UI/GUI, never reached TortoiseGit. Including IDE integrations where I'm already in the IDE; I prefer the separate better TortoiseGit.
GitButler is interesting for it's different approach, but when I tried it out the git auth didn't remember my key password. (Since trying out jj I found out it may have been due to disabled OpenSSH Service.)
These changes will apply to operations like cloning repositories over HTTPS, anonymously interacting with our REST APIs, and downloading files from raw.githubusercontent.com.
let us resurrect the ancient art of Bittorrent
haha
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.
I'm very skeptical of sticking to "old and tested" without reasoning.
If you're talking about the implementation, if they're making changes it's no longer "well tested". If it's undocumented, it's not approachable. If you're talking about toolchain, if the old is unapproachable because of inherent toolchain barriers, and custom toolchain dialects, I think it's good to question.
There may also be something to say about them struggling to get new contributors and maintainers (from what I heard/read).
🏃♂️💨
The dash emoji. Always looks like a fart.
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.
This is not a supply chain attack, it is sudden extreme enshitification. according to the article, the attacker also bought the GitHub repo
I don't see how buying the GitHub repo as well makes it not a supply chain attack but enshitification.
They bought into the supply chain. It's a supply chain attack.
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
Just gotta close it off on both ends
<===>(parens for round ends didn't look good)