8,577 karma · joined July 21, 2009
Oh that sounds lovely! And potentially a useful memory aid: "I don't remember when I read it, but I think it was in a dark magenta issue…"
For example, there are modern games made by hobbyists for old systems that completely outclass literally anything that was available contemporaneously. Today anyone with a computer has access to development hardware, software, documentation, and community resources that are all just lightyears beyond what was available then at any price. Changing a few lines of code and instantly hopping into a cycle-accurate emulator to test takes milliseconds versus writing out floppies or EEPROMs. Arcane tricks that only a privileged few knew (if that) are now common knowledge. That stuff leads to whole other strata of capabilities being accessible.
EDIT: Upon doing a web search, actually it looks like it was "brain dead".
If I remember right, it was said at the time that they had included the migrator code in one or more of the releases before the one in which they actually did the migration. They ran it during those upgrades in a "do as much of the migration as we can without actually committing the changes" mode so that encountered errors could be reported back. So they had most of it tested on millions of devices.
One more resource I'd add for a beginner, the book The Swift Programming Language: https://docs.swift.org/swift-book/documentation/the-swift-pr...
Effectively, there will be two bottom layers of Swift, and the lower one, “non-allocating” Embedded Swift, will necessarily be a more restricted compilation mode (e.g. classes will be disallowed as they fundamentally require heap allocations) and likely to be used only in very specialized use cases. “Allocating” Embedded Swift should allow classes and other language facilities that rely on the heap (e.g. indirect enums).
Also, this seems to maybe hint at (most of?) the Swift runtime eventually being reimplemented in non-allocating Embedded Swift rather than the C++ (?) that it uses now: The Swift runtime APIs will be provided as an implementation that’s optimized for small codesize and will be available as a static library in the toolchain for common CPU architectures. Interestingly, it’s possible to write that implementation in “non-allocating” Baremetal Swift.If you wanted to do email on your home computer, you'd [buy and] install an email client.
You wanted to go on AOL? Install the AOL client.
Need to use Lotus Notes? Have MIS send a guy over to install the Notes client.
Wanted to run X programs? Install an X server. What? Seemed weird!
You still hear that terminology some, but nowadays you're much more likely to hear about an email app.
I see what you're saying, and definitely agree in a way, but also those two things aren't incompatible.
Rust didn't invent those concepts, but Java is becoming more like it by incorporating them. If Rust is much more widely known about than other languages that have those things, it may be more informative to people to hear "Java is getting some stuff from Rust" than to hear a statement that apportions the credit in more detail.
What fools Apple engineering management must be, then!
Wasn’t 16-bit OS/2 demand paged on the 286?
I think I've heard Miyamoto talk about that. When the frustration is all with yourself (rather than with the game itself), and you just know that if you try one more time, that'll be the one where you won't make any dumb mistakes. I think it's the cornerstone of every action game that appeals to me.
So, while I tried to figure out what to do, I worked on my hobby NES emulator for Apple platforms, Blackbox[1]. It's written in Swift and uses SwiftUI.
When a potential contracting role (100% SwiftUI) dropped in my lap, I had the confidence and skills to go for it. It's been great (my meeting-to-coding ratio has inverted!) and they're wanting me to extend my contract for another 12 months. I know the project helped make them feel confidence in my capabilities, but I think it's possible that they'd have gone for me regardless. But, I would've struggled, and I probably wouldn't have even gone for it in the first place because I'd have known that my skills weren't where I wanted them to be.