Yeah, as minimal as possible.

Note the minimal, bohemian lifestyle demonstrated in the linked picture.

He also purchased 20,000+ square feet of house in what I assume must have been a demonstration against the evils of capitalism, right?

Have you ever been so far as to wanting the Microsoft needful search? With JavaScript, you will experience the very social!

As modern Internet Explorer browser and functionality such as JavaScript support, download and try requested site again. ...

Yeah. About that... I'll leave NoScript on, thanks. :D

Come again?

What "family values" are these? If you're talking about the educational values of "yes, your child *can* and will fail if he doesn't work" or "no, we're not going to change his grades because you bitched about it", then I'm with you.

If, on the other hand, you're using "family values" in the way that many "Republican" candidates have... I'm not so sure that's the root problem.

I was about to comment with a similar slam of iOS by linking to the bug tracker and source repository for it, but then I realized that Radar (Apple's bug tracker) is private, and iOS is closed source.

Funny isn't it. When iOS development is in question, $99 to join the developer programme is too much money. But when it's Android, spending $thousands on test hardware is neither here nor there. It's even waved away with fantasies of free test hardware for developers.

Or, alternatively, it's possible that *both* are too much for some low levels of hobbyist developer. The difference is that the Android cost isn't a barrier to entry for version 1.0 by the "bedroom programmer" types.

A lot of good software starts as "some dude writing a program to do that thing that he needs" and goes from there. If he has to pay $99 just to scratch that itch, he might just learn to ignore it. If he's got an Android phone, writing and publishing an app to "scratch his itch" is as simple as grabbing the SDK and firing up Eclipse.

It's important to distinguish between a platform's appeal to the entrepreneurial "professional mobile start-up" types and the classic, "I'm releasing this because it might be useful to you" types. I'd hope that the latter resembles many of us on /. For these people, several large on hardware isn't realistic -- we write what we need for our device and release it so that it might help somebody else. And yeah, for that, $99 often too much.

Actually, in the US at least, only one of those would be *potentially* criminal ("DieJewScum"), and even then only if it could be argued that it seemed to present a threat.

"CohensRKikes", offensive and juvenile as it is, is legal. It's protected speech for me to call somebody a "kike", just as it's protected speech for someone to call me a fat Polish fag.

Can you describe it without the weasel words?

What do you mean when you describe Debian as "crufty"? What do you mean when you say Arch is "fun"?

I could use those words to describe just about any distro, but they don't really communicate anything other than that you prefer Arch over Debian for some unspecified reason(s) -- which we could easily guess from the rest of your post.

I'm not saying it is or is not a good distro -- I just don't think that "crufty" and "fun" mean much of anything. As The Dude says: "Yeah, well, you know, that's just, like, your opinion, man."

Confirmation bias ahoy!

There was *plenty* of crappy hardware back in the 70s/80s. It's just that the crappy stuff never lasted long enough for geeks like you and I to get all nostalgic about it.

I think it's still indicative of the problem GP mentions. The more code you are trying to pull in, the larger the footprint during the build process. You don't see a 'Hello world' program requiring a 3GB+ build footprint do you? No, because it's not doing enough to warrant that. Likewise, Firefox apparently *is* trying to do a lot. More than it used to at any rate.

Well you're right in that Firefox does need a hell rather large amount of RAM to build... but it's not just them; all browsers are trying to do a lot nowadays.

Chrome doesn't exactly have light build requirements either. In fact, the Chromium project already seems to have dropped 32-bit build environments:

A 64 bit OS is highly recommended as building on 32 bit OS is constantly becoming harder, is a lot slower and is not actively maintained.

(From "Build Instructions (Windows) - Build Environment")

That's why I think that the parent poster's implication that it's due to Firefox becoming "bloated" is basically hogwash. Browsers are more complex than they were in the mid-90s. That's what happens when you add 10+ years of new formats and technologies that must be supported for a browser to be considered "usable". Directing one's ire at Firefox is unwarranted, IMHO.

An excellent takeaway from this article.

Unfortunately, it's completely incorrect. TFA is talking about the build process on a 32-bit host, specifically that VS builds using profile-guided optimization require more memory than is available in the address space *DURING THE BUILD PROCESS*, not an issue encountered by the resulting binary.

I know you want a chance to get in a quick dig at Firefox, but this isn't the article for that.

You're technically right, but you're being misleading by comparing TMI to Chernobyl and you know it. From the article you linked to:

The average radiation dose to people living within ten miles of the plant was eight millirem, and no more than 100 millirem to any single individual. Eight millirem is about equal to a chest X-ray, and 100 millirem is about a third of the average background level of radiation received by US residents in a year.

So did it spread radiation to "our east coast"? Yes. Did it spread any significant, or even slightly meaningful radiation to our east coast? No.

Even better, the GUIs for things like Exchange 2010 allow you to view the CLI commands being used for any of the changes you make, so that you can easily script them, rather than having to try and work out which particular command and property name that checkbox needs.

Holy SMIT! (Everything old is new again.)

Annnnd now I feel old.

The sponsor will not be given any special treatment with regards to comment score and moderation. The "expert" the sponsor will be providing to take part in the conversation will have an account which is "badged", meaning that it will be visually apparent when the a comment was posted by the sponsor.

So essentially the sponsor's representative can be modded up or down in the same way as anyone else? I can't see that going down well in companies without a sense of humour.

That is not a bad thing.

I hate to break it to you, but Ubuntu's UI is Unity, not GNOME Shell. It has nothing to do with GNOME.

Has it occurred to you that some people don't share your view that everyone should be forced to use their code in a way consistent with Stallman's ideologies?

(As an aside: Apple has actually done a fair bit -- but since you're borderline trolling I wouldn't expect you to mention that.)

And yes, I do use FreeBSD exclusively on everything but my laptop. Who gives a shit if it's not listed on some popularity-ranking website? There were plenty of doofuses saying the same thing about Linux when it started, and Mac OS X back in 2001.

The BSD license allows people to use code for pretty much whatever purpose, provided that they don't claim to have written it. The GPL allows people to use code for whatever purpose -- provided they conform to the GPL ideology, license their code under the GPL, and don't use it in certain ways that Stallman et al. think are unacceptable.

You tell me which embodies the spirit of freedom more.