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.
Kissaki
joined 1 year ago
Maybe something to add to the side-bar?
The linked post doesn't seem like that good of a reference that I would put it in the sidebar. IMO it could be done better. But if you mean to say, something like it; yeah, the .NET environment is vast and can be confusing, especially when new to it. An overview or reference to one makes sense.
I suppose the term “.NET” encompasses both, but most of us that write and speak in this space tend to use “.NET Framework” for legacy, and “.NET” for modern .NET.
there’s the whole “.NET Core” thing
Before around net7, the open source cross platform non-framework dotnet was called Core. net6/7/8 is the .NET Core technology, but Core was dropped from the naming.
Now, .NET may refer to that modern dotnet tech, or .NET Framework. Presumably, the latter is referred to only in contexts where it's obvious that .NET Framework is meant.
and .NET Standard (2 versions). […] Are those relevant in the world right now, today? Hopefully not really!
.NET Standard is still relevant for libraries that target/publish for both .NET Framework and net6+. .NET Standard is the cross-platform baseline.
If you only care about contributing improvements, no, it doesn't matter.
If you want to at least be recognized as an author, and be able to say "I made this", the license opposes that.
Waiver of Rights: You waive any rights to claim authorship of the contributions […]
I don't know how they intend to accept contributions though. I guess code blocks in tickets or patch files? Forking is not allowed, so the typical fork + branch + create a pull request does not work.
libsass.so: cannot open shared object file: No such file or directory (LoadError)
You're missing the SASS library
I've been using TortoiseGit since the beginning, and it covers everything I need. Including advanced use cases. I can access almost all functionality from the log view, which is very nice.
I've tried a few other GUIs, but they were never able to reach parity to that for me. As you say, most offer only a subset of functionalities. Most of the time I even found the main advantage of GUIs in general, a visual log, inferior to TortoiseGit.
GitButler looks interesting for its new set of functionalities, new approaches. Unfortunately, it doesn't integrate well on Windows yet. Asking for my key password on every fetch and push is not an acceptable workflow to me.
That's less than I expected. If there's 141 commands that on average comes down to 10 per.
git has 17 million options
proof needed /s
I wonder how many it actually is.
I think using display: grid; as your default is the better default, so you're all set. :)
Looking at the Web Archive; Diatraxis has been around since 2021. That divio docs since May of this year.
I doubt they didn't "get inspiration" from Diatraxis.
It's certainly something that looks better, but contrary to green washing, I see real, practical value.
I would rather be able to see and inspect source code than not. And I would rather have the right to take and fork a two year old version than not. Or be able to wait two years to fork the current version.
Those are real good value. Those bring certainty in infrastructure robustness and freedoms.
I'm using the website / native website interface. It's at least possible there to edit the post and url. May be different for "Lemmy clients".