Hemingway's style had a lot of influence. It would not surprise me if text influenced by it is widespread in the LLM training corpus.

Look up the WW2 FP-45 Liberator. A bad gun you could use to get a better gun. Theoretically you only need to use it once.

https://en.wikipedia.org/wiki/FP-45_Liberator

I highly doubt that anyone who 3d prints a lower does so to “use” it (I.e. shoot someone) in order to procure a better firearm.

The FGC-9 was used extensively in Myanmar for that exact purpose. The rebels would set up ambushes with FGC-9's and recover better firearms for future use

https://en.wikipedia.org/wiki/FGC-9#Users_and_use

I would think they just print multiple guns and switch if one breaks.

Smalltalk keyword message syntax seems to be in a middle ground

Culturally they're not really the same organization. JPL has a different culture than Goddard, which is different than Marshall, etc.

I'm still of the opinion that the right direction is something architectEd more like NeWS with better underlying language support. If you're going to break stuff make it a real improvement.

We basically have it, it's called Blink (and it's a dumpster fire for unrelated reasons).

Did they get the sulfurous compounds out as well?

Did they do anything to fix the OpenSmalltalk VM lamentable keyboard input?

Have you looked at the tooling in Genera or other lisp machines?

In case you want to know more about them, they're called "Miller columns"

There was a browser that worked on Squeak 3, Whisker, that had some of these attributes. I used it up until it became unsupported. It took a little getting used to as its primary orientation was horizontal, but in the age of widescreen monitors that is an advantage.

Wiki description: https://wiki.squeak.org/squeak/1993

Archive of its homepage. Has an image of the browser in use. https://web.archive.org/web/20070228113449/http://www.mindsp...

Yes, Whisker is exactly what came to mind for me as well.

I don't currently use Smalltalk, most of my code is now written (and read) in vscode. The means available for showing the context around the code under consideration (splitting and resizing panes, hunting through lists of tabs, scrolling around) feel pretty crude by comparison.