Kote Isaev / is on Nostr

Web Developer. Proud citizen of Republic of Georgia.
Proud political migrant from RF.
#GloryToUkraine
Don't get scared if I boost sometimes #NSFW content - I want support #BBW & #SSBBW content creators this way.
Thinking and reading a lot about #anarchy but not brave and communicable enough to do something in practice.

Web Developer: SakartveloSoft
Location: Tbilisi
Freedom: Priceless
Medium: https://https://medium.com/@kote.isaev

Last Notes

2024-07-20 17:05:52

- reply

Sounds as argument against big kernel and in favor more isolated drivers, and against "hyper-privileged" software in general...
Kernel could unlock all mutexes on process death (and even if process leaked mutexes lock without crash), same way as file handles freed even if you use kill command on process....
At userspace it resembles how nodejs domains used to intercept error to prevent ungraceful process crash.

2024-07-20 16:55:35

- reply

If it was always so, then nobody would ever see THAT bsod, as it was caused by crashing kernel driver, a very privileged software. So it means that for windows at least it is not ended up with some standard protocol with 'exclamation on a software device".

2024-07-20 16:44:43

- reply

"w (typically by returning and propagating an error)." Propagating to the exit of process with an error code. Here we are again at need for some standard of how to deal with faulty drivers in general, such as "reboot with replacement by error reporting code that will send error dump somewhere", "isolate drivers in some container-like environment that would NOT cause complete boot BSOD, unless special cases like filesystem driver" (but then such EDR impossible per se), at os level...

2024-07-20 16:26:44

- reply

Still, this is NOT enough to prevent failure in situation when "user input" is involved, even if it is some "content update" for security driver.
Real problem there was not the fact the kernel panic happened but more the fact that recovery strategy that does not require manual intervention did not implemented.

2024-07-20 15:16:12

- reply

Null deref?
Like, some `switch` construct got optimized into kind of `foo[bar].doCrap(ctx, data)` construct? But the `foo[bar]` kind of construct without default pathway can happen in Rust anyway if that thing constructed dynamically (e. g. by other earlier part of arriving data).
this can be a common situation for some "rules engine" or other high-level code execution branching infrastructure.
Does Rust can enforce "always have a meaningful result for `foo[bar]` construct?

2024-07-20 11:23:04

- reply

Here broken piece of input comes, and your memory safe code dies with exit code 9000. I mean, this whole situaiton when faulty driver can cause crash whole system instead of markng this driver as faulty and to not not use it at next boot, and if necessary, reboot with new settings, or use special fallback driver whose purpose would be to report about problem on next reboot, and then it would be quite short outage and systems would be alive after few reboots, read - few minutes max.

2024-07-20 11:17:04

- reply

I agree that memory-safe languages are necessary. And many others here would agree on this.
But many coders write in C and C++ in a way like these languages are memory-safe. Like, "Hey, Bob, why you check this parameter for array size bounds here? I already checked it in function which calls this code! Your check slows code for 0.3%!".
But problem that caused this outage is NOT a memory leak or out-of-bounds data read/write. It was malformed "content update". Broken input data.

2024-07-19 14:00:27

- reply

Imagine if someone write such kernel driver in memory-safe language. But malformed update arrives anyway. So this memory-safe driver crashes, but may be with other error code, leaving the system unbootable anyway. So, it really require complex changes, which will not happen.

2024-07-09 23:43:16

- reply

Cryptocurrency is a scam per-se, but POW (proof of burned electricity for nothing lol) such as btc are worse of them all.
Lots of burned electricity, and ended up with lack of promised decentralization because eventually it ended up with few whales sucking most of generation with more and more expensive piles of computational hardware.
And all that just to compute next block hash for 1 nanosecond faster than "next guy".

2024-06-28 11:18:37

- reply

What is eID you talking about? Is it some id card a-la smart-card with gov-issued certificate usable for official digital signatures, or something else?
Asking that because rest from your list sound scary yet clear to understand what it is about.

2024-06-22 03:31:14

- reply

May be mass usage of React should not happen at first place?
Well, it could happen with any popular library. Imagine if some breaking change like that would be introduced in jQuery when it was really widely used?

2024-06-21 01:55:51

- reply

I use typescript mostly because of:
1️⃣ it work more or less like compilation step, and prevent running broken code in most cases
2️⃣ It better supports generics than JSDOC's `@template` directive.
3️⃣ IDE's itellisense features love TS more than these JSDoc declarations. So with typescript i get some productivity boost than without it.
If vanila JS and JSDoc will give me that, I will not need TS anymore

2024-06-17 19:59:58

- reply

Beware flickering in Electron-based apps for some video cards, especially nvidia.