![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
The approach I’ve seen most is using semantic versioning for releases, and having a continuously upward counting (not bothering to reset) build number for everything in between.
The approach I’ve seen most is using semantic versioning for releases, and having a continuously upward counting (not bothering to reset) build number for everything in between.
Yeah. I’ve had mentors regail me of other tools they used alongside ‘Ed’, but I wasn’t listening very attentively. Hopefully that’s something that can be dug out of the history of the Internet.
I would definitely choose the old reliable stuff over something new and fancy, if I had this use case.
Sweet. Welcome to the cult of Debian.
We (Debian users and contributors) are inevitable. Our quiet satisfied computing cannot be stopped, only delayed.
We should consider getting some fancy robes and a few club houses, though. The only thing that can make Debian better is cookies and tea.
Delightful!
“Of course, on the system I administrate, vi is symlinked to ed. Emacs has been replaced by a shell script which 1) Generates a syslog message at level LOG_EMERG; 2) reduces the user’s disk quota by 100K; and 3) RUNS ED!!!”
Gave me a giggle. That 100k loss has got to hurt for a user who still tries to run ‘vi’ on a classic system, I imagine.
Edit:
Another gem:
“Ed is generous enough to flag errors, yet prudent enough not to overwhelm the novice with verbosity.”
The ‘ed’ editor was designed for high latency networks. I would pull on that thread. That is, in your shoes, I would read up on ‘ed’ and related tools.
Lunchtime, doubly so!
will tell you if a game supports the controller you currently have plugged in
Today I learned that. It never came up for me since I do most of my game shopping on my phone. That could be really helpful later.
Thank you!
Oh. That makes sense, I play mainly on SteamDeck, but I’ve been thinking of getting a Steam Controller for my PC, since the majority of what I’ve bought in the last year has been “SteamDeck Verified”.
It’s been tickling my brain that “SteamDeck Verified” badge also makes it a lot easier to tell how a game will act with a controller on PC.
There is no legitimate reason for this to exist.
Normally I would agree but this turned out to be the only way to protect the T800 model from the rigors of traveling via time sphere.
I’ve not worked with a marketing team where that would work, but maybe it will for some.
I’ve never been anywhere that I thought it would work, but it ultimately did, almost everywhere.
I’ve found it takes a few iterations, but the marketing folks in on it love being the ones who actually can reliably deliver on their promises.
It doesn’t work for the marketers that promise whatever they please without talking to dev, but I don’t find them to be worthwhile professional allies, so I don’t sweat it.
It doesn’t change the “massive customer will only renew if” scenario, though.
Very true. It doesn’t help with that case, and that one does happen. I’ve had the best luck saying “we don’t do that, but we’re scrambling to add it” in that situation.
The stupidly easy solution is to just give them stuff that has already been successfully delivered to production to market, 9 months from now. There’s invariably a huge backlog of years worth of successes that marketing wasn’t even aware of.
“No deviations will be approved from this year’s Agile product roadmap!”
We’re in a “fuck around” cycle where they pretend that the problem was we didn’t have “copilot”, and not that all of our development managers are wildly unqualified.
The “find out” part comes next.
Which is fucking impossible to fathom, because my fucking grocery store’s app can’t even implement search reliably, today.
I’m not sure how they’re going to manage to make things worse.
Actually, I’ll make a guess. My guess is we will go under the critical skill level needed for building safe hospital equipment, and we will get a rash of that stuff killing people due to lack of programmer skills.
I hope the asshole CEOs are the ones that die, but there’s not enough karma in the world for that.
“extra fingers, too many fingers, not toasted, bad anatomy,” got me. It’s perfect.
Also, your username is perfect for this moment.
NDISWrapper was a big turning point for me - the first time I got Linux working and kept it for the life of the hardware, it was due to NDISWrapper.
I hope I’m rocking that hard at 84.
My next non-alcohol bubbly drink will be in your honor, Larry.
Great summary bot, as ever. But missed this absolute gem from the comments:
“Thanks for helping me wardrive and steal the WiFi from that dentist, Larry.”
Blind faith in organizations claiming to protect our long held traditions makes us vulnerable to fascism?
I don’t like to jump to conclusions. I’m going to give it a few more films to see if the pattern holds. Lol.
I find this outcome delightful for all the compliance mandated organizations that are leaching with no intention to contribute back.
It could be really helpful for developers at pure leech organizations to make a case for being ready to contribute in an agile manner.
Now they’re all stuck waiting on either a good Samaritan, or their lawyers to get out of the way of progress.
I have little doubt that the fix has been committed to private forks dozens of times already, of course.