LOL

They are trying to bore only your customers, attackers have direct access (=

distcc so you can compile on the faster ones and distribute it

I think you meant no data cap.

The right thing to whom? Shareholders? (=

It hasn’t crashed yet, but I won’t be able to test it for a couple weeks (vacation time \o/).

For normal use, it looks like the crash is resolved or, at least, as stable as 6.7 was. Next test is to play Helldivers 2 with the Vulkan backend and see if it crashes or run.

Powercolor, red devil.

Under 6.7 I was able to find some a combination that was usable for a few days.

With 6.8, timeouts would happen within 30 minutes.

I fiddles with sched_job module option and the system seems stable now.

They still have, I replaced my 3070 with a 7900 xtx and the 7900 is constantly freezing with ring GPU errors and drivers completely effing up the system. I have already replaced it twice, and I am using workarounds to not hit bugs, but they happen every few days…

On nvidia, there are still too many edge cases involving Wayland that are just crippled. Orca slicer doesn’t work for me for example, you are completely missing any of the 3d accelerated graphics in there.

On the other hand, the AMD 7x00 series have different kind of bugs, with ring0 errors leading to full resets.

I think once nvidia drivers are squared out (the proprietary ones) it will be smooth sailing.

It is user friendly, and technically incorrect, since nothing ever lines up with reality when you use 1000 because the underlying system is base 8.

Or you get the weird non-sense all around “my computer has 18.8gb of memory”…

What? Every BIOS in the world still uses the same system. Same thing for me on Linux.

Only hard driver manufacturers used a different system to inflate their numbers and pushed a market campaign, a lot of people who didn’t even use computers said “oh that makes sense - approved”

People who actually work with computer, memory, CPU, and other components in base 8 just ignores this non-sense of “x1000”

I feel like you just confirmed exactly what I said, few people were able to beat it.

To be fair, very few people used to be better at go, let alone a lot better.

Ty!

By secure they mean “the only way we can easily see everything you do”

Weird numbering system? Things are still stored in blocks of 8 bits at the end, it doesn’t matter.

When it gets down to what matter on hard drives, every byte still uses 8 bits, and all other numbers for people actually working with computer science that matter are multiples of 8, not 10.

And because all internal systems use base 8, base 10 is “slower” (not that it matters any longer.

While I don’t use TPM myself (I dislike being tied to a specific hardware) the way it protects you is:

Disk is protected through encryption, so you can’t remove and inject anything/hack the password.

If boot is protected/signed/authorized only, a random person can’t load an external OS and modify the disk either.

All this together would say, even if someone acquires your computer, they can’t do anything to it without an account with access, or an exploit that works before a user logs.

In a way, the attack surface can be bigger than if you simply encrypted your disk with a key and password protect that key.

You can always compile your own Iosevka and adjust several pieces, I have done that selecting what I consider the best pieces a long time ago.

The compiled font lives in an easy to access internal webserver that I just grab from every computer I use (=

I really love the current trend in R&D PowerPoints

• generic text
• problem: x doesn’t work
• solution: do something so x works
• some contributor list/thanks