Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
It turns out the consuming public LOVES street cars. Who woulda guessed?

Having lived in multiple cities with streetcars, including one which never stopped or slowed down running them, I could have easily guessed.

The op-editor’s analogy is woefully misplaced and reflects a monocultural (home in one place, work in a second place, shopping in a third, houses of worship in a fourth — only accessible by car) way of spatial thinking prevalent to that moment — one largely unchallenged back in 1984. I know this way of thinking well, as I was coming of age in a monocultural suburb of Houston back then and it was the only way presented to develop a populated community.

Of course, one could program applications for the Mac then, but it wasn’t readily accessible to casual users then/just yet. And this is what the writer was lamenting in a kind of eggheaded, antediluvian, exclusive kind of way. What he touched upon, probably by accident, but didn’t analyze further, is the paradigm of a GUI-oriented computing platform being the springboard for doing other things and getting other things done — not in an “appliance” kind of way, as expressed in the opinion piece, but in more of a multi-tool kind of way or, heck, even an IKEA kind of way: modular, extensible, interchangeable, customizable.

The “appliance”, as we know it, didn’t really arrive until the walled garden, jailed, and touchscreen-heavy paradigm of the glass UX — birthed in part by Palm and maybe also the Jornada (running Windows CE), but brought to the next level with the iPhone and Android.
 
The op-editor’s analogy is woefully misplaced and reflects a monocultural (home in one place, work in a second place, shopping in a third, houses of worship in a fourth — only accessible by car) way of spatial thinking prevalent to that moment — one largely unchallenged back in 1984. I know this way of thinking well, as I was coming of age in a monocultural suburb of Houston back then and it was the only way presented to develop a populated community.
A fellow Houstonian! Kingwood? The Woodlands? Cinco Ranch?
 
  • Like
Reactions: eyoungren
The classic Mac OS doesn't even include a COMMAND LINE.

How on Earth do I use an OS that doesn't have a command line?

Do I type commands into TeachText/SimpleText and recite "Humpty Dumpty" thirteen times to run them?
 
What we see in this is the beginning of the PC/Mac conflict. Computers were for nerds then, or people just really into them. Apple introduced a computer for people who didn't want to get that involved but still needed/wanted a computer to do something.

MS effectively conceded this IMO with the introduction of Windows. All the MS-DOS people (including me) screamed bloody murder, but the truth was that MS finally recognized that the average person didn't want to have to digest all this knowledge just to use a computer.

Offer people something that they like/want and tell them that they don't have much of a learning curve to use it and it will sell. People don't want to think about things. That stuff is for all of us here.
 
A fellow Houstonian! Kingwood? The Woodlands? Cinco Ranch?
11406 Sageyork Drive.

I can give you this specific address and not worry about it because the last time I was there was 1979 and I was eight years old. I attended Kindergarten at the school down the street and played in the park near there.

If you look it up on Google Maps you'll see a lamp post. My dad put that lamp post in some time in the mid 70s and it's still there. When we moved in there were no fences as the development had just started.
 
MS effectively conceded this IMO with the introduction of Windows.
Windows (Version 1.0) was introduced in 1985 but didn't really take off until 1990, with the introduction of Version 3.0. So, the Mac and various other computers with a GUI had a lead of a few years.
 
  • Like
Reactions: TheShortTimer
Windows (Version 1.0) was introduced in 1985 but didn't really take off until 1990, with the introduction of Version 3.0. So, the Mac and various other computers with a GUI had a lead of a few years.

If anything, Amiga had a jump on Windows 1.0 by something like 4–6 months, and its price point put in right in between high-end Macintoshes and bare-bones DOS boxes (which were still not cheap either, but clones were by then beginning to put a dent in IBM’s stronghold) — which is to say, Amiga probably put GUIs in more homes and offices than Macintosh, at least in those early years.
 
And since the Amiga and Mac used the same CPU, you could kinda virtualise Mac OS on an Amiga back in the Eighties. :D

I swore I saw something like this recently.

11406 Sageyork Drive.

I can give you this specific address and not worry about it because the last time I was there was 1979 and I was eight years old. I attended Kindergarten at the school down the street and played in the park near there.

If you look it up on Google Maps you'll see a lamp post. My dad put that lamp post in some time in the mid 70s and it's still there. When we moved in there were no fences as the development had just started.

