And you know what? WPF _is_ nice. I _liked_ Silverlight (but am frustrated that it doesn't work under Linux, though not surprised). Microsoft make _good_ developer tools, in my personal humble opinion.
The problem I see are they still make a large amount of missteps, and don't engage the "tastemakers" of tech anymore. Any goodwill they once had has been squandered, and if you look at Yahoo! you can see that it's super difficult to get it back.
Now that Ballmer is leaving, it will be interesting to see what happens in the future -- will they get a CEO that isn't afraid to take big, bold risks? To cook the golden goose in the short-term, perhaps, to allow for growth into new markets?
Somehow I doubt it, but I wish they would.
Windows 8 has been really good to me; I've installed it (and Office 2013) on all the devices of my family and (ex)girlfriends, my ex has a Windows Phone on my recommendation. They all love it, and find it easier to use than anything in the past. Just today, I purchased a touch-screen HP All-In-One for my Grandfather, and he loves it (and is super excited about using the Kindle app while in his lean-back chair on the 22" screen, synced with his Kindle itself).
When I was working at Harvey Norman, I sold $15 000 worth of Surface and Surface Pros to customers in one month; They were easy to sell as long as you knew how to appeal to the consumers _actual_ needs. They didn't suit everyone, but for those that did no other Tablet came close.
Basically, they have more potential than nearly any other tech company out there. Something has been holding them back, and they've succeeded in spite of themselves. I hope that they can turn it around moving forward.
Your post is all about how much you like Microsoft. It could likely be replaced by the words "But I like Microsoft developer tools", and still get the exact same message across. There is no sources to back it up, or arguments against or in favor of the parent post. Its the exact style of comment that creates flame-wars which HN want to eliminate.
Please, if you reply to a commenter about mono-culture and job seeking, focus your comment on that subject. Do not fall into "but I like X" kind of replies, or all you get back is "you are wrong, X is bad".
I think Microsoft has potential, but currently there is a reason I don't use any of their products nor plan to personally. Doesn't mean they don't have their place, like any product.
Also, an argument could easily be made that OP's post, which I found really interesting, is just another way of saying "Microsoft sucks", as it is merely anecdotes without sources again.
Regardless, I merely posted my opinion, like many others here. Sorry that it doesn't conform to your ideal.
However, saying "I _liked_ Silverlight" is not an anecdote. I can't discuss it, poke or question it, as it is without doubt true that you do indeed like Silverlight. As substance for a discussion, it as empty as it can be. At best, I can ask you to write a new comment which explains why you like Silverlight, in which you maybe then end up using anecdotes to support your view. That would then be the actually comment of substance, in which debate, research and discussion might flow from.
In the hierarchy, "I like X" and "I don't like X" is at the bottom. As such, my "ideal" is that comments should indeed strive to be above the lowest of the lowest, even if that means just going a step above into the realm of Anecdotes.
There was a recent HN discussion about anti-MS bias on the site. I wonder if that may be relevant.
I think they pretty much account for most of the hate you see on HN. Brand identity is the new opiate of the masses.
Awesome, but really brings to light how poorly MS handles advertising.
And if you're stating '_good_ developer tools', then what is your opinion on MS-supplied basic tools - ssh app? copy/paste in Powershell? Connection libraries for their SQL server in all common (including non-MS) languages? Unicode support in console? I mean, theres a bajillion tiny, insignificant things that add up to a death by papercuts, since on Mac or Linux all third-party development environments for common languages Just Work the way they should, but I've seen numerous cases where getting up the same perl/haskell/whatever package on windows requires jumping through a dozen hoops.
C# is a quite nice language - but can I get one-click setup of it's tools on all major OS'es, and deploy code on non-windows servers as easily as with java or ruby?
Surface Pro seems like really nice hardware - but for any development needs, I'd rather want Ubuntu or MacOS on similar hardware.
MS problem is not, in general, poor tools - the problem is that it doesn't play well and integrate with the rest of the world; and in the rest of the world good integration with everything is a basic assumption even for low-quality recently started tools.
1. s/for it's time/for its time/
2. Instead of using _underscores_ for emphasis, on HN you can use asterisks, like this:
asterisks, *like this*So, I joined a .NET user group, I installed VS, I started learning.
Problem was, MS was churning out the "next great thing" faster than I could learn the last great thing. While I was getting my head around WinForms, WPF came out. I started using WPF, then Silverlight arrived, which was like WPF, just a subset of it, and therefore different enough to be problematic.
But that wasn't too bad. It was the 'blessed' data layer stuff that threw me. When I started it was DataSets etc. Then it was LINQ-to-SQL, then it was very much not LINQ-to-SQL, but instead was Entity Framework.
As a newbie who was trying to make myself marketable, it felt like a bit of a hamster wheel, but then through the user group, I met .NET pros who felt exactly the same way.
And at the end of the day, the greatest irony was that when I finally broke into the market, it was a Java-based developer role on the basis of my JavaScript. So all my years of frantically spinning the .NET wheel was for naught.
I still do love F# though.
In hindsight, the thing that strikes me about .NET development is that most businesses using it really want the whole stack to be from one provider whom they trust - and as a result, third party alternatives never really get a look-in if an MS or MS blessed technology such as JSON.net (http://james.newtonking.com/json) can do the same job.
That is a massive sweeping generalisation of course, and only applicable to the limits of my experience in a small city in a small country.
As a newbie who was trying to make myself marketable, it felt like a bit of a hamster wheel, but then through the user group, I met .NET pros who felt exactly the same way.
Most .NET developers learn what they need to know for the project at hand. A year ago, I worked on a fairly cutting-edge EF Code-First n-tier project, with knockout.js on the front end, using ASP.NET MVC web API. I am currently extending a crufty ASP.NET 2.0 webforms app.
Adaptability is an important skill for developers. Also, each iteration of the Microsoft data access stack feels like an improvement over the earlier ones, so it's not an unbearable burden to learn it.
And at the end of the day, the greatest irony was that when I finally broke into the market, it was a Java-based developer role on the basis of my JavaScript. So all my years of frantically spinning the .NET wheel was for naught.
Hiring someone for a Java job, based on their JavaScript knowledge is fairly unconventional (to put it politely). Are you certain that the general programming knowledge you acquired through "spinning the wheel" wasn't a factor?
I never stopped (and never do stop) learning as much as I could, and I apologise if I gave the impression I was only learning .NET stuff. I was primarily coding in Python, but got into JS to write stealth code to automate a horrendously manual part of my day job in a government contact centre.
To clarify for you on the hire, I was hired for the JS, but expected to learn Java pretty quickly.
> Adaptability is an important skill for developers.
For sure.
Same here. I design databases, and MS kept bringing new data access methods every three years; I never could wrap my head around the ADO/DAO difference, but that did not matter for long because both were replaced by .Net
I sincerely wondered if this was not a deliberate tactic by Microsoft : while developpers are busy learning their newest "next great thing", they can't invest time in anything else.
Meanwhile I learned how to use an OSS lamp stack and have been happily using it for the last 10 years. Very stable and reliable, I could not be happier.
Bingo!
Either Microsoft is incompetent or promoting/retirement of APIs is more profitable.
mmmh... I thought about this too.
However, MS is anything but stupid marketing wise, I find. So I dismissed incompetence.
I find that Java's biggest problem (stability/stagnation depending on who you ask) is also the JVM development ecosystem's benefit. There's not one body driving adoption of technologies by deciding what's supported and what's not, so technology choice is less dictated by economic imperatives.
Linux, Apache, Mod_perl, Postgresql
All very pleasant to work with (1) and stable; mod_perl has a rather steep learning curve, but worth it for web work. Very powerful _and_ low cost.
( 1 : if you like Perl, obviously )
[Edit] asterik in note caused weird formatting; replaced with 1
WPF and Silverlight share almost the XAML stack with little differences. One just needs to know those differences.
LINQ-to-SQL and Entity Framework are usually used together and also share common concepts.
Other vendors also keep changing their stacks, it is the job of a developer to keep up with changes and learn to quickly pick up what is relevant for a given project.
Sure, on Windows Phone I'm forced to use LINQ, and I've written some really crazy code to hide it from my app, but at least my app is fast.
Consistency leaves a lot to be desired as well.
Their findings: PHP and .Net. That's what the vast majority of companies they spoke to are hiring for.
My point is that there's a whole world of tech outside HN.
.NET - 1000+ positions
Java - 1000+ positions
PHP - 454 positions
Python - 295 positions
Ruby - 280 positions
Node.js - 55 positions
Lisp, Haskell, Scheme - 0 positions
I expect to find a larger percentage of competent programmers for the python/ruby jobs than for the .net/java jobs.
Every job I've had so far seems to prove this true.
Competent programmers exist in all types of jobs with all types of platforms. In fact, I would argue that those of us who don't jump to every new fad language that comes out may likely be more productive by default. Instead of worrying about what frameworks we're going to use to supplement our Node+Json+Rails+Bootstrap+Coffeescript+blergh security nightmare, we just start coding.
There are fantastic programmers in every language and lousy programmers in every language. Just the way it is.
Do tech companies even post on monster?
Get a grip on reality.
I also don't see this: "I would fault them for building their entire ecosystem with total disregard for standards, their refusal to work with whatever community existed outside." My daily experience is very different. If I start a new project, it'll almost certainly be on the open-source (Apache 2.0) ASP.NET MVC platform. That gives me Twitter Bootstrap, Knockout.js, OAuth2.0, etc. It's a neatly integrated patchwork of commonly-used, standards-happy, open-source frameworks and libraries, and it'll work happily on safari and chrome and on my phone. So I don't feel particularly isolated away from the rest of the development world.
Summary is, I'm sure this vision was true years ago, but things seem to have moved on. I think that now, if I want to put together software using modern approach, there aren't approaches or technologies that the MS stack makes tricky. But I'm happy to be corrected; are there technologies or approaches I can't use fairly easily on the MS stack? Cloud computing? single page apps? continuous integration? BDD? etc. What am I missing?
Show up at a few meetings (ther's various hacker stuff going on) and get some names on your LinkedIn. I bet that'll fix it.
On top of that, Apple's done more than any other single player (except perhaps Adobe!) to move the industry away from Flash, to open alternatives.
No, they don't always follow standards or always have open implementations, but their garden is arguably quite a bit less walled than the one in Redmond. Which makes your point a little confusing, at best.
Also related: http://www.apple.com/opensource/
Microsoft has released open formats as well, like XPS. And Microsoft does open source today as well. That's how the industry works today.
Sure flash is bad thing but if Sun had its way with the internet and Microsoft had not stopped them we be all doing Java applets by now.
However that's all beside the point, the point is that complaining against Microsofts closed culture and in the same sentence referencing Steve Jobs is like taking a bath in koolaid, regardless of Microsofts closed culture.
It's just double standards.
Apple created Webkit. They were using/forked KHTML for that, but it quickly diverged.
> Also related: http://www.apple.com/opensource/
Also related: http://www.microsoft.com/en-us/openness/default.aspx#project... and http://research.microsoft.com/en-us/
According to the guy who implemented FFmpeg's ALAC encoder, there are power benefits to ALAC over FLAC. ALAC was developed when iPods were struggling to get 8 hours of playback, so it doesn't seem unreasonable that Apple's engineers wanted to be able to match the codec to the hardware as efficiently as possible.
I think that the main problem is the MS has always tried to make things appealing to a certain crowd known as "VB developers", "drag and drop developers", etc.
I've heard too many times "You can do this with almost no code" with our cool new "Microsoft Foundation For Next Big Bullsh Blah Blah". And this is presented as a good practice. And the whole army of evangelists starts touting and praising the next BS framework. People start adopting it, other people start building other things on top of it, until everyone realizes it's BS and such practices, proclaiming "you'll write less code" lead to a pile of bad design decisions that you will later deeply regret.
Seriously, this is my biggest pain when changing between OSes.
I suspect ‘Kayoone’ was referring to the functionality of the ‘alt’ and ‘ctrl’ keys on a Mac keyboard versus what those keys do in Windows. For example, in Windows, ‘ctrl-C‘ is used to copy, while on OS X, it’s done with ‘command-C’. The placement of the actual keys are quite similar between PCs and Macs.
The Apple ][ keyboard didn’t have an ‘alt’ or ‘ctrl’ key. The Apple IIGS had both keys, and they were placed in the same arrangement as the original IBM PC keyboard (with the ‘ctrl’ key above the left ‘shift’ key.) On later Apple and IBM PC compatible keyboards, the ‘ctrl’ key was moved to the bottom row, to the left of the alt key.
I already changed to the US keyboard layout which makes this alot better, the standard german Mac Layout is just total garbage.
No, this was very much intentional: https://en.wikipedia.org/wiki/Criticism_of_Microsoft#Vendor_...
Aren't both of those technologies, if not actually dead, certainly not the things that even _Microsoft_ wants people to be using these days?
Greg has been a believer in Microsoft. He went to all the Tech-Ed conferences, attended every MSDN event he could. Conferences are grand stages that leave an impression. He drank all the cool-aid that was served at these conferences.
Things were really good early on, this was the last decade. The computing scene at that time revolved around Microsoft like the many moons of Jupiter. Greg and his team built products with Silverlight, WPF, .Net, Windows Workflow, Biztalk, Remoting, and the like. Every conference offered something new, something exciting. The apps they built worked great, looked great.
Fast forward to now. Greg is a decent programmer, but he wants a new job badly. The problem is that nobody wants to use all that stuff that he knows. People want to build on standards; apps that work on every device. Not just on Windows and not just on Internet Explorer. Greg still doesn't get it. He hasn't seen much of the world outside Microsoft, and still wonders why people don't want Silverlight. Still tells me how WPF is so much better that anything else out there. And running only on IE, why is that even a problem? Everybody has IE. Poor Greg, tough times.
There may be many issues with Microsoft. But more than anything else, I would fault them for building their entire ecosystem with total disregard for standards, their refusal to work with whatever community existed outside. This probably wasn't intentional, they must have probably believed in what they told their developers. Even though so much has changed since their glory days, there's a part of Microsoft which still refuses to engage.
There was a Steve Jobs interview from the late 90s in which he said, "The problem with Microsoft is that they have absolutely no taste". Jobs wasn't talking about aesthetics; it is true of pretty much everything from Microsoft. From UIs, to development frameworks, to tools, to shells and even APIs. Back then, having "no taste" was totally fine because people communicated far less.
Now we have a whole bunch of people who are stuck using this stuff. And many of them don't really get it yet.
Edit: I just saw that you work for Microsoft, and specifically Microsoft Research. You guys make awesome stuff. The above is mostly about the Windows platform.