@tindall

MJG's observation that Microsoft has been much less effective at securing their boot process than the FOSS community makes a good argument for forcibly removing them from stewardship of this standard and giving it to a more neutral industry body. It may not fly in North America but I could see the EU requiring it.

@ajroach42

Needs 70s metal album cover mural.

@neauoire

"'Cloud sevices are going to be big!', says CEO of cloud services company."

@loke @ne1for23

<shitpost>Ruby is sufficiently Lisp.</shitpost>

@loke @ne1for23

Also: Atwood has said in a number of issue threads that the point of this is to be an aid to new programmers so he's going with common, accessible languages.

That being said, there's nothing stopping you from forking the repo and adding APL, J, K, Scheme, and Haskell to it.

@ne1for23

BTW, Jeff Atwood is crowd-sourcing rewrites of these games in various modern languages. I've done a couple of Ruby versions and it's an excuse for a fun little hack.

https://github.com/coding-horror/basic-computer-games

@silico_biomancer @RobinHood

Apparently, history shows this to be false:

https://acoup.blog/2020/01/17/collections-the-fremen-mirage-part-i-war-at-the-dawn-of-civilization/

@eyeling @dch

Wait, so this is straight infrared? You didn't photoshop in a natural-light picture of Balu?

@maxeddy

In the mid-late oughties, I'd rip 8-ish hours of Radio Paradise to 64kps MP3s and put them on a cheapass flashdrive player. This thing had three buttons (play/stop & volume) and one LED. I'd leave it in the car connected to my cassette player via one of these and listen to a wide(-ish) variety of commercial-free music while I drove.

And because the player didn't have a display, I kept a printed one-sheet track list I'd generated with a Perl script from the metadata.

@stsp @meena

It seems to be that it'd be easy to design a git workflow that mimics the current tools and just teach the git process in terms of how it relates to that, e.g.

svn co -> git clone
svn merge -> git pull
svn commit -> git add + commit + push

etc.

More motivated users can figure out the extra capabilities on their own, but even with the above mappings, you benefit from being able to roll back a botched merge.

@stsp @meena

Yeah, but that's like complaining that C lets you use different indentation styles. If it matters, you write out a policy and require people to stick to it.

And in the case of git, it's pretty easy for an individual developer to use it however they wish on their own machine before coalescing their changes into something that conforms to the project's policy.

@meena @stsp

The way to teach git is to first teach the underlying model. (Object IDs behave like pointer values; branches are linked lists of change sets; branch names are just a named box holding the object ID of the latest commit.)

After that, the quirks kind of make sense as handy shortcuts.

(You need to know a small amount of computer science to get this, but it *is* a software development tool.)

@clacke @paul @neauoire @futzle

It's definitely more nuanced than my previous toot would imply.

Although if I were going to reduce it to a single driving factor (because reductionism is one of my bad habits), I'd attribute it to Moore's law training people in the 90s and 00s that today's computer is always going to be dramatically better than last year's computer. Those days are long past but the industry keeps faking it by ending support and increasingly desperate gimmickry.

@futzle @paul @neauoire

It doesn't really, just because conspicuous upgrading is considered a sign of wealth. But we want to shift perceptions to a place where it does.

@paul @neauoire

I'd rephrase this as something more like "get used to buying high quality electronics that will last a decade or more."

Same idea, but sounds better.