Ah yes, the natural gas lanterns. My grandmum’s home had one of those fuelled by, I think, Entex.

Your old house looks like it was lifted from the neighbourhood where I was raised.

On street view, I just had a look at the old house where I lived for much of my childhood, and I see the present/recent owners felled the pine tree which had been there (which was still barely more than a sapling when we moved in, also in 1979). It was even sporting pine cones in that penultimate pic (something I never saw when I was little because the tree wasn’t mature enough). It’s possible, of course, a storm brought it down, but I noticed all the other trees and tree-like shrubs which were there in an older street view are just wiped away now, leaving the place looking not terribly different from what it looked like when the house was first built during the mid ’70s.
 
Last edited:
  • Like
Reactions: Amethyst1
What hasn’t changed is the “elitism” for using more technically complex systems. Much of the Linux community comes to mind (though there’s enough outcry that I believe that attitude is beginning to change now. I do see more complaints about the elitism than I do about “normies” anymore.)

Also, I find it humorous that the article mentions the lack of programming functions when one of the biggest users of Macs today are programmers (stemming from the POSIX-compliance of OS X).

I don’t think I need to mention the sentence about phones.

So, in a sense the article has aged poorly, but one part aged well.
 
  • Like
Reactions: Amethyst1
I wonder how many Europeans will look at this address and marvel at the house number. The highest street number in the UK only reached the very low 2000s and that itself was very much a rarity.
In many citys in the US, house number is dependent upon a grid system or a specific series of streets/avenues.

For instance, here in Phoenix, the system starts at zero - which is Central Ave. 1st Street, 2nd Street, etc are east of Central and 1st Ave, 2nd Ave, etc are west of central. Aves and streets run north/south.

So, someone living at say 3510 W Osborne would have a cross street of 35th Avenue, while 3510 E Osborne would have a cross street of 35th Street. Addresses pay no respect to city as both streets and avenues are in several cities out here. Each city having it's own addressing system doesn't work because citys are right next to each other.

For example, if I go a couple of streets north from my own house I will be in Glendale, AZ and not Phoenix.

Phoenix goes out as far west as 339th Ave. So, it's possible to have a very high street address if you want to be a desert hermit.
 
In many citys in the US, house number is dependent upon a grid system or a specific series of streets/avenues.

For instance, here in Phoenix, the system starts at zero - which is Central Ave. 1st Street, 2nd Street, etc are east of Central and 1st Ave, 2nd Ave, etc are west of central. Aves and streets run north/south.

So, someone living at say 3510 W Osborne would have a cross street of 35th Avenue, while 3510 E Osborne would have a cross street of 35th Street. Addresses pay no respect to city as both streets and avenues are in several cities out here. Each city having it's own addressing system doesn't work because citys are right next to each other.

For example, if I go a couple of streets north from my own house I will be in Glendale, AZ and not Phoenix.

Phoenix goes out as far west as 339th Ave. So, it's possible to have a very high street address if you want to be a desert hermit.

To make this even more interesting: in most major U.S. cities, especially so west of the Mississippi River, the address number (which keeps increasing until one crosses not the city limits, but rather, the county/parish limits) is predicated on each “block” — the distance between two parallel, consecutive streets — being one-tenth of one mile apart and making ten city blocks roughly one mile. This way, an address like 3510 Appleton Avenue indicates, roughly, one is 3.5 miles from the centre of the county seat.

Except, that is, for Seattle — well, technically, Washington state.

Washington went instead with the metric system. This reveals a lot about how young the city and state are, relative to other U.S. continental states, and it also presents a rare instance when a U.S. jurisdiction implemented metric/SI units, rather than imperial units, onto administrative geographies.

In other words, if you’re in Seattle, and you’re on 45th Street, you’re 4.5km from the heart of the county seat (King County/downtown Seattle), and those numbers increase all the way into the 40000-block range in the eastern reaches of King County, deep in the Cascade Mountains. (It’s actually a bit more complicated with Seattle’s case, as two warring developers during the late 19th century chose to draw the original city centre streets in different directions — one developer drew them parallel to Elliot Bay (part of the Puget Sound) and, thus, diagonal, whereas the other developer drew streets to align with cardinal compass points of north/south and east/west. Eventually, the latter won out and only a small grid of diagonal streets remain.)

