If I recall correctly, for Commodores, the equivalent of the disk operating system was handled by the drive itself. If you wanted to do anything beyond a LOAD or a SAVE, you were effectively opening the device then sending a command to the device. The exception was getting a directory, which used the LOAD command (as described earlier) rather than a dedicated command. In my opinion, it is accurate to describe loading a special file in order to retrieve a directory listing as a trick.
Looking at the Apple II and Commodore 64, I think it is fair to say that while the BASIC environments supported varying degrees of disk command they were quite different from what we think of as command interpreters. With Unix shells, anything you can enter into a shell script can be executed from the command line, and vice versa. If memory serves me correctly, anything that could be done from the MS/PC-DOS command line could be done from a batch file (though I don't recall if the opposite is true).
A personal example: I don't drive. I use public transit a couple of times a year. I am in private cars maybe once every two year. I haven't flown in about 15 years. Clearly this is a contrived example. My energy use patterns are much more typical when using other metrics. That said, it is also the flip side of being a Taylor Swift of the world. There is a point in the developed world where the millions are using much more energy than the thousands.
I said developed world because there are also parts of the world that simply don't have access to my gratuitous level of energy use. To say that they are guilty of contributing based upon the technicality that they are directly or indirectly using a disproportionately small amount of energy is beyond insulting. It is also a blatant way to paper over our responsibility.
> Globally, the poorest 50% emit roughly 4.4 billion tons to 4.7 billion tons equivalent annually, accounting for about 11% to 12% of total global greenhouse gas emissions.
The “less-developed” bottom half of the world population still produces about a tenth of the annual co2 production annually.
That means instead of potential climate catastrophe in 10 years it’d take 100 years if the top half disappeared tomorrow. Obviously an overly simplistic argument but its meant to show that the problem would just be slower but not gone if we got rid of the “wealthy”.
Now I don’t believe they’re equally as culpable. Yet I also firmly believe the vast majority would choose the same as us in developed world have if they could.
Ultimately that’s more of my point. What’s happening isn’t due to some evil plot by the ultra wealthy. It’s the result of human nature.
Some unscrupulous ultra wealthy might hasten it by a few years or a decade, but the core problem is human nature and an abundance of fossil fuels.
The “wealthy” are also the most likely to prevent catastrophe by developing renewables, etc.
If it is an emergency, it is a voice call. It is both immediate and conveys urgency. If it is something that you need to talk through, it is a scheduled voice call. Asynchronous communications may demonstrate respect for a person's time since it does not (need to) interrupt them in the moment, but the inefficiency results in a disrespectful waste of time for bidirectional conversations.
If it is something where you need a simple response by the end of the day, it is a text. If it requires a lengthy response, email. Never expect a lengthy response by the end of the day, or for it to be handled on devices with terrible input methods (like phones).
Anything that isn't covered by those scenarios will be largely dependent on the person.
If it's an emergency I want it in text first because I read faster than I listen to voicemails, and can do so in more spaces/contexts/environments (say, at a loud concert or eating in a restaurant), and I trust a person to write the message better than the voicemail system will transcribe a call. Certain emergency keywords sent in a text will especially alert me faster than a call would. (I have call notifications as practically turned off as possible in current operating systems [way too much phone call spam], but a measured set of notification levels for text notifications.)
I think even for emergency situations the relationship between voice calls and text messages is flipping. Text messages are immediate and can convey urgency. Phone calls are for private, quiet spaces, which take time to find (or schedule). With the death of the private phone booths in public spaces, phone calls are inconvenient to take almost everywhere now outside of one's home, but urgent text messages can be read and even acted upon just about anywhere.
Why are we talking about voicemails in the context of emergencies? If it was an emergency, I'm calling every number I have for someone until they pickup or enough time has passed that I write them off as a flake and find the next person on the list who might be able to help with whatever it is.
I think that's what I'm complaining about, too, but again from a just slightly different perspective. In an emergency I also don't want to take time to "call every number I have for someone". I don't want to worry about safe calling hours or people that prescreen every call/make every call go to voicemail (including myself). I'd much prefer to send a much faster, single text message and they either get it or they don't, and often there's a quick read receipt if they do get it.
Phone calls have so much ceremony and ritual and take so much time to play phone tag, and every single part of that, especially the phone tag, has gotten so much worse because of spammers. Phone calls just don't feel reliable anymore. It's easier to assume you are more likely to hit someone's voicemail than reach them many hours of the day. It's easier to assume people don't even check their voicemail in some cases, because they expect a text message if it was important.
I think we have different definitions of "emergency" if a text message that they may or may not see any time soon is an acceptable solution.
If it is an actual emergency, I need to know that they have received the communication in real time. I'm never leaving someone a voicemail in an emergency situation.
I think it is possibly more we have a different sense of "received the communication and feedback to the communication in real time" and the kinds of feedback we get from the medium. Text messages give immediate feedback quicker when they are received. Especially iMessage and/or RCS you have read receipts and "quick reactions" and "someone is typing bubbles" to text messages for very immediate feedback. If you have enough people in your life that never answer phone calls, the phone is a much slower way to get in touch with someone and it is missing all sorts of useful quick feedback (did it go to voicemail because they are in a bathroom or a loud concert or did it go to voicemail because they are screening calls after 30 spam calls a day got to be too much for them? did they hear the voicemail or hopefully see a transcript of it? are they going to call back or are they going to not see it for another three days or do they not pay attention to voicemail at all and just expect a text?), most of which additional messaging gets moved to text channels today among many of my friends. ("Can I call you in like twenty minutes?" is a somewhat common text message to and from some of my friends who always text before a call.) In a real emergency you should text me to try to call me before you call me if you want the likeliest results that I will pick up any phone call, but most of the time it is probably just faster to include a headline in the text itself and save us both the time and emotional roller coaster of also making a call.
In an emergency, I can often text 15-20 people in the time it takes to try to get a phone call through to a single person. (Especially with the multiplying effects of copy and paste and group chats.) I'm still probably going to follow up with a bunch of people by phone calls after the texts go out, but most of that will be by request ("can you call me when you get a chance?" texts) for details or shared emotion bonding after the key points are already distributed (and possibly some emergency conditions better).
If you're talking about the modified web pages, then disabling the licenses is intentional. If you're talking about the original decision to use certificates around 2019, it is more doubtful. Sure, they would have known the certificates would expire, they could push out a small update to remedy that, and that they would eventually stop doing so. On the other hand, doing so seven or eight years later on a platform where they could probably wait another five years and expect Apple to do the job for them (i.e. Apple isn't going to maintain Intel support forever). That seems like an invitation for angry and potentially litigious users.
Assuming the Mac folks had no interest in converging the platform in favour of the Lisa is somewhat unfair. While it sounds like some code was shared between the two platforms, the Lisa's operating system was quite different. It would have been difficult to make Lisa software operate under the Macintosh System Software. To my knowledge, there was virtually no software for the Lisa anyhow. Breaking software compatibility on the Macintosh to get the benefits of Lisa would have been a terrible business decision.
Aside from that, the MMU in the Lisa would have been a custom solution which Apple would have to support. When Motorola introduced an MMU, it was for 68020 generation machines. Apple should have been able to introduce memory protection at that point, but didn't. One of the reasons was that Apple struggled to make that next generation operating system while retaining compatibility with existing software (albeit, memory protection may have been only one of many problems). This was by no means a problem exclusive to Apple. Other platforms ran into similar issues.
Apple doesn't seem to have leveraged or combined work on (Lisa, Lisa Smalltalk, Lisa Xenix, Mac OS, A/UX, ...) as successfully as they might have. As you note, protected memory was deferred to multiple failed Mac OS successor projects (Pink/Taligent, Copland/NuKernel, etc.)
Ultimately Apple gave up, acquired Steve Jobs and NeXT, and eventually successfully migrated the Mac platform to an OS with memory protection.
Since then however Apple's OS and hardware strategy has been much more coherent, with macOS, iOS, iPadOS, tvOS, watchOS etc. sharing code, and sharing SoC technology as well. Ironically this is similar to Microsoft's "Windows [NT] everywhere" strategy.
That delay in shipping a memory-protected Mac was probably originally at least as much the result of upper-management politics as anything else. After Jobs left Apple Gassée cancelled Jobs’ pet project, the Big Mac which was intended to run Mac applications on a Unix base. Big Mac project leader Rich Page (and IIRC some other project members) rang Steve Jobs begging him to do something, and the rest is history.
> The Canon Cat is a good text editor. That's about all it does.
Everything I've read suggested that Raskin intended it to be programmable from the beginning, using Forth. Other descriptions suggested that, while document oriented, it was not intended to be exclusively oriented towards word processing. At least not in the sense of the (dedicated) word processors of the day. That said, I'm not surprised that user interaction was keyboard based. The project had it's origins around 1978/79. It would be about 5 years until computers were sufficiently powerful to support a coherent GUI at a reasonable price.
The corrections may not amount to much, but there is no reason to believe that his version would be a failed experiment like the Apple III or the Lisa would have taken it's place.
Part of the magic of the Macintosh was the simplicity of the hardware. In that respect, it was much closer to the Apple II than the Apple III or Lisa. Consumers may not think much about what's inside the case, but it matters when it comes to manufacturing costs and that translates into the cost for consumers. While the original Macintosh was by no means cheap, it was about half the cost of the Apple III and a quarter of the cost of the Lisa. Heck, even the adoption of the Macintosh was slow because of its price. Maybe a less expensive 6809 based Macintosh would have had more success in the market, at least early on. It's also too easy to read too much into the failure of the Canon Cat. The Canon Cat was introduced years later. User expectations were starting to solidify around the GUI at that point. (Then again, success was not guaranteed. Lacking compatibility with the Apple II would have held it back. Especially so after the introduction of the IBM PC since the IBM PC had IBM backing it.)
I also think the adoption of the GUI for consumer computers would have been delayed considerably without the Macintosh 128k. Early machines that supported a GUI tended to be expensive. Early versions of Windows were crude. The only real outliers in that respect were the Atari and the Amiga. Would they have supported a GUI without Apple taking that first step? It's hard to tell.
The defining aspect of the Macintosh for me will always be the mandatory GUI - most everything else had it as either an entire afterthought, or at least as a “program started later”.
The mandatory graphic GUI - and MacPaint - made the point that the Mac was primarily a visual design tool that happened to handle text.
That was absolutely revolutionary.
S-100 systems and the early PCs were primarily text systems that sometimes happened to do crude graphics.
The original Apple II tried to do graphics but the tech to do it properly just didn't exist. And the underlying UI was still text based.
Raskin's Mac vision didn't make that leap. It wasn't just about the mouse, it was about the philosophy of the product. Raskin wanted text-but-cheaper-and-better, Jobs wanted pictures and art.
Early on, sure. I seem to recall Apple having their Human Interface Guidelines early on, which helped, yet there were developers who were either unaware of them or experimenting with different ideas. Other platforms tried to improve consistency later on though. For example: there was CUA for IBM. Of course, most of that went out the windows in the late 1990's and early 2000's when companies figured out that the easiest way to differentiate their products to consumers was visually, rather than technically.
> While the original Macintosh was by no means cheap, it was about half the cost of the Apple III
Made me look it up! I was developing Apple ][/III/Lisa/Mac software at the time. I used the Apple III to write Apple Pascal for the Apple ][, and the Lisa to develop for the Mac. I'd completely forgotten the initial pricing of the Apple III, which was stratospheric. The $7,800 config was 256K I think (~$31K in today's dollars).
"It sold initially for between $4,340 and $7,800, depending on the configuration. The original Apple III had many problems, and was replaced by a revised model in mid 1981, which featured 256K RAM, updated system software, and a lower price ($3495). A 5 MB external hard disk was also made available. The Apple /// sold very poorly and was replaced by the Apple ///+ ($2995) in Late 1983. The Apple ///+ was discontinued in 1985."
There are various reasons to avoid a fork. Having the resources to maintain such a site, spreading resources thin, and moving over or rebuilding a community of trusted editors are among them.
That said, I am one of the people who downloaded a copy of Wikipedia. It wasn't with the intent of working it. Rather, it was to wait out any political strife (since that is bound to happen with such a large and diverse audience).
> I attribute people returning AI answers to a desire to feel valued and to feel that they contribute something to the person asking the question.
At least with the example in the article (with the ChatGPT screenshots), I don't think it's all that different from the olden days when people would include links to an unnvetted webpage after a quick web search, or a link to something like let me Google that for you. It isn't about feeling like they contributed. It's more a passive aggressive way of saying do your own research.
With free trials, I can understand revoking the benefits once the subscription has been canceled. While I can understand the consumer's perspective of not wanting to be billed for future months (say if they forgot to cancel), free trials are intended to attract future customers. If a person signals that they are not going to be a future customer, why should the business offer the free service?
Are they signaling that they're not going to be a future customer? Or are they just signaling that they want to take positive action if they make the decision to subscribe?
And what about signaling in the other direction? Canceling the trial immediately signals that they have no confidence in the product itself to sell you on it, that the company itself believes that if you use their product for another few days, you still won't want to give them any money for it. If the company has so little confidence in their own product then why would I pay for it?
Sorry, but they set their signaling mechanisms so that that signal is worthless. How many people who don't cancel want to signal they are going to be a future customer, as opposed to it being an accident? How many people who do cancel do it to signal they don't want to be a customer, and not because they don't want to be automatically billed? I believe the answer for both is "not many".
I think the companies do it because it benefits them, and because they can.
Looking at the Apple II and Commodore 64, I think it is fair to say that while the BASIC environments supported varying degrees of disk command they were quite different from what we think of as command interpreters. With Unix shells, anything you can enter into a shell script can be executed from the command line, and vice versa. If memory serves me correctly, anything that could be done from the MS/PC-DOS command line could be done from a batch file (though I don't recall if the opposite is true).
reply