It's not just a budget constraint problem. If you have multiple servers in a farm for an application that is currently running 2003, you don't want to add a new variable into that with a new OS. You'll need to update your existing servers first.
That's debatable, and depends on the context. I think generally, if you have a server farm, you would want to add a new variable by adding new servers. You'd add new servers, migrate the old services to them, and then decommission the old servers-- re-purposing them if they're still good, tossing them if they aren't. And if you run a server farm, you probably should have started doing that to move from 2003 to 2008R2 a few years ago. At this point, you should be planning your migration from 2008R2 to 2012R2, or whatever comes next.
The point is, IT departments should always be planning for and budgeting for the next upgrade. The idea of migrating from a 12 year-old OS to a newer version shouldn't be catching anyone by surprise. If they can't do it because there's no budget for it, then the person doing the budgeting doesn't understand IT needs.
Eh... you make a good point in that it caused the sort of problems that Microsoft seemed to be aiming to cause, but on the other hand, it was temporary and eventually led to IE losing a lot of market share. Now web developers often target Firefox and Chrome, and IE has sort of become the second-class browser.
That's really not fair. He's responding to someone claiming that Windows 2003 is the default for many companies for new deployments. If you're deploying a new server, you shouldn't be deploying a Windows 2003 server, and that's been the case for a few years. Whether you have the budget to deploy a new server is a different question.
Aside from that, honestly, any company who is relying on servers and other IT resources, and doesn't have an IT budget to fund regular updates/upgrades/replacements, really needs to rethink their strategy. It's not the IT worker's fault that there's no IT budget, but it's certainly someone's fault.
I think "empathy" is generally characterized more by feelings. You see someone who looks upset, and you find it upsetting. I think this "Theory of Mind" business is more about understanding what else might be going on in another person's head.
Like... you know how when you're a kid, and you're shocked to see your teacher at the grocery store? You hadn't really thought about it, but you had somehow assumed that your teacher lived at the school, and perhaps didn't need to eat. And the important part there is, you hadn't really thought about it.
I think that's sort of an early level of the realization, "Other people are also people, like me. They have lives of their own, they think their own thoughts, just like me." There are deeper understandings of this that people develop, like perhaps realizing, "I sort of think of life like a story, and I'm the main character. But other people must also think of themselves as the main character. To an outside observer, there's no reason why my perspective is more correct."
And I think that in adulthood, some people develop that sensibility in much deeper and more profound ways. They can put themselves in another person's shoes, and not just feel empathy for them, but actually understand how things must appear to another person. They can think about things like, "I disagree with you, but I completely understand why you think that, and I'm not sure you're wrong." Some adults develop very strong skills and impulses along those lines, while others don't. Many people, even into adulthood, think as simply as, "I disagree with you, and therefore you must be wrong and stupid."
I'm not sure that's what they mean, but I would guess that's the sort of thing being included in "keeping track of what other people feel, know, and believe."
Imagine you were in a foreign country that speaks two languages, only one of which is your native one. You speak the other language well enough, but it's still mental effort compared to your native tongue.
You go in for an interview and go through a procession of seven people who speak the other language. You are confronted with the possibility that this is what your work environment will be like. Not everyone is up for that.
Well let's clarify your analogy a little bit. Let's say that in this land, people speak Language-X and Language-Y. Now, there's an industry dominated by people who speak Language-X, and a lot of people complain that there aren't enough Language-Y speakers in the industry. You're a business owner in that industry, and you look at your staff and, sure enough, everyone there speaks Language-X. You think, "You know, for our next hire, let's actively seek out a Language-Y speaking person.'
So you go through various channels, and you set up an interview. You have a Language-Y speaker come in. You and some of your employees interview the Language-Y speaker.
And then that Language-Y speaker complains, "I don't want to work there. Everyone there speaks Language-X! That seems like a terrible environment to work in!"
And then, still, people turn around and blame you for not hiring a Language-Y speaker. When you say, "I interviewed a Language-Y speaker. That person wouldn't take the job!" And they say, "Well of course. The interviewers were all Language-X speakers."
You respond, "But that's all I have right now! All of my employees speak Language-X, and that's the problem I'm trying to fix!"
And they fire back, "Well no Language-Y speaker is going to take a job working in an all Language-X environment. You should hire a bunch of people who speak Language-Y first, and once you have a lot of Language-Y speakers, then Language-Y speakers will be willing to work for you."
And as I'm writing this, I'm becoming very aware of two things. First, I've written "Language-X" and "Language-Y" a lot of times, and I hope I've kept them straight. I should have just said we were in Canada, in an area that speaks both French and English. It'd be easier to remember.
But second, there's a big problem with your analogy. Language is something that actually, directly keeps people from being able to work together, but on the other hand it's something that you can learn. Differences in gender/sex do not have that feature. It does not directly keep you from working with people, and a man can't "learn to also be female" the way English-speaking people can simply, "learn to speak French."
From what I've read, you're right that they didn't insult Muslims, but you're splitting hairs a bit. They intentionally offended Muslims, and they did it for the sake of offending Muslims.
But I disagree with the person who said, "I think Muslims, like anyone else, have the right for protection from such open insults." Nobody has the right to be protected from being offended. You can be offended all day long, and you have no right to respond with violence, and nobody has any obligation to prevent you from feeling offended.
It reminds me of this comedian, who makes the point that the right to "free speech" is the same as the right to "be offensive/insulting". It's terribly important that we can be offensive or insulting, because otherwise there's no limit to the restrictions that can be put on free speech. For anything you might say, someone might claim to be insulted. I also appreciate his point that we must be able to ridicule anyone (or anything) in a position of power, in order to have a free society.
I just think people are overreacting. You could argue that he shouldn't have said it, or he should have said something else, but what he's saying isn't wrong. Not in context.
First, he said that killing in the name of God is absolutely wrong. He made no concessions there. But yes, he also commented, “One cannot react violently, but if [someone] says something bad about my mother, he can expect a punch. It’s to be expected." So he's saying that violence is wrong. You shouldn't react with violence. But at the same time, "freedom of speech" is not "freedom from consequences of your speech." The point is, if you say something that you know others will find horribly offensive, you should expect that you have to deal with people being offended. That may have consequences to your life.
I think that's a misunderstand of what he's saying. Note that he didn't say, "if someone says a curse word against my mother, I'm going to punch him." He said, "he can expect a punch."
I may be wrong, but I think he's not advocating violence, but saying, "If you go around spitting in people's faces, and then someone punches you, don't be surprised." That is, it'd be foolish not to expect some kind of response.
Not so fast. What you're saying is great for home users or even small businesses, but for larger scale situations (enterprise or MSP, managing thousands of computers), it creates a lot of extra work to manage and maintain a fleet of computers of all kinds of different models from different manufacturers, running different operating systems deployed from different images, with different levels of warranty support, purchased over a range of time between "yesterday" and "10 years ago".
It's just not really the way you want to run things. Old machines break more often and take more time to fix. You use scripting to manage computers en masse, and you find that you have to jump through a bunch of hoops to get the scripts to run uniformly because different versions of the scripting language are supported on different versions of the operating system, and you have to support them all. Some things that you could easily do in a script, the old scripting language just doesn't support. The new imaging solution you've implemented because it saves your IT department a bunch of time, and therefore money, doesn't work on the computers from 7 years ago because the BIOS support is different, or you can't get the right kind of driver packages, or whatever bit of nonsense you run into dealing with old computers.
In short, when you're doing real IT work, "meeting the user's needs" is not the only consideration.
I would guess that's a component, but I suspect some of it was also just an issue of timing.
I work in IT servicing a lot of small businesses, and from what I've seen over the years, it seems like most businesses had gotten into the habit of buying new computers every few years. Both the hardware and software were improving quickly and drastically, and it made sense to buy a new computer every 3 years or so.
And then around... I don't know, 2006, when it came time for the 3 year upgrade cycle, a lot of businesses looked at the computer they already had and said, "Meh... this is still doing what I need it to do. I don't see there being much value in spending another $1,500 for a new computer."
And that continued, one year after the other. In 2010, they were still looking at some of their computers from 2005 and saying, "I know it's an old computer, but it still does everything we need it to do. I'm not going to spend money I don't need to."
But then in the last couple years, we hit a couple of milestones. First, a lot of those computers are now getting to be around 10 years old. In computer terms, "7 years old" sounds bad, but it sounds to the decision-makers like something they can live with, whereas "10 years old" apparently sounds like it ought to be replaced.
The other big milestone was that Microsoft dropped support for Windows XP, which means all of the old Windows XP machines either need to be replaced or updated to Windows 7 or Windows 8. Upgrading an old, outdated machine with no warranty is often not really worth the trouble, and so the need to move to a new version of Windows was the last straw for all those old machines that should have been replaced a few years ago.
So honestly, if I had to guess, I'd guess that you're going to see an uptick in laptop/desktop PC purchases over 2014-2015, and then you're going to see it drop off again. Once most of those old 10-year-old Windows XP machines are replaced, sales will go back down. But I also don't see them stopping anytime soon. Tablets are not going to be a real replacement for business use-- unless you're talking about something like the Microsoft Surface, where it's really just a laptop without a keyboard.
If you want to know that We Are Fucked if things get serious, I can tell you that for free(though we do have backup tapes, and I am perfectly capable of restoring, were the hypothetical attack to stop); but if you aren't interested in doing anything that might actually make you less fucked; because that'd cost a whole lot more, upset users, or both, what's the drill for?
Yeah, that's kind of my first thought. I've been doing this IT thing for a while, and I think doing an occasional fire drill is great. But the fire drill itself costs money, and there's no point in doing it if you're not committed to fixing the problems you've found. So if you do a test restore to make sure your backups can be restored successfully, that's great. But if you find your backups don't restore successfully, are you willing to put in whatever time and money are required to fix those problems, and then test again to make sure your "fix" actually fixed the problem?
Too often, the answer is "no". People want the fire drill, but they want the result to come out that the drill was successful and nothing needs to change. They have no plan or budget for what to do if the drill is unsuccessful. It's purely a "cover-your-ass" move so that later on, they can say, "We performed regular tests." Those tests are a waste of money unless they're producing actionable information, and unless you're then willing to act on that actionable information.
Well, for one thing I would probably argue that the support expectations for phones have become different than for desktops/laptops, especially in businesses. People replace their phone every 2 years, and the OS is treated like an embedded OS.
But regardless, I think people are kind of being babies to complain about MS no longer patching v8, and only patching v8.1. It's a free update. It's basically a service pack. Just keep your damned OS up to date.
I shudder to think about what the technology world would be like now if the current "mobile device" business model was applied to the general PC market in the 90s.
Yeah, imagine if, in order to get the new Windows service pack, not only did Microsoft have to write it, but Gateway 2000 had to modify it to their liking, and then AOL had to allow it to be installed. That's some nightmare fuel right there.
Google is saying that they will not patch the flaw. Google's only reasoning seems to be that they are not fixing vulnerabilities in 4.3 (introduced in June 2012) anymore, as they have moved focus to newer releases.
To me, this only really seems like a valid position if vendors allowed people to upgrade at will, but as far as I know, Android users are still held to whichever version their carrier/manufacturer allow. June 2012 is only 2.5 years ago, which means (I'm guessing) that it's possible you purchased a phone less than 2 years ago that had this version of the OS. That means, you could have purchased your phone brand new, it might still be under contract, and it's unsupported.
Now, if you're free to install the latest version on your phone, then it seems much more reasonable.
Given my experience with public education, I expect someone will take this idea seriously, and then we'll see classes on "grit" and "persistence" which will consist of a teacher telling kids that they should have "grit" and "persistence". Of course, they won't explain what these concepts mean to the children, because the teachers themselves won't understand it. But they will punish the students and generally try to make them feel bad for failing to live up to these ideals. A student seems hesitant to participate? Perhaps a little humiliation will help. A student acts out? Detention. A kid doesn't show persistence? Give him an F and hold him back a grade.
For me, the most compelling practical argument for switching to an on-demand model is that live events (be they sports, breaking news, or, worst of all, political speeches) would no longer preempt pre-recorded shows.
There's another non-obvious benefit, which has to do with how shows are chosen for airing or cancellation. Let's say that NBC picks up a pilot for a new show, and they decide to air it on Thursdays at 8pm. That's an important time slot. They put a decent budget behind it, and they market the hell out of it. It doesn't do as well as they'd hope, so the executives decide they want to give that 8pm time slot to something else, so they start looking for other shows to put into that time slot. By the time they start shuffling things around, the show has gotten a bit of a following, so some of the people keep watching when the show is moved to Friday nights instead.
Of course, Friday nights are not a great night for television, so the viewership is lower when they moved it to Friday nights. Since the ratings are lower, the network cuts their budget, which means that they can't produce the same quality of show. As the quality suffers, the viewership wanes, and so they cut the budget some more. The show goes into a death spiral and gets cancelled.
So in this case, you had a show that people liked enough that it was making money. Through whichever revenue channels, it was making enough money to pay for its production, but NBC moved it out of it's time slot-- not because it wasn't making money, but because they thought they had another show that would make more money. The result is that a profitable show that people liked was cancelled.
Now this is a hypothetical situation, but these kinds of factors are at least partially responsible for the cancellation of a bunch of shows that people liked. Some example might be Firefly, Farscape, Futurama, and Family Guy. Whenever you see a show with a fanbase get cancelled, it may be that the show was profitable, but that someone guessed that putting another show in the same time slot would be more profitable. This is also part of the reason there have been so many reality shows in the past decade. Although comedies and dramas are profitable and make a lot of money, reality shows are extremely cheap to make, so even if the ratings are bit lower, the profits are higher. Because time slots are limited, each network focuses on the most profitable shows and cancels everything else.
With on-demand viewing, there are no time slots, so that whole limitation goes away. Shows can live or die by their own profitability, rather than seeing if there's a time slot available on a channel that caters to the appropriate demographic's viewing habits. Not that this will solve all the problems that lead to good shows being cancelled, but my guess is that it'll be better than what we have now.
I don't want to be rude, but I think you have unrealistic requirements. Like, to the point of being silly.
As others point out, you're not going to get the "Turbo Boost" speeds all day long, since the whole point of the "Turbo Boost" speeds is to ramp up performance for short periods. You're looking for balls-out performance from laptops, whereas manufacturers have been pushing mobility and power-efficiency. And you're looking at gaming laptops for business use. It makes me thing that you don't know what you're doing.
My guess is-- and don't take this personally, I'm just basing this off of my experience with working with people who've asked for similarly unrealistic expectations-- that you don't actually need the kind of performance you're asking for. It is not "impossible to write code and run db/test environment" on a single laptop. People do that kind of thing all the time, and not even with very high-end machines. No, your performance will not be quite as fast as running on a super-high-end server, but it should be good enough for development work. If you want good performance, look to workstation-class laptops (e.g. Dell Precision laptops), get the best quad-core processor available, max out the RAM, and be sure to get a fast SSD. With that, you should be able to run a couple virtual machines with reasonable performance.
If that's not enough-- if you really need much faster performance, and you need to work on a laptop, then put your development environment on a server that you connect to remotely. Set up a big bad-ass powerful VM host, and give all the developers remote access to create VMs and connect to them. Use that whenever you're internet accessible, and only use a local VM when you're stuck without access. It's not complicated.
Apart from Apple fanboys, I don't think anybody is stupid enough to buy a new device just to get a software upgrade.
Actually Apple stuff usually has very fast uptake for new versions. You're looking at upgrade rates in the 1% range? iOS updates are usually at 50% within a few days. iOS 8 is considered "slow" because a lot of users with older devices aren't moving to it, meaning only ~65% of iOS devices are using version 8.
It's actually Android users who frequently need to buy a new device to get the software upgrade, since their carrier/manufacturer would allow it otherwise.
That's not really addressing the issue. Again, those people are not ultimately interested in what channel it's on or when the official broadcast is, they just want to be able to watch it as close to "live" as possible. It's not like people are usually sitting down to watch whichever show and thinking, "Gee, I sure wish this game were at the 8:30 slot on CBS rather than the 8:00 slot on ABC." They just want to watch it when they want to watch it.
Slashdot Mirror
It's not just a budget constraint problem. If you have multiple servers in a farm for an application that is currently running 2003, you don't want to add a new variable into that with a new OS. You'll need to update your existing servers first.
That's debatable, and depends on the context. I think generally, if you have a server farm, you would want to add a new variable by adding new servers. You'd add new servers, migrate the old services to them, and then decommission the old servers-- re-purposing them if they're still good, tossing them if they aren't. And if you run a server farm, you probably should have started doing that to move from 2003 to 2008R2 a few years ago. At this point, you should be planning your migration from 2008R2 to 2012R2, or whatever comes next.
The point is, IT departments should always be planning for and budgeting for the next upgrade. The idea of migrating from a 12 year-old OS to a newer version shouldn't be catching anyone by surprise. If they can't do it because there's no budget for it, then the person doing the budgeting doesn't understand IT needs.
Eh... you make a good point in that it caused the sort of problems that Microsoft seemed to be aiming to cause, but on the other hand, it was temporary and eventually led to IE losing a lot of market share. Now web developers often target Firefox and Chrome, and IE has sort of become the second-class browser.
That's really not fair. He's responding to someone claiming that Windows 2003 is the default for many companies for new deployments. If you're deploying a new server, you shouldn't be deploying a Windows 2003 server, and that's been the case for a few years. Whether you have the budget to deploy a new server is a different question.
Aside from that, honestly, any company who is relying on servers and other IT resources, and doesn't have an IT budget to fund regular updates/upgrades/replacements, really needs to rethink their strategy. It's not the IT worker's fault that there's no IT budget, but it's certainly someone's fault.
I think "empathy" is generally characterized more by feelings. You see someone who looks upset, and you find it upsetting. I think this "Theory of Mind" business is more about understanding what else might be going on in another person's head.
Like... you know how when you're a kid, and you're shocked to see your teacher at the grocery store? You hadn't really thought about it, but you had somehow assumed that your teacher lived at the school, and perhaps didn't need to eat. And the important part there is, you hadn't really thought about it.
I think that's sort of an early level of the realization, "Other people are also people, like me. They have lives of their own, they think their own thoughts, just like me." There are deeper understandings of this that people develop, like perhaps realizing, "I sort of think of life like a story, and I'm the main character. But other people must also think of themselves as the main character. To an outside observer, there's no reason why my perspective is more correct."
And I think that in adulthood, some people develop that sensibility in much deeper and more profound ways. They can put themselves in another person's shoes, and not just feel empathy for them, but actually understand how things must appear to another person. They can think about things like, "I disagree with you, but I completely understand why you think that, and I'm not sure you're wrong." Some adults develop very strong skills and impulses along those lines, while others don't. Many people, even into adulthood, think as simply as, "I disagree with you, and therefore you must be wrong and stupid."
I'm not sure that's what they mean, but I would guess that's the sort of thing being included in "keeping track of what other people feel, know, and believe."
Imagine you were in a foreign country that speaks two languages, only one of which is your native one. You speak the other language well enough, but it's still mental effort compared to your native tongue.
You go in for an interview and go through a procession of seven people who speak the other language. You are confronted with the possibility that this is what your work environment will be like. Not everyone is up for that.
Well let's clarify your analogy a little bit. Let's say that in this land, people speak Language-X and Language-Y. Now, there's an industry dominated by people who speak Language-X, and a lot of people complain that there aren't enough Language-Y speakers in the industry. You're a business owner in that industry, and you look at your staff and, sure enough, everyone there speaks Language-X. You think, "You know, for our next hire, let's actively seek out a Language-Y speaking person.'
So you go through various channels, and you set up an interview. You have a Language-Y speaker come in. You and some of your employees interview the Language-Y speaker.
And then that Language-Y speaker complains, "I don't want to work there. Everyone there speaks Language-X! That seems like a terrible environment to work in!"
And then, still, people turn around and blame you for not hiring a Language-Y speaker. When you say, "I interviewed a Language-Y speaker. That person wouldn't take the job!" And they say, "Well of course. The interviewers were all Language-X speakers."
You respond, "But that's all I have right now! All of my employees speak Language-X, and that's the problem I'm trying to fix!"
And they fire back, "Well no Language-Y speaker is going to take a job working in an all Language-X environment. You should hire a bunch of people who speak Language-Y first, and once you have a lot of Language-Y speakers, then Language-Y speakers will be willing to work for you."
And as I'm writing this, I'm becoming very aware of two things. First, I've written "Language-X" and "Language-Y" a lot of times, and I hope I've kept them straight. I should have just said we were in Canada, in an area that speaks both French and English. It'd be easier to remember.
But second, there's a big problem with your analogy. Language is something that actually, directly keeps people from being able to work together, but on the other hand it's something that you can learn. Differences in gender/sex do not have that feature. It does not directly keep you from working with people, and a man can't "learn to also be female" the way English-speaking people can simply, "learn to speak French."
Yes, I agree with you. And it seems Pope Francis agrees with you, too.
From what I've read, you're right that they didn't insult Muslims, but you're splitting hairs a bit. They intentionally offended Muslims, and they did it for the sake of offending Muslims.
But I disagree with the person who said, "I think Muslims, like anyone else, have the right for protection from such open insults." Nobody has the right to be protected from being offended. You can be offended all day long, and you have no right to respond with violence, and nobody has any obligation to prevent you from feeling offended.
It reminds me of this comedian, who makes the point that the right to "free speech" is the same as the right to "be offensive/insulting". It's terribly important that we can be offensive or insulting, because otherwise there's no limit to the restrictions that can be put on free speech. For anything you might say, someone might claim to be insulted. I also appreciate his point that we must be able to ridicule anyone (or anything) in a position of power, in order to have a free society.
I just think people are overreacting. You could argue that he shouldn't have said it, or he should have said something else, but what he's saying isn't wrong. Not in context.
First, he said that killing in the name of God is absolutely wrong. He made no concessions there. But yes, he also commented, “One cannot react violently, but if [someone] says something bad about my mother, he can expect a punch. It’s to be expected." So he's saying that violence is wrong. You shouldn't react with violence. But at the same time, "freedom of speech" is not "freedom from consequences of your speech." The point is, if you say something that you know others will find horribly offensive, you should expect that you have to deal with people being offended. That may have consequences to your life.
I think that's a misunderstand of what he's saying. Note that he didn't say, "if someone says a curse word against my mother, I'm going to punch him." He said, "he can expect a punch."
I may be wrong, but I think he's not advocating violence, but saying, "If you go around spitting in people's faces, and then someone punches you, don't be surprised." That is, it'd be foolish not to expect some kind of response.
Not so fast. What you're saying is great for home users or even small businesses, but for larger scale situations (enterprise or MSP, managing thousands of computers), it creates a lot of extra work to manage and maintain a fleet of computers of all kinds of different models from different manufacturers, running different operating systems deployed from different images, with different levels of warranty support, purchased over a range of time between "yesterday" and "10 years ago".
It's just not really the way you want to run things. Old machines break more often and take more time to fix. You use scripting to manage computers en masse, and you find that you have to jump through a bunch of hoops to get the scripts to run uniformly because different versions of the scripting language are supported on different versions of the operating system, and you have to support them all. Some things that you could easily do in a script, the old scripting language just doesn't support. The new imaging solution you've implemented because it saves your IT department a bunch of time, and therefore money, doesn't work on the computers from 7 years ago because the BIOS support is different, or you can't get the right kind of driver packages, or whatever bit of nonsense you run into dealing with old computers.
In short, when you're doing real IT work, "meeting the user's needs" is not the only consideration.
I would guess that's a component, but I suspect some of it was also just an issue of timing.
I work in IT servicing a lot of small businesses, and from what I've seen over the years, it seems like most businesses had gotten into the habit of buying new computers every few years. Both the hardware and software were improving quickly and drastically, and it made sense to buy a new computer every 3 years or so.
And then around... I don't know, 2006, when it came time for the 3 year upgrade cycle, a lot of businesses looked at the computer they already had and said, "Meh... this is still doing what I need it to do. I don't see there being much value in spending another $1,500 for a new computer."
And that continued, one year after the other. In 2010, they were still looking at some of their computers from 2005 and saying, "I know it's an old computer, but it still does everything we need it to do. I'm not going to spend money I don't need to."
But then in the last couple years, we hit a couple of milestones. First, a lot of those computers are now getting to be around 10 years old. In computer terms, "7 years old" sounds bad, but it sounds to the decision-makers like something they can live with, whereas "10 years old" apparently sounds like it ought to be replaced.
The other big milestone was that Microsoft dropped support for Windows XP, which means all of the old Windows XP machines either need to be replaced or updated to Windows 7 or Windows 8. Upgrading an old, outdated machine with no warranty is often not really worth the trouble, and so the need to move to a new version of Windows was the last straw for all those old machines that should have been replaced a few years ago.
So honestly, if I had to guess, I'd guess that you're going to see an uptick in laptop/desktop PC purchases over 2014-2015, and then you're going to see it drop off again. Once most of those old 10-year-old Windows XP machines are replaced, sales will go back down. But I also don't see them stopping anytime soon. Tablets are not going to be a real replacement for business use-- unless you're talking about something like the Microsoft Surface, where it's really just a laptop without a keyboard.
Also ninite is still safe, AFAIK. It's especially helpful if you want to download and install a bunch of different applications at once.
If you want to know that We Are Fucked if things get serious, I can tell you that for free(though we do have backup tapes, and I am perfectly capable of restoring, were the hypothetical attack to stop); but if you aren't interested in doing anything that might actually make you less fucked; because that'd cost a whole lot more, upset users, or both, what's the drill for?
Yeah, that's kind of my first thought. I've been doing this IT thing for a while, and I think doing an occasional fire drill is great. But the fire drill itself costs money, and there's no point in doing it if you're not committed to fixing the problems you've found. So if you do a test restore to make sure your backups can be restored successfully, that's great. But if you find your backups don't restore successfully, are you willing to put in whatever time and money are required to fix those problems, and then test again to make sure your "fix" actually fixed the problem?
Too often, the answer is "no". People want the fire drill, but they want the result to come out that the drill was successful and nothing needs to change. They have no plan or budget for what to do if the drill is unsuccessful. It's purely a "cover-your-ass" move so that later on, they can say, "We performed regular tests." Those tests are a waste of money unless they're producing actionable information, and unless you're then willing to act on that actionable information.
And I'm sure they got that pay raise for coming up with brilliant ideas to increase revenue. Ideas like increasing their prices.
Well, for one thing I would probably argue that the support expectations for phones have become different than for desktops/laptops, especially in businesses. People replace their phone every 2 years, and the OS is treated like an embedded OS.
But regardless, I think people are kind of being babies to complain about MS no longer patching v8, and only patching v8.1. It's a free update. It's basically a service pack. Just keep your damned OS up to date.
I shudder to think about what the technology world would be like now if the current "mobile device" business model was applied to the general PC market in the 90s.
Yeah, imagine if, in order to get the new Windows service pack, not only did Microsoft have to write it, but Gateway 2000 had to modify it to their liking, and then AOL had to allow it to be installed. That's some nightmare fuel right there.
Google is saying that they will not patch the flaw. Google's only reasoning seems to be that they are not fixing vulnerabilities in 4.3 (introduced in June 2012) anymore, as they have moved focus to newer releases.
To me, this only really seems like a valid position if vendors allowed people to upgrade at will, but as far as I know, Android users are still held to whichever version their carrier/manufacturer allow. June 2012 is only 2.5 years ago, which means (I'm guessing) that it's possible you purchased a phone less than 2 years ago that had this version of the OS. That means, you could have purchased your phone brand new, it might still be under contract, and it's unsupported.
Now, if you're free to install the latest version on your phone, then it seems much more reasonable.
Given my experience with public education, I expect someone will take this idea seriously, and then we'll see classes on "grit" and "persistence" which will consist of a teacher telling kids that they should have "grit" and "persistence". Of course, they won't explain what these concepts mean to the children, because the teachers themselves won't understand it. But they will punish the students and generally try to make them feel bad for failing to live up to these ideals. A student seems hesitant to participate? Perhaps a little humiliation will help. A student acts out? Detention. A kid doesn't show persistence? Give him an F and hold him back a grade.
Wonderful.
Unfortunately, our schools are often run by people, and attended by people, who place no value in knowledge.
For me, the most compelling practical argument for switching to an on-demand model is that live events (be they sports, breaking news, or, worst of all, political speeches) would no longer preempt pre-recorded shows.
There's another non-obvious benefit, which has to do with how shows are chosen for airing or cancellation. Let's say that NBC picks up a pilot for a new show, and they decide to air it on Thursdays at 8pm. That's an important time slot. They put a decent budget behind it, and they market the hell out of it. It doesn't do as well as they'd hope, so the executives decide they want to give that 8pm time slot to something else, so they start looking for other shows to put into that time slot. By the time they start shuffling things around, the show has gotten a bit of a following, so some of the people keep watching when the show is moved to Friday nights instead.
Of course, Friday nights are not a great night for television, so the viewership is lower when they moved it to Friday nights. Since the ratings are lower, the network cuts their budget, which means that they can't produce the same quality of show. As the quality suffers, the viewership wanes, and so they cut the budget some more. The show goes into a death spiral and gets cancelled.
So in this case, you had a show that people liked enough that it was making money. Through whichever revenue channels, it was making enough money to pay for its production, but NBC moved it out of it's time slot-- not because it wasn't making money, but because they thought they had another show that would make more money. The result is that a profitable show that people liked was cancelled.
Now this is a hypothetical situation, but these kinds of factors are at least partially responsible for the cancellation of a bunch of shows that people liked. Some example might be Firefly, Farscape, Futurama, and Family Guy. Whenever you see a show with a fanbase get cancelled, it may be that the show was profitable, but that someone guessed that putting another show in the same time slot would be more profitable. This is also part of the reason there have been so many reality shows in the past decade. Although comedies and dramas are profitable and make a lot of money, reality shows are extremely cheap to make, so even if the ratings are bit lower, the profits are higher. Because time slots are limited, each network focuses on the most profitable shows and cancels everything else.
With on-demand viewing, there are no time slots, so that whole limitation goes away. Shows can live or die by their own profitability, rather than seeing if there's a time slot available on a channel that caters to the appropriate demographic's viewing habits. Not that this will solve all the problems that lead to good shows being cancelled, but my guess is that it'll be better than what we have now.
I don't want to be rude, but I think you have unrealistic requirements. Like, to the point of being silly.
As others point out, you're not going to get the "Turbo Boost" speeds all day long, since the whole point of the "Turbo Boost" speeds is to ramp up performance for short periods. You're looking for balls-out performance from laptops, whereas manufacturers have been pushing mobility and power-efficiency. And you're looking at gaming laptops for business use. It makes me thing that you don't know what you're doing.
My guess is-- and don't take this personally, I'm just basing this off of my experience with working with people who've asked for similarly unrealistic expectations-- that you don't actually need the kind of performance you're asking for. It is not "impossible to write code and run db/test environment" on a single laptop. People do that kind of thing all the time, and not even with very high-end machines. No, your performance will not be quite as fast as running on a super-high-end server, but it should be good enough for development work. If you want good performance, look to workstation-class laptops (e.g. Dell Precision laptops), get the best quad-core processor available, max out the RAM, and be sure to get a fast SSD. With that, you should be able to run a couple virtual machines with reasonable performance.
If that's not enough-- if you really need much faster performance, and you need to work on a laptop, then put your development environment on a server that you connect to remotely. Set up a big bad-ass powerful VM host, and give all the developers remote access to create VMs and connect to them. Use that whenever you're internet accessible, and only use a local VM when you're stuck without access. It's not complicated.
This whole thing was... I think it was in November.
Nope, no zombies in the movie.
Apart from Apple fanboys, I don't think anybody is stupid enough to buy a new device just to get a software upgrade.
Actually Apple stuff usually has very fast uptake for new versions. You're looking at upgrade rates in the 1% range? iOS updates are usually at 50% within a few days. iOS 8 is considered "slow" because a lot of users with older devices aren't moving to it, meaning only ~65% of iOS devices are using version 8.
It's actually Android users who frequently need to buy a new device to get the software upgrade, since their carrier/manufacturer would allow it otherwise.
That's not really addressing the issue. Again, those people are not ultimately interested in what channel it's on or when the official broadcast is, they just want to be able to watch it as close to "live" as possible. It's not like people are usually sitting down to watch whichever show and thinking, "Gee, I sure wish this game were at the 8:30 slot on CBS rather than the 8:00 slot on ABC." They just want to watch it when they want to watch it.