The outcome of the above is city blocks in Seattle are fairly short (~100m apart), and this tends to make the streetscapes more walkable and compact.

In Canada, meanwhile, cities within provinces whose regions (counties) were subdivided by English concessions tend to have every street begin at 1. In a city like Toronto, the most visible example of this is 1 Yonge Street, once called “the longest street in Canada”, but every street, no matter where one is in the city, starts at 1 (east of Yonge, which bisects the city in half, east-west street numbers increase as one travels east, and west of Yonge, they increase as one travels west; Yonge is also a rare case of seeing a Canadian address number spool up beyond 10000). In Québec, whose land was not subdivided by concessions, but by Catholic church parish (known as seigneurial subdivisions), relative to the nearest body of navigable water, all address numbers begin with where land meets water. So in a city like Montréal, one sees addresses like 5281 rue St-Laurent, which superficially looks more “American” than most places around Canada, but the address numbers are less based on distance and more on simple, incremental allocation as land was developed further inland of the shoreline.

Sorry, all of this totally veering off-topic, but it’s one of the rare times I get to share fun stuff which touches on my trained background. :)
 
To make this even more interesting: in most major U.S. cities, especially so west of the Mississippi River, the address number (which keeps increasing until one crosses not the city limits, but rather, the county/parish limits) is predicated on each “block” — the distance between two parallel, consecutive streets — being one-tenth of one mile apart and making ten city blocks roughly one mile. This way, an address like 3510 Appleton Avenue indicates, roughly, one is 3.5 miles from the centre of the county seat.

Except, that is, for Seattle — well, technically, Washington state.

Washington went instead with the metric system. This reveals a lot about how young the city and state are, relative to other U.S. continental states, and it also presents a rare instance when a U.S. jurisdiction implemented metric/SI units, rather than imperial units, onto administrative geographies.

In other words, if you’re in Seattle, and you’re on 45th Street, you’re 4.5km from the heart of the county seat (King County/downtown Seattle), and those numbers increase all the way into the 40000-block range in the eastern reaches of King County, deep in the Cascade Mountains. (It’s actually a bit more complicated with Seattle’s case, as two warring developers during the late 19th century chose to draw the original city centre streets in different directions — one developer drew them parallel to Elliot Bay (part of the Puget Sound) and, thus, diagonal, whereas the other developer drew streets to align with cardinal compass points of north/south and east/west. Eventually, the latter won out and only a small grid of diagonal streets remain.)

The outcome of the above is city blocks in Seattle are fairly short (~100m apart), and this tends to make the streetscapes more walkable and compact.

In Canada, meanwhile, cities within provinces whose regions (counties) were subdivided by English concessions tend to have every street begin at 1. In a city like Toronto, the most visible example of this is 1 Yonge Street, once called “the longest street in Canada”, but every street, no matter where one is in the city, starts at 1 (east of Yonge, which bisects the city in half, east-west street numbers increase as one travels east, and west of Yonge, they increase as one travels west; Yonge is also a rare case of seeing a Canadian address number spool up beyond 10000). In Québec, whose land was not subdivided by concessions, but by Catholic church parish (known as seigneurial subdivisions), relative to the nearest body of navigable water, all address numbers begin with where land meets water. So in a city like Montréal, one sees addresses like 5281 rue St-Laurent, which superficially looks more “American” than most places around Canada, but the address numbers are less based on distance and more on simple, incremental allocation as land was developed further inland of the shoreline.

Sorry, all of this totally veering off-topic, but it’s one of the rare times I get to share fun stuff which touches on my trained background. :)
As you know, I visited Seattle over Christmas. I still can't get my head wrapped around the streets there. My sister, who has lived there mostly since the early 90s (with a stint in Anchorage) uses Google Maps. So, I guess you just have to grow up there or REALLY want to learn the system.

It's all still confusing to me because city blocks in places like Kent seem to be interrupted by mountains and forests. You drive in and out of civilization going down one street.
 
As you know, I visited Seattle over Christmas. I still can't get my head wrapped around the streets there. My sister, who has lived there mostly since the early 90s (with a stint in Anchorage) uses Google Maps. So, I guess you just have to grow up there or REALLY want to learn the system.

