bleistift2 @ bleistift2 @sopuli.xyz

Posts

61

Comments

903

Joined

1 yr. ago

For others like me who have no clue what this meme is about:

In 2016, a 3-year old got into the Gorilla enclosure, where he was grabbed and dragged around by a gorilla, Harambe, which was then shot.

PrOtEcTiNg ThE sUpPlY cHaIn Is ImPoRtAnT tO uS. tHeReFoRe We NoW fOrCe 2Fa On YoU.

Every bug falls for this at most once.

I never said that it was impossible for a farmer to learn things outside their immediate field. Just like computer programmers often have knowledge of hardware and the general technology stack.

My point, to make it explicit to a few of the illiterates who’ve replied to my comment so far, is that it is not necessary to teach a web developer how a goddamn CPU works. They can gain nothing from that knowledge because there are at least 3 levels of abstraction between JavaScript and assembly.

You don’t teach a farmer how an internal combustion engine works. Computers are tools to software engineers. What they need to know is how to operate them, not how to maintain them.

That’s the price of specialization. Don’t ask a software engineer to troubleshoot hardware. Don’t ask a backend dev to write a frontend. Don’t ask a proctologist to look at your cough.

You simply cannot be proficient at every sub-sub-specialty. That’s why we collaborate and hand the ‘my computer gets hot’ problems to the hardware people. The alternative would be only moderately useful generalist.

I thought C++ was meant to get rid of C’s footguns?

Even if querying data was processing-heavy and even if somehow the ‘hard drive’ got warm during this, then there still would need to be a hardware defect in order for the drive to overheat.

“And the mitochondria”

“Is the power house of the cell”

Children cheer in applause and repeat it, because it rhymes.

Where the hell is the rhyme in this?

I must admit that I’m more harmed by this image than I thought I would be.

How about with a friend?

I give my users instructions on how to report an error if they seek assistance. It’s regularly ignored. Instead we get the ubiquitous “Something bad happened … somewhere. HALP!”

This looks more like an extended table of contents, where you get introductory paragraphs instead of just the headings. Much preferrable, IMHO.

You can’t do that when things are above/below.

You obviously have never been near a tree with a singing bird in it. You can definitely tell that the sound comes from above. That’s because the shape of the outer portion of the ear somehow funnels the sound in a way that makes it possible for the brain to determine the origin of the sound.

WTF is going on on that article’s Talk page? Are teachers now assigning students to edit Wikipedia articles and have others “peer review” them?

My neck wishes this weren’t so true.

What benefit does the dispenser bring, exactly?

Is there any evidence for what was actually removed or do we have to take this guy’s word for it?

Without the Google Search deal, Firefox will have less resources to build a competent browser.

Firefox has neglected their browser for years, pursuing vanity features like pocket instead of implementing web standards.

That sounds like you ran into problems when deserializing a number value from JSON, which then got slightly changed due to floating point shenanigans. That’s technically not JSON’s fault. JSON numbers aren’t IEEE754. They’re just numbers. It’s only the deserializers that usually choose to represent JSON numbers as floating point values.

Quoting https://www.rfc-editor.org/rfc/rfc8259#page-7

A number is represented in base 10 using decimal digits. It contains an integer component that may be prefixed with an optional minus sign, which may be followed by a fraction part and/or an exponent part. […]

A fraction part is a decimal point followed by one or more digits.

Numeric values that cannot be represented in the grammar below (such as Infinity and NaN) are not permitted.

This specification allows implementations to set limits on the range and precision of numbers accepted. Since software that implements IEEE 754 binary64 (double precision) numbers [IEEE754] is generally available and widely used, good interoperability can be achieved by implementations that expect no more precision or range than these provide, in the sense that implementations will approximate JSON numbers within the expected precision. A JSON number such as 1E400 or 3.141592653589793238462643383279 may indicate potential interoperability problems, since it suggests that the software that created it expects receiving software to have greater capabilities for numeric magnitude and precision than is widely available.