capitol_

Just understanding the rules are not enough, you also need to be consistently good so that you never make a mistake that gets into production.

On both your average days and your bad days.

Over the 40 to 50 years that your carer lasts.

I guess those kind of developers exist, but I know that I'm not one of them.

Why do you need it to be cooler than 18c?

Eza is nice, but lsd is a step up imho, since it uses the same arguments as ls so that I don't get confused when I change systems.

Is this some sort of troll comment?

I'm sure that you are perfectly able to do your own research, why are you trying to push that work onto some stranger on the internet?

But how do that relate to their class? The working class desire money just as much as the owning class.

I'm confused about the timeline here, the tag for 2.50.1 is from 2025-06-16 ( https://github.com/git/git/tags ). And the date for 2.50.1 on https://git-scm.com is also 2025-06-16.

But it seems like almost no distributions have patched it yet

https://security-tracker.debian.org/tracker/CVE-2025-48386 (debian as an example)

And the security advisory is from yesterday: https://github.com/git/git/security/advisories/GHSA-4v56-3xv...

Did git backdate the release?

What is legal and what is moral are two circles in a venn diagram.

In a good and just society there is a large overlap between them, and in others there is less overlap.

But it's impossible to build a legal system where there is a 100% overlap, and it would most likely be a broken society in other ways.

I totally agree with your second paragraph, that the government needs to remove loopholes and other ways for people to weasel out of contributing to society. But there will always be some corruption and a lot of money to be earned by only taking from our shared resources and never contributing back.

Maybe they should have said something along the line "replaces the pain with a new one and gives you adrenalin that surpresses it and is addictive"

I would draw the opposite conclusion from the WSL1 attempt.

It was a strategy that failed in practice and needed to be replaced with a vm based approach.

The Linux kernel have a huge surface area with some subtle behavior in it. There was no economic way to replicate all of that and keep it up to date in a proprietary kernel. Specially as the VM tech is well established and reusable.

I thought that (for example) deno executed typescript natively?

So they allowed you to know that you are in the control group? Doesn't that introduce bias ;)

If you only have 1tb of data then you can have it in ram on a modern server.

It's also easy for people to have the opinion the those who do the unpaid work of packaging software should do even more work for free.

I have sent about 50 or so patches upstream for the 300 packages I maintain and while it reduces the amount of work long-term it's also surprisingly amount of work.

Typically the Debian patches are licensed under the same license as the original project. So there is nothing stopping anyone who feels that more patches should be sent upstream to send them.

Typically the Debian maintai

With that said, there is a long and proven track record of attacks on phones.

But those tend to be against journalists and activists.

What threat model you operate under is a nontrivial problem.

The LGPL hits the sweet spot for libraries in my opinion.

Since rust is popular it naturally attracts a counter movement, so some people will grasp at straws in order to say something negative.

No, there is a lot of us who live in countries that framework doesn't ship to.

No, the idea behind yk-backed keys are that part of the secret lives on the yubikey and can't be extracted.

So you need to approve the usage of that secret by touching the yubikey.

The amount of coal that can be captured by planting trees doesn't compare in volume to the amount of coal we dig/pump up.

At best it will make the planet prettier and at worst it will simply be feelgood.

A very very long list of CVEs disagrees with that parsers are "not too difficult".

Maybe because zig isn't memory safe.

I would say that this is true for protocols, tls have been significantly improved by dropping support for many different algorithms.

But its not obvious that the same is true for a library.

The RustCrypto project breaks each algorithm into its own crate, while botan implrments everything.

Its not obvious to me that one approach is clearly superior to the other.

I wonder what the ratio of people actively deactivating to people silently never returning to the website/app is.

At least 1 to 10 is my guess.

How does this protect against dangerous things?

My understanding is that this would just cause the dangerous things to be repeatable.

This sounds like a reasonable complaint, that refactorings are too complex in large programs.

But I have a hard time to envision any other solution than "better tooling for refactoring".

My experience with our riscv build deamons in Debian is everything works, but there is some spurious segfaults from time to time.

Check the green build matrix on this page: https://qa.debian.org/developer.php?login=alexander.kjall%40...

If you only build things that are so simple that anyone can understand the code on day one and you don't need any domain knowledge, then what is your value proposition?

If the most complex thing you can build is a todo-app, then I think you don't produce much value to society.

Could you share more of your thoughts on why that kind of memory corruption wouldn't be exploitable? Do go have something in place that prevents it?

HDMI is really not a very good choice as they try to block open source implementations: https://arstechnica.com/gadgets/2024/02/hdmi-forum-to-amd-no...

It should be kept out of regulations.

Wouldn't this make engine version upgrades a nightmare?