cellularmitosis

I just Ed to say thank you for keeping your nibless posts from 2007 online. Handy for those of us doing a bit of retro computing on Tiger and Leopard. https://forums.macrumors.com/threads/developing-for-tiger-an...

Did you try putting a relative path into $PATH?

How is this an insanely common task? I literally never have to dink with $PATH on Linux, and only rarely on Mac because homewbrew has decided that certain executables shouldn’t be linked in by default.

I think the reason you are getting pushback is that you’ve proposed a complex replacement to a simple existing solution which basically just isn’t a problem. Most developers become allergic to complexity over time, hence the response.

It sounds like your actual problem is with the homebrew project, not with $PATH.

There's a kid on youtube (username 'dodoid') who put together a series of videos on SGI. Neat to see someone young get super enthusiastic about computing history.

Sometimes you don’t realize things about yourself until someone else puts it into words. Thank you, internet stranger

As an only occasional windows user, I certainly wouldn’t mind seeing such a list, maybe in a GitHub gist if you find yourself bored one day :)

I'll echo OP's frustration / lament. I have domain expertise in a specific platform, and it is pretty common that I'll see an answer which could use some clarification or additional detail about edge cases to consider. However, 1) I never ask questions on SO, and 2) I don't have time to wade through unanswered questions. As a result, though I would like to give them free labor by adding useful comments, I will never be able to.

The point is that SO is missing out here.

The real problem with having a sham mixed in with non-shams is that I've seen folks develop the attitude of "all recycling is a sham!".

For those not aware, recycling aluminum is absolutely not a sham. It takes about 2x the energy to make new steel than to melt down old steel. For aluminum, that energy difference is 20x!!!

This is why people will actually pay you to recycle aluminum, because running electrolysis through bauxite ore to make new aluminum is incredibly energy expensive.

Nice work! It captures the same fast, small-track feel of RC Pro-Am from back in the days of the NES.

"...or as I've taken to calling it recently, SAT slash LAPACK slash MUSL slash GNU slash Linux"

I'm much less concerned with this because github seems to have to lowest vendor lock-in of any platform. If you want to switch platforms, it should be as easy as changing your upstream and push. Switching from MySpace to Facebook never looked like that.

Though I love Swift, the transition from ObjC has left some warts in parts of Foundation / UIKit, and regular expressions are a great example of that.

In Python, I can use regex from memory. In Swift, I have to look up the docs every time. It would be nice to have it memorized.

Very interesting to see a Racket/Swift hybrid! Though this seems more of a strict front-end / back-end division, I was reminded at least initially of Shrimp / Goby from Mike Fikes https://github.com/mfikes/shrimp

But we are comparing the pain of searching vs the pain of having to re-run the help command for each possible subcommand, and parsing through all of that. Much easier to just have one command invocation and search through it.

There is a web analogy for this in how people organize FAQs. Some have a list of section links, and you have to click on a section to get the FAQs for that topic. Others just put everything on one giant page.

Here's the problem scenario with splitting things up into section pages: You think you see the appropriate section, but then you don't see your concern answered. There are two possibilities: either the organization was counter-intuitive and your concern was answered in one of the other sections, or your concern wasn't answered anywhere. And what's the only way to be sure? Visit every single section page and search through all of them.

Much, much less painful to just have it all on one page and search it.

I was about to say, it loaded pretty quickly and I found two interesting places right around the corner from where I live. If this is a "failure", I'd hate to hear how he classifies my personal projects...

Whoa, what a treasure trove! https://bernsteinbear.com/pl-resources/

Yeah, the problem / benefit is never the one framework you added / removed, it is the mindset of reaching for another dependency as a default which leads to a behemoth which no one enjoys working with.

Easier to write a rust compiler than a C compiler? I must be somehow misinterpreting this.

As someone whose idea of fun is trying to compile open source software on OS X / PowerPC, portability has a special place in my heart. While I view open source software as a "gift to the world", C89 + MIT is at the far end of the spectrum of how generous that gift is.

https://imgflip.com/i/89b05r

Think Different

"You should check out this thing" has a very different implied context than "You should check out this thing I made". The first sounds like a recommendation from an enthusiastic user, not from the the author. Because of this, discovering that you are the author makes your recommendation feel deceptive.

Ah, yes, my favorite sort of HN reply. The author puts in a lot of effort to precisely articulate an issue which is difficult to articulate, and a commenter just dismisses the entire thing with a vague "You're holding it wrong".

Yes, the "inverted pyramid" concept from journalism. Most important details up top, implementation details down below.

In our (Swift) codebase, this typically translates into "publicly-consumable interface up top, private and internal functions down below".

I stopped using [ a few years ago because ‘test’ reinforces the idea that this is just a command like any other, not syntax. Also, “man test” is much more pleasant that sifting through “man bash”.

One of the things which the racket fork added was resurrecting support for OS X on PowerPC. Very cool to be running the fastest scheme on my old iMac!

The question of "how long would a non-famous repository stay alive on github" is actually an interesting thought experiment.

That’s surprising — the education market seems like an even better fit for sharding: students and teachers generally stay within the context of a single school.

I’ve heard of university courses which are taught from original sources, ie teaching calculus from principia mathematica.

I’ve had a fantasy about the same approach for computer science: learn assembly on the Manchester baby, write a C compiler for the pdp-11, etc.

How realistic would the first bit be? Are there simulators and programming manuals for the Manchester baby?

Herb Sutter has a talk where he makes a pretty convincing argument that making a backwards incompatible change in your language costs you about 10 years in adoption

Reimplementing classic games (Pong, Tetris, Snake) sits at a great spot along the effort-to-reward curve.