blame-troi

This what I call peasant metabolism.

I have not but I’ll look. 90% of my computer use these days is laptop on my actual lap so I don’t have a real need. But there is a definite want!

A couple of years on Mounjaro here. Huge QOL benefits for me. I’m on it for diabetes but enjoy the weight loss benefits. I’ve read some articles saying that these meds are like the hotel California. Once on always on.

At my age this doesn’t bother me but I do wonder if there’s a lower maintenance dose that would work for those who got all the weight loss benefits they are going to get via medication alone.

At the risk of dating myself, I’m still looking for a keyboard as good feeling as this.

Different platform but the simplest mainframe utility IEFBR14, a noop process to trigger JCL events started as one instruction. Then two. Then debate started about which machine instruction should be used to set the return code to zero …

I've been struggling with this lately. My defaults are either 65 (8 1/2 wide paper, 6 1/2 text, leaves an inch either side for notes and hole punch), 72 (usable card image width), or 80 (because terminal were either 80 x 25 or 80 x 43).

My mainframe indoctrination there.

In terms of screen reading width, there's some sweet spot where characters per screen "page" and characters per line are easily readable without the text being "big". I need to be able to move my eyes left to right without losing track of my vertical position on the page.

Obvious to whom? We don’t all know everything. Also, rolling your own can be an interesting learning exercise.

Being both inspiring and unsettling to me says he did the job well. I will remember him as the smiling Pope.

Very cool. But so many of us paid not enough attention to the details. Only two of the people in my first shop attempted channel programming.

So the AI trained on Stack Overflow and Reddit and learned to say “Do your own homework”. I don’t see a problem.

Ignorant. When I learned COBOL, which would have been contemporary to many of the original systems, data types were numbers of various formats, characters, primitive fixed length strings, and bits. There was no data type for dates. It would have been roll your own. Pre UNIX being mainstream we used '7-4-5' dates in assembly based from 1900 (this was a financial business but not the IRS).

This isn't a COBOL issue (if it's even an issue at all), it's a data design issue. As many have pointed out, there are reasons for this possible origin date.

Oh come on! Let my people curse! Minority Report meets New Speak…

I find this to be a very reasonable license. Cost is low but provides an ongoing revenue source. I like free or perpetual licensing as much as the next guy, but us programmers gotta eat and pay the rent.

I’d like to think Trek watchers are smarter than that.

I certainly did not intend to ignite any flamewar. IMO both Emacs and (Neo)Vi(m) are fine editors. I wish more people would accept other people's right to have a personal preference.

My choice of Emacs was based on what I see as a fragmenting of (Neo)Vi(m) ecosystem. When writing extensions, I was uncomfortable with a "which of the three languages do I use" decision. The only common language is old Vimscript, and both forks are moving on from it and neither seems willing to support the other fork's preferred language.

That's their right, to be sure. It's just a deal breaker for me.