Exactly. Check out EnterpriseQualityCoding/FizzBuzzEnterpriseEdition for a "proper" example:
https://github.com/EnterpriseQ...

Linus Q&A at Debconf 2014
https://www.youtube.com/watch?...
starts at 18:43

"I think systemd does a lot of things right."

"Systemd gives a lot of features you couldn't get any other way. The boot-up speeds are real. And it's not saying you couldn't get the same things with non-systemd. But systemd stepped up and did it."

"I think the fight is mostly over."

"The lack of portability is sad. The thing I that I absolutely hate is that the bug reports have been basically ignored in some cases."

"I realize people expected me to hate systemd. I don't hate it, really. I think it is somewhat interesting and it has quirks, but what does not?"

Stock holders are forgiving to Apple because they constantly show profits. Even during the dot-com implosion, Apple continued to show growth and profits in their Mac lines as the rest of the PC industry struggled.

Amazon is the opposite. Amazon has never had a profitable quarter. Instead their spending always outstrips their revenue. Stock holders have been amazingly patient because Amazon has been doing this for like 20 years now. But a $170 million write-down is a lot of money (unless you are Microsoft, and they at least have enormous profits to offset their huge billion dollar losses), especially for a company that has never had a profitable quarter.

And this is for a product that everybody sees as outside Amazon's strengths. And the market reaction shows there is little interest and demand for this product, yet Amazon intends to double-down.

Considering it has been over 20 years, I'm surprised Amazon hasn't seen a lot more criticism. Kudos I guess to Amazon's ever-patient shareholders.

You are correct. But there is a much more direct answer to defend Bubble Sort.

In the real world, i.e. on real hardware, bubble sort usually faster than other algorithms for small data sets. This is due to cache locality. A cache miss can mean the difference between 4 clock cycles vs. over 400 cycles, simply waiting for 4 little bytes to be read from RAM.

Cache misses are now the biggest problem for high performance programming. For instance, (good) video game programmers are very aware of this fact.

Agreed. And for the op, Obj-C is the best language to use right now. Being well versed in C means he can learn Obj-C in a day. Obj-C is a very small superset of C.

The hard part is learning Cocoa, but that is true of any framework whether that is Swing, Android, MFC, GNOME, Qt.

Swift is so new, you will have to learn Obj-C anyway to learn Cocoa.

The best bet is for the op to write model/cross-platform code in C, and then use Obj-C for the native UI layer. Then repeat for Android/Java (via JNI) and Windows Phone/C++CX.

But is the ratings decline reflective of revenue or an overall problem with the show? Over the past 10 years, television viewership has been falling in general, losing out to other forms of entertainment.

However, the irony is that the cost for advertising in television is at an all time premium. This is because there is still no other advertising outlet that can capture such a wide audience at the same time with and also with well understood demographics.

I thought Dark Matter was conceived to account for missing matter that the Big Bang theory predicts needs to exist.

48 replies to "DON'T FORCE ME TO UPGRADE!...PLEASE!", where the majority are people trying to help the few that are complaining, does not constitute "swamped".

In contrast there are 471 replies to "I show up as Online when I'm not"

No, this is proof we need autonomous vehicles. Consider the current alternative that these "idiots" are driving.

You can tell Siri to enable VoiceOver for you on iOS.

Suck Blue Frog (Quest for Glory 2)
Command parsers were fun.

The thing that happened was Microsoft started building/selling their own devices, competing directly with their former partners. That was a stab in the back and maybe they actually learned their lesson.

The op complaint was no 64-bit Firefox for Mac. Apple doesn't do x32, so it's not even an option.

Data starvation can be mitigated/manually controlled in 64-bit by understanding your data. High performance code utilizes contiguous blocks of memory and is very aware of data layout, and isn't going to be pointer chasing. So allocating arrays of types that use int32_t instead of int64_t is a trivial example. So in a 64-bit architecture, you still generally win performance-wise.

x32 failed for a lot of reasons.
From the article you cited, here's a quote:
"they just really don't see the [x32] ABI as being worthwhile ... to make maintaining an extra ABI worthwhile."

As the quote highlights, the real crux of the problem is how much of a pain it is to maintain yet another ABI.
The performance differences for x32 didn't justify it over true 64-bit. That means the data starvation due to larger pointer sizes wasn't the dominating factor. So going from i386 to x32 vs. i386 to x64, the latter wins because it gets the speed of more registers, negligible performance impact for pointer size differences, and the plus of large addressable memory if you need it.

To show the pain of another ABI, here is a simplified example: You are using a video editor in GNOME under x32. You suddenly need more than 4GB of addressable memory. That means you needs a x64 version. But then you need a GNOME that is also built as x64, so you have to load up an entirely separate instance of GNOME, all its dependencies, and the video editor. Either you need to shutdown your current environment and reboot another, or you need to load both simultaneously. (This is what happens now when you load 32-bit i386 on modern Mac, hence a large RAM hit, not to mention that every binary also takes double the disk space.)

It's not about addressable memory space.

64-bit usually yields better performance due to more registers and the fact that i386 was a register starved architecture.

But more importantly, everything on modern Mac is now 64-bit. Anything that is 32-bit must load in a 32-bit version of every shared system library that the application touches. At a minimum, Firefox would have to load in the entire 32-bit version of the Cocoa frameworks (because Firefox needs to at least create a native window). If Firefox is the only 32-bit app resident on your system (which is highly likely today), then it's wasting gobs of your system RAM and probably making you swap to disk more.

Simply stating "Corporatization" is a massive mischaracterization and oversimplification of describing the situation.
Here is a peek in history from 2005 on the IETF mailing list itself and how IETF tried to sabotage the ratification of Zeroconf (Apple's Bonjour is the best known implementation of the Zeroconf protocol). This isn't simply "Corporatization" as both Apple and Microsoft are fighting and some in the the IETF actively trying to undermine it under the guise of simply offering alternatives (that nobody wants or plans to implement and is broken by design).

Stuart Cheshire is the creator of Zeroconf and calls them out directly on the IETF mailing list in 2005.
http://www.mhonarc.org/archive...
http://www.mhonarc.org/archive...
http://www.mhonarc.org/archive...
http://www.mhonarc.org/archive...