Live data from Hacker News

Ask HN: Was anyone working at Apple during Steve Jobs' return in 1997?

news.ycombinator.com

41–50 of 322 posts

Re: Ask HN: Was anyone working at Apple during Steve Jobs' return in 1997?

#41

Earlier quoted context omitted.

Sounds about right for Java..

I disagree with what I call Java's OOP obsession, but I have to admire the drive behind that ecosystem.

I'm disgusted by it, but admire the ability for the system to run in spite of the mess that the pattern generate.

Re: Ask HN: Was anyone working at Apple during Steve Jobs' return in 1997?

#42
post #16

It's hard to overstate how bloated Apple was internally. Marketing had products for every conceivable niche. Engineering was all posturing: great hand-waving plans papered over nasty middle-management infighting. Hundreds of engineers in new glass-walled offices, producing plans. I wrote test code against a component that had been delivered months earlier only to find that it was just a stub. Even the debugger had bu…

You guys were creating Java? > ~1,000 classes in 1.1, ~10K in 1.2 the next year. 9K classes in a year sounds crazy as hell

A typical well-designed class will usually be a few hundred lines of code, tops. Often less than 100 lines.

9k classes * 100-300 == 900k-2.7m LOC

Not TOO crazy for the most complete standard library ever developed, for a language meant from the beginning to take over enterprise business computing.

How many LOC are in whatever meme language is hype this year? Hell, I feel like I see nearly that many lines of console output, when I run NPM to pull in dependencies, lol.

Re: Ask HN: Was anyone working at Apple during Steve Jobs' return in 1997?

#43

Earlier quoted context omitted.

You guys were creating Java? > ~1,000 classes in 1.1, ~10K in 1.2 the next year. 9K classes in a year sounds crazy as hell

Sounds about right for Java..

How many classes do you think it should have, ballpark, given the same feature set? GUI toolkits alone can produce thousands of classes because there are thousands of concepts that make sense to model, then add on security, collections, many utilities, XML handling, multiple RPC systems and so on. It's hard to over-state how large the Java standard library is.

And it's not like other ecosystems do better. The standard complaint about JS is that you try to do something basic in that ecosystem and discover you have 10,000 modules in node_modules. Not so different, really, except that the Java stuff comes from a single team with a relatively coherent design philosophy.

Re: Ask HN: Was anyone working at Apple during Steve Jobs' return in 1997?

#44
post #16

It's hard to overstate how bloated Apple was internally. Marketing had products for every conceivable niche. Engineering was all posturing: great hand-waving plans papered over nasty middle-management infighting. Hundreds of engineers in new glass-walled offices, producing plans. I wrote test code against a component that had been delivered months earlier only to find that it was just a stub. Even the debugger had bu…

Your description of 1997 Apple sounds uncomfortably close to modern Google. I miss working for startups.

That was also echoing through my brain while reading through the comment (worked there awhile ago)

It would be crazy if someone just shook up the whole company top to bottom, but google is still making money and apple wasn’t

So I think it will never happen

Re: Ask HN: Was anyone working at Apple during Steve Jobs' return in 1997?

#45

Earlier quoted context omitted.

You guys were creating Java? > ~1,000 classes in 1.1, ~10K in 1.2 the next year. 9K classes in a year sounds crazy as hell

Sounds about right for Java..

Sounds like a typical enterprise Java hello world type application.

Re: Ask HN: Was anyone working at Apple during Steve Jobs' return in 1997?

#46
post #19
post #16

It's hard to overstate how bloated Apple was internally. Marketing had products for every conceivable niche. Engineering was all posturing: great hand-waving plans papered over nasty middle-management infighting. Hundreds of engineers in new glass-walled offices, producing plans. I wrote test code against a component that had been delivered months earlier only to find that it was just a stub. Even the debugger had bu…

What do you look at in engineering culture?

I would assume there is no one thing to put a finger on. But there are some signs one can take a note of. Generally speaking, to name a few:

- The ability and willingness of the management to invest time and resources into development of proper work processes and infrustructure (imagine having to code without version control in a team)

- Understanding that things aren't always done the moment they appear to be done

- Realization that many things are done to lower the cognitive load exclusively (why do we have to spend 20 hours refactoring the thing if it already works?)

- Understanding why it is important to lower the cognitive load

- And dozens more

These are merely signs, though. One can put 'dnd' signs on doors, but what difference does that make if the same people who introduce the signs still disturb the people behind the doors whenever they feel like it. (no pun intended, couldn't word it better)

It comes down to understanding the nuances, and mutual respect, I think?

Re: Ask HN: Was anyone working at Apple during Steve Jobs' return in 1997?

#47

Earlier quoted context omitted.

Sounds about right for Java..

How many classes do you think it should have, ballpark, given the same feature set? GUI toolkits alone can produce thousands of classes because there are thousands of concepts that make sense to model, then add on security, collections, many utilities, XML handling, multiple RPC systems and so on. It's hard to over-state how large the Java standard library is. And it's not like other ecosystems do better. The standar…

If it is necessary to have that many classes, then there should be so many classes.

but in Java everything is a class, main function? in a class. a library of static functions? in a class.

Re: Ask HN: Was anyone working at Apple during Steve Jobs' return in 1997?

#48
post #44

Earlier quoted context omitted.

Your description of 1997 Apple sounds uncomfortably close to modern Google. I miss working for startups.

That was also echoing through my brain while reading through the comment (worked there awhile ago) It would be crazy if someone just shook up the whole company top to bottom, but google is still making money and apple wasn’t So I think it will never happen

Nothing is forever.

Re: Ask HN: Was anyone working at Apple during Steve Jobs' return in 1997?

#49
post #16

It's hard to overstate how bloated Apple was internally. Marketing had products for every conceivable niche. Engineering was all posturing: great hand-waving plans papered over nasty middle-management infighting. Hundreds of engineers in new glass-walled offices, producing plans. I wrote test code against a component that had been delivered months earlier only to find that it was just a stub. Even the debugger had bu…

Your description of 1997 Apple sounds uncomfortably close to modern Google. I miss working for startups.

It's very much apples to goggles - google is gigantic, mature company with some problems and one that makes occasional missteps. It still makes many things people like, including truckfuls of money. 1997 Apple had a very enthusiastic userbase, small and dwindling market share, mostly terrible products and was teetering on the edge of extinction.

Re: Ask HN: Was anyone working at Apple during Steve Jobs' return in 1997?

#50
post #44

Earlier quoted context omitted.

Your description of 1997 Apple sounds uncomfortably close to modern Google. I miss working for startups.

That was also echoing through my brain while reading through the comment (worked there awhile ago) It would be crazy if someone just shook up the whole company top to bottom, but google is still making money and apple wasn’t So I think it will never happen

Good point, it's not a good comparison.

> it will never happen

I can see it happening. They have just one cash cow in advertising, and it's not terribly secure. TikTok is already a serious threat to YouTube. If this became a crisis, it wouldn't sink the company, but it'd certainly shake it up.

Post reply on HN