The difference is that when Apple patches a security flaw, every semi-current iPhone user worldwide can install the patch and Apple usually patches the current version and one version back. For instance, the "goto fail" security patch that was released in March 2014 patched every phone back to iPhone 3GS in 2009 (patch for 6.x) and IOS 7.
I am facing the same situation. I could choose to get a larger house with a longer commute or a smaller house/condo with a shorter commute. We decided that getting 10 hours of our week back and less money spent on gas and car maintenance was worth the trade off.
But yes I know the pain of having a house that is worth less than what you owe.
I didn't say relocate for a job. I said choose a place that is a convenient commute to where the jobs are. For instance, I wouldn't live anywhere that I have to spend 30 minutes just to get to the interstate or on the opposite side of town than the tech center.
So if you have chosen to be a developer, why wouldn't you live somewhere within an acceptable (to you) commuting distance to where the jobs are? You might end up with less square footage for your money but you aren't wasting hours of your day in traffic. I know of a few metropolitan areas where there are plenty of jobs and reasonable home prices.
That's easy - leave off irrelevant work history. If I'm applying for a job as a "full stack
I'm in my early 40s and in my last set of interviews, I would work into the conversation that I'm married, have kids, and believe in a work/family balance. I wanted to be "discriminated" against. I didn't want to work for a company that expected me to work consistently more than 45 hours a week. The market is way too good for qualified, experienced developers to just accept anything. I am sure I was declined one job offer because of "discrimination". I was offered another job that was a much better fit the next week.
I don't see any reason that a qualified person in IT should have trouble finding a job or at least go into consulting. There are so many openings right now, I would classify the unemployment rate to be negative in tech.
This might bet the point at which Apple without Jobs falters.
Well a few responses....
1. If you look at Apple's stock price, revenue, and profit since Cook took over, Apple clearly hasn't "faltered".
2. Even before the iPhone came out, the phone market was clearly the largest consumer tech category. In other words, there is no conceivable electronic market that is going to be larger than the phone market in the foreseeable future. The watch couldn't hope to be as larger as the iPhone market.
3. The watch doesn't need third party apps to be useful. For instance, I am thinking about buying one just to replace my old Garmin GPS watch when I'm running -- yes I know it doesn't have GPS built in. When I run I have my phone on an armband anyway and my watch. I tried using the Nike+ GPS and it works well enough, but trying to look at the phone screen on an armband is not nearly as convenient as looking on my arm.
For another take:
Yes if only the guy who was in charge of logistics and procuring hardware when Jobs died hadn't disappeared. I wonder what happen to that guy.....
Apple had their old creaky OS, had just failed doing a deal with another OS company and then just jumped into BSD.
Huh?
Around '96 Apple was internally working on a new OS that was a failure and bought NeXT started by this guy you may have heard of named Steve Jobs. They then ported NeXT to PPC, replaced Display Postscript with Quartz, added a few classic MacOS technologies and the Carbon API to make developing apps compatible with OS X and classic Mac OS.
OS X. Is based on the internally written NuKernal with a BSD user level and the Next API's.
So should Apple wait 10 years to make improvements to their OS while waiting on standards to catch up?
Of course it is a slower process to achieve interoperability between vendors, that doesn't mean we should abandon open standards except as a baseline to create your own proprietary extensions otherwise we end up back in the IE6/Netscape days.
Yes because it's much better to wait 10 years for a standard to finalize like in the case of HTML5 and web designers still have to go to a site like caniuseit to see what features they can use with which browsers.
Because anytime that you have an "open standard" that you don't control its always a slower process and not optimized for your needs. It's the same reason that Google forked WebKit.
If you want to use an open graphic standard on iOS/MacOS, you're free to use OpenGL.
Not necessarily. Apple provided a security patch for IOS 6 for the 3GS after iOS 7 came out to fix the goth fail bug.
AFAIK, you can still release software that supports iOS 4.1.2 or at least iOS 5
Imagine that, a phone introduced in September 2011, still getting updates....
"legally? pandora, spotify and many many others. then there are torrents"
Neither Pandora nor the free tier of Spotify allow you to create your own playlist of songs.
All seems condemned in the long run to approximate a state akin to Gaussian noise. -- James Martin
