The problem is a bit more complex than that. Microsoft has not really been all that informative about their end-of-life policy for their operations systems, and it is certainly nowhere to be found in the EULA or the contracts they happily signed for $$$ with the companies, that are now in a pickle because of it.
Further, Microsoft can support Windows XP, they just want more $$$ to do it (so, if they can do it for one company, and the goods they're selling are infinite, why can't they for all the rest?). If they offered a path to upgrade that didn't cost an arm and a leg, they wouldn't see this kind of lingering on XP that they do. If they spent a little more time streamlining their upgrade process and provided proper support for older binaries, maybe. Try to run a Win16 binary on Windows Vista+ and see what happens - hell, even binaries officially supposed to run under Windows 8 won't. Not every company has a bottomless budget for IT and development to remake their critical software, and Microsoft has until now seemed completely oblivious to that.
Lots of private customers are still lingering on XP too, why wouldn't they? It came pre-installed. It works. Its familiar. It won't get upgraded until the hardware dies. So, Microsoft, live with the consequences of your greed and offer free upgrades, it's not going to hurt the bottom line - hell, it might even prop up those dismal sales figures for Win8.
Or do the right thing and release XP as open source.
Desktop apps are a very important part of our strategy. Initially, we are focusing on Windows Store apps with.NET Native. In the longer term we will continue to improve native compilation for all.NET applications.
I'm not your Google bitch, so you can figure out where that quote came from on your own yeah?
This is actually fucking awesome. They've got native compilation of Win32/64 desktop and server apps on the road-map. You're right, nobody cares about the Windows Store, which is why they targeted those apps first (you know, developers, developers, developers and all that shit).
The FAQ clearly states that they're planning to propagate this feature to all.Net apps.
Desktop apps are a very important part of our strategy. Initially, we are focusing on Windows Store apps with.NET Native. In the longer term we will continue to improve native compilation for all.NET applications.
I'm guessing that means.Net 4.5+ apps, which in turn means Windows 8+. So here's for hoping that Windows 9 is not gonna suck so much donkey ball, that we can actually expect to be able to upgrade 7 -> 9 without relinquishing part of our soul to the UX demon-child they hired to "improve the user experience".
Well, to be fair, most of the passwords that exist are all variants of 12345. Also, several and very many is not infinite. The amount of work put into the Internet might be quite large, but it is still finite.
Hook the keyboards up in parallel and combine all the inputs to produce infinite outputs and you get instant monkey cracking. Thought now you're stuck with infinite monkeys with nothing to do.
I don't see the lack of a treatment as an argument for not knowing, but I do get why some might not wish to know in that instance. My problem is with the general sentiment that it is ok to stick your head in the sand. The problem does not go away by doing that. And in the case I have a terminal incurable illness, I'd like to know so that I can make the most of my time left, and make sure that the people closest to me won't suffer needlessly because of my ignorance.
Because the choice is not always yours alone. What about your wife? Should she have to deal with the consequences of your head-in-the-sand approach when you develop Alzheimer's? When the time could have been used to set her up properly, it was instead used dicking about and suddenly you're all out of choices, and so is she.
Not knowing is akin to not opening that envelope from the bank you know contains your next mortgage payment reminder. It's not going to go away just because you put your head in the sand. It is a proven fact that early diagnosis significantly improves the chances of being cured or having comfortable life.
I doubt anyone is going to force you to know your faulty DNA, but opting out of knowing if given the choice is just stupid, and potentially very expensive - because you will change your mind on having that treatment once the symptoms appear, which might very well be too late.
When you're competing with someone who doesn't check anything they put up, you start to look pretty follow-the-leaders when you post after fact-checking
So maybe they're doing it wrong? Not every article has to be breaking to be worthy. You don't always have to be first. Remember, news aren't made by journalists, it's covered by them, and newsworthy stuff happens regardless of whether anyone covers it. The obsession with being first is putting the cart before the horse. Do proper fact-checking and be a better source of news, it's that simple. Oh, and dropping the obvious party affiliations would go a long way too.
It could be down from 300 or any other arbitrarily chosen number. There are 19 insurers involved, I doubt they landed on the 201 on their first meeting.
You do not badmouth your former employer, no matter what they did.
And had she not done so, you would still be able to read the quoted statement, right? Wrong. Nothing happens if people don't speak up, and if it has to be in a public statement about the hows and whys, so be it. It can only be construed as illoyal or unprofessional if your first course of action is whining on the Internet. That is not what happened, according to both Julie and GitHub.
Suing is not going to fix the problem, it is most likely to end in a dismissal or a settlement (with an NDA), both outcomes less than ideal for the other employees.
If your company culture is so sick, that it cannot survive the light of day, I'm not sure you deserve to hire Julie, or anyone else for that matter.
I don't know. And if they did, which of the bugs were fixed? Is it possible that there could be even more? I simply don't know. I scrapped it all for unrelated reasons and moved on, but it haunts me still - were there 2 or 3 bugs when the comment was made?
I delete more comments than I make. One place it's some guys initials and nothing else, another just has the word "bug" and a date, some are clearly wrong or outright betray a fundamental lack of understanding. Hence the qualification that the comment had to be correct. Incorrect comments are the bane of all existence, and in that context I would prefer no comment at all.
But working with this crap all day, and then coming across a comment that is both short, and accurate, even if it is blindingly obvious that Math.Round does in fact round numbers, is sweet relief.
Yes indeed, the massive wall of empty XML tags approach to commenting. I've got an ample supply of those too, "I'll do it later I swear, I just did it to shut up the build agent!".
Slashdot Mirror
The problem is a bit more complex than that. Microsoft has not really been all that informative about their end-of-life policy for their operations systems, and it is certainly nowhere to be found in the EULA or the contracts they happily signed for $$$ with the companies, that are now in a pickle because of it.
Further, Microsoft can support Windows XP, they just want more $$$ to do it (so, if they can do it for one company, and the goods they're selling are infinite, why can't they for all the rest?). If they offered a path to upgrade that didn't cost an arm and a leg, they wouldn't see this kind of lingering on XP that they do. If they spent a little more time streamlining their upgrade process and provided proper support for older binaries, maybe. Try to run a Win16 binary on Windows Vista+ and see what happens - hell, even binaries officially supposed to run under Windows 8 won't. Not every company has a bottomless budget for IT and development to remake their critical software, and Microsoft has until now seemed completely oblivious to that.
Lots of private customers are still lingering on XP too, why wouldn't they? It came pre-installed. It works. Its familiar. It won't get upgraded until the hardware dies. So, Microsoft, live with the consequences of your greed and offer free upgrades, it's not going to hurt the bottom line - hell, it might even prop up those dismal sales figures for Win8.
Or do the right thing and release XP as open source.
Of course you blithering idiot, why do you think we have all this bloat lying around, if not for your protection?
Some of us are capable of writing anything we need, we just have better things to do than re-invent wheels all the time. Grow up.
Sounds like a great user experience right there. Hmm, I just updated, maybe this app will work, maybe it won't?
This new compiler actually links the dependent parts of the .Net framework into your native code, to produce a stand alone executable.
Desktop apps are a very important part of our strategy. Initially, we are focusing on Windows Store apps with .NET Native. In the longer term we will continue to improve native compilation for all .NET applications.
I'm not your Google bitch, so you can figure out where that quote came from on your own yeah?
This is actually fucking awesome. They've got native compilation of Win32/64 desktop and server apps on the road-map. You're right, nobody cares about the Windows Store, which is why they targeted those apps first (you know, developers, developers, developers and all that shit).
The FAQ clearly states that they're planning to propagate this feature to all .Net apps.
Desktop apps are a very important part of our strategy. Initially, we are focusing on Windows Store apps with .NET Native. In the longer term we will continue to improve native compilation for all .NET applications.
I'm guessing that means .Net 4.5+ apps, which in turn means Windows 8+. So here's for hoping that Windows 9 is not gonna suck so much donkey ball, that we can actually expect to be able to upgrade 7 -> 9 without relinquishing part of our soul to the UX demon-child they hired to "improve the user experience".
NGEN just caches the JIT output of an assembly, it does not produce a native executable.
Well, to be fair, most of the passwords that exist are all variants of 12345. Also, several and very many is not infinite. The amount of work put into the Internet might be quite large, but it is still finite.
There is nothing to suggest that an infinite amount of monkeys wont produce an infinite amount of "a"s. Adding more monkeys could produce more "a"s.
Hook the keyboards up in parallel and combine all the inputs to produce infinite outputs and you get instant monkey cracking. Thought now you're stuck with infinite monkeys with nothing to do.
I don't see the lack of a treatment as an argument for not knowing, but I do get why some might not wish to know in that instance. My problem is with the general sentiment that it is ok to stick your head in the sand. The problem does not go away by doing that. And in the case I have a terminal incurable illness, I'd like to know so that I can make the most of my time left, and make sure that the people closest to me won't suffer needlessly because of my ignorance.
Because the choice is not always yours alone. What about your wife? Should she have to deal with the consequences of your head-in-the-sand approach when you develop Alzheimer's? When the time could have been used to set her up properly, it was instead used dicking about and suddenly you're all out of choices, and so is she.
Not knowing is akin to not opening that envelope from the bank you know contains your next mortgage payment reminder. It's not going to go away just because you put your head in the sand. It is a proven fact that early diagnosis significantly improves the chances of being cured or having comfortable life.
I doubt anyone is going to force you to know your faulty DNA, but opting out of knowing if given the choice is just stupid, and potentially very expensive - because you will change your mind on having that treatment once the symptoms appear, which might very well be too late.
Obscurity is a valid layer
No.
Fail to convert back and forth between...
When you're competing with someone who doesn't check anything they put up, you start to look pretty follow-the-leaders when you post after fact-checking
So maybe they're doing it wrong? Not every article has to be breaking to be worthy. You don't always have to be first. Remember, news aren't made by journalists, it's covered by them, and newsworthy stuff happens regardless of whether anyone covers it. The obsession with being first is putting the cart before the horse. Do proper fact-checking and be a better source of news, it's that simple. Oh, and dropping the obvious party affiliations would go a long way too.
this site exists for a reason
Heat kiddo. You know it's still water even if we call it ice in it's solid phase right? Just like steam is also just water.
It could be down from 300 or any other arbitrarily chosen number. There are 19 insurers involved, I doubt they landed on the 201 on their first meeting.
Beautiful.
You do not badmouth your former employer, no matter what they did.
And had she not done so, you would still be able to read the quoted statement, right? Wrong. Nothing happens if people don't speak up, and if it has to be in a public statement about the hows and whys, so be it. It can only be construed as illoyal or unprofessional if your first course of action is whining on the Internet. That is not what happened, according to both Julie and GitHub.
Suing is not going to fix the problem, it is most likely to end in a dismissal or a settlement (with an NDA), both outcomes less than ideal for the other employees.
If your company culture is so sick, that it cannot survive the light of day, I'm not sure you deserve to hire Julie, or anyone else for that matter.
Well, they might. Or maybe it's a sign of the end times, a sign that the righteous must arm themselves. Who the fuck knows with these people?
I don't know. And if they did, which of the bugs were fixed? Is it possible that there could be even more? I simply don't know. I scrapped it all for unrelated reasons and moved on, but it haunts me still - were there 2 or 3 bugs when the comment was made?
I delete more comments than I make. One place it's some guys initials and nothing else, another just has the word "bug" and a date, some are clearly wrong or outright betray a fundamental lack of understanding. Hence the qualification that the comment had to be correct. Incorrect comments are the bane of all existence, and in that context I would prefer no comment at all.
But working with this crap all day, and then coming across a comment that is both short, and accurate, even if it is blindingly obvious that Math.Round does in fact round numbers, is sweet relief.
Yes indeed, the massive wall of empty XML tags approach to commenting. I've got an ample supply of those too, "I'll do it later I swear, I just did it to shut up the build agent!".