Bandersnatch 2024
GnuBreed 2024
Captain Hate 2023
moon_over_vermont 2023
westminsterdogshow 2023
Ann Wilson(Empire1) 2022 Dave In Texas 2022
Jesse in D.C. 2022 OregonMuse 2022
redc1c4 2021
Tami 2021
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
Finally getting some time to set up my two new notebooks. Some quick thoughts:
16:10 high-resolution IPS matte panels are really nice these days. The smaller one is 14" at 2560x1600, the larger is 16" at 3072*1920. I have an older notebook with a 3840x2160 screen, but it's a glossy finish and the colours are more muted (plus it has huge bezels). The new screens are bright and vibrant without being oversaturated.
Four cores, 16GB of RAM, and 1TB of SSD just aren't enough for the work I do, but that's the limit of most small laptops. Fortunately the larger of the two has eight cores, 32GB of RAM, and a second M.2 slot. For the last four years I've been using an eight-core Ryzen system, and for three of those, two eight-core Ryzen systems.
I'm likely to supplement the laptops with a couple of NUCs running Linux, since I have spare RAM and SSDs just sitting around now.
Microsoft really wants you to sign in with an online account, and really doesn't want you to stop using Edge. I'm still using Windows 10 so it doesn't force the issue, but that day will come.
Disk space disappears fast and Windows doesn't tell you where it's going. Yes, sure, I did just install the entire JetBrains IDE suite, plus the Anaconda Python distro which chews up something like 3GB all by itself, but that still doesn't account for it all. And none of those apps appears on the Windows app list that tells you how much space they are using.
The author picked up an old JavaScript UI project - six months old, that he wrote himself - and tried to get it working.
It didn't work.
The fix for the problem caused another problem, and the fix for that broke things even more. The workaround for the fix for the fix failed because the library versions were incompatible and probably will be for a year.
The alternative was also incompatible, and the workaround for that was incompatible in a different way.
The solution to this didn't work, and the fix for the solution for the workaround for the original problem wouldn't even compile.