Ace: aceofspadeshq at gee mail.com
Buck: buck.throckmorton at protonmail.com
CBD: cbd at cutjibnewsletter.com
joe mannix: mannix2024 at proton.me
MisHum: petmorons at gee mail.com
J.J. Sefton: sefton at cutjibnewsletter.com
Chavez the Hugo 2020
Ibguy 2020
Rickl 2019
Joffen 2014
AoSHQ Writers Group
A site for members of the Horde to post their stories seeking beta readers, editing help, brainstorming, and story ideas. Also to share links to potential publishing outlets, writing help sites, and videos posting tips to get published.
Contact OrangeEnt for info: maildrop62 at proton dot me
DDR4 is mostly produced on older equipment than DDR5 and was not profitable - particularly with CXMT dumping DDR4 at below cost - so the plan was to refit the factories and switch them to DDR5.
But that's time-consuming and expensive and suddenly DDR4 is profitable again - very much so - so both companies plan to keep producing it at least through 2026.
The article that kicked off this typhoon in a tea cosy was actually talking about a research project investigating the use of AI in such tasks, not any intent to do so for anything in any fixed time frame. But it made none of that clear.
It uses eye-tracking to create glasses-free 3D images as long as there's a single viewer.
There's also a non-3D model if you don't need all those dimensions, a 5k 180Hz model that can boost up to 360Hz at 1440p, and a 600Hz 1440p model that can boost up to 1040Hz at 1080p.
We're talking about bat hearing levels of frame rates.
The LG 4k monitor I favour is now available in a 144Hz model - up from the standard 60Hz - with no other changes.
I might pick one up once I've paid off all the recent purchases.
The Radeon 780M GPU - found for example in the MinisForum AI X1-255 - loses 30-40% of its performance running in single-channel mode, if, for example, you pulled out half the memory from each of two systems to populate a compatible motherboard.
Even then it is faster than the older Vega 8 found in the Ryzen 7730U.
If you don't read the rest of this rant, I can sum up my advice as just this: if you're making a web project, even a simple one, do your rapid, many-times-a-day iteration loop testing on an older iPhone as your test mule. Yes this is a pain, because none of us are programming on an iPhone soft keyboard. We're sitting at a computer or laptop, and so that's the platform it's most natural to iterate on. Most frontend tools do not make it easy to have a quick edit-and-reload cycle with a real mobile device. So you'll have to either frequently push to a private web server, or use some exotic ssh tunnel contraption, to get it so that your test mule iPhone can view your test web project.
This is not because iPhones are good, it's because they're bad. iPhones are more peculiar and less compliant than any other device I tried. I promise that if you get your web project looking good and working smoothly on a crappy iPhone, your residual costs to test and polish on all other platforms and browsers will be fairly low. (For extra bravery, I recommend Firefox iOS instead of Safari, because it is the most buggy, least compliant browser I was able to find. If it works on Firefox iOS it's going to work anywhere. See below.)