Live data from Hacker News

Carefully but Purposefully Oxidising Ubuntu

jnsgr.uk

21–30 of 50 posts

Re: Carefully but Purposefully Oxidising Ubuntu

#23

Earlier quoted context omitted.

Haha, nah. I think hackers have been naming things like this since the beginning of time and it's absolutely part of the culture. I don't think everything needs to be corporate Memphis in text form. Let's have some squirrelfish extreme in this. Corporate mode comes eventually with quality. And Rust has passed the initial hurdle of adoption. It's pretty much what Python was in the year 2000: the exciting new tech that…

What is “corporate Memphis”?

A mysterious company in Illinois. If you sail your boardroom past Cairo there it is.

Re: Carefully but Purposefully Oxidising Ubuntu

#24

I don't buy that uutils will be a meaningful improvement for security. Though replacing GPL licensed coreutils with a MIT licensed alternative is not a good look for Ubuntu's support of free software.

It could be argued that it's not a good look for Ubuntu's support of copyleft, but MIT license _is_ free software, as per the FSF definition of free software.

Re: Carefully but Purposefully Oxidising Ubuntu

#25
post #16

"with an increase in security comes an increase in overall resilience of the system" This isn't within my realm of expertise.. but I find it a bit hard to believe that GNU Coreutils is a source of a lot of security and resilience issues with Ubuntu.. Is this true? Does anyone in the know, know if Ubuntu has any answer to the Nix explosion? I feel my Ubuntu problems are always weird package issue. The system doesn't m…

Debian definitely has packaging docs https://www.debian.org/doc/manuals/debmake-doc/index.en.html and it's not that hard to customize an existing package (at least I found it easier than using rpmbuild...).

Re: Carefully but Purposefully Oxidising Ubuntu

#26
post #3

I think more people might adopt this language if there weren't such in-group terminology like "oxidizing", "Rusteceans", pictures of rusty equipment etc. I still wish for a serious book in the style of K&R or Stroustrup with no pictures, no mentioning of the package manager at all (sometimes it is mentioned in the first chapter!) and interesting code examples.

The package manager is an integral part of how the language is intended to be used in everyday practice, so it makes sense that it would be mentioned in the book, though.

Re: Carefully but Purposefully Oxidising Ubuntu

#27
post #3

I think more people might adopt this language if there weren't such in-group terminology like "oxidizing", "Rusteceans", pictures of rusty equipment etc. I still wish for a serious book in the style of K&R or Stroustrup with no pictures, no mentioning of the package manager at all (sometimes it is mentioned in the first chapter!) and interesting code examples.

Haha, nah. I think hackers have been naming things like this since the beginning of time and it's absolutely part of the culture. I don't think everything needs to be corporate Memphis in text form. Let's have some squirrelfish extreme in this. Corporate mode comes eventually with quality. And Rust has passed the initial hurdle of adoption. It's pretty much what Python was in the year 2000: the exciting new tech that…

We tend to forget, being so used to them, but both C and C++ have playful names (C is a successor to B, and C++ is an incremented version of C)

UNIX also has a playful name (from Multics)

Re: Carefully but Purposefully Oxidising Ubuntu

#28

Earlier quoted context omitted.

Haha, nah. I think hackers have been naming things like this since the beginning of time and it's absolutely part of the culture. I don't think everything needs to be corporate Memphis in text form. Let's have some squirrelfish extreme in this. Corporate mode comes eventually with quality. And Rust has passed the initial hurdle of adoption. It's pretty much what Python was in the year 2000: the exciting new tech that…

What is “corporate Memphis”?

It's an art style that you'd recognize from thousands of slapped together 2000s web sites and PowerPoint slides. It's flat and colorful and a bit blobby. It has become a watchword for bland, boring, and approved by upper management.

Re: Carefully but Purposefully Oxidising Ubuntu

#29
post #3

I think more people might adopt this language if there weren't such in-group terminology like "oxidizing", "Rusteceans", pictures of rusty equipment etc. I still wish for a serious book in the style of K&R or Stroustrup with no pictures, no mentioning of the package manager at all (sometimes it is mentioned in the first chapter!) and interesting code examples.

The package manager is an integral part of how the language is intended to be used in everyday practice, so it makes sense that it would be mentioned in the book, though.

So if I am on a plane at 36,000 feet, I cannot start a new hobby project without paying for WiFi and downloading shit from people I don’t know or trust? That is just unserious, when your competition is the much more mature gcc+make+vim combo, which is 100% offline and self-contained.

And yes, I’ve done this (start a new project in a plane with no internet). Many times. eg: the world’s only PalmOS 5 device emulator (uARM-palm) was started while I was in a plane.

Re: Carefully but Purposefully Oxidising Ubuntu

#30

I don't buy that uutils will be a meaningful improvement for security. Though replacing GPL licensed coreutils with a MIT licensed alternative is not a good look for Ubuntu's support of free software.

It could be argued that it's not a good look for Ubuntu's support of copyleft, but MIT license _is_ free software, as per the FSF definition of free software.

FSF defined “free software” licenses other than GPL are “free for me, fee for thee”.
Post reply on HN