PointyFluff

That's a thing, in Washington.

Meh.

wake me up for Emacs 42

ASCII has tones of unused chars we could grab for coding.

Is there an actual new source on this, beyond the Bezos Gazette?

this.

not the lame knock-off that is rimworld.

A single threaded heap of hot garbage-collection.

We use metric in the "American Space Program".

I cannot think of an engineering or scientific endeavor in the US that DOESN'T use the metric system.

The US is officially, metric; ansi converts back for the uneducated.

Here's a colorful video: https://youtu.be/SmSJXC6_qQ8?t=63

Here's boring government text: https://www.nist.gov/pml/owm/si-units-mass

Honestly, I think it's just silly that we are still trying to make these things on the ground.

pff...whatever.

I was a merely 4000 Meters from the moon's surface in KSP just lasts week.

I don't understand why sites like this are not HTTPS, yet.

I'm not giving you a security exception to read your blog.

Let's Encrypt is free.

A little early in the morning for so much alphabet soup.

LOL.

Far from the first RISC-V site.

As someone who's moved on to Rust, I see this as one long list of nightmares.

It's open source.

Put your code where your comment is.

I thought Fahrenheit 451 was supposed to be fiction...

Lime green is an objectively terrible background color.

Why do yo inject quotes randomly everywhere throughout the document?

Why is only 1/3 of the screen used for content?

Dammit, Jeff!

Stop buying up all the Raspberry PIs!

</jk>

I imagine this is to make Torvalds happy.

I found Nushell to be too buggy for day to day use, but I sure am looking forward to the day it's stable!

Hi. Medical professional here.

You are high if you think we are better off with paper than an ePCR.

Sometimes we have to default back to paper, some times the pt record system goes down.

When that does happen, it's a literal fucking nightmare in the ER.

We plan on it happening and we train for it happening, but ePCRs have made our lives so much fucking easier. Simple fucking fact.

Have you ever had to read the pissed off notes in a hand-written chart from the last nurse who has been working 48 hours straight, taking care of 12 critical care pts? Huh? Give that a try sometime.

Seriously?

Fuck off, Jeff.

Pay your FUCKING TAXES, Jeff.

You are an asshole, JEFF.

Presented like a true graduate of the Facebook School of Medicine and Immunology.

Not only are news articles like this terribly ignorant they are dangerous.

I'm all for freedom of speech, but when your speech hurts people there need to be consequences.

The name is cute, but I would change it out of concern of being sued by the movie industry.

Hello.

You've just described the Rust programming language.

May the Borrow Checker bless you and all your bits until the head-death of the universe.

Past Barry writes comments to Future Barry, so Future Barry knows what the fuck is going on and doesn't have to try and figure out the spaghetti-code Past Barry apishly bludgeoned into the keyboard with his penis-tipped meat-stumps.

Both Barry's think the other is an insufferable asshole.

Reading someone else's FP is like reading Perl, aka line-noise.

For all it's faults. C++ (along with other languages) already has an international standards body.

While a language made by committee is invariably garbage (citation: JavaScript), there is something to be said for stabilizing the standard for safety-sensitive systems like flight, space, medicine, automotive, and the ilk. Not a grate look if your space-balloon goes over like a lead-balloon.

Also, Rust is not something you can just "switch" to; it's not javascript or python. You have to UNLEARN a lot of bad nuns before you can truly be productive in Rust. Learning rust is a steep climb, coming from languages like C & C++; if you are coming from a language like python or lisp, it's a damn near smooth-vertical-shaft.

Frustratingly, a lot of the books for newbs are like: "So you wanna do this cool thing in Rust? Then do this tutorial project for this crate!", and they don't actually go over idiomatic rust algorithms. The way rust handles code and data, lends to "different" ways of solving problems. The best way to learn rust, is to read rust, but that can get confusing with the traits and typing bounds and lifetimes and unwraps. On the other hand you get to say "turbofish" a lot; so there's that, which is nice.

And so the issue becomes one of monkey-power. I can find bucket-fulls of hairless apes to bludgeon in C or C++ code, but it takes a more sophisticated `Ook<T>` to see the Octarine that is Rust.

That'll fix C++.

More standards.

Nothing better than a language designed by a committee of middle-managers with a half-warmed-over-IQ.