It's somewhat true that there's a bell curve in taxation, peaking with the middle class.

1) The poor have nothing to tax. They are generally on welfare or just off it, and struggling. The "freebies" a la "welfare" is not so much about the welfare receiving parents as giving their kids a chance to break out of the poverty trap, which they can't do if undernourished or uneducated.

2) The middle class has something to tax, but don't have the resources to defend themselves adequately. This is where the peak begins.

3) The upper middle class has a lot to tax, and is just starting to have enough resources to start to defend themselves, This is where the taxation peak starts to drop. (pretty much: between the 2% and the 0.5%)

3) The super wealthy hold all the cards. They can hire legions of lawyers and bankrupt countries if need be. This category controls or directly owns 50% of the world's wealth. Taxation doesn't even make sense to this class.

10+ years ago, I used to log all packets that didn't "fit" in expected services. It really was an eye opener, there are perpetual and constant probes of all sorts, all day long. We're not talking actual attacks, just the equivalent of walking around, trying doors to see if any are unlocked or even present.

At that time, I was logging well over 1,000/day on a *home 1.5 Mbit DSL modem*. Today, I would log that many actual attacks against our small-ish website every few minutes if I cared to log them. The Internet is an incredibly hostile place, and it's only because the routers, servers, and networks etc. are actually rather good at their job that we manage to make it such a useful tool.

Somebody had to see these notes, decide that they were worthless, and actually roll them up to make insulation. I want to punch that guy. How does this happen!?!?

Although Apple has never officially acknowledged issues surrounding Yosemite and Wi-Fi connectivity, the company is clearly aware of the problem: Leading off the improvements offered in the update 10.10.2 update released Tuesday was 'resolves an issue that might cause Wi-Fi to disconnect,' according to the release notes.

So basically, you said that Apple haven't acknowledged the problem, then quoted them acknowledging the problem?

Please stop with the "sky is falling" routine - it only makes the problem worse and the stakes are too high to just throw your hands up in the air and give up in blissful ignorance.

I suspect that, at a basic level, you have a fundamental misunderstanding as to what a "certificate" is and does.

1) A cookie is an identifier that allows you to tie numerous http(s) sessions together by domain. It can thus be used to track you by having many sites contain images or content from a common domain. (EG: doubleclick.com)

2) A certificate is used to negotiate a private session with a single domain. It's provided by the server and validated by the client to set up an encrypted connection. It allows you, the user, to verify that you are connected with the correct domain and *not* a nefarious person. The use of HTTPS and certificates foils the Verizon "supercookie" as they have no meaningful way to pierce the encryption provided between you and, say, Google.com.

It is broke though. Look at the SendFile bug, for example. It's been there for years, it bites a tonne of people who try to virtualise web servers, and there has been seemingly no attempt whatsoever to fix it. Its kernel drivers on OS X and Linux aren't particularly stable either.

the functionality of the devices is about the same

It's very different. On Android, you have to decide whether to grant permission before you've ever run the application, and it's all or nothing. On iOS, you run the application before deciding whether or not to grant it permission. You have the ability to deny permission while still running the application. You can also allow permission for some things but not others.

This functionality is partially available to Android users who root their phones and install the right tools, but that's far from the common case.

It's true that the majority of the profits in App Store sales is focused at the extreme top, but it's not true that 99.999% of the rest make "near 0". This analysis estimates that the top 3,175 applications earn at least the average annual income for a US household per year, and applications that rank about number 6000 still earn $25K/yr.

And that's only counting App Store revenue. I've earned a lot more than average since I started developing for iOS, and most of the applications I've worked on are free. You don't see things like banking applications earn revenue directly, but the developers responsible certainly profit from it. The Facebook application is free, but you don't think its developers are working on it for free do you? I've been paid to built plenty of enterprise applications that will never appear in the App Store.

There is a huge amount of profit in the "app economy" that will never be accounted for merely by looking at App Store profits. The "app economy" is much bigger than the App Store.

I'm probably going to lose some karma for this...

I, too, could come with a half-dozen answers that would be "far superior" to what 100+ years of the finest minds in the industry could come up with. But in reality, I really, seriously doubt that my designs would hold up because there's a *reason* that things are done the way they are.

Mechanical engineering is a *very old* industry, and any radical, new design would have significant hurdles to pass before it could be accepted and used in a real scenario. The cost of failure is very high and there are real lives on the line.

My first thought was to use something like a caterpillar drive along the sides of the shaft, each of which would operate like a mini elevator for perhaps 10 floors. But, very quickly, I can see that this type of system would have many, many more moving parts and consequently many more points of failure.

So, I think it *might* be best to trust that 100+ years of experience are, in fact, at work, and that we should first understand that there is *real knowledge* at work before assuming that our half-baked and thoroughly unproven ideas hold any merit in reality.... ?

It wasn't impossible to write cross platform browser stuff in the late 1990s, when most corporations started this whole "We'll standardize on browser X" policy making, but it required a discipline that had most developers throwing their hands up in the air in disgust.

I had these arguments many times back then. It was laziness more than anything else. We were writing cross-platform web applications without problems at that time. We were trying to convince other developers to follow the same route, but their attitude was mainly "IE has 90%+ market share, why bother?" They didn't believe a time would come when proprietary IE code wouldn't work - even if other browsers caught on, they were expecting them to copy the IEisms. They certainly didn't believe that even later versions of Internet Explorer wouldn't support their crappy code.

- IE4+ was the most standard. Yes, really. Those versions had a relatively complete implementation of CSS.

Let's not overstate things. Netscape bet on JSSS and when the W3C selected CSS as the standard instead, they scrambled to fix Netscape 4 to convert from CSS to JSSS on the fly. So Netscape 4 was exceptionally bad at CSS. Internet Explorer 4 was merely very bad at CSS. Opera was ahead at that time. I don't think you can call IE4 "relatively complete" unless you only compare it to Netscape 4, which was unusually bad.

reverse engineering is allowed, and could be opening themselves up to legal action.

Just because reverse engineering is legal, it doesn't mean WhatsApp are legally obligated to provide their services to third-party clients.

The legal matter here is the blatant trademark infringement by WhatsApp Plus.

If they are making it easy to run "normal" Linux, why not install the appropriate libs and allow Linux apps to run side-by-side with Chrome apps?

I prefer Apple to keep iMessage to themselves. It will make sure its adoption never become widespread.

It's already widespread. Several billion iMessages are sent per day.

Are you switching to BSD just for ZFS?

Learning BSD is probably a good investment, but ZFS on Linux is production/stable and is excellent. I've been using on CENTOS 6 for over a year and it has been even more stable than EXT4 in a production environment.