Ask Slashdot: Which Businesses Will Go Away In the Next 10 Years? (nbcnews.com)

AmiMoJo writes: Ten years ago NBC published a list of business types that it predicted would disappear in the following decade. Ten years later and we can see how good their fortune telling was. What businesses do you think will go away by 2027? Who is destined to become the next buggy whip manufacturer, whose demand dried up due to changing technology and a changing world?

For reference, NBC's list was: Record stores; Camera film manufacturing; Crop dusters; Gay bars; Newspapers; Pay phones; Used bookstores; Piggy banks; Telemarketing; Coin-operated arcades.

Comments

Lobbyists

[Pseudonym]

Just kidding. Lobbying will be a growth industry for the next decade at least.

Re:Mozilla will likely disappear before Google.

[ArmoredDragon]

I doubt it. Remember that Google Chrome literately stole Safari and rebranded it Chrome

Were you born retarded, or were you just kicked in the head by a horse later in life?

The only thing Chrome shares in common with Safari is that older versions of Chrome used the same rendering engine as Safari called Webkit. Webkit itself was a fork of KHTML (of the Konquerer web browser,) which was written by KDE. Google, at one time, made the majority of the contributions to Webkit to support a lot more HTML5/CSS features. Google then forked only the WebCore component of Webkit because they wanted to support sandboxing, deprecate vendor tags, and use a multi-process model. This fork became the Blink rendering engine that other browsers besides Chrome use, such as Opera and Vivaldi.

Ever since Google stopped contributing to Webkit, Apple has been developing it at a snail's pace, just like IE6 back in the day, making Safari the lowest common denominator, which is pissing off a lot of developers. Perhaps because Apple wants users on their app store (read: $$$) rather than on the web? Pretty much the same motivation Microsoft had (Microsoft literally circulated an internal memo describing the web as a threat to its cash cow, Windows.)

Re:Not prophetic, but very accurate

[darkain]

In fact, some of those are actually on a massive rise due to recent retro trends. Arcades and more specifically Barcades are popping up all over the place now. Film cameras are as of 2017 just starting to make a retro comeback as well. Used book stores seem to be doing just fine, too. Amazon only killed off retailers, not the second hand market. In fact, vinyl records also has a surge going on right now. So like almost half their list is currently being fueled by nostalgia into new market territory.

Re:Mozilla will likely disappear before Google.

[Anubis IV]

You got most of that right, but one important correction: Chrome had a multiprocess model years before they ever forked Blink from WebKit, and WebKit already had a multiprocess model by the time Blink was forked.

Backing up a bit, years and years prior to the split, Google baked a multiprocess model into Chromium, rather than WebKit. This gave Chrome a major competitive advantage over Safari and other browsers that relied on WebKit. Apple, of course, wanted to have a multiprocess model as well, so they later baked it directly into WebKit, but it was a significant enough departure that they forked it as WebKit 2. As you’d expect, Google didn’t contribute much (anything?) towards WebKit 2 since it wasn’t compatible with their existing multiprocess model, and, as you’d expect, Apple’s contributions towards WebKit dried up as they focused on WebKit 2. Making things even more interesting, WebKit 2 was a buggy mess for quite awhile, so Apple itself didn’t even adopt it in Safari for Mac or iOS immediately, and Google would have had even less reason to adopt it.

Google’s eventual forking of Blink from WebKit was really the natural conclusion to the choice Apple had made years earlier when they forked WebKit 2, which was itself the natural next step after Google decided to keep its multiprocess model to itself, which was itself the natural next step after Apple left such a glaring hole in WebKit’s architecture, and so on and so in.

Re: Slashdot

[angel'o'sphere]

Logged in you can only post once per minute, and if you are above a certain amount per day, every 5 minutes.
And there is a maximum of posts per day, 25 or 50, don't remember.

Re:Mozilla will likely disappear before Google.

[TheRaven64]

Google then forked only the WebCore component of Webkit because they wanted to support sandboxing

Except that Google supported sandboxing in a crappy way. Apple implemented sandboxing in WebKit, so every application that uses WebKit gets the benefit. For example, when you view an HTML email in Apple Mail, it's rendered in a separate process that has no network or filesystem access, and the changes to enable this amount to about 4 lines of code (basically, opt into this behaviour and promise that you won't use any of the deprecated APIs that it breaks). In contrast, Chrome puts the sandboxing in the browser, so anyone using Blink has to implement their own sandboxing layer.