Lots of people kept buying/selling/using XP after MS ended mainstream support for it too. Or rather, after MS threatened to end mainstream support and then backed off. Twice, wasn't it?
That didn't really happen with Vista. Lots of places kept right on selling computers with XP, because customers wanted them.
Plus the "use our monopoly to force everyone to upgrade to whatever we want" strategy is getting more and more dangerous. Most of the barriers to switching to a Mac or Linux have fallen.
MS tried the desktop interface on a tablet and it didn't work. Now they're trying the tablet interface on a desktop. Nobody except MS really expects that will work any better, but they're going to try anyway.
Very white dirty blonde with freckles actually. But apparently I have the same (extremely common) name as a black international badass and US border goons panic before they get far enough in the file to see the physical description. I don't think the TSA even gets the physical description, just the name.
On the one hand it's nice to see that US security agencies don't profile entirely by race. On the other hand, it's a bit scary that they waste so much time and effort on such obvious false positives. On the gripping hand, if I'm travelling with people they're usually impressed when I sigh, roll my eyes, get dragged off, sometimes in handcuffs at gunpoint, only to reappear an hour later. It does tend to make travel more exciting.
As mildly annoying as it is, it's really a cakewalk any time I've gone through. But driving (not even flying) from Canada to the USA... oh, now THAT'S typically a half hour wait while they scour the car and ask idiotic questions. Holy god, you'd think I had a trunk full of assault rifles the way they act.
You should cross the border with me. Guns, swarms of agents, handcuffs, nervous Michael Jackson jokes, the whole bit.
Qt is a great cross-platform GUI toolkit, but it doesn't compare to Cocoa on a Mac. Qt took eight years to properly support OS X (carbon was never meant as more than a transition API). Qt apps on OS X don't quite get the look and feel right, and they are usually noticeably slower. Plus they're shackled by being cross-platform: they don't get to use any of the specific OS features that a native app can.
A cross platform GUI library, assuming it matches the look of a platform and doesn't reimplement the entire platform-specific GUI library, must have an abstraction layer. At the very least calls through the abstraction layer carry the penalty of an extra function call.
In reality, a lot of cross platform GUI toolkits seem to be designed primarily on one platform, where they work quite well, but require a lot of translation on other platforms, where they don't work as well. Less time is often spent on the non-primary platform as well. For anything where they have to roll their own they usually miss out on GPU acceleration.
Translating between different platforms is work, so a cross platform GUI toolkit is going to be slower. Strangely, I wasn't able to find benchmarks. I was going to write one quickly to compare Qt and Cocoa, but the Qt download is 780 MB and I've got actual work to do.
Practically, when I read this story I went looking for good code editors. I found lots, quite a few of which were cross platform. A couple couldn't scroll text without an annoying delay (!?). A few took five to ten seconds to start up... on my SSD. The differences between native and cross platform are noticeable and annoying.
Cross platform is great for special purpose stuff, and if it's the only option, or something you don't use regularly, fine. But converting an excellent native text editor just so it can be cross platform? Absolutely the wrong thing to do.
Ah, someone who thinks that making software perform correctly involves putting in lots of little band-aid... er, sanity checks.
It's quite possible to write code that is correct in itself. No checks necessary. In the aviation industry "oh, it fails sometimes but the sanity checks catch it" isn't good enough. In this case, if they'd been a little more careful, they wouldn't have had a problem.
Software failed in a situation where it shouldn't have. Therefore, it is a software development problem.
Peak oil is the point in time when the maximum rate of petroleum extraction is reached, after which the rate of production is expected to enter terminal decline.
SOME of the cross platform GUIs, on SOME of the platforms they support, have reasonable performance. Many of them don't. All of them are slower than native.
The definition of peak oil does not contain any reference to supply or demand. It does not mean, as the GP stated, that we are burning more oil than we are discovering. That happened quite a bit before peak oil.
I use TextMate because it's small, fast, has lots of features that I never use that stay completely out of my way, renders text nicely, and ISN'T (necessarily) a one-window system. Did I mention it's fast?
No, no, no. The run anywhere stuff all has the same Achilles heel - it has to use some kind of platform independent GUI toolkit. And those are slow, clunky, and can't use any of the nice OS features.
It takes time to develop and test an update and flash a system (not to mention money). Gauss is certainly time-limited, but that might be a feature. If you wanted to shut down Iranian centrifuges, for example, you could just send out a copy specific to those configurations. The Iranian centrifuge operators get attacked, realized they're the target (but nobody believes them), and spend time and money flashing their systems. Next week, Gauss2 comes out, same as last time but with "Penis" appended to the version strings it's looking for. Repeat. Good deniability, no collateral damage and annoying as hell to your target.
Peak oil means just that - our peak production of oil. It has nothing (directly) to do with either consumption or supply.
The idea is that at some point our demand for oil will push us to exploit as much as we practically can. As we then use that oil faster than our technology advances to allow us to get more, our production will fall.
Slashdot Mirror
Lots of people kept buying/selling/using XP after MS ended mainstream support for it too. Or rather, after MS threatened to end mainstream support and then backed off. Twice, wasn't it?
That didn't really happen with Vista. Lots of places kept right on selling computers with XP, because customers wanted them.
Plus the "use our monopoly to force everyone to upgrade to whatever we want" strategy is getting more and more dangerous. Most of the barriers to switching to a Mac or Linux have fallen.
MS tried the desktop interface on a tablet and it didn't work. Now they're trying the tablet interface on a desktop. Nobody except MS really expects that will work any better, but they're going to try anyway.
Very white dirty blonde with freckles actually. But apparently I have the same (extremely common) name as a black international badass and US border goons panic before they get far enough in the file to see the physical description. I don't think the TSA even gets the physical description, just the name.
On the one hand it's nice to see that US security agencies don't profile entirely by race. On the other hand, it's a bit scary that they waste so much time and effort on such obvious false positives. On the gripping hand, if I'm travelling with people they're usually impressed when I sigh, roll my eyes, get dragged off, sometimes in handcuffs at gunpoint, only to reappear an hour later. It does tend to make travel more exciting.
Exactly. At some point you pass out from alcohol poisoning, which serves to regulate your cannabis intake.
Actually, if you calculate the barycentre of the Earth-Oprah system....
You should cross the border with me. Guns, swarms of agents, handcuffs, nervous Michael Jackson jokes, the whole bit.
Perhaps you're one of the lucky ones that doesn't get detained for an hour plus every single time you fly in or near the US.
Yeah, but they take them away again unless you put them in your checked baggage.
Qt is a great cross-platform GUI toolkit, but it doesn't compare to Cocoa on a Mac. Qt took eight years to properly support OS X (carbon was never meant as more than a transition API). Qt apps on OS X don't quite get the look and feel right, and they are usually noticeably slower. Plus they're shackled by being cross-platform: they don't get to use any of the specific OS features that a native app can.
A cross platform GUI library, assuming it matches the look of a platform and doesn't reimplement the entire platform-specific GUI library, must have an abstraction layer. At the very least calls through the abstraction layer carry the penalty of an extra function call.
In reality, a lot of cross platform GUI toolkits seem to be designed primarily on one platform, where they work quite well, but require a lot of translation on other platforms, where they don't work as well. Less time is often spent on the non-primary platform as well. For anything where they have to roll their own they usually miss out on GPU acceleration.
Translating between different platforms is work, so a cross platform GUI toolkit is going to be slower. Strangely, I wasn't able to find benchmarks. I was going to write one quickly to compare Qt and Cocoa, but the Qt download is 780 MB and I've got actual work to do.
Practically, when I read this story I went looking for good code editors. I found lots, quite a few of which were cross platform. A couple couldn't scroll text without an annoying delay (!?). A few took five to ten seconds to start up... on my SSD. The differences between native and cross platform are noticeable and annoying.
Cross platform is great for special purpose stuff, and if it's the only option, or something you don't use regularly, fine. But converting an excellent native text editor just so it can be cross platform? Absolutely the wrong thing to do.
You're right, but that doesn't mean they couldn't take a few hints from other industries.
Hooking the new software up to run in parallel with the old for a while, without actually executing trades, might be a good place to start.
Ah, someone who thinks that making software perform correctly involves putting in lots of little band-aid... er, sanity checks.
It's quite possible to write code that is correct in itself. No checks necessary. In the aviation industry "oh, it fails sometimes but the sanity checks catch it" isn't good enough. In this case, if they'd been a little more careful, they wouldn't have had a problem.
Software failed in a situation where it shouldn't have. Therefore, it is a software development problem.
In the age of Wikipedia and Google you really should look things up first.
http://en.wikipedia.org/wiki/Peak_oil
So eloquent.
SOME of the cross platform GUIs, on SOME of the platforms they support, have reasonable performance. Many of them don't. All of them are slower than native.
The definition of peak oil does not contain any reference to supply or demand. It does not mean, as the GP stated, that we are burning more oil than we are discovering. That happened quite a bit before peak oil.
Clarified for you?
I use TextMate because it's small, fast, has lots of features that I never use that stay completely out of my way, renders text nicely, and ISN'T (necessarily) a one-window system. Did I mention it's fast?
I use TextMate as my primary Python development environment. My first thought upon hearing that it was going open source was "minimalist Python IDE."
No, no, no. The run anywhere stuff all has the same Achilles heel - it has to use some kind of platform independent GUI toolkit. And those are slow, clunky, and can't use any of the nice OS features.
I abandoned BBEdit years ago when it got big and slow. And it was always a little ugly. TextMate is much cleaner.
It takes time to develop and test an update and flash a system (not to mention money). Gauss is certainly time-limited, but that might be a feature. If you wanted to shut down Iranian centrifuges, for example, you could just send out a copy specific to those configurations. The Iranian centrifuge operators get attacked, realized they're the target (but nobody believes them), and spend time and money flashing their systems. Next week, Gauss2 comes out, same as last time but with "Penis" appended to the version strings it's looking for. Repeat. Good deniability, no collateral damage and annoying as hell to your target.
"Demand outstripping [sustainable] supply."
Better?
Peak oil means just that - our peak production of oil. It has nothing (directly) to do with either consumption or supply.
The idea is that at some point our demand for oil will push us to exploit as much as we practically can. As we then use that oil faster than our technology advances to allow us to get more, our production will fall.
Taking the shower head off can also work, in a pinch.
Cool. So it just tries whatever configuration it finds itself on and, if it decrypts, bam. That's probably a useful little trick to remember.