Show HN: Reviving a 20 year old OS X App(andrewshaw.nl) |
Show HN: Reviving a 20 year old OS X App(andrewshaw.nl) |
Source: my first released Mac OS X app came out in 2003. https://github.com/aaronbrethorst/irooster
I was even kinda okay with the [callee verbingTheSubject withFooValueBeing 7 andBarValueSetTo "good argument"] but that was just too much.
https://docs.ankiweb.net/deck-options.html#learning-steps Details what _actually happens_ when you pick again/hard/good etc. I much prefer understanding this to the vibes-based approach of “did you pause before answering”.
Secondly turns out you can indeed very easily set up type-to-answer in a deck by editing the front template and adding
{type:Field}
where field is the answer part of the card’s data.
So… I’m actually using Anki again. I’m still very happy I did this, it was a fun little journey!
On a similar note, a few months ago, I took over a 14 year old Objective-C iPhone app called Painteresque and brought it back to life. Discussed here:
https://news.ycombinator.com/item?id=43222099
If OP is interested, maybe I can help with the Sandbox issues or having it published on the Mac App Store?
I’d definitely be really grateful for help with that! I’m not planning to publish to the Mac App Store, but it would be great to have the build step a bit more compliant with current practises.
Turns out it changes based on light/dark mode.
[1] Macromedia Dreamweaver 4 is the fourth major version of Dreamweaver that was released by Macromedia on November 27, 2000.
I had to clock "enable 640x480" compatibility mode and I need to directly run the EXE (the wrapper launcher doesn't work) but otherwise it works fine.
There are some reimplemetations like dgVoodoo2 and DXWrapper but they can be pretty buggy.
A couple years back on Windows 10 I successfully installed and used a PCB layout tool from 1998. I was shocked at how smooth it went. I think it needed to run as administrator but otherwise zero issues.
Trying to add ARM desktop to the mix hasn't indeed been easy, because of backwards compatibility efforts, most folks don't care about Windows ARM laptops.
Pocket PC/Windows CE also had ARM/MIPS variants.
Win16 is only supported up to Windows 10.
Win32 did not run in special variations of Windows 8, like Windows RT tablets, where only UWP was supported (guess why they didn't took off).
All Windows versions that descend from Windows NT, also support many architectures, only a few had x86 emulators.
The latest attempt to push Windows on ARM, only started taking off with Arm64EC binaries, which are the Windows version of fat binaries, and the emulator isn't as good as Rosetta.
Finally even Microsoft does indeed drop functions every now and then, even if that is a seldom event.
Then the random exe might appear run, but crash into issues like modern HDPi, new security model,...
I used it under Windows 3.11 as a child, and kept using it for French and German into my late teens and Windows ME. It is simple, just as this tool. To this day, it's a piece of freeware that gives me good memories of a forgotten era.
Since the author describes learning Dutch, I though I might mention its existence.
I am not looking forward to Rosetta going away.
Author discusses/compares Duolingo and Anki. Anki is disapproved for lack of precise right/wrong feedback.
Repository of updated code: https://github.com/shawa/genius
Because MS doesn't require special emulation hardware like Rosetta2 does, I expect amd64 emulation on Windows to last a lot longer than it will on macOS, too.
Depends on how much you care about Khronos APIs for example.
https://devblogs.microsoft.com/directx/announcing-the-opencl...
No other updates since 2020.
True in theory, but in practice you're not going to take a Windows NT PPC .exe and run it anywhere today. Apple's done a decent job with Rosetta and Rosetta 2 doing CPU emulation when doing the transitions but I don't think they've ever targeted the same "You can run Windows 95 x86 .exes on Windows 11 x86-64" backwards-compatibility goal.
My experience with OSX and iOS backwards compatibility is similar to the post author's: things might break once in a while on a long timeframe but it's usually pretty easy to rebuild for a newer version. This works fine so long as the company that owns the source code actually still exists and is willing to build a new version.