I wonder how that parallel universe would have looked like where the gnome part of Xamarin inside Novell would have partied with the kde guys at SUSE towards shared components.

the only reason kde wasn't dead right there was the solid kde market share in corporate linux gui deployments at the time. and then came the Novell Microsoft (Balmer days) deal, "look, Linux desktop doesn't make any sense...".

Linux desktops were doing amazingly well in "kiosk" deployments, hundreds and thousands of very similar centrally managed workplaces. think selling tickets, showing time tables, atms, think sears or the likes (it was those days)

but I get astray

how would a universe look like where Xamarin and SUSE had had the phantasy to see gnome and kde synergize instead of cage fight?

sigh, a woman may dram...

I love the animal-owner analogy of owning something and being responsible for what it does when set loose. the concept is the same in todays Germany. you own a pet, and if it's friendly it's all nifty but if it creates my damage, the owner is liable. not the person who guided it at the time. no. the owner. "Halterhaftung"

is it ok if I skip the Uber part? I think that leads as try s evidenced by the other reactions.

the "who is liable for the damage an ai creates, in the hands of an incompetent or even malignant guide?" question is fantastic. and who "owns" an ai?

non native speaker here - I don't get it.

It's an old English word (predating the sexual connotation):

cum - Used in indicating a thing or person which has two or more roles, functions, or natures, or which has changed from one to another.

Basically nobody uses that language construct anymore until you run headlong into it in a Hackernews comment or something

thank you! this was most helpful to lead me into asking the right question.

https://share.google/aimode/dDekJEZzfKaE6FCvH

I use it, but you're supposed to hyphenate on both sides so this usage was incorrect.

“cum” (rhymes with “broom”, rather than “dumb”) is Latin for “with”.

that's when it appears cum "laude" (eg)

in commonwealth (seniors in everyday UK, HR and pedants otherwise) usage it rhymes with dumb, like you'd expect

https://youtu.be/RzESsmv5FhM

Radcliff-cum-Chackmore

No it isn't. It's Latin.

only the ethymology is latin. the use combining role names is old English, indeed.

'cum' is latin for 'with', and it is commonly hyphenated when inserted in between other words.

It's also a slang word for semen, but that's not relevant here.

I suspect they mean "with" but in latin. But I'm not entirely sure.

That's correct

confusing indeed. I wondered "which RAM? nvram? dram? vram? dram? now what's g-ram?"

GPU RAM, clearly. At least that's where my mind went.

Pretty sure it's "GNU Is Not Unix Rapid Access Memory", actually

GPURAM is Probably Unix Rapid Access Memory

We already have VRAM for that purpose, thankfully.

ah that's the actual paper the OP is about! took me a bit. thanks for the link.

(1964)

a webcast about the many great benefits of the novel DASD (direct access storage device) over ISAM (index sequential access)

aka disk and tape.

16mm film

Flipchart

impeccable presentation

thx for the time machine :-)

DASDs supported ISAM.

And they're not strictly just a disk. It's more like a complex multiplexing system for an array of disks. It has interesting capabilities like "channel programs" that persist to this day which allow you to send miniature programs to the disk controller to have it seek out the precise record you're looking for in one of several access modes.

IBM still provides almost the entirety of it's OS documentation online:

https://www.ibm.com/docs/en/zos-basic-skills?topic=set-what-...

> send miniature programs to the disk controller to have it seek out the precise record you're looking for

A very long time ago, a guy I used to work with was porting a sales and stock control database he'd written on the Commodore PET to a PC. By then he had a 286 with a 20MB hard disk and 2MB of RAM to play with - whopping stuff! - but his original program would assemble up a query routine, and transmit it to the 6502 in the PET disk drives over HPIB. Then it would chunter away discovering the records it needed to construct a reply while the host computer could continue working as normal. It was absolutely genius stuff, and it made the whole system seem really responsive even though in reality it was pretty slow.

ISAM in all important variants pretty much required DASDs, CKDs (Count Key Data) in fact as opposed to FBAs (Fixed Block Access - which act like normal drives people are familiar with)

Tapes don't provide CKD interface and thus do not work with ISAM.

Why do you think that the presentation was done in 1964?

On Youtube there is no mention about the date.

OS/360 was announced in 1964 but it was first delivered more than a year later.

I doubt that such presentations were done about a product that no customers could use and which might still be changed until the first deliverable version.

So I believe that it is unlikely that this presentation was done earlier than 1965 and it is likely that it was not done before 1966. The first OS/360 versions were delivered in November/December 1965.

The earlier video from the series, GG46955 IBM SYSTEM/360 READ ONLY STORAGE, is dated to 1964

https://www.youtube.com/watch?v=gcc_SAy-I80

If the videos are indeed so old, then probably they were not intended for customers but for the internal training of IBM employees, which would match the "CONFIDENTIAL" label.

Indeed, he actually adresses that in the first video

>This presentation is one of a series which is intended to present you the systems engineer and salesman some of the advantages of Systems/360

paip=Paradigms of AI Programming

I'm positively surprised such a little guidance makes such a difference.

is it also useful with the smaller (and cheaper) cloud models?

Yes. I run local models, Qwen3.6-27B and IMHO the massive level up was the agents and skills files that I've worked on.

Basically I run a flow

Brainstorming > Create Spec > Review Spec* > Create Plans > Review Plan* > Execute Plan (in subagents) > Review Against Plan > Code Review* > Open PR > Finish Plan (marks plan files done)

* Each review step marked with an asterisk uses a paid larger LLM, right now Deepseek V4 Pro. Having it do this catches a lot of small things, and now I'm effectively one shotting any task I give it.

And it's not costing me much at all, just those three reviews. I could use a free model like Gemini but I'm happy with what I've got.

Would you mind sharing your HW configuration? Thank you.

Sure. It's just an old I7 8700 (non-k), 64gb ram. Running proxmox. But recently I put an AMD R9700 AI Pro, in there which is a 32gb inference focused card, think of it as a 32gb version of a 9070xt.

All the inference happens on that card, so the CPU/RAM is there for the other containers.

I'll eventually swap the motherboard and CPU for something better, so I can fit 1 or 3 more of those cards.

Why not NVIDIA? 32gb on team green means spending crazy money. And I can get 4 R9700s for the cost of one 32gb 5090.

128gb ... Vs 32gb.

Right on target

with an unexplained circus trick the article jumps from Barnum's 20 rules to "here are the four core principles" --- why these four?

I love project Gutenberg to provide the rest. it's a short pamphlet:

https://www.gutenberg.org/files/8581/8581-h/8581-h.htm

Thank you for the link - I was just thinking that there were some core principles missing imo and yet there they are in the full text

For me "Persevere" is probably the main one, many people in the comments here mention the difficulty of making it in a niche field, one that you love and are good at. Personally I lived in a tent/garage for 5 years before finally becoming successful.

Also "Location" resonates. I had to move to a new city when I was starting out due to over saturation in my field at home.

most specifically the problem is that markdown tables don't allow breaking the table row in multiple lines

but then you can always use HTML tables in markdown and Pandoc transforms it just fine

<br> has worked fine whenever I’ve needed line breaking in markdown tables

I think they mean breaking the line in the markup, not the output

yes, that's what I meant, indeed.

They mean in the Markdown code, not in the output.

Every markdown implementation is supposed to allow inline HTML.