bearskins

To this day the debugging situation on Linux is still stone knives and bearskins compared to what VS offers.

Clearly you have never met a tool which afterwards made you regard all other supposedly similar tools as stone knives and bearskins.

The difference with bearskins and crystals is you can measure and contrast effects.

I've been trying to fuse my stone knives and bearskins, but I fear I will never craft a tricorder.

Debugging by printf() is only extant because the debugging tools generally available under Unix are stone-knives-and-bearskins compared to other environments (Windows comes to mind).

Many of the practices that were ruled illegal in your crystal-spires-and-togas utopia are alive and quite well in the stone-knives-and-bearskins hellscape across the pond.

But they lift the rest of us beyond starting from scratch with flint and bearskins, so it shouldn't be dismissed just because it isn't universal.

I was kind of expecting a piece about how stone-knives-and-bearskins mathematics was before The Wolfram single-handedly brought fire down from Olympus.

A primitive, stone-knives-and-bearskins language model, but a language model nevertheless.

I have been to the land of stone knives and bearskins, and I am so very grateful we don't still live there.

I'm telling you it's no better than bearskins and sky gods.

There'll be casualties along the way, but it's a lot better than being stuck in the dark ages blindly trying to repair neurological problems with stone knives and bearskins for another 3 generations.

XEmacs only came about because Lucid needed a front end to their IDE, Energize, which was extremely comprehensive and could even do "edit and continue" style development of C++ on Unix but, as jwz has it, the Unix community preferred its stone-knives-and-bearskins approach with command line tools.