That would be good. Unfortunately not ever is financially secure enough to just up and quit their job at a moment's notice. Disney knows this and will use this fear as a way to screw these people over at some point in the future.
Yeah, they'll likely try to slap an onerous non-compete and NDA into the employment terms as the first wave to weed people out. Then all the people who were too scared of losing their job not to agree will then get silently laid off later.
Which ironically will give them the exact justification to bring in the contractors -
Which is no reason to stick around working for a company that clearly wants to fire you.
What does quitting do other than fulfilling what management wanted all along??
It gives you a chance to get a job at a company that might actually value you? It's not like staying around is somehow sticking it to Disney or any of the boneheads pushing the H1-B plans. So why stick around at a place that doesn't even pretend to have loyalty to you?
They should have already been looking for a job when the layoff was first announced. Unless they have no other job prospects, none of those IT people should be wanting to stay with Disney after this.
One of the workers said, "We were told our jobs were continuing and we should consider it as if nothing had happened until further notice."
Yeah, that notice will be updated employment terms to try to aggressive prevent people from leaking out the details when they attempt to do the H1-B swap the next time.
And to add to this UIWebView uses a different JavaScript engine and actually renders pages differently than Mobile Safari does. So, it's quite a silly claim to say that an alternate browser that uses UIWebView (such as Chrome on iOS use) is just a shell around Safari. If it was, you wouldn't see such disparity in both rendering and its JavaScript engine.
Yes, they will keep using the very language that is being claimed to be "on the way out". Sort of like how Microsoft never stopped using C or C++ for system libraries and APIs even after.NET came out.
No, it won't. Unless you're going to claim that Apple is going to stop supporting C development on their systems. Because the only way to support C in this supposed future where system frameworks will be written in Swift is that Objective-C will still need to be around.
Objective-C is hardly "legacy" considering most, if not all, of the new system libraries and APIa in both iOS 9 and OS X 10.11 are written in Objective-C. Not a single system library or service is written in Swift.
Microsoft has already announced an Objective-C toolchain for Windows that certain select groups have already been using.
With Project Islandwood, iOS developers will be able to take their iOS apps and build them for Windows. Microsoft has developed an Objective C toolchain and middleware layer that provide the operating system APIs that iOS apps expect. A select group of third parties have been using the Islandwood tools already, with King's Candy Crush Saga for Windows Phone being one of the first apps built this way. King's developers had to change only a "few percent" of the code in order to fully port it to Windows Phone.
Uhh, no. So much of the system libraries on both OS X and iOS are written in Objective-C and they aren't going anywhere. Also, all the new APIs of iOS 9 and OS X 10.11 are still written in both C and Objective-C with Swift bridge headers. Basically, it's the opposite of what you claim.
I'd guess that we're about a year away from the point where the majority new code at Apple is written in Swift.
Maybe at the application level, but not for system libraries.
Slashdot Mirror
Likely, but at least they will pretend to want to keep you around. Disney has clearly stated in public that they don't want these people around.
It likely is if you're a C-level.
They're still going to get laid off. Disney has just delayed it a little bit.
That would be good. Unfortunately not ever is financially secure enough to just up and quit their job at a moment's notice. Disney knows this and will use this fear as a way to screw these people over at some point in the future.
Yeah, they'll likely try to slap an onerous non-compete and NDA into the employment terms as the first wave to weed people out. Then all the people who were too scared of losing their job not to agree will then get silently laid off later.
Which ironically will give them the exact justification to bring in the contractors -
Which is no reason to stick around working for a company that clearly wants to fire you.
What does quitting do other than fulfilling what management wanted all along??
It gives you a chance to get a job at a company that might actually value you? It's not like staying around is somehow sticking it to Disney or any of the boneheads pushing the H1-B plans. So why stick around at a place that doesn't even pretend to have loyalty to you?
They should have already been looking for a job when the layoff was first announced. Unless they have no other job prospects, none of those IT people should be wanting to stay with Disney after this.
It's not really Chrome. It's a Chrome shell for Webkit.
You realize how silly this sounds right? From 2008 until they forked WebKit in 2013, that was exactly what Chrome was. It was a shell around WebKit.
One of the workers said, "We were told our jobs were continuing and we should consider it as if nothing had happened until further notice."
Yeah, that notice will be updated employment terms to try to aggressive prevent people from leaking out the details when they attempt to do the H1-B swap the next time.
Sure can.. Been on the App Store since June of 2012.
And to add to this UIWebView uses a different JavaScript engine and actually renders pages differently than Mobile Safari does. So, it's quite a silly claim to say that an alternate browser that uses UIWebView (such as Chrome on iOS use) is just a shell around Safari. If it was, you wouldn't see such disparity in both rendering and its JavaScript engine.
There are alternate shells around the engine of Safari
Nope. They are shells around either UIWebView or WKWebView which are wrappers for the iOS-provided WebKit. They are not Safari.
They cannot enable any HTML5 features that Apple has chosen to leave out of Safari.
Which in no way changes whether something is an alternate browser or not.
Yes, they will keep using the very language that is being claimed to be "on the way out". Sort of like how Microsoft never stopped using C or C++ for system libraries and APIs even after .NET came out.
That will change over time.
No, it won't. Unless you're going to claim that Apple is going to stop supporting C development on their systems. Because the only way to support C in this supposed future where system frameworks will be written in Swift is that Objective-C will still need to be around.
Objective-C is hardly "legacy" considering most, if not all, of the new system libraries and APIa in both iOS 9 and OS X 10.11 are written in Objective-C. Not a single system library or service is written in Swift.
Microsoft has already announced an Objective-C toolchain for Windows that certain select groups have already been using.
With Project Islandwood, iOS developers will be able to take their iOS apps and build them for Windows. Microsoft has developed an Objective C toolchain and middleware layer that provide the operating system APIs that iOS apps expect. A select group of third parties have been using the Islandwood tools already, with King's Candy Crush Saga for Windows Phone being one of the first apps built this way. King's developers had to change only a "few percent" of the code in order to fully port it to Windows Phone.
Obj-C is on the way out.
Uhh, no. So much of the system libraries on both OS X and iOS are written in Objective-C and they aren't going anywhere. Also, all the new APIs of iOS 9 and OS X 10.11 are still written in both C and Objective-C with Swift bridge headers. Basically, it's the opposite of what you claim.
I'd guess that we're about a year away from the point where the majority new code at Apple is written in Swift.
Maybe at the application level, but not for system libraries.
http://arstechnica.com/apple/2...
Well, that used to be true.
Oh really? When was there this mythical time period?
Big industry won't be able to claim a shortage of CS workers to justify more H1B visas for long.
Sure they will. They'll be able to claim anything they want and with their money they will have plenty of receptive ears.
What standard consumer product will that go into? Likely nothing.
Of course not. It would be to the server market like Intel who was pairing FPGAs with Xeons.
It is suggested
No, it wasn't. It was suggested that Xilinx should buy AMD.
Why would AMD buy Xilinx, the company?
They wouldn't and it wasn't what was being suggested.
So basically no different than managing any group of people?
They said "equivalent" not "outperform". You've added some sort of qualifier that the original person didn't to try to inflate the price.