cogburnd02

GNU ls also has options to automatically add quoting to its output.

this is one fugly text file:

https://docs.fcc.gov/public/attachments/DOC-378593A1.txt

I've got both DOS 3.3 and ProDOS on 5 1/4 floppy. I can use ADTPro and I recently got (but haven't yet installed) an Uthernet ethernet card.

I'm looking for some kind of tiny ssh client I can squeeze into an Apple II. I'm pretty sure even dropbear is too big (I haven't actually tried yet, though so YMMV.)

Are there any other smaller SSH clients out there?

WTF? Why?

Then you're already in deep $#!+.

I mean, unless you're working in the leaning tower of Pisa, I can't imagine any change of tilt would be in any way useful.

Yeah when somebody says something like 'deeply embedded' the platform that comes to my mind is the Dreamcast VMU, which has a cpu that doesn't (AFAICT) yet even have a C compiler. ("C compiler....the idea was abandoned."--https://dmitry.gr/?r=05.Projects&proj=25.%20VMU%20Hacking) I doubt something written in Rust would be adequate for such a CPU.

There's a project called woob (https://woob.tech/) that implements python scripts that are a little bit like scrapers but only 'scrape' on demand from requests from console & desktop programs.

How much of this article do you think would apply to something like that? e.g. something like 'wait a second (or even two!) between successive hits' might not be necessary (one could perhaps shorten it to 1/4 second) if one is only doing a few requests followed by long periods of no requests.

Author could just write a script that takes slope input from a Wiimote attached to the back of the monitor & sets xrandr accordingly.

3DOF?

I legitimately laughed out loud at this.

yes, but using fewer horizontal pixels.

This.

I know the DEC VT340 was capable of 132 columns, as was an Apple II with a Videx Ultraterm card and a suitable (hi-res) monitor.

There are probably even more examples, but those two are what came to mind first.

Have an air gap between development machines and anything attached to the internet.

Or just put your machine in a bank vault.

yes.

> Unauthorized distribution prohibited. Link to this page, not copy it.

So, if I print it out on paper and give it to a colleague, that's copyright infringement?

What about if the page no longer exists and it got archived on the Internet Archive? Is accessing that copy a violation of copyright?

My favorite is probably this 8 bit card made to attach a vga monitor to the S-100 bus: http://www.s100computers.com/My%20System%20Pages/VGA%20Board...

There is also a 16 bit version: http://www.s100computers.com/My%20System%20Pages/VGA_16_Boar...

Or the giant person holding that iron wrong in a stock photo.

The Chicago sculpture The Bean (despite its appearance) is not a giant blob of solder.

I mean, this would be doable if one happened to own a daisy wheel printer or IBM 2741 terminal (which is basically a Selectric typewriter plus the circuitry to turn it into a terminal), that would actually be pretty easy to set up.

> (small, tasteful) ads

These did used to exist. They were called 120x60 px buttons.

Just a heads up: name collision with the default shell on (now Apache) Nuttx.

http://nuttx.incubator.apache.org/docs/latest/applications/n...

I suppose an epub would be pretty easy to convert (on a modern machine) into something like ZIL for ZILF. Good thinking.

Would be great if there were files available for the Z-machine that played out the original Edward Packard CYOA series, like Through The Black Hole, e.g.

I had not heard of the FastChip before today, so thanks for letting me know it exists. :-D

for other interested parties:

http://www.a2heaven.com/webshop/index.php?rt=product/product...

Would be interesting to have some -small- (not necessarily small, but portable) C program such as info-zip compiled to bf via ELVM [1] and do a speed comparison.

https://github.com/shinh/elvm

'meraki' or whatever my job is using seems to think it fits in the category 'illegal'. Ha!

> I'm bothered by this comment.

I'm sorry you're bothered by my comment; it's simply an expression of how I feel.

> PICO-8 is one of the most vibrant communities in existence for beginners making games. Thousands of people have made thousands of games with this software....licensing allows people who purchase the engine to distribute it in their own games.

Windows is also very popular, and it is also proprietary software. It enables lots of other people's jobs to exist, but that doesn't mean that it's ethical to deprive its users of the source code to the software that's running on their machine.

>The price point to purchase is extremely cheap, supports the person that created it...

I don't have a problem with donating money to help out a project; I have a problem with the software not respecting the four freedoms (liberties) of free software. (https://www.gnu.org/philosophy/free-sw.en.html)

> It is one of the most open, empowering, user-supporting pieces of software...

It isn't open and it isn't user-supporting or empowering. Users don't have access to the source code, and in that way the developer holds power over the users. Bruce Perens, who really popularized the idea of 'open source' once said "When I say 'Open Source', I mean the same thing that Richard means when he says 'Free Software'."

> there are plenty of open-source projects that are actively user-hostile.

would you like to provide some specific examples?

> aren't saying that out of any interest for how that would make the project better or create a better community, but instead are saying it from a standpoint that only considers how it would benefit them personally.

A better community would be able to improve the software itself with access to the source code. Also, simply because it-being-libre-software would benefit me personally doesn't mean it wouldn't also benefit the rest of the community equally as much.

I never said I had a problem donating money to help; what I have a problem with is lack of access to, and lack of share-ability (not sure if that's a word, but I'm going with it anyway) of the source code.