techbrovanguard

american exceptionalism at work

this is not the gotcha you think it is, you just dropped your gluestick

you’ve taken a slightly smaller shit on the floor than the seo slop factory next to you. do you want a medal?

> Tech pundits still seem to commonly assume that UB is so fundamentally entangled in C++’s specification and programs that C++ will never be able to address enough UB to really matter.

- denial ← you are here

- anger

- bargaining

- depression

- acceptance

Cope, seethe, mald, etc.

> 3) The overreliance on dbus turns the “the unix philosophy” ;) away. Text as a universal communication medium, everything is a file, etc.

have you considered the reality that the "unix philosophy" results in incredibly brittle systems? byte streams ("""plain text""") are untyped and prone to mishaps.

the second i tried writing go to solve a non-trivial problem the whole language collapsed in on itself. footguns upon footguns hand-waved away with "it's the go way!". i just don't understand. the "the go way" feels more like a mantra that discourages critical thinking about programming language design.

the greens could always use more votes

> The first rule of kremnology is that Russia always lies without a shame, as lies are usefull and they incur zero cost on the liar.

you’re describing international relations, none of this is specific to russia. people are indoctrinated from birth into nationalist propaganda. when these mouthpieces speak they aren’t lying, but it’s not the truth.

this is pretty obvious bait

i've seen a sharp increase in panzer tanks (f150s especially!) spreading like a plague throughout australian streets. can yanks keep their child slaughtering, pedestrian maiming, two tonne kill-boxes to themselves? every cunt with a disposable income has entered a nuclear arms race to prove they have the smallest cock while picking up groceries.

siri’s speech recognition and intent handling is so comically bad. as of late, for some unknown reason, when i ask siri to favourite the current song while driving it curtly replies that it doesn’t know which speaker i’m referring to. this used to work.

another fun problem is siri not recognising my speech despite me not having a particularly strong accent, speaking slowly, and enunciating. i’ve gotten into the habit putting on a valley girl or bbc news anchor voice while using siri since that usually works.

whoever is in charge of siri needs a reality check, the feature is borderline unusable.

this is a joke… right?

tangent, but you can’t send mail on ios with an idn because “the sender address was invalid”, despite it working in macos. i’ve read this is caused by a broken regex check. if any apple employees are reading please take a look

wowee, color me surprised

quality post from `throwaway984393`.

maybe too little memory safety means your wit overflows back to 0?

> I don't understand why people criticizing Rust tend so heavily to let perfect be the enemy of good.

if you've convinced yourself that you're special and all problems with c are solved by trying harder, clearly everyone else is just lazy. with that line of logic, there's nothing to fix with c. rust is not just redundant, but also aggravating, since its popularity causes the cognitive dissonance to start creeping in.

maybe i can make mistakes? should we improve tooling somewhat? no, it's the children who are wrong.

ah yes, the incumbents: Big DNS™. your suggestion is laughable, come back when you have a solution that isn't looking for a problem.

> To do anything interesting you will require unsafe blocks

this is just flagrantly false, have you no shame?

because it won’t—entertaining the question legitimises these snake-oil peddlers

did you have a crowdstroke while writing this reply?

pointing out the obvious? why are you upset i’m stating mixing hot oil and water will make a mess?

this all-or-nothing mindset is is reductive and defeatist—harm reduction is valuable. sure, rust won’t magically make your kernel driver bug free, but will reduce the surface area for bugs, which will likely make it more stable.

be the change you wish to see

> Well how much of those kernel-level drivers we rely upon ARE written in a memory unsafe language ??? Like 99% ? And we are not crashing and dying every day?

we shouldn't discount the consequences of memory safety vulnerabilities just because flights haven't physically been grounded.

> Also, quite frankly, if your unwrap() makes your program terminate because an array out of bounds isn't that exactly the same thing ? (program terminates)

this is a strawman, if you were writing a kernel-level driver in rust you'd configure the linter to deny code which can cause panics.

here's a subset:

- https://rust-lang.github.io/rust-clippy/master/index.html#/u...

- https://rust-lang.github.io/rust-clippy/master/index.html#in...

i've seen photos of the bsod from an affected machine, the error code is `PAGE_FAULT_IN_NONPAGED_AREA`. here's some helpful takeaways from this incident:

1) mistakes in kernel-level drivers can and will crash the entire os

2) do not write kernel-level drivers

3) do not write kernel-level drivers

4) do not write kernel-level drivers

5) if you really need a kernel-level driver, do not write it in a memory unsafe language

I'm glad Rob Pike didn't contribute to Go, that'd have been catastrophic to my productivity! Imagine having tools do work instead of users, it'd be like a world without lawyers. Anyhow, I've got to refactor my WIP code for the 10th time today since unused variables are compiler errors. Seeya!

Clearly, the solution is more neoliberalism.

If you want to call an async function from a sync context, use `futures::executor::block_on`. Nobody is forcing you to use async.

> It would have stopped virtually all of them?

Do you have a source for that claim?