I've heard of Android, but so what? Everywhere I look*, someone is either using an iPhone (or occasionally a Blackberry) and very rarely do I see anything else. I've yet to actually see an Android based phone.
I was about 9, and hadn't really dealt with computers at all. My family didn't own one, and none of the classrooms at school had one either. The extent of my computer knowledge at that point revolved largely around playing Cannon Fodder at a friends place. If you mentioned Apple, Atari, IBM or Microsoft to me, I probably would have given you a blank look. Kids at that age don't have much disposable income to be able to pick and choose what technology they grow up with.
"completely proprietary" - which is why they have so many open source projects going, and use.mbox, documented xml, aac, h.264,.ics...
uh.. hate to burst your bubble there but aac and h.264 aren't exactly open-source.
OP didn't say they were. Apple have many open source projects going (such as Darwin, Clang, OpenCL), and they also use a list of standards that aren't "completely proprietary" (but weren't the examples of open source projects).
I would say no even if they did find out through Facebook. That doesn't change the fact that if you want certain information private, it's not the best idea to publish it.
If you want your "private attendance" of a bar to remain private, don't paste all about it on a public website (if the employers were able to view the data, I'm assuming the privacy settings weren't locked down).
Asking the FSF to intervene in a random GPL case is sort of like asking the printers to intervene in a dispute between you and your car lease company, simply because they printed the lease forms.
Asking the authors of the legal documents for assistance as expert witnesses is a perfectly acceptable thing to do. Your analogy only works if the printers wrote the lease form as well as making physical copies.
That's not a fair test. To be able to come up with a parsing solution to all of those formats off the top of ones head, they need to know in advance all about all of those formats. Not memorising formats that one has never encountered doesn't indicate the inability to design parsers.
Yes, because those that work in office building spend lots of time mounting ~3Gb+ DVD ISOs...not.
I accept that most don't, but I do. See below.
And on what OS? Vista?
It happened on Vista and still happens (to a lesser extent) on Windows 7.
You are a gamer, yes?
No. The ISOs I mount are our in-house product that were generated from the build server (and this happens in the office building that I work in) plus occasional MSDN images for installing test environments in a virtual machine.
If so you should probably be running more than 2Gb of RAM anyway, but I mount large files into mine all the time and never have a problem.
I've since upgraded to 4GB, but even then it won't hold the ISO plus all my running apps plus whatever else Superfetch wanted to pull in.
But if you want to use superfetch without that particular, if pretty rare, problem here is what you do. Simply clear prefetch/superfetch using this handy dandy tool which works on XP-Windows 7.
Thanks, I wasn't aware of that one. I'll look into it.
I always found Superfetch to be useless because when I mount a ~3GB DVD ISO to install something, it keeps fetching that into my 2GB of RAM and then writing it back to the pagefile as it overflows for the next week or more.
Perhaps I exaggerated a little, but there was a big push to try to focus user space as primarily managed code. Singularity et al are doing crazy stuff with managed code in the kernel amongst other things, which is interesting but not what I was alluding to in my original post.
The Engineering Windows 7 blog goes into great detail about the development process that was vastly improved over Windows Vista's.
I'm aware, I followed the blog while it was still active. I particularly found the GDI concurrency post interesting. I wonder if having a similar blog for Vista would have allowed them to realise earlier on that it was going out of control.
Innovation requires risk and not the kind of risks Microsoft took with their Vista debacle. It requires that you do things entirely differently than everyone else. This is not Microsoft. This is not Windows Vista nor Windows 7 nor IE anything.
Microsoft took a big risk with Longhorn and tried to write pretty much the whole OS in managed code (entirely different to everyone else) and it didn't pay off. Most of the delay came from throwing most of that work away and starting again back in native code.
Even if starting the copy is faster for you through a GUI, the copy itself will finish faster with rsync most of the time. Rsync won't retransfer blocks that already exist, and if you're transferring over a network it will use compression.
What's to say the GUI can't use rsync technology underneath? You're now comparing specific implementations of copy technologies in a discussion over interfaces.
Having to replace hardware on commodity computers is hardly due to Windows supposedly being unreliable or complex. Don't get me wrong, I'm not trying to defend Windows here. The whole comparison is apples to oranges, it's silly to expect a consumer grade computer to last 30 years even if it had the mythical perfectly fault free OS.
The main argument that I feel does work in this case is mean time between power cycles. A Windows box really starts to struggle after a couple of months.
Chromium does have addons now, and since it is an open source project it'll be rather difficult for Google to hide snooping mechanisms in it. Also, I highly doubt that Ubuntu will decide to stick with Firefox as the default purely because one user who knows how to uninstall software and install an alternative expressed that they will change from the default.
Of course a Macintosh is no more locked down than a Windows or Linux computer, so there is no issue if we're sticking with computers.
While I mostly agree with that, most of my beef is with the App store and the way Apple tried to leverage their apps onto Windows machines (installing Safari without permission just because iTunes is installed for example). Another issue I have is the way Apple keeps making strange decisions with their port configuration on their computers, for example the removal of Firewire from a bunch of machines, and the new Mac Mini doesn't have HDMI but it does have Mini DisplayPort (without audio support), and as a result most of their advertised connectivity to other devices requires buying additional adapters.
Slashdot Mirror
I've heard of Android, but so what? Everywhere I look*, someone is either using an iPhone (or occasionally a Blackberry) and very rarely do I see anything else. I've yet to actually see an Android based phone.
*Everywhere consists of Melbourne.
I was about 9, and hadn't really dealt with computers at all. My family didn't own one, and none of the classrooms at school had one either. The extent of my computer knowledge at that point revolved largely around playing Cannon Fodder at a friends place. If you mentioned Apple, Atari, IBM or Microsoft to me, I probably would have given you a blank look. Kids at that age don't have much disposable income to be able to pick and choose what technology they grow up with.
"completely proprietary" - which is why they have so many open source projects going, and use .mbox, documented xml, aac, h.264, .ics...
uh.. hate to burst your bubble there but aac and h.264 aren't exactly open-source.
OP didn't say they were. Apple have many open source projects going (such as Darwin, Clang, OpenCL), and they also use a list of standards that aren't "completely proprietary" (but weren't the examples of open source projects).
On which system do you play indie games?
The iPad.
And you should be able to remember Oh! wait... were you in a coma from `90 - `97?
I hadn't even heard of Microsoft until somewhere around 1995 and even then I didn't own a computer until some time after 1998.
Building the same version of source code multiple times is sufficient to raise the version number?
I would say no even if they did find out through Facebook. That doesn't change the fact that if you want certain information private, it's not the best idea to publish it.
If you want your "private attendance" of a bar to remain private, don't paste all about it on a public website (if the employers were able to view the data, I'm assuming the privacy settings weren't locked down).
Darn, so buying that generator was a waste of time.
Asking the FSF to intervene in a random GPL case is sort of like asking the printers to intervene in a dispute between you and your car lease company, simply because they printed the lease forms.
Asking the authors of the legal documents for assistance as expert witnesses is a perfectly acceptable thing to do. Your analogy only works if the printers wrote the lease form as well as making physical copies.
That's not a fair test. To be able to come up with a parsing solution to all of those formats off the top of ones head, they need to know in advance all about all of those formats. Not memorising formats that one has never encountered doesn't indicate the inability to design parsers.
It worked perfectly fine for me.
If you really want Unix, don't install an actual Unix system but instead install Linux which isn't Unix?
Yes, because those that work in office building spend lots of time mounting ~3Gb+ DVD ISOs...not.
I accept that most don't, but I do. See below.
And on what OS? Vista?
It happened on Vista and still happens (to a lesser extent) on Windows 7.
You are a gamer, yes?
No. The ISOs I mount are our in-house product that were generated from the build server (and this happens in the office building that I work in) plus occasional MSDN images for installing test environments in a virtual machine.
If so you should probably be running more than 2Gb of RAM anyway, but I mount large files into mine all the time and never have a problem.
I've since upgraded to 4GB, but even then it won't hold the ISO plus all my running apps plus whatever else Superfetch wanted to pull in.
But if you want to use superfetch without that particular, if pretty rare, problem here is what you do. Simply clear prefetch/superfetch using this handy dandy tool which works on XP-Windows 7.
Thanks, I wasn't aware of that one. I'll look into it.
I always found Superfetch to be useless because when I mount a ~3GB DVD ISO to install something, it keeps fetching that into my 2GB of RAM and then writing it back to the pagefile as it overflows for the next week or more.
Longhorn never was a managed code approach
Perhaps I exaggerated a little, but there was a big push to try to focus user space as primarily managed code. Singularity et al are doing crazy stuff with managed code in the kernel amongst other things, which is interesting but not what I was alluding to in my original post.
The Engineering Windows 7 blog goes into great detail about the development process that was vastly improved over Windows Vista's.
I'm aware, I followed the blog while it was still active. I particularly found the GDI concurrency post interesting. I wonder if having a similar blog for Vista would have allowed them to realise earlier on that it was going out of control.
Innovation requires risk and not the kind of risks Microsoft took with their Vista debacle. It requires that you do things entirely differently than everyone else. This is not Microsoft. This is not Windows Vista nor Windows 7 nor IE anything.
Microsoft took a big risk with Longhorn and tried to write pretty much the whole OS in managed code (entirely different to everyone else) and it didn't pay off. Most of the delay came from throwing most of that work away and starting again back in native code.
Even if starting the copy is faster for you through a GUI, the copy itself will finish faster with rsync most of the time. Rsync won't retransfer blocks that already exist, and if you're transferring over a network it will use compression.
What's to say the GUI can't use rsync technology underneath? You're now comparing specific implementations of copy technologies in a discussion over interfaces.
Having to replace hardware on commodity computers is hardly due to Windows supposedly being unreliable or complex. Don't get me wrong, I'm not trying to defend Windows here. The whole comparison is apples to oranges, it's silly to expect a consumer grade computer to last 30 years even if it had the mythical perfectly fault free OS.
The main argument that I feel does work in this case is mean time between power cycles. A Windows box really starts to struggle after a couple of months.
Binary postfix? As far as I was aware, the G in GB prefixes the B...
Clearly you missed the word "about".
I would not trust a Windows system to run until 2040 without a critical problem which requires hands-on maintenance.
I doubt that this is the first time they've had to perform diagnostics or maintenance on Voyager.
This all started when estranged Wikipedia co-founder Larry Sanger contacted the FBI with an allegation of child porn on Wikipedia.
Emphasis mine.
Chromium does have addons now, and since it is an open source project it'll be rather difficult for Google to hide snooping mechanisms in it. Also, I highly doubt that Ubuntu will decide to stick with Firefox as the default purely because one user who knows how to uninstall software and install an alternative expressed that they will change from the default.
Of course a Macintosh is no more locked down than a Windows or Linux computer, so there is no issue if we're sticking with computers.
While I mostly agree with that, most of my beef is with the App store and the way Apple tried to leverage their apps onto Windows machines (installing Safari without permission just because iTunes is installed for example). Another issue I have is the way Apple keeps making strange decisions with their port configuration on their computers, for example the removal of Firewire from a bunch of machines, and the new Mac Mini doesn't have HDMI but it does have Mini DisplayPort (without audio support), and as a result most of their advertised connectivity to other devices requires buying additional adapters.