Live data from Hacker News

Bloatware and the 80/20 Myth (2001)

joelonsoftware.com

11–20 of 59 posts

Re: Bloatware and the 80/20 Myth (2001)

#11
The 20% thing is interesting, but Microsoft themselves later empirically established through application usage metrics that there is an ordering of features.

That is, some features (eg, italics) are used more than others (eg, macros). Such an ordering can be used to established, with considerable confidence, the "20% that 80% of customers use".

Which is how we got the Ribbon. It was intended to place the most commonly used features front and centre.

Re: Bloatware and the 80/20 Myth (2001)

#13

The 20% thing is interesting, but Microsoft themselves later empirically established through application usage metrics that there is an ordering of features. That is, some features (eg, italics) are used more than others (eg, macros). Such an ordering can be used to established, with considerable confidence, the "20% that 80% of customers use". Which is how we got the Ribbon. It was intended to place the most commonl…

> Which is how we got the Ribbon. It was intended to place the most commonly used features front and centre.

So how come we ended up with something that placed all the features front and centre?

Re: Bloatware and the 80/20 Myth (2001)

#14

15 mb? I was using Excel on the Macintosh for laboratory analysis as early as 1987. It could run on two 800K floppies. So, 1.6 mb. It had 80% of the functionality I ever used Excel for.

The version of Excel mentioned in the article was Excel 5.0 for Windows, that came out in 1993. No one is denying that previous versions were been smaller.

Re: Bloatware and the 80/20 Myth (2001)

#15
I strongly disagree with Joel here. It's true that storage is much cheaper today, but every piece of software I use is downloaded from the internet. Not everyone has 10MBit connections. If you make software, and especially updates, unnecessarily large, you will cut off a percentage of your users.

I'm not saying you should axe features to make the app smaller. But please, if you distribute software, spend a few hours and try to make the download size as small as possible.

Re: Bloatware and the 80/20 Myth (2001)

#17
post #13

The 20% thing is interesting, but Microsoft themselves later empirically established through application usage metrics that there is an ordering of features. That is, some features (eg, italics) are used more than others (eg, macros). Such an ordering can be used to established, with considerable confidence, the "20% that 80% of customers use". Which is how we got the Ribbon. It was intended to place the most commonl…

> Which is how we got the Ribbon. It was intended to place the most commonly used features front and centre. So how come we ended up with something that placed all the features front and centre?

I'm not sure I follow you.

Re: Bloatware and the 80/20 Myth (2001)

#19

Joel writes this like bloat doesn't exist, and discusses how programs are large because of all the features they have. Two contrasting examples spring to mind: - Outlook 2010 in Exchange mode usually occupies about 50MB of memory, at least for me. Think of all the functionality Outlook 2010 has in those 50MB. - An old notebook I used a few years ago had a disk-parking feature, in case of drops. The service applicatio…

His article is bloatware.

He tries to justify hisbloatware work from the past, and only uses false arguments, like dismissing linus argument about having to load a huge program not being an issue, when excel and outlook are still the only applications i use with a damn loading screen... His article uses space and provide no honest statement, hence bloatware.

Re: Bloatware and the 80/20 Myth (2001)

#20

The 20% thing is interesting, but Microsoft themselves later empirically established through application usage metrics that there is an ordering of features. That is, some features (eg, italics) are used more than others (eg, macros). Such an ordering can be used to established, with considerable confidence, the "20% that 80% of customers use". Which is how we got the Ribbon. It was intended to place the most commonl…

I love the Ribbon. It's fantastic for grouping like functionality together and, most importantly for me, it provided just about every single function with a sequence of keyboard shortcuts. Pilot enough spreadsheets or produce enough decks, and they become muscle memory. I'm sorely disappointed that Microsoft still hasn't brought it to the Mac. The design choice to make the Office for Mac apps look more Mac-like has been a bad one.
Post reply on HN