Holy crap, I can't proofread very well. That first bit should read "bought OFF of him when *HE* was making the switch to PC"... Goat forbid I ever switch to beige!
I grew up on an Amiga 500. It, as well as a friend's A2000 which I bought of of him some years later when I was making the switch to PC, are still sitting in my parents' house somewehre. =) (In fact, probably in almost pristine quality with a snapshot of the BBS that I was running on it some years later until the fateful day I decided to pull the plug and make some more desk space for the new Mac that had infiltrated and upstaged.)
My first introduction to computers was actually the QNX/Unisys ICON system in elementary school (yep, a networked system running a Unix-like operating system... something that *also* ahead of its time, well, kinda). Following that, the Commodore PET and 64 on which I learned BASIC and got my start in software development. =) A few years later, I was back to the ICONS where I started learning C in about grade 8, but through that time we had an Amiga in the house.
Ours was an A500 which Dad bought from the local Canadian Tire (!) and revealed as a surprise family Christmas gift in 1987. It was a phenomenal machine. I can still recall the school-yard conversations with my 286- and Mac SE-toting friends about how many simultaneous colours their computers could display ("16, eh? Howzabout FOUR THOUSAND NINETY SIX, foo'").
Ahh, good times.
Truly a revolutionary force in its day, though. The intervening years (death of Commodore, slow atrophy of the Amiga brand and innovation) were painful but inevitable to watch, kind of like a withering tree you know is past its prime and on its way.
The early stages of OS X (which really where an open beta), slow kernel, slow UI and not even easy to use. To the Apple users was of course the best thing.
Well, that's because we were sick and tired of our systems locking up and crashing all the time. Pre-emptive multi and memory protection were way waaaaaay overdue. (Before the Mac I had an Amiga in 1987 so I was already used to a decade and a half of pre-emptiveness.)
Certainly though, I agree, 10.0 and 10.1 were no hell compared to where we're at today.
I have a better idea. Why don't we just call it version 22.0 to begin with. Hey, that's wonderful! I think I'll submit a new slashdot article which discusses my stupid naming decision. Great.
Update: forget about this... I misunderstood the issue. The article and summary say "javascript dialog box" which I took to mean one of those spawned by alert() or prompt() call. Evidently they're just talking about a regular window.
I thought Safari fixed this many months ago, with a change whereby the JS alerts come down in the form of sheets attached to the window/tab to which they correspond? I could swear there was a/. piece on exactly this.
Or maybe I'm clued out and this is something different?
Know why Macs could read PC disks but not vice versa? Easy. Apple's HFS filesystem was copyrighted;-)
I thought it had to do with the physical geometry on the disk. IIRC, something to do with the Mac drives spinning the disk at a variable velocity whereas PC drives ran at a constant velocity.
Maybe I am partly confusing the issue with Amigas not being able to read Mac floppies, but I presumed the issue was similar.
Hmm... that's true. You're right, my question was perhaps a bit off-the-cuff.
I had it in the back of my mind that "satellite-based" internet services give terrible lag though, hence this inquiry. Why would they be high-latency relative to wireline?
For better or for worse, Microsoft has definatly become a better company because of open source.
Whenever someone misspells definitely as "definatly", I often read it as defiantly. Sometimes, depending on the context, it's an even more appropriate word.
There are agreements in place that require overseas suppliers to charge me UK sales tax
Please cite these agreements.
The EU would like to have the rest of the world act as its tax collector; remarkably, many of the large American corporations have bent over already. But as small suppliers, I and many of my colleagues are scratching our heads saying "wtf".
I serve web and mail for a whole bunch of domains off of two servers which are far apart and unrelated (geographically and in terms of network topology). Under normal conditions one is primary and the other secondary; the two of them sync up via cron and rsync at ten-minute intervals. The A records for web sites point to the primary, it has a higher-preference MX and so on. Both machines are authoritative DNS for all domains.
I have TTLs on all the domains set to 120 (yep, two minutes). The idea is that in case of failure of the primary, the secondary will reconfigure itself as primary and begin handling all traffic, while the end user will experience a maximum of two minutes downtime.
With 278 days uptime on the primary though and great service from the colo provider, I've never had to implement this scenario. Is my planning fundamentally flawed? Is this an unadvisable practice?
Slashdot Mirror
Holy crap, I can't proofread very well. That first bit should read "bought OFF of him when *HE* was making the switch to PC"... Goat forbid I ever switch to beige!
-b
(Chiming in with all fellow retrospectives)
I grew up on an Amiga 500. It, as well as a friend's A2000 which I bought of of him some years later when I was making the switch to PC, are still sitting in my parents' house somewehre. =) (In fact, probably in almost pristine quality with a snapshot of the BBS that I was running on it some years later until the fateful day I decided to pull the plug and make some more desk space for the new Mac that had infiltrated and upstaged.)
My first introduction to computers was actually the QNX/Unisys ICON system in elementary school (yep, a networked system running a Unix-like operating system... something that *also* ahead of its time, well, kinda). Following that, the Commodore PET and 64 on which I learned BASIC and got my start in software development. =) A few years later, I was back to the ICONS where I started learning C in about grade 8, but through that time we had an Amiga in the house.
Ours was an A500 which Dad bought from the local Canadian Tire (!) and revealed as a surprise family Christmas gift in 1987. It was a phenomenal machine. I can still recall the school-yard conversations with my 286- and Mac SE-toting friends about how many simultaneous colours their computers could display ("16, eh? Howzabout FOUR THOUSAND NINETY SIX, foo'").
Ahh, good times.
Truly a revolutionary force in its day, though. The intervening years (death of Commodore, slow atrophy of the Amiga brand and innovation) were painful but inevitable to watch, kind of like a withering tree you know is past its prime and on its way.
-b
The early stages of OS X (which really where an open beta), slow kernel, slow UI and not even easy to use. To the Apple users was of course the best thing.
Well, that's because we were sick and tired of our systems locking up and crashing all the time. Pre-emptive multi and memory protection were way waaaaaay overdue. (Before the Mac I had an Amiga in 1987 so I was already used to a decade and a half of pre-emptiveness.)
Certainly though, I agree, 10.0 and 10.1 were no hell compared to where we're at today.
-b
I have a better idea. Why don't we just call it version 22.0 to begin with. Hey, that's wonderful! I think I'll submit a new slashdot article which discusses my stupid naming decision. Great.
-b
This area needs to have some laws made
For the love of goat, please, no.
-b
God help us all.
Which one?
-b
Taco, read your own fucking site much?
-b
...what in the hell is a RAZR or a PEBL?
-b
Also, since (presumably) Rob hasn't actually *tried* the software, isn't judging it a little harsh?
That's his job. To be a smartass and teach the trolls how it's done.
And under his watch, the editorial quality of slashdot has increased significantly over time, haven't you noticed? (Oh wait... no it hasn't.)
-b
For what it's worth, I participated in the first calf trial of this device at Louisville.
You are a bovine?
-b
Update: forget about this... I misunderstood the issue. The article and summary say "javascript dialog box" which I took to mean one of those spawned by alert() or prompt() call. Evidently they're just talking about a regular window.
-b
I thought Safari fixed this many months ago, with a change whereby the JS alerts come down in the form of sheets attached to the window/tab to which they correspond? I could swear there was a /. piece on exactly this.
Or maybe I'm clued out and this is something different?
-b
so middle of the road it might well be the white line
Huh, where are you driving?!
-b
Horse hockey!
I'd pay to see that. Guaranteed to be more interesting than the NHL lately.
-b
Know why Macs could read PC disks but not vice versa? Easy. Apple's HFS filesystem was copyrighted ;-)
I thought it had to do with the physical geometry on the disk. IIRC, something to do with the Mac drives spinning the disk at a variable velocity whereas PC drives ran at a constant velocity.
Maybe I am partly confusing the issue with Amigas not being able to read Mac floppies, but I presumed the issue was similar.
-b
Coding would be infinitely expensive if you pour money in and gain nothing
Is this the new math? Seems to me that if you pour in X dollars and gain nothing, the expense is not infinite, but X.
-b
Hmm... that's true. You're right, my question was perhaps a bit off-the-cuff.
I had it in the back of my mind that "satellite-based" internet services give terrible lag though, hence this inquiry. Why would they be high-latency relative to wireline?
-b
repeat: uh, latency?
So in other words, "not in my back yard please?"
I'm not sure who has the more narrow view of globalism, here.
-b
For better or for worse, Microsoft has definatly become a better company because of open source.
Whenever someone misspells definitely as "definatly", I often read it as defiantly. Sometimes, depending on the context, it's an even more appropriate word.
-b
it is pretty easy to see that someone has been fired over blogging already
Also: Dooce, etc.
-b
Repeat after me: Netscape, Is, Now, Just, A, Brand.
Per, haps, but, I, always, find, gratuitious, punctu, ation, to, be, annoying?
-b
The Mac OS X writes data to the machine's NVRAM on kernel panic, which is then retrievable and interpretable once the system reboots.
-ben
There are agreements in place that require overseas suppliers to charge me UK sales tax
Please cite these agreements.
The EU would like to have the rest of the world act as its tax collector; remarkably, many of the large American corporations have bent over already. But as small suppliers, I and many of my colleagues are scratching our heads saying "wtf".
-b
I serve web and mail for a whole bunch of domains off of two servers which are far apart and unrelated (geographically and in terms of network topology). Under normal conditions one is primary and the other secondary; the two of them sync up via cron and rsync at ten-minute intervals. The A records for web sites point to the primary, it has a higher-preference MX and so on. Both machines are authoritative DNS for all domains.
I have TTLs on all the domains set to 120 (yep, two minutes). The idea is that in case of failure of the primary, the secondary will reconfigure itself as primary and begin handling all traffic, while the end user will experience a maximum of two minutes downtime.
With 278 days uptime on the primary though and great service from the colo provider, I've never had to implement this scenario. Is my planning fundamentally flawed? Is this an unadvisable practice?
-ben