@svrjs I fear that a generation of web-devs have been raised that literally don't know how to do things without JavaScript and the bloat will never stop just as with app RAM bloat
@gameboycamera Hurts every time seeing what a waste the P-series was. It was barely usable on XP (Japan) and utterly unusable on Vista(!). Too many proprietary hardware gubbins means they're hell to get working and getting acceptable performance is insurmountable :(
#Frieren was incredible; I didn't think it was possible to create a series that set its own pace in this day and age. Now to catch up on Shield Hero season 3, which I can only compare to having a clown try warm up the crowd at a funeral for someone who died in a horrific car accident.
If I want to have any hope of learning to write #EPOC16 device drivers in the future, I'm going to need to learn x86 (specifically 8086 and NEC V30) assembly.
That is DEFINITELY not a Today Problem. It's not even a This Year Problem.
@thelastpsion If we consider an alternative universe is forked off at every decision, then we are in the reality where given every choice Intel made in the design of x86, they made the worst one.
@bread80@thelastpsion A company of too many hardware engineers and not enough software ones; if they weren't creating over-engineered designs that should have left behaviour to software (OOP in hardware!) they were making awkward and broken software interfaces (ISA)
I wonder if it's worth making a little interface using #FreeVision (the #TurboVision-compatible library that comes with #FreePascal) to display information about #Psion OO category (class definition) files?
Yes, I realise this is feature creep. But currently I'm outputting a lot of information to the terminal that the original CTRAN.EXE doesn't do. How much do I leave in as a "verbose" option, and how much to I move to a shiny TUI?
I love the idea that there are #PS4 and GTX 1080 PC players holed up in their gamer rooms that haven’t noticed the events of the last 5 years go by, still rocking the latest games like nothing happened
FINALLY. That was hell, but my Z80 assembler in Z80 now parses all Z80 opcodes (794!) and unlike other native assemblers it uses a static binary tree to match strings to opcodes so the lookup code is only 179 bytes and the table is 3'733 bytes! #z80#v80#cpm#retroprogramming#retrocomputing
Total size is currently 5K but it's not finished yet and the limit will be 8KB. Once complete I will rewrite it in itself meaning that you'll be able to assemble your #Z80 projects using a native Z80/CPM assembler, even on PC via RunCPM, rather than massive PC-only toolchains. Z80 software that can't be built on real HW is useless!!
Last year someone finally (after 22 years!) made a patch to disable the broken adaptive scaling algorithm from Max Payne's starting difficulty setting. Playing the game with it is like playing it for the first time. Final levels are no longer an exercise in patience and savescumming. I recommend it highly. https://www.moddb.com/games/max-payne/downloads/mpadaptivedifficultyremover
@dosnostalgic Oh man, that must have been hell. Max Payne was the last time I ever had a top-tier PC that could handle it maxed out -- PIII 1GHz and Voodoo5500. Of course, I've never been able to afford an up-to-date computer since and play games on a decade-long delay :P