This talks about one issue. You seem to be confident that this one case is representative of the whole FOSS space? I am not.

Can you elaborate how it would be much easier in closed source software? Because as far as I can see, it’s different. In most cases, you need an actual person instead of an online persona, pass interview and contracting, and then you’re still “the new guy” or Junior in the company or project. It’s not like closed off from public eyes means anyone can do anything without any eyes.

At the end, pointing to their Bugzilla issue tracker

I’ve always found Bugzilla incredibly inaccessible. It’s so overloaded, so complicated, so noisy with unrelated and irrelevant things. It always baffled me how projects use it and keep using it, and especially projects like Thunderbird and Mozilla, for such a long time.

I regularly use bug trackers, to report, comment, or work on. When I see Bugzilla, in most cases, I give up/leave right away.

Consequently, I find it ironic that they point to Bugzilla at the end.

That being said, I think this video is a good intro to accessibility, common issues, and study findings.

How do you guys view Bugzilla as an issue tracker, bug tracker, and work task tracker?

One file, almost 7k lines of code.

https://github.com/microsoft/BASIC-M6502

This assembly language source code represents one of the most historically significant pieces of software from the early personal computer era. It is the complete source code for Microsoft BASIC Version 1.1 for the 6502 microprocessor, originally developed and copyrighted by Microsoft in 1976-1978.

Are you attempting to indicate D much better than Nim or from D to Nim?

Feature richness as a user, documentation as a developer.

"For weeks I typed random letters into the command line, and when I entered ls /usr/bin and man finally something happened!

This is the next level of learning. Not only do you read how it is, you have to deduct, to assess and explore. Writing your own documentation is the best way to learn after all.

I’ve not used it much, I think I only had to use it in two instances due to customers. From what I remember, the structure and navigation was not hierarchical making navigating very inefficient and irritating.

I’m used to GitLab (and Phabricator in the past, and outside of work GitHub), and much prefer their repo, project, group representation and review UI/UX/workflow.

Codeberg only hosts open source.

I don’t think there’s a need to switch away.

Many people in Lemmy think otherwise, and have thought so for a long time.

Nothing changed yet due to product integration into Corp.

There’s a threshold where good integration does not trump shit product. Bitbucket sucks. I’m glad we’re not using it even when we’re still stuck with shit Jira and confluence.

Why is it called toll booth simulator (primary title) when most of it is not toll booth handling/gameplay?

OpenGL is an API standard. It defines data structures, operation interfaces, and behavior.

Mesa 3D is an implementation of OpenGL. It can be used so users of OpenGL can call it to draw stuff.

Vulkan is a newer API standard. It is newer and was designed with a lot of new hardware and hardware capabilities in mind, and significantly reduced what the job of the API is supposed to do compared to OpenGL. Essentially giving API users many more opportunities to control graphics pipeline behavior for better efficiency and performance. Libraries and frameworks exist that provide more convenience and prepared setup or opinionated usage patterns on top of Vulkan.

DirectX had a similar shift with DirectX version 12, which also implemented closer-to-hardware APIs similar to Vulkan vs OpenGL.

/edit: Noteworthy are also OpenGL and Vulkan extensions. They extend the core API with additional APIs. An app can check if they are supported, and if the driver supports it, can use them.

Notice: sr.ht is currently in alpha, and the quality of the service may reflect that.

Are these all different services? Seems like quite a hassle. Like a split of project resources.

An alpha classification doesn’t spark confidence in using it productively and for significant projects.