“Click to Play” on the video - nah mate, you gotta auto-play those videos, and embed them in the article. Bonus points for the video being unrelated to the article.

I’ve seen it. I’ve experienced it. I hate it.

The bottom right videos were the previous iteration of that.

“I think Nvidia is very much a community,

🤨

Very interesting. It certainly shows the potential a replacement of the very old ELF could offer. It even looks very plausibly doable. Now it just needs to get all distros on board. :P

I’m not sure I understood the jump from single file SELF to userland-wide.

Can the SQL be precompiled into binary for faster lookups? I imagine there’s not much variance in the standard queries. That could offer some speedup, skipping the query analyzer/tokenizer/interpreter.

I’m not sure I followed how the LD_PRELOAD equivalent works now.

What are disadvantages of using SELF? (Assuming a full OS switch to SELF. Mixed is always additional burden.)

Presumably, this only covers the operation of an instance, not the project and development of the project itself?

Makes sense, I agree with you and your assessments. Except for the last point, maybe. Seems like it’d be a weighing of effort and use, or maybe someone implements it out of technical interest. As a feature, I think integrated bug reporting is a good thing. It reduces various barriers. No need for the user to know or learn about and register with whatever tracker the project uses, etc. Still, depends on the project, kind of users, and certainly effort. If implemented it has a maintenance cost and potential for bugs too.

Do these kinds of templates actually help against really bad submissions, though? A bit or significantly?

While I can see that maybe they do, I also think of low-effort submissions as if they didn’t care without a template, will they care and invest more when guided with a template? Maybe it’s enough to make some not post in the first place. I don’t know.

I wish it was more of a “open or guided submission”, or a “open submission by default, guide/request if insufficient”. If it doesn’t get a follow up, can still be closed.

The git forge ticketing systems not differentiating between issue description and first comment is another issue that relates to this.

That sounds like it’s unmaintainable. No chance to guard against (severe) consequential issues(?).

When I get genuinely frustrated and irritated, when I communicate that it’s typically still with a smile. Dark humor, if you will. I’m mostly thinking of team-external factors, though.

Within team, it’s mainly about one specific colleague’s work. I’ve voiced issues and frustrations, to them, teammates, and HR. Nothing fundamentally helped, though. By now, I try to act and think in damage-control mode. To not waste too much time and effort or mental capacity on their work. Still a waste to go through review iterations you feel are useless and wasteful, that they should have noticed and solved beforehand on their own.

Only once have I used harsh, blunt wording in an email to an admin after prod was down yet again, and there was no upfront or at any point communication regarding that they made some changes. It didn’t have a lasting (negative) effect, at least.

That sounds more like frustration and resignation than (heated) anger.

Or do you mean you don’t care about the fallout of getting angry?

Hating on Jira and Confluence together is a great team bonding experience.

If you’re a project and want to receive (good) bug reports, don’t do it like GitLab.com.
A huge list of ticket templates, asking you to to select a “group” label a “category label” and some other such label from very long lists with unfamiliar names.
I almost gave up even filing and just went YOLO at the end.

For me, issue templates are barriers and annoyances most of the time, that make my report less concise and less useful. At least that’s my strong opinion. Of course, I’m not the reason and target audience of what these templates try to protect against and guide submitters. Or maybe I am the target, who knows.

At work I remember a company managing our Jira migration set up a service desk that I found absolutely awful. When I wrote the exact same thing in four separate text fields, it’s just stupid. The end-user first level support guard being used for us software developers felt like the completely wrong tool for the job.

In German, we have the acronym DAU for dümmster anzunehmender User - stupidest user to expect. Is there an EN term for DAU?

In the past month, 15.8k commits came from “robobun,” 1.6k commits from “autofix-ci[bot],” and 790 commits from Jarred.

No chance anybody is reviewing those. Worse, nobody else can reasonably inspect or review changes. I suspect even from release to release, you’re looking basically at a new codebase, the next release invalidating all your previous assessment, and release to release assessment to be impossible.

16/30 = 533 per day. I don’t know when 1.3 was, but even just the three month delay means 48k commits. Who knows how many changes per commit. Crazy numbers.

Where I used to recommend Bun, I now just recommend pnpm/Node.js.

Do you have an assessment or opinion on Deno?

or install Age of Empires as well /s

• https://tuios.gaurav.zip/
• https://github.com/Gaurav-Gosain/tuios

I accept your cookies

It’s from the Eclipse foundation/org, but based on the classic Eclipse IDE platform.

I only looked at Theia when it first came up publicly, not sure how it evolved. It’s similar to VSCode, supports VSCode extensions IIRC, but also does some (technical) things differently.

I categorize it as “VSCode but under the Eclipse foundation and from their own codebase” (rather than a fork or fork+reduce).

For a small exorbitant consulting fee that legitimizes me, I can tell them that.

That’s… an interesting approach.

What a horrendously stupid tweet. I find everything that follows is stupid and problematic too.

VideoLAN calling them disrespectful, when it was more than that. Someone saying it works for them on Linux, so it must be Windows (not evidence, could still be VLC). Article suggesting Defender exclusion, without mentioning the security implication. Original person doubling down, saying VLC should or has to fix the Defender issue (like they did for an AMD crash).

Insane…