And in any case, it would be up to DR-DOS to emulate whatever MS-DOS was doing.
5,145 karma · joined April 6, 2010
And in any case, it would be up to DR-DOS to emulate whatever MS-DOS was doing.
However, Windows 3.1 relies on an utterly absurd hack to determine size of entries in the MS-DOS System File Table, despite the fact that MS-DOS and Windows are both under control of the same company.
It scans raw memory looking for three instances of the string "CON", assumes this is the location the SFT, and uses the distance between the first two CONs as the size of a SFT entry.
The hack breaks if the SFT has been moved to high memory, which prevents Windows from running. The workaround is to put three CON instances in conventional memory, correctly spaced, before starting Windows.
Apple has never described Swift, Catalyst, or SwiftUI as a transition from or to anything. Instead, Apple has gone out of its way to say that these are not transitions. Remember that big "NO" slide from last year?
When a transition is required, Apple does not ever hide it.
Classic Mac to OS X was a transition.
PPC to Intel was a transition.
UIWebView to WKWebView is a transition.
SwiftUI is no more a transition from AppKit/UIKit than Storyboards were a transition from NIBs and programmatic UI.
Modern ObjC syntax, Enterprise Objects, Java/Cocoa Bridge, Ruby/Cocoa, Python/Cocoa, Key-Value Observing/Encoding, ObjC Garbage Collection, ARC, Storyboards, Playgrounds, Swift, SwiftUI, etc. These are not transitions. These are all just tools in the toolbox. Some more useful than others.
The only thing Apple's engineers are trying to do here is create stuff that developers find useful. There is no hidden or invisible strategy with this stuff.
"Traditionally, it was done by mounting file systems on top of directories in the root file system. With the number of crossing points which we need to introduce and the number of volumes which it would require in the file system, that approach becomes rather expensive."
(At least it appears that way, going by the WWDC session descriptions. We'll know more in a couple of hours)
The future of MacOS development is not Marzipan and never was. The future is SwiftUI.
> Don't think this has to do with Reddit so much as the way
> we interact with each other online, in general.
Welcome to 1989.Dial-up Unix shell/internet access was free through the university. I picked up an original 128k Mac and Mac Plus with 40 MB SCSI HD at a local thrift shop for $40, both of which I still own.
A CD cost $25, a pack of cigarettes was $5, and pitchers of beer were $8.
Ten short years later I would be walking around with an always-connected Blackberry in my pocket wondering how I ever survived without Google Maps, push email, and IM.
And the butterfly mechanism is unproven and untrustworthy, I don't care how many times they update it.
They need to go back to using the same keyboard mechanisms for both their desktops and laptops, and they need to go back to the old arrow key layout.
I will wait another year until 2020.
Anyway, it sounds like a fun project.
[0] https://www.reddit.com/r/c64/comments/6d8ss0/who_owns_the_co...
This type of user needs to be able to lock on to the arrow keys repeatedly and unconsciously without fail throughout the work day.
Apple's keyboard designers understood this and got it right for over 15 years. But that changed in 2016.
As of 2016, Apple's new keyboards provide zero affordances for these kinds of users and are completely unsuitable for real work.
You couldn't pay me enough to use one of these keyboard for writing code, and I certainly wouldn't pay my own money for one.
And when I do drive an automatic, I end up driving it like a manual anyway. I can't resist downshifting when slowing down.
I'm thinking:
1977: Annie Hall
1979: Manhattan
1986: Hannah and Her Sisters
1989: Crimes and Misdemeanours
1992: Husbands and Wives
1993: Manhattan Murder Mystery
2005: Match Point
2008: Vicky Cristina Barcelona
2009: Whatever Works
2011: Midnight in Paris
2013: Blue Jasmin
Have I missed anything?If Microsoft acquires a new user and subscription through the App Store then Apple is entitled to their cut. If Microsoft acquires a new subscription organically outside of the App Store then Apple is obviously not entitled to a cut.
If Microsoft doesn't want the ability to acquire new subscriptions through the App Store (and pay Apple for it) then that's their prerogative, but right now that's not the case.
If you purchase an in-app subscription through the App Store with your Apple ID, the only option is a yearly subscription.
If you purchase a subscription directly from Microsoft's website, you can purchase either a yearly or monthly subscription.
The yearly subscription costs the same in both cases, and is cheaper unless you only want to use the app for a few months.
It's Atari's arcade font from 1978 paired with some generic low-res graphics.
I've switched almost entirely to watching content I own, whether its iTunes purchases or ripped DVDs. I control the entire experience, I don't have to worry about content suddenly vanishing, I don't have to deal with anyone trying to steal my attention.
I feel the same way about dropping Netflix now as I did about dropping cable TV 5 years ago. I'm never going back.
2018: I never thought I'd be walking around with a full Symbolics Lisp Machine in my pocket.
A souped-up Apple II at that time would have had 64 KB of RAM, and 140 KB of storage per floppy disk.
I guess you needed a PDP-11 to do any real work in those days.
When Marzipan was first announced, Apple was very careful to temper people's expectations. Marzipan is not about some grand new cross-platform development framework. It's not about merging Mac and iOS. It's about allowing iOS developers to port certain iOS apps to the Mac with as little friction as possible.
And in that sense it's a complete success. Many 3rd-party apps can already run inside of Marzipan with little or no code changes. That's a huge win.
There are some very obvious downsides. Most iOS apps are a poor fit on the desktop and won't conform to the expected Mac desktop expectations. I suppose Apple could have gone the Windows 8 route and put these iOS apps in a completely separate environment, but we all know how that turned out on Windows. At least these apps attempt to mesh with the regular desktop environment.
Another downside is that it's a hack. These are pure iOS apps running inside of an iOS simulator designed to look like a Mac app. These apps have no access to the world outside of iOS.
If you're looking to make a great modern Mac app, Marzipan isn't for you. If you're looking for an easier way to share UI code between your AppKit and UIKit apps, Marzipan has nothing for you. If you have a relatively simple iOS app that you think might be useful on a Mac, Marzipan is exactly what you've been waiting for.
If you want a peek into what a grand new cross-platform development framework might be, take a look at the JetEngine.framework embedded in the Mac App Store app. It appears to be a separate UI framework that is neither AppKit nor UIKit, but can run on top of either. However, it's full of App Store-specific UI components and I would expect that it was developed only for internal use at Apple.
http://el.media.mit.edu/logo-foundation/what_is_logo/history...
Apparently they're still around: http://www.microworlds.com/company/profile.html
The version I used in 1983 was for the Coleco Adam computer, which uses the same video and sound chips as the TI99/4A. This version of Logo supported 32 sprites, 16 color graphics, 4 channel sound, and had a built-in sprite editor.
The language itself was quite slow, but it was very easy to come up with all sorts of interesting animations using the 32 sprites. You give a sprite a speed and direction and off it goes. It was a lot of fun and I spent many hours with it as a kid.
If you don't trust Google, don't use Google services. If you need to sign into different Google accounts, use a different browser.
Apple makes Safari to sell its Macs and iPhones.
Microsoft makes IE/Edge to sell its Windows licenses.
Google makes Chrome to sell its advertising.
Face ID is fine, but multiplexing so many different features on to the single, poorly-placed, side button has been a huge negative for me.
The side button is way too easy to hit when the device is in your pocket, and when that happens you're activating Siri, or Apple Pay, or some accessibility shortcut, or you're taking a screenshot, or you're activating emergency mode.
I've lost count of the number of times I've pulled my iPhone X from pocket to find that the screen is on, Siri is waiting for a command, and the accessibility menu is on screen.
And when I actually need to take a screenshot, or shutdown the device, I can never remember the actual key combination. It's such a mess.
Porting AppKit to ARM is easy. It's another thing entirely to commit to supporting parallel versions of AppKit for the next 8+ years.
It would be a colossal waste of Apple's software engineering resources, which many people believe are already stretched too thin. And for what, a little better battery life? It's just not realistic.