Slashdot Mirror
Yahoo Excludes BlackBerry From Employee Smartphone List
Nerval's Lobster writes "Freshly minted Yahoo CEO Marissa Mayer is promising the company's U.S. employees a new smartphone of their choice. There's just one catch: it can't be a BlackBerry. According to Business Insider, which posted significant portions of Mayer's memo, employees will have a choice of the Samsung Galaxy S3, HTC One X, HTC EVO 4G LTE, Nokia Lumia 920, or the upcoming iPhone 5. 'We'd like our employees to have devices similar to our users, so we can think and work as the majority of our users do,' she wrote, adding that Yahoo will shift away from BlackBerry as its corporate device of choice. Somewhere up in Waterloo, at least one Research In Motion executive could be screaming in frustration over this development. Not because Yahoo is a bellwether for corporate smartphone use; its U.S. employees shifting to an iOS, Windows Phone or Android device won't automatically drive other major companies will follow suit. But as a symbol of RIM's current issues, it's difficult to find a better one than a high-profile technology company dumping its collective BlackBerry stock in favor of pretty much any other platform."
What's next, RIM employees stop using Yahoo for search and tell their employees to use Google or Bing?
No one buys Microsoft phones.
Not true. This is posted from a Windows 7 Phone. They work just fine. I'm happy with mine. You don't know what you're talking about.
I don't respond to AC's.
Because RIM is on the decline and there is a fair amount of momentum behind MS.
I think you misspelled the word "money". The first two letters were right, but then you went right off the tracks.
My WTF was different than yours.
CEO Marissa Mayer: "so we can think and work as the majority of our users do".
VLM questions "Yahoo still has users?" Who?
But then I'm CEO of nothing.
Patience young grasshopper. Yahoo will achieve nothingness soon enough. Then you can be its CEO.
I've occasionally wondered how much it would cost to start collecting companies as a hobby. For example, mint condition dotcom 1.0 corporations. How much would it cost me to buy flooz or drkoop.com or whatever it was called? I would imagine there's some ongoing accounting/tax costs. I do know people who collected paper stock certificates, for example Disney's paper stock certs used to be really cool and artistic, and I've always thought a collection of dotcom stock certs would be funny... but why collect a paper printout of a millionth of the dotcom when I could own the whole thing? My budget for this amusement would be on the scale of three digits, four is really pushing it. Is this a realistic collecting hobby for me? I'm not going to be one of those old people collecting a houseful of ceramic frogs... no not me... I'm gonna collect mint condition dotcom 1.0 companies. That sounds like fun.
"Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
I'm glad to see they chose Nokia Lumia 920 as a phone. It is very powerful, sleek and well-done smartphone with enterprise features from Microsoft. It's really much better business phone than iPhone or Android-based smart phones. On top of that Yahoo can use Visual Studio to develop their own apps - all with the maturity and familiarity of C# and Windows programming. Great choice!
Hum. You guys aren't up to the standard of the normal turfers from waggeneredstrom.com. They usually throw in some links:
I'm glad to see they chose Nokia Lumia 920 as a phone. It is very powerful, sleek and well-done smartphone with enterprise features from Microsoft. It's really much better business phone than iPhone or Android-based smart phones. On top of that Yahoo can use Visual Studio to develop their own apps - all with the maturity and familiarity of C# and Windows programming. Great choice!
What's next, RIM employees stop using Yahoo for search and tell their employees to use Google or Bing?
I think the vast majority of them are already using monster.com and dice.com, etc. Oh wait, do you mean general internet searching, not looking for a new job after the downsizing?
"Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
It's like being dumped by the dorkiest fat kid in school.
That's one way of interpreting it.
So here's an ex-google exec saying Yahoo employees can use a bunch of android phones or a currently-unavailable iphone. Didn't a certain Nokia exec do something similar recently.. hmm
So Yahoo thinks it should discard RIM... When was the last time Yahoo got much of anything right? How do we know this isn't yet another miss-step? Aren't there some BB users that use Yahoo? Wouldn't it be better if Yahoo employees used ALL of the common smartphones?
You think that's bad, I'm a VB.Net developer. People rant endlessly about VB.Net. It's almost got the exact same feature set as C#, minus a few and plus a few features. For a long time, C# was missing simple things like optional parameters. Also, VB.Net has always had a much superior background compiler. A lot of what you hear about VB.Net is based on biases from the old VB, as well as complaints about syntax and verbosity. Neither of which really address it's merits.
Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
Hey look! You found him!
Oh, let's see.
Proper anonymous functions, including lambdas.
Proper function pointers (called delegates) without needing to write entire classes for them.
Support for stack-allocated complex types (structs).
Support for bi-directional and output parameters, even of types normally passed by value.
Unsigned integer types.
Object parameters (technically functions, but cleaner than a bunch of Get*and Set* function definitions and usages).
Proper generics (try declaring an array of generic type in Java, for example).
Easy interop with native code (P/Invoke, good marshaling capabilities, support for ordered structs and unsigned types, etc.).
Support for direct memory access (if you want/need it; use the unsafe keyword and byte* or similar types).
LINQ.
Tuples.
No one-public-class-per-source-file restriction, or the associated restriction on file name.
No restriction on project directory structure.
Partial classes (allows separating parts of the same class, such as autogenerated code from developer code, into different files).
The using keyword (in both of its uses).
Conditional compilation (similar to C preprocessor) to do things like exclude debug code without any overhead at all.
These are the ones that came to mind in just a few minutes of thinking about it, based on personal experiences, I'm sure there's a ton more. C# is a vastly more advanced language than Java. I don't deny that MS learned heavily from Java, but half of that learning was "let's not repeat their mistakes" and the other half was "what is it really lame that this language lacks? Let's do better."
There's no place I could be, since I've found Serenity...