The trick with City of Seattle proper is getting used to the significance of the embedded directionals in the street name. The “N”, ”S”, ”E” and ”W” designations are relatively straightforward. All the “NW” streets suggest they’re gonna be in (or near) Ballard or Fremont, whereas all the “SW” streets are those way over in West Seattle, which is generally pretty isolated from the rest of the city (especially so since the key bridge connecting the two was shut down a couple of years ago due to structural issues).

In downtown Seattle, an easy mnemonic for remembering the street order, south-to-north, is every two streets share the same starting letter, JJCCMMSSUUPP (Jefferson, James, Cherry, Columbia, Marion, Madison, Spring, Seneca, University, Union, Pike, Pine), or JCMSUP — which I like to remember as John Cougar Made Songs Under Pressure.

When in Seattle, I tend to wayfind faster with two elements: those streets/avenues which are named, not numbered (Aurora, Ravenna, Rainier, Broadway), and when that isn’t practical, to rely on the streets ending in “5”s — 45th, 65th, 75th, 85th — to give me a sense of how far away something probably is. Central Bellevue, meanwhile, is just weird with nothing but high-numbered “E”-signed streets.

It's all still confusing to me because city blocks in places like Kent seem to be interrupted by mountains and forests. You drive in and out of civilization going down one street.

Yah, Kent (and other towns down there, like Enumclaw and Orting) really feel like the borderlands between how the region used to be throughout, versus all the development since about 1900. It’s also like that on the other end of the MSA, in Snohomish, Mulikteo, and Gold Bar.
 
While not specifically PowerMac specific I thought this would be as good a place as any to post this:


I recall reading many of these types of articles. Does anyone else?
That article didn't even quite make sense back in the 80s, at least for the part about the programming.

"In the brouhaha surrounding the introduction of Apple's new Macintosh, little has been said about the most shocking thing about this "new generation" computer—it doesn't include a language. You can't program it. There's no BASIC inside. BASIC and other programming languages will be available later, but the essence of this machine, its spirit, is a rejection of programming itself."

I wasn't a big fan of the Mac back then, but mainly because it was expensive, had a tiny screen, was comparatively slow, and had no software. However, nobody I knew with Apple II series machines (and their clones) actually programmed them. They used software like Apple Writer or VisiCalc or games, and the only times they played with a programming language was when they were learning them for school.

The biggest difference on the Mac was that instead of using keyboard commands to launch those programs, you pressed some buttons.

So, it's not that the article didn't age well. It's that the writer misunderstood the consumer and business market even at that time.
 
That article didn't even quite make sense back in the 80s, at least for the part about the programming.

"In the brouhaha surrounding the introduction of Apple's new Macintosh, little has been said about the most shocking thing about this "new generation" computer—it doesn't include a language. You can't program it. There's no BASIC inside. BASIC and other programming languages will be available later, but the essence of this machine, its spirit, is a rejection of programming itself."

I wasn't a big fan of the Mac back then, but mainly because it was expensive, had a tiny screen, was comparatively slow, and had no software. However, nobody I knew with Apple II series machines (and their clones) actually programmed them. They used software like Apple Writer or VisiCalc or games, and the only times they played with a programming language was when they were learning them for school.

The biggest difference on the Mac was that instead of using keyboard commands to launch those programs, you pressed some buttons.

So, it's not that the article didn't age well. It's that the writer misunderstood the consumer and business market even at that time.
I visited a friend in 1988 I think, could have been '87. Anyway, his dad had one of the black and white Macs. All I can recall is how primitive the graphics looked and how small the screen was.

But, at that point I'd had a Commodore 64 since 1984. It was hooked up to the TVs of that era or the monitors of that era. By that point I think I had the 1802 monitor (the one with the big adjustment knobs on the front right) which would have been a 13" display and color.

Through the 90s I worked on Mac II series computers at design school and was similarly unimpressed. A particular focus of my then developing hate for the Mac was the LC II. As an example of what the Mac could do, it couldn't.

So I recognize what this opinion writer was saying because that was a facet of my low opinion of the Mac at that time. I would vehemently claim that both Windows and the Mac were crutches for users/people who refused to learn DOS or computers.

Yet, here we are now. :D
 
  • Like
