Earlier quoted context omitted.
I propose that developers are allowed to use it in production... so long as they do all the development work on a 9600 baud dialup with a VT102.
A few years ago, a submarine cable was knocked out, between our startup's MVP servers in Singapore AWS, and our networked factory stations in Asia. In lieu of the submarine cable, something closer to a wet string was being routed over. It had such high latency and packet loss, that a watchdog timer I'd implemented on the stations was timing out. Fortunately, the remote access we'd built into our stations (SSH and Ope…
TTE: Terminal Text Effects
221–230 of 279 posts
Re: TTE: Terminal Text Effects
#222Earlier quoted context omitted.
That's a delightful thing you've made. Have you added a command-line switch for the direction of gravity? Some of the animations (eg Pour), could fall up the screen instead of down it. That way, the user can start reading the text immediately.
ls -latr | tte pour --pour-direction up I have not implemented gravity, haha. I have actually worked on a custom terminal game engine in the past and realized with TTE I am very small amount of scope creep away from landing in that territory again. I promised myself I will not implement physics or collision. Keeping it simple. That being said, as with the example pour syntax above, all of the effects have a ton of co…
3d... 3d... 3d... you know you want to.
Re: TTE: Terminal Text Effects
#223Re: TTE: Terminal Text Effects
#224Earlier quoted context omitted.
Smart, and not something someone would realize if they'd been too insulated from how things work. Regarding planes/cafes/guest/etc. WiFi, I now usually put any "emergency remote plumbing access" on port 443 (though usually not HTTPS), to reduce the likelihood of some random non-SPI ruleset blocking us in an emergency.
I think that by 2050, 443 will be the only port used by applications that require a non local connection, because the chance that some participant in the network has blocked any other port is simply too high.
Re: TTE: Terminal Text Effects
#225These effects would pair really well with an old school bbs/mud simulation.
Re: TTE: Terminal Text Effects
#226Earlier quoted context omitted.
I'm very glad that TCP is so robust. I'd take a solid 300 baud connection over a spotty cellular connection during most emergencies. Having worked and played on flaky high-latency and low-throughput networks much of my life, I mostly visualize things in my head—as you likely mean by 'command-line-and-editor-when-you-feel-every-byte-transmitted'. Open a connection and queue your commands; wait for output. It works if…
> local script [...] nohup [...] redirect output to a file mosh hostname -- screen -S philsnow I don't think I've had to use this over a truly terrible connection, but mosh worked a treat a ~decade ago while tunneling through DNS from a cruise ship that charged exorbitant rates for wifi while underway, but which allowed unlimited DNS traffic. > It works if you don't make any typos mosh helps a bit with that too: you…
Re: TTE: Terminal Text Effects
#227Re: TTE: Terminal Text Effects
#228I love terminals, but I have to say, I kind of hate this sort of thing? Where you need at least 256 colors, GPU acceleration, and 240 columns x 80 lines? At that point it's just a curiosity, anywhere you could do that in a terminal you could do it easier and better in a graphical window. I want my terminal apps to actually still work in an 80x24 monochrome VT220 at 19200 baud. I want them to use termcap instead of ha…
Re: TTE: Terminal Text Effects
#229I'm imagining several genres of text based adventures that could make very good use of this library. Cyberpunk, fantasy, and horror. Very subtle uses of this could go a long way.