I've always wanted a Vectrex. With the new board we made (appletini.org) and the alternative firmware called "multitini" I can finally have one, along with a C64 and Gameboy Color.
Young people don't understand the levels of abstractions that exist in modern computers, and how slow everything becomes. Here is a thread of the boot speed of a 1983 Apple //e coupled with an Appletini ONE card which makes it run at 33MHz... a turtle by today's standards
For anyone with an Apple //e: appletini.org
Coming in September.
ONE physical card with:
33MHz TransWarp, 8MB RAMWorks, beam accurate HDMI, Smartport, DiskII with WOZ, Phasor, Z80, mousecard, Uthernet II, SuperSprite
Copy protected (WOZ) of our boxed Ultima V from '89 running on a physical //e accelerated via Appletini ONE.
The DiskII FPGA code runs at the speed of the processor (33MHz) and I have forced the virtual Transwarp to disregard U5's use of $C074 that tries to slow it down to 1MHz.
Apple's 50th Birthday - A gift you can give the community - Sign the Petition! c.org/59jxDGjFfk via @Change
I completely agree. The platform should make it easy to filter and choose what you want, and only "curate" against malware and spam.
This is a genuine missstep. It is not the job of the platform to critique the quality of the game; it is their job, however, to ensure we don't buy malware, that the products are safe.
It is the job of reviewers to curate a game's quality, not the job of the storefront, as what may be "Junk" to one person is a "Gem" to another. By denying indies an oppurtunity to fail, it also equally denies them a chance to succeed.
That is the STRENGTH of Steam, not a weakness.
RikRetro retweeted
Can we talk about how Vanilla WoW's Trees are the best lowpoly trees ever? This is 199 tris.
They really just woke up one day and chose excellence.
RikRetro retweeted
You wanted JavaScript developers to write desktop software and you got JavaScript developers writing desktop software
Why is pasting into VSCode Terminal slow? Because it sleeps for 5ms every 50 characters.

ALT + // Writing large amounts of data can be corrupted for some reason, after looking into this is + // appears to be a race condition around writing to the FD which may be based on how powerful the + // hardware is. The workaround for this is to space out when large amounts of data is being written + // to the terminal. See https://github.com/microsoft/vscode/issues/38137 + const WRITE_MAX_CHUNK_SIZE = 50; + const WRITE_ INTERVAL_MS = 5; + export class TerminalProcess extends Disposable implements + + + + + + // Queue the next write this. writeTimeout = setTimeout ( () →> { this. writeTimeout = undefined; this._ startWrite(); WRITE_INTERVAL_MS) ;



















