On the website, Dyson regulates the heat of the drier so that it does not exceed a certain temperature that will damage hair. Preventing hair damage is the main goal.
If speed of drying isn't that much of an issue, set your current hair dryer on a low heat setting to achieve a similar (not the same) effect.
People generally don't know how to read maps, that's why people tend to ask for directions (less and less now) and/or stop along the way and ask for more directions. The GPS made people comfortable enough that they put all trust into it, and no longer ask other people for direction.
Ultimately, the better solution is to continue to improve GPS, but people also need to learn how to read a map and/or ask for directions and how long it will take to get from point A to point B when unfamiliar with the area.
How is using *my* electricity, risking *my* computer's integrity, distracting *my* attention for *your* profit not abusing *my* resources?
I think your definition of "abuse" in this instance is stretching things a bit.
Using your logic, your comment(s) used *my* electricity, risking *my* computer's integrity, distracting *my* attention for *your* profit not abusing *my* resources.
Feel free to stop writing comments so I won't keep getting usage charges.
Is this not the same as reading and commenting on Slashdot, on a daily basis?
Since Slashdot was introduced to me, I think more kindly of Linux and, boy, do I hate Microsoft.
$105K is not worth it, if you spend 75% of your time supporting it, when the other 25% goes to supporting the iOS version which probably earns an equal amount. It's just a business decision, and I completely understand where they are coming from. Sometimes it just isn't worth it.
In my experience new developers are very bad at adapting to new ways of doing things and very good at blaming the system for their own problems. They'll do something that is not the right way to do it on this system, hasn't been for a long time, is documented on how to do it, and then blame the system.
Two of my favourite examples of developer laziness:
1) Lack of 64-bit apps for Windows. While I realize most apps don't need to be 64-bit, and 64-bit Windows provides flawless 32-bit support, you should still have 64-bit version available. They do run a tiny bit faster and it is just the right way of doing things. Let's start getting rid of the legacy stuff. What's more, it isn't hard to do, at least according to the developers I hang out with. You set the compile target for 64-bit and go. Maybe a couple things to correct but all in all the compiler takes care of the details. However most don't. The reason is they were doing shit in the code they never should have, like casting pointers in to 4 byte integers and so on. They write bad code, and it makes 32/64-bit porting a problem.
Your assumptions are based on assumptions of assumptions.
As a developer of a Windows app that is 20 years old, it’s not as easy as “setting the compile target”. You have to continually port over the years, and that takes time, resources and money, which for almost all companies is limited. Time is often spent on continual improvements and not on moving up to 64-bit.
Touting a product as 64-bit is not a selling point for 99% of the customers out there – they either don’t understand, don’t care, or both.
So, in summary, I reject the notion that it is laziness. Time is better spent elsewhere, until the Facebook/Apple gobs of money start pouring in.
But why does a developer have to work on the kernel?
I believe the mindset of older, "more experienced" developers of Linux that new developers must know the kernel is exactly the reason why new blood isn't being injected into the ranks of Linux developers.
He is odd, to say the least. Nothing wrong with being odd, but that is what he is, and from what I can tell, he doesn't care.
If you are offended by the notion that others see him as odd/weird/strange, then the problem is yours and yours alone, because he doesn't seem to care. Perhaps you should do some navel gazing, because he has...and he has found mushrooms! (Sorry, couldn't resist)
True, you are taking some of the load off of the local air connection, but then you are connecting to their internal routing.
To the bigger point, I agree that they are nickel-and-diming us.
Slashdot Mirror
On the website, Dyson regulates the heat of the drier so that it does not exceed a certain temperature that will damage hair. Preventing hair damage is the main goal. If speed of drying isn't that much of an issue, set your current hair dryer on a low heat setting to achieve a similar (not the same) effect.
People generally don't know how to read maps, that's why people tend to ask for directions (less and less now) and/or stop along the way and ask for more directions. The GPS made people comfortable enough that they put all trust into it, and no longer ask other people for direction. Ultimately, the better solution is to continue to improve GPS, but people also need to learn how to read a map and/or ask for directions and how long it will take to get from point A to point B when unfamiliar with the area.
How is using *my* electricity, risking *my* computer's integrity, distracting *my* attention for *your* profit not abusing *my* resources?
I think your definition of "abuse" in this instance is stretching things a bit. Using your logic, your comment(s) used *my* electricity, risking *my* computer's integrity, distracting *my* attention for *your* profit not abusing *my* resources. Feel free to stop writing comments so I won't keep getting usage charges.
Von Clownstick 2016...make America Great Again!
Is this not the same as reading and commenting on Slashdot, on a daily basis? Since Slashdot was introduced to me, I think more kindly of Linux and, boy, do I hate Microsoft.
Forget the company itself apologizing. I want the Apple "geniuses" to publicly apologize for being pompous asses. Seeing tears would be a bonus.
$105K is not worth it, if you spend 75% of your time supporting it, when the other 25% goes to supporting the iOS version which probably earns an equal amount. It's just a business decision, and I completely understand where they are coming from. Sometimes it just isn't worth it.
In my experience new developers are very bad at adapting to new ways of doing things and very good at blaming the system for their own problems. They'll do something that is not the right way to do it on this system, hasn't been for a long time, is documented on how to do it, and then blame the system.
Two of my favourite examples of developer laziness:
1) Lack of 64-bit apps for Windows. While I realize most apps don't need to be 64-bit, and 64-bit Windows provides flawless 32-bit support, you should still have 64-bit version available. They do run a tiny bit faster and it is just the right way of doing things. Let's start getting rid of the legacy stuff. What's more, it isn't hard to do, at least according to the developers I hang out with. You set the compile target for 64-bit and go. Maybe a couple things to correct but all in all the compiler takes care of the details. However most don't. The reason is they were doing shit in the code they never should have, like casting pointers in to 4 byte integers and so on. They write bad code, and it makes 32/64-bit porting a problem.
Your assumptions are based on assumptions of assumptions. As a developer of a Windows app that is 20 years old, it’s not as easy as “setting the compile target”. You have to continually port over the years, and that takes time, resources and money, which for almost all companies is limited. Time is often spent on continual improvements and not on moving up to 64-bit. Touting a product as 64-bit is not a selling point for 99% of the customers out there – they either don’t understand, don’t care, or both. So, in summary, I reject the notion that it is laziness. Time is better spent elsewhere, until the Facebook/Apple gobs of money start pouring in.
Just another story explaining why some people never get la*d.
But why does a developer have to work on the kernel? I believe the mindset of older, "more experienced" developers of Linux that new developers must know the kernel is exactly the reason why new blood isn't being injected into the ranks of Linux developers.
He is odd, to say the least. Nothing wrong with being odd, but that is what he is, and from what I can tell, he doesn't care. If you are offended by the notion that others see him as odd/weird/strange, then the problem is yours and yours alone, because he doesn't seem to care. Perhaps you should do some navel gazing, because he has...and he has found mushrooms! (Sorry, couldn't resist)
True, you are taking some of the load off of the local air connection, but then you are connecting to their internal routing. To the bigger point, I agree that they are nickel-and-diming us.
LOL. How about just typing the hostname and pressing -enter? Most browsers today have this and other keystroke time-savers built in.