Earlier quoted context omitted.
Right before that era I worked on Mosaic for Windows, and the Mac developers sat across the stairwell from us. The Mac guys had a very love hate relationship with Macs. On the one hand the lead was infinitely proud of being able to have 2 (or was it three?) monitors on his desk, big CRTs on a desk designed during the Cold War, by a designer who had nightmares about nuclear blasts and wanted someplace safe to duck and…
>On the other hand they were writing what is ostensibly a concurrent application on an operating system with no protected memory and no pre-emptive multitasking, so the whole thing was using hand-rolled cooperative multitasking via C longjumps. It's no wonder the Windows team had an easier time keeping up with Netscape for that golden year. As one among your customer base for both versions, indeed. People who never u…
Ask HN: Was anyone working at Apple during Steve Jobs' return in 1997?
251–260 of 322 posts
Re: Ask HN: Was anyone working at Apple during Steve Jobs' return in 1997?
#252I was at Claris (subsidiary of Apple at the time, my paychecks were from Apple) up in Portland right before then. Everyone in the office was really excited about the BeOS (edit, not Steve Jobs, but a new company by former Apple employees). We had a few devices. I remember the demos where they would click on a button to turn off a processor in the GUI while rendering a mandelbrot image, and it would slow to a crawl. I…
Claris is STILL a subsidiary of Apple
Re: Ask HN: Was anyone working at Apple during Steve Jobs' return in 1997?
#253I've only heard it twice, and only once in any detail. It strikes me as both far fetched rationally but also weirdly possible with Jobs.
Re: Ask HN: Was anyone working at Apple during Steve Jobs' return in 1997?
#254Earlier quoted context omitted.
Right before that era I worked on Mosaic for Windows, and the Mac developers sat across the stairwell from us. The Mac guys had a very love hate relationship with Macs. On the one hand the lead was infinitely proud of being able to have 2 (or was it three?) monitors on his desk, big CRTs on a desk designed during the Cold War, by a designer who had nightmares about nuclear blasts and wanted someplace safe to duck and…
> A lot of Apple's OS people ended up going to Palm, where they made pretty much the same set of tradeoffs. It was very weird watching subsequent Palm models start to bump up against the same ceiling. Didn't know about this. This is before ‘webOS’, right? What kind of OS problems are we talking here?
In 1996 Palm OS had hardcoded screen resolution with no color support. They had no memory protection. Palm also used already-obsolete DragonBall/68K processors when faster ARMs were already available.
Re: Ask HN: Was anyone working at Apple during Steve Jobs' return in 1997?
#255Earlier quoted context omitted.
The iron law of bureaucracy: Pournelle's Iron Law of Bureaucracy states that in any bureaucratic organization there will be two kinds of people: First, there will be those who are devoted to the goals of the organization. Examples are dedicated classroom teachers in an educational bureaucracy, many of the engineers and launch technicians and scientists at NASA, even some agricultural scientists and advisors in the fo…
I've always wondered what the Iron Solution to Bureaucracy looks like. Usually it's smaller companies eating the big companies lunch via competition. But that usually takes a very long time (or competition is crushed by 'good intentions' aka gov policy). I know 'intrapenuership' and spawning isolated startups internally, where teams that are walled off from the middle managers of the larger company, was pushed by Cla…
Open Source?
Specifically, removing the power to coerce.
Re: Ask HN: Was anyone working at Apple during Steve Jobs' return in 1997?
#256Re: Ask HN: Was anyone working at Apple during Steve Jobs' return in 1997?
#257Earlier quoted context omitted.
Well he did cut Stadia, which had a sizable team working on it.
The fact that Stadia even launched was a failure. The most basic of market research would tell you that in gaming, content is king. And with Google's track record of cancelling products, nobody would trust what they offered even if it was vastly technically superior.
The only problem is I may have been the only person in the target market so that wasn't going to work financially... And even I was going to have an exceptionally low LTV at maybe one game purchase per year (or less). And if they charged a monthly subscription, I'd never do it. So, yeah, terrible business.
But Google's track record wasn't a showstopper for me on a toy. It's different for business stuff like GCP.
Re: Ask HN: Was anyone working at Apple during Steve Jobs' return in 1997?
#258Earlier quoted context omitted.
No, Gil and Ellen were incompetent. If they had understood how to separate the wheat from the chaff, a useful version of Copland could have been out in 1997. They were not willing to say no and fire people. The first thing Steve did when he took over? Mass layoff. It was absolute malpractice to buy NeXT for the OS, which was an obsolete, moribund, and expensive version of Unix. What they ended up getting was adult ma…
How could Apple could have gotten a real OS more quickly? The Mac OS of the time had no preemptive multitasking or protected memory, so software running on it was doomed to be made unstable by all the other software. NextStep, maybe it was what you say, but they needed to make a change.
Re: Ask HN: Was anyone working at Apple during Steve Jobs' return in 1997?
#259Earlier quoted context omitted.
> Ask where the documentation is. I've had a reasonably long career and worked at a number of companies at this point, and I've never seen this 'documentation' that engineers are supposedly producing.
I think existence of documentation is a poor metric, personally.
Re: Ask HN: Was anyone working at Apple during Steve Jobs' return in 1997?
#260Earlier quoted context omitted.
That's 36 classes per *day* (900/250 workdays) I don't know how many people were working on that but when developing standard library you do not really want to rush designs. You want to be very, very careful about it. Here's a book about it from one of the most experienced people in API/Standard lib design on the planet https://www.amazon.com/Framework-Design-Guidelines-Conventio...
I think the first part of a standard lib is pretty straightforward to design. String operations, math, standard protocols, I/O are petty well understood. It gets more tricky once you get to higher levels abstraction like UI.
Tell that to Haskell.
Also, I've seen some pretty gnarly use of String in Java.