Jordan_U

joined 1 year ago
[–] Jordan_U@lemmy.ml 6 points 5 months ago

Find the mutual aid networks in your community and join / support them.

Just generally be in community with those around you.

Join or form local weekly protests for a permanent ceasefire.

Join a union and encourage others to. Help ensure that your union has enough resources to provide support for more vulnerable members when they need to strike.

Run for local office.

[–] Jordan_U@lemmy.ml 2 points 6 months ago* (last edited 6 months ago) (1 children)

I quite happily run HAOS on my raspberry pi 3 to control the lights, my Roomba, and various other devices in my home.

Interacting with it via the home-assistant Android app, or the web interface, I'm never waiting for anything, and interacting via mosh is quite pleasant.

Part of what makes Linux nice is that you can use just what you need.

If what you need includes something like a web browser, then yes; 4 GiB of RAM is going to be a bad time, and 1 GiB is going to be unusable.

[–] Jordan_U@lemmy.ml 1 points 7 months ago

No.

This is a vulnerability which allows bypassing secure boot protections. You have already manually bypassed those protections by disabling secure boot.

[–] Jordan_U@lemmy.ml 56 points 7 months ago (1 children)

No single person should be your moral barometer.

Stanning is bad.

(I also appreciate everything I've heard of Greta Thunberg saying and doing.)

[–] Jordan_U@lemmy.ml 12 points 7 months ago* (last edited 7 months ago) (1 children)

A concrete example of this is doctors and hospitals creating guidelines about how to triage care when ICUs were/are full because of unmitigated spread of COVID.

It is definitely an "interesting" phylisophical question to ask:

"If a long term ventilator user comes into the ICU, with the ventilator they own and brought from home, and they are less likely to survive than an otherwise healthy young man who needs a respirator due to COVID infection, is the morally best choice to steal the disabled person's ventilator (killing them) and use it to save the young man's life?"

The policy question that should be asked instead, and never really ways, is "How do we make sure that we never get to the point where we have so many people in the ICU from a preventable disease that we run out of respirators and need to start choosing who to let die?"

This is not just a hypothetical question:

https://www.reuters.com/legal/government/long-term-ventilator-users-lose-bid-revive-suit-over-ny-emergency-guidelines-2022-11-23/

Disabled people continue to plead with us for the bare minimum, like requiring doctors who work with immunocompromised patients to wear N95 respirators while treating those patients.

We continue to chose to stack more people on both sets of tracks instead.

[–] Jordan_U@lemmy.ml 2 points 7 months ago

Either way, this is a rule that you as a human are required to follow, and if you fail the compiler is allowed to do anything, including killing your cat.

It's not a rule that the compiler enforces by failing to build code with undefined behavior.

That is a fundamental, and extremely important, difference between C and rust.

Also, C compilers do make optimization decisions by assuming that you as a human programmer have followed these strict aliasing rules.

https://gist.github.com/shafik/848ae25ee209f698763cffee272a58f8

Has a few examples where code runs "properly" without optimizations but "improperly" with optimizations.

I put "improperly" in quotes because the C spec says that a compiler can do whatever it wants if you as a human invoke undefined behavior. Safe rust does not have undefined behavior, because if you write code which would invoke UB, rustc will refuse to build it.

[–] Jordan_U@lemmy.ml 1 points 7 months ago

It has already been translated into rust. Python wasn't ever intended to be used in the "real" driver, but I thought it was a fun anecdote none the less.

[–] Jordan_U@lemmy.ml 1 points 7 months ago (2 children)

To put it another way:

Strict aliasing is an invariant that C compilers assume you as a developer will not violate, and use that assumption to make optimization choices that, if you as the developer have failed to follow the strict aliasing rules, could lead to undefined behavior. So it's a variant that the compiler expects, but doesn't enforce at compile time.

I guess it is possible to just disable all such optimizations to get a C compiler that doesn't create UB just because strict aliasing rules were broken, but there are still many ways that you can trigger UB in C, while safe rust that compiles successfully theoretically has no UB at all.

[–] Jordan_U@lemmy.ml 0 points 7 months ago (4 children)

By refusing to compile any code that has undefined behavior. This is what rust's compiler does, and is simply not possible for a C compiler to do.

[–] Jordan_U@lemmy.ml 1 points 7 months ago (1 children)

The comment I was replying to was specifically talking about autism.

" I think that's the "proper" term. I mean what's been known as low end autism or asperger)? "

view more: next ›