Reactions: EugW
I visited a friend in 1988 I think, could have been '87. Anyway, his dad had one of the black and white Macs. All I can recall is how primitive the graphics looked and how small the screen was.

But, at that point I'd had a Commodore 64 since 1984. It was hooked up to the TVs of that era or the monitors of that era. By that point I think I had the 1802 monitor (the one with the big adjustment knobs on the front right) which would have been a 13" display and color.

Through the 90s I worked on Mac II series computers at design school and was similarly unimpressed. A particular focus of my then developing hate for the Mac was the LC II. As an example of what the Mac could do, it couldn't.

So I recognize what this opinion writer was saying because that a facet of my low opinion of the Mac at that time. I would vehemently claim that both Windows and the Mac were crutches for users/people who refused to learn DOS or computers.

Yet, here we are now. :D
Yeah, I didn't buy a Mac until 2001. I disliked the Macs prior to that time for various reasons, and when I grew out of my Apple II+ clone, I bought a MS-DOS PC and eventually transitioned to Windows 95 and Windows 98. I disliked System x and OS x on Mac, until OS X 10.1 came out. Then I bought an iBook G3 600.
 
  • Like
Reactions: eyoungren
Yeah, I didn't buy a Mac until 2001. I disliked the Macs at that time, and when I grew out of my Apple II+ clone, I bought a MS-DOS PC and eventually transitioned to Windows 95 and Windows 98. I disliked System .. and OS .. until OS X 10.1 came out. Then I bought an iBook G3 600.
My dad brought home a TRS-80 CoCo in 1980. Initially it saw some use, but there weren't a lot of games for it and I had to type in a lot of programs by hand so eventually I stopped using it. But I got that C64 in '84 and that was my main computer until some time around 1988 when I got a C-128.

I went PC in 1990 (286 AT clone, home built). My very first Mac was Christmas 2001 and it was a gift. A TiBook 400. It came with OS X at the time, but I stupidly wiped the drive and put OS9 on it. Only because I understood OS9 as that was the OS on the G4s that work used.

It wasn't until the 17" PowerBook G4 that I actually WANTED a Mac. I liked the Quicksilver, but not enough to actually try and get one like the 17" PB. I was attracted to the G3 B&W though back in 1999.

Today, those are really the only three Macs I actually like. I have other Macs and I like them for what they can do. But I really only like the looks of my G3, my 17" PowerBook and my Quicksilver.
 
  • Like
Reactions: TheShortTimer
My very first Mac was Christmas 2001 and it was a gift. A TiBook 400. It came with OS X at the time, but I stupidly wiped the drive and put OS9 on it. Only because I understood OS9 as that was the OS on the G4s that work used.
My iBook G3 600 actually shipped with dual boot OS 9 / OS X 10.1.

I strictly used OS X 10.1 and haven't looked back. :) Well not strictly. On OS 9, you could spoof WiFi MAC addresses, and I used that to get free internet access at the local coffee shop. ;) So my usage was >95% OS X and <5% OS 9, even in 2001.
 
  • Like
Reactions: eyoungren
So, someone living at say 3510 W Osborne would have a cross street of 35th Avenue, while 3510 E Osborne would have a cross street of 35th Street. Addresses pay no respect to city as both streets and avenues are in several cities out here. Each city having it's own addressing system doesn't work because citys are right next to each other.
That doesn't really work in Europe. For the most part, cities were founded before serious town planning was a thing and grew organically - that is, chaotically. Winding narrow streets, for the most part (Germany seems to be an exception) that do not go on for miles. Arterial roads connecting towns and villages tend not to have houses outside of the urban limits and often change names, even within the city limits.

Fore example, just around the corner from me is a shortish road with maybe 150 dwellings on it. The district (neighborhood in US speak) boundary cuts right through it about a third of the way up. The road changes names and the house numbers start from scratch again. This is within the same city. Street names in my city also carry a postcode number to identify the district (very roughly speaking; there is some overlap) and both road signs have different numbers. The number will determine house price, council tax, school catchment area etc. Those will vary widely even for adjacent houses. Location is the key.

Screenshot 2022-06-11 at 18.39.20.pngScreenshot 2022-06-11 at 18.38.36.pngScreenshot 2022-06-11 at 18.38.03.png
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.