Thank you, Microsoft
-
For what it's worth... Scott Guthrie just put the issue to rest once and for all. http://weblogs.asp.net/scottgu/archive/2010/11/04/silverlight-questions.aspx Silverlight is not going away any time soon, especially in the enterprise space, which I would assume is where a lot of us are at.
I don't think anything is put to rest... Microsoft is banking on Silverlight and the more coders that buy into it the better for Microsoft.... .Net... lib always changing, vb6 - gone... but was awesome, SilverLight... guess WinCE is... what? All that ribbon fuss... But if I code javascript, any kind of server output, and html... perhaps xhtml.. I can pretty much do the same stuff. Videos... need a compatible runtime or plugin for the browser... or something the OS can render from the browser... or at least launch a viewer for... I use microsoft technologies.. but only to get a job done... when it comes to innovation.. it's not my first pick... because way too many times I've invested in Microsoft wholeheartedly to finely get some good software done to have it antiquated by their current marketing pushes... yet... my UNIX knowlegde... keeps expanding... old stays working pretty much identical... still new technologies... but all centered around standards... makes it easy for everyone to play in the sandbox.... versus choosing a TEAM....
Know way too many languages... master of none!
-
About two weeks ago I suggested to my boss that we move all new development over to WPF/Silverlight. I purchased books and installed VS2010 along with the .NET 4 Framework. I've been working on learning the basics of Silverlight over the past two weeks and so far I love the technology. It appears that anything is possible. Today my boss put a print version of this article on my desk: http://www.infoworld.com/t/html5/microsoft-surrenders-silverlight-html5-cross-platform-front-654 Given the clarifications Microsoft has made so far I think the article is ignorant. Irresponsible reporting aside, none of this changes that fact I've been put in a less than ideal situation. Part of the problem is that the life cycle on so many products is getting to be ridiculous. New technologies/methodologies arise quickly, enjoy 15 minutes of fame, and then disappear. My view on this is best illustrated by my actions: I waited until Silverlight 4 to even look at the technology. WPF and Silverlight required a huge investment of time to master. The time involved makes learning "the hottest" every 18 months a foolish waste of time. I don't want VS 2012. I don't want Silverlight 5. I don't want HTML 5. I want a standard IDE that I can use long enough to master and enjoy without three new versions of a platform being introduced while I've yet to complete a project in the original. If they'd slow down a bit and allow a user base to develop maybe they'd enjoy more success. A development life cycle that seems to be driven more by panic than need will destroy adoption. I realize thing are competative, but if the development community is contantly playing catch up I cannot help but feel many of them will get tired and go someplace less dynamic. Where I work we have a 30+ year old mainframe that still does it's job. While we'll never get that from Microsoft I'd settle for something that lasts 5 years.
I agree, technology is moving too fast. It's great when you have all the time in the world to study, but given our work and priorities it's very easy to loose pace and be left behind. I'm trying to catch up now with .Net Framework 4 and it's technologies, but I'm not sure if I will be able to until they release a next version.
-
You may as well buck up and learn HTML/JavaScript because that stuff is proven, platform/company-agnostic, and is only going to ...change as rapidly as all the other development platforms, as it has been for the last 15 years. Sticking with HTML has been clinging to a rollercoaster just as much as sticking with Microsoft has been. Plus it means sticking to the whims of 5 different browser makers all at once, which is even more work than sticking to the whims of a single company. I tend to agree that the Microsoft "platform of tomorrow" becomes the platform of yesterday faster than you can even learn it, and that is frustrating, but the entire development world has been doing this in recent years, MS no more or less than anyone else.
Well of course it changes, any tech changes eventually unless it's Bad Tech™. But the point is that HTML/JavaScript probably won't ever be thrown under the bus by a single company; in my view having 5 entities work on it is a pro, not a con. It's not a silver bullet but nothing ever is, really. I just see it as the most future-proof tech right now. YMMV.
-
Yesterday, goldfish, today, pawns. You have to realize that we developers are merely pawns in Microsoft's chess game to market its real meat and potatoes product, namely Windows and secondly, Office. The reason being, the more sexy products we develop for those platforms, and the more we develop stuff that looks and feels like whatever Microsoft's current fancy is (ribbon bars, what a crock of crap), the more the naive consumer will say, wow, look at all those nice shiny apps, or something to that effect. So, the sooner you realize you are a pawn, the sooner you can free yourself of the game. Consider the difference: WPF, Silverlight, C#, F#, .NET, Visual Studio, are all pieces in Microsoft's chess game. HTML 5? There is no "product" that this technology is pushing--it's agnostic, and even more insidious to some, it's not directly connected with profit. Microsoft hates that with a passion because it leads to free thinking and free thinking leads to free action. Microsoft wants you all under the yoke of making money for Microsoft. Marc
This is the same type of thinking I get from some folks who always 'blame the politicians' for the messes democratic countries get in, without considering the voter side of things that drives the stupidity. I've worked for many orgs that stay away from the 'hottest tech' rat-wheel.. those folks tend to create better/more stable/more predictable/more profitable products, and for some orgs run by folks completely in love with that same rat-wheel (with the coincident lack of quality and chaos that results). Its easy to blame the provider, but remember that they are simply providing what their customers ask for.. in the absence of that need, things would be a tad more rational. Remember.. Microsoft can't force folks to buy things, its a two way street. Your post ignores this part of the human equation, making it, err.. less than reflective of reality.
-
Well, my thinking for going with Silverlight is as follows: 1: I read it's a good place to start as an introduction to WPF - sort of a WPF light. 2: WPF seems to be the replacement for Windows Forms and while Windows Forms will be supported for the forseable future it is a very limited technology when compared to WPF and I think Windows Forms will be dropped at some point. Sure you can get customized controls for Windows Forms but I refuse to use 3rd party controls (license fees, upgrades - it's a nightmare) 3: The web applications I write are for internal use only and I see Silverlight as a way to check out of the HTML uproar. Remember XHTML? Yeah, so much for stability there. 4: I don't think HTML 5 will be any more cross browser than HTML 4. It will work, but each browser will have it's quirks. Committee + Different Vendors = Headache. 5: I really hate AJAX and Javascript. I think it is unneccesarily complex and seems to be a bit of a bailing wire/chewing gum/twine approach to development. You can get some slick results but I'd hate to have to maintain it. How accessible is the average AJAX site? Checking business rules client side (for snappy feedback) and server side (for security) is always fun.... totally awful tools, IMHO.
3. XHTML is still around. 1 and 1.1 won't ever be depracated and browsers will always understand them so there's nothing wrong with that. XHTML lives on in HTML 5 as well, just serve the document as application/xml and close your tags and it's automatically converted. 4. I don't think you've been paying much attention to HTML5 at all from the sounds of it. This isn't really an insult to you but I'd refrain from talking about it until you research things a bit. HTML5 is actually a massive spec and to conform to it you also have to follow the rules on what to do about quirks. Probably the worst thing we've seen from browsers are browser-specific CSS attributes, and those existed long before HTML5/CSS3 and are for mostly trivial things anyways like rounded corners. If you made an HTML5 site using the currently most stable features, it would render exactly the same in any of the current browsers, including IE9. I guarantee you that. 5. Personally I wouldn't code any JavaScript outside of jQuery unless I have to. jQuery is just a really nice, small library that lets you do amazing things, simply. As for tools, the debuggers in Firefox and Chrome are great, although for actual code creation things still seem to be a work in progress. But then again I just use Notepad++.
-
3. XHTML is still around. 1 and 1.1 won't ever be depracated and browsers will always understand them so there's nothing wrong with that. XHTML lives on in HTML 5 as well, just serve the document as application/xml and close your tags and it's automatically converted. 4. I don't think you've been paying much attention to HTML5 at all from the sounds of it. This isn't really an insult to you but I'd refrain from talking about it until you research things a bit. HTML5 is actually a massive spec and to conform to it you also have to follow the rules on what to do about quirks. Probably the worst thing we've seen from browsers are browser-specific CSS attributes, and those existed long before HTML5/CSS3 and are for mostly trivial things anyways like rounded corners. If you made an HTML5 site using the currently most stable features, it would render exactly the same in any of the current browsers, including IE9. I guarantee you that. 5. Personally I wouldn't code any JavaScript outside of jQuery unless I have to. jQuery is just a really nice, small library that lets you do amazing things, simply. As for tools, the debuggers in Firefox and Chrome are great, although for actual code creation things still seem to be a work in progress. But then again I just use Notepad++.
-
My bad about the HTML 5 comments. I thought they were designing browsers (and releasing them) to work against specs that weren't yet complete.
While it is true that HTML5 as a spec is still under active development, certain parts are more mature than others and those parts are the ones being implemented in browsers right now. I've seen examples of both differences being resolved by newer versions of the spec (Google's O3D vs. WebGL for an easy example, although not really a 1:1 correspondence) and differences in fact being created by newer versions (the whole codec debate for example was because the OGG mandate was removed.) So as to whether quirks will pop up when everything is finally said and done, it is tough to say, I'll give you that. But I don't think any quirks will actually impede development, certainly not like how difficult coding around IE6 used to be (even when it was released.)
-
This is the same type of thinking I get from some folks who always 'blame the politicians' for the messes democratic countries get in, without considering the voter side of things that drives the stupidity. I've worked for many orgs that stay away from the 'hottest tech' rat-wheel.. those folks tend to create better/more stable/more predictable/more profitable products, and for some orgs run by folks completely in love with that same rat-wheel (with the coincident lack of quality and chaos that results). Its easy to blame the provider, but remember that they are simply providing what their customers ask for.. in the absence of that need, things would be a tad more rational. Remember.. Microsoft can't force folks to buy things, its a two way street. Your post ignores this part of the human equation, making it, err.. less than reflective of reality.
richard_k wrote:
Your post ignores this part of the human equation, making it, err.. less than reflective of reality.
Indeed! Which begs the question, did someone ask for a platform specific browser package like Silverlight? IIRC, people have been bemoaning the conflicting support of HTML/Javascript in different browsers, wishing for that companies like Microsoft adhered to standards, and that standards addressed real world needs. So how does Silverlight fit this bill? I'm terribly cynical. After watching the PDC presentation on F#, I was left shaking my head, my god, they are REALLY talented at taking a technology and twisting it to promote their own agenda (Azure, cloud computing, etc) while hiding that under something we all theoretically want: access to lots of information and a good way of filtering that information. How they twist F# into a tool to accomplish their agenda (making money for themselves and information providers) while convincing us that F# is THE technology to use for interacting with that information, man, that's truly an accomplishment. Marc
-
While it is true that HTML5 as a spec is still under active development, certain parts are more mature than others and those parts are the ones being implemented in browsers right now. I've seen examples of both differences being resolved by newer versions of the spec (Google's O3D vs. WebGL for an easy example, although not really a 1:1 correspondence) and differences in fact being created by newer versions (the whole codec debate for example was because the OGG mandate was removed.) So as to whether quirks will pop up when everything is finally said and done, it is tough to say, I'll give you that. But I don't think any quirks will actually impede development, certainly not like how difficult coding around IE6 used to be (even when it was released.)
I hope you are right. I'm a bit on the pessimistic side in that this whole thing has all the elements of epic failure: 1: A Committee 2: Unfinished specs 3: Multiple Vendors (all of which want to kill each other) 4: Race to Market I'm so excited about this... I can hardly wait for the BLINK tag to make a big comeback.
-
richard_k wrote:
Your post ignores this part of the human equation, making it, err.. less than reflective of reality.
Indeed! Which begs the question, did someone ask for a platform specific browser package like Silverlight? IIRC, people have been bemoaning the conflicting support of HTML/Javascript in different browsers, wishing for that companies like Microsoft adhered to standards, and that standards addressed real world needs. So how does Silverlight fit this bill? I'm terribly cynical. After watching the PDC presentation on F#, I was left shaking my head, my god, they are REALLY talented at taking a technology and twisting it to promote their own agenda (Azure, cloud computing, etc) while hiding that under something we all theoretically want: access to lots of information and a good way of filtering that information. How they twist F# into a tool to accomplish their agenda (making money for themselves and information providers) while convincing us that F# is THE technology to use for interacting with that information, man, that's truly an accomplishment. Marc
People are doing what they always do, looking for solutions to their problems. Don't mistake statements by columnists as reality.. they are just statements. Microsoft has done well because they've generally listened to the marketplace and built what it looked like their customers needed. All companies will look to forward their own interests, and its up to customers to decide whether those self-same interests helps/hurts their cause as a customer.. which is why every decision to uptake a technology must be done carefully (I know this because I've been involved in many such decisions over the years, since I'm senior technical). I've been in this industry since 1982 and I've never seen overt manipulation as you suggest. Lots of folks imagine that Microsoft is evil, but imagining isn't the same as it being true. I just see a typical large company with a much better than average marketing/product research group and one heck of a technical staff. As long as the buying relationship is voluntary, it still comes down to personal choice and manipulation as you suggest just isn't possible. At the end of the day if customers don't want Silverlight (or any other tech of interest), they simply won't buy it. There IS such a thing as herd mentality.. and large companies play to this.. they are large which makes them stable.. which gives the marketplace a higher tendency to pick them rather than the small players.. but it still comes down to need. If folks didn't think Silverlight would solve a problem they had, it would die. Finally, I've been skeptical of some of the claims of certain languages being some type of magic bullet (F# and lambda based languages come to mind). At the end of the day, its not the language that determines good code, it the human being laying that code down. No matter how 'good' the system, it won't save you from a monkey at the keyboard. And given how business is normally transacted and technical management actually occurs, it can be supremely difficult for an engineer to actually design in extensibility and look ahead (assuming he even has the willingness or tendency to care about such things).. I've lived this reality too much over the years to fool myself about how languages and technologies play into the mix (I seriously thing 5% influence is all I'd give.. quality is about discipline and good management.. both of which have been sorely lacking in this industry EVER SINCE I STARTED). I've always been concerned about an over emphasis on technologies rather than the huma
-
On a different but very related issue... I realised something was wrong the day I (with a decade and a half as a Microsoft developer) needed to ask someone where the 'Save As' option was in the new version of Word. I still find myself wasting time trying to figure out how to do things I've been able to do for years with previous versions. I thought it was early signs of old age, but yesterday I saw a gathering huddled around a PC trying to figure out how to Print Preview. Somebody in Redmond needs to have a Wireless Keyboard shoved so far up their ass that they can type their resignation letter with their tonsils. -Rd
Hit any user to continue.
I worked at Oracle for more than a decade. Their internal site for doing employee related admin stuff changed every two years. And I'm not talking minor changes. From one day to the next the entire menu structure/layout would change, and the entire community of employees would be caught have to figure out where their 5 important menu choices went. This is a software company doing this. One with a whole division committed to usability. This experience, repeated every two years, convinced me that very little rationality went into some technical/UI Design decisions. I don't blame Oracle per se.. I think its just human nature. I think the folks in control of the UI for that internal site were more concerned about 'showing progress' in their work than about the effect their changes would have on the community using their product. I think this exact claim can be leveled at the redesign of the Office UI in recent years. Such is the world we live in.
-
This is the same type of thinking I get from some folks who always 'blame the politicians' for the messes democratic countries get in, without considering the voter side of things that drives the stupidity. I've worked for many orgs that stay away from the 'hottest tech' rat-wheel.. those folks tend to create better/more stable/more predictable/more profitable products, and for some orgs run by folks completely in love with that same rat-wheel (with the coincident lack of quality and chaos that results). Its easy to blame the provider, but remember that they are simply providing what their customers ask for.. in the absence of that need, things would be a tad more rational. Remember.. Microsoft can't force folks to buy things, its a two way street. Your post ignores this part of the human equation, making it, err.. less than reflective of reality.
Umm, that isn't exactly correct. Case in point, multicore processors. From a software standpoint, there is nothing lovable about multicore. Getting full performance out of multicore chips is a nightmare of multithreading. Users get nothing either, except the performance boost they've come to expect. For the chipmakers though, multicore is easy. Chipmakers couldn't make their current processes go faster because the transisters were too leaky, so they replicated older chip designs to get 2, 4, and soon 8 on a die and called that a performance increase. Otherwise they'd have to drop the price of their chips. But aggregate performance is not what we want. We want faster uniprocessor performance so we don't have to mess with multithreading. It's not what customers want. They want performance increase that works with their existing code too. But it is what chip makers want, because it's cheaper and quicker than investing in new process technology. Same thing with microsoft. We don't want a new OS every three years. But if microsoft doesn't make a new OS every three years, buyers expect the old one to get cheaper and cheaper, or at worst to not get more expensive. So there has to be a new feature. And it has to be in the OS because otherwise you could just add it onto the old one. And you have to get programmers to develop code that only runs on the new OS, to give users another reason to upgrade, so there has to be new and incompatible APIs to learn every few years. OK, it also helps that the way microsoft develops APIs, the old ones can't be extended very well. That would be dumb for another company but for microsoft, it helps them sell OS upgrades. It's very true that you don't get to buy what you want or need, you get to buy what somebody wants to sell you. And smart somebodies only want to sell you stuff that helps them out, whether it helps you or not. Sigh.
-
Umm, that isn't exactly correct. Case in point, multicore processors. From a software standpoint, there is nothing lovable about multicore. Getting full performance out of multicore chips is a nightmare of multithreading. Users get nothing either, except the performance boost they've come to expect. For the chipmakers though, multicore is easy. Chipmakers couldn't make their current processes go faster because the transisters were too leaky, so they replicated older chip designs to get 2, 4, and soon 8 on a die and called that a performance increase. Otherwise they'd have to drop the price of their chips. But aggregate performance is not what we want. We want faster uniprocessor performance so we don't have to mess with multithreading. It's not what customers want. They want performance increase that works with their existing code too. But it is what chip makers want, because it's cheaper and quicker than investing in new process technology. Same thing with microsoft. We don't want a new OS every three years. But if microsoft doesn't make a new OS every three years, buyers expect the old one to get cheaper and cheaper, or at worst to not get more expensive. So there has to be a new feature. And it has to be in the OS because otherwise you could just add it onto the old one. And you have to get programmers to develop code that only runs on the new OS, to give users another reason to upgrade, so there has to be new and incompatible APIs to learn every few years. OK, it also helps that the way microsoft develops APIs, the old ones can't be extended very well. That would be dumb for another company but for microsoft, it helps them sell OS upgrades. It's very true that you don't get to buy what you want or need, you get to buy what somebody wants to sell you. And smart somebodies only want to sell you stuff that helps them out, whether it helps you or not. Sigh.
Have you actually worked for one of these companies? I have (Oracle). The decisions you assume are being made are the furthest from reality I can think of. All the API/product oriented decisions are made to meet customer needs, not manipulate the market. Believe what you wish, but after over a decade at Oracle, I can personally tell you that you don't know what you are talking about. The folks working at the large companies are feverishly trying to meet the needs of their customers. All the talk about having stuff forced down folks throats and them just accepting it is utter hogwash. If that was the case the teams I saw disbanded due to bad feature/quality wouldn't have been disbanded.
-
MehGerbil wrote:
It appears that anything is possible.
Ahhhh, fresh-faced programmers always seem so impressionable and full of hope. And then...
MehGerbil wrote:
Today my boss put a print version of this article on my desk:
Reality comes crashing down on them, killing their dreams, dashing previously held assumptions and beliefs over the rocky cliffs of dispair, making them rethink their liberal view of firearms ownership, if only long wenough to "teach those bastards in Redmond a lesson the won't soon forget". Welcome to hell, young Jedi. I have ammunition older than most Microsoft tech, and it's still viable.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
Wow a real life example exactly illustrating my point of why the original statements and lukewarm retraction were such a calamity for Silverlight. I've become convinced that in fact it's a safe platform to bet on but your situation illustrates perfectly why it could become a sort of self fulfilling prophecy in a world where perception can quickly become reality.
“If you want to build a ship, don't drum up people together to collect wood and don't assign them tasks and work, but rather teach them to long for the endless immensity of the sea” - Antoine de Saint-Exupery
Sadly, its seems like perception is frequently reality.... I'm beginning to think of the 21st century as the 'century of the conspiracy theory'.. it seems to apply to all walks of life. The internet, rather than acting as a conduit for information and truth, has become an echo chamber of fear.
-
Sadly, its seems like perception is frequently reality.... I'm beginning to think of the 21st century as the 'century of the conspiracy theory'.. it seems to apply to all walks of life. The internet, rather than acting as a conduit for information and truth, has become an echo chamber of fear.
Don't you think that's a wee bit pessimistic. It's the same internet that can allow a gay person in rural Mississippi to access support groups that can help them anonymously and privately get counseling they need. It's the same internet that can help an auto worker in Detroit who lost their job years ago keep their house by selling hand made items online. It's the same internet that can and often does feature thousands operating out of complete selflessness to debunk false information. I think it just depends on your point of view.
“If you want to build a ship, don't drum up people together to collect wood and don't assign them tasks and work, but rather teach them to long for the endless immensity of the sea” - Antoine de Saint-Exupery
-
Don't you think that's a wee bit pessimistic. It's the same internet that can allow a gay person in rural Mississippi to access support groups that can help them anonymously and privately get counseling they need. It's the same internet that can help an auto worker in Detroit who lost their job years ago keep their house by selling hand made items online. It's the same internet that can and often does feature thousands operating out of complete selflessness to debunk false information. I think it just depends on your point of view.
“If you want to build a ship, don't drum up people together to collect wood and don't assign them tasks and work, but rather teach them to long for the endless immensity of the sea” - Antoine de Saint-Exupery
I didn't say it isn't used for good.. you are correct.. it certainly is! You are missing my point.. its acting as a magnifier for these types of things. There have always been conspiracy theorists amongst us (read history and you'll see it).. but the raw incidence of it has gone up considerably.. And when it went up coincided with the explosion of the internet. Those amongst us who are easily fooled have access to google! Wikipedia is a microcosm of the greater effect.. I've been reading history for decades.. so I know how to tell good stuff from trash.. and the pure history on Wikipedia is NOT trash! Just an excellent reference source :) But.. There are pages on wikipedia that are subject to edit wars because of some popular cause/political position/ideology/belief which have as much relationship to truth as I have to the Pope. The internet taken as a whole seems very similar to me.. and those folks that are easily fooled..
-
I can't say I feel very sorry for Silverlight developers right now. They have staked their livelihood on a single company's whims, a company mind you that has a storied history of changing its mind whenever it pleases. "Oh wow, Win32! Time to-" "Err, .NET is in now? Well OK, let's-" "Oh, WPF? I guess that makes since with Vista-" "Silverlight? Really?!" Just to give some examples of how spastic their desktop development toolchain has been. You may as well buck up and learn HTML/JavaScript because that stuff is proven, platform/company-agnostic, and is only going to grow in the future. Now I'm also a bit of an open web app zealot but I wasn't always that way. I still use Windows and I've always loved C#'s syntax and features - I just wouldn't stake my job on them given the choice.
Did you miss the fact that much of .NET is a wrapper round Win32? And that you still have direct access if you want? Not only does Win32 still live, it still lives in .NET! .NET is there to help insulate against change.. whether that is a successful goal will be judged 10 years from now, but I CAN tell you that .NET speeds things up considerably from the old Win32 days. Similar problems today written in .NET take me 1/3rd of the time than they did in the mid 90s. And those days where a HUGE change from when I was coding embedded stuff in Z80 and 6502 in the mid 80s.
-
richard_k wrote:
Your post ignores this part of the human equation, making it, err.. less than reflective of reality.
Indeed! Which begs the question, did someone ask for a platform specific browser package like Silverlight? IIRC, people have been bemoaning the conflicting support of HTML/Javascript in different browsers, wishing for that companies like Microsoft adhered to standards, and that standards addressed real world needs. So how does Silverlight fit this bill? I'm terribly cynical. After watching the PDC presentation on F#, I was left shaking my head, my god, they are REALLY talented at taking a technology and twisting it to promote their own agenda (Azure, cloud computing, etc) while hiding that under something we all theoretically want: access to lots of information and a good way of filtering that information. How they twist F# into a tool to accomplish their agenda (making money for themselves and information providers) while convincing us that F# is THE technology to use for interacting with that information, man, that's truly an accomplishment. Marc
Well, as someone who builds enterprise browser-deployed apps we love it. The pain we suffered through previously fiddling with ASP.NET apps to get them to run on two or three different browsers, and even then they looked like crap. Flash was never up to the job. I still can't understand the carry on. All because one guy feels the need to use ten words where one will do. His boss replied to his attempted clarification, and the boss's response was pretty clear. Silverlight is not dead, and will be a core platform. HTML5 is supported for cross-platform purposes (they're never going to built Silverlight for all the possible devices out there - phones, thin clients, whatever) and they're going to do both properly. I used to hate Microsoft's development tools, but things have changed in the last 5 years. There is a reason Borland declined .. many of their diehards, like us, went over to Microsoft. I personally am a big .NET fan .. a consistent managed environment from little devices, through CE and all the way up to Enterprise class apps.
I hate signatures, so I'm not going to add one. See?
-
Have you actually worked for one of these companies? I have (Oracle). The decisions you assume are being made are the furthest from reality I can think of. All the API/product oriented decisions are made to meet customer needs, not manipulate the market. Believe what you wish, but after over a decade at Oracle, I can personally tell you that you don't know what you are talking about. The folks working at the large companies are feverishly trying to meet the needs of their customers. All the talk about having stuff forced down folks throats and them just accepting it is utter hogwash. If that was the case the teams I saw disbanded due to bad feature/quality wouldn't have been disbanded.
So, buying up MySQL and then making it more expensive was done strictly to meet customers' needs, right? No, clearly this move was made to remove a successful low-cost alternative. The market responded clearly too, warming up the Postgress open source project. So don't try to tell me this was about meeting customer needs. Customers needed an inexpensive, reliable database, and top transaction rate was not the most important thing to them. Customers *wanted* MySQL. Oracle *wanted* customers to pay more (to Oracle) for any choice they made. Yes, I've worked for big companies. And yes, on individual projects, the design teams work hard to meet customer needs. But at the strategic level, where projects are selected, you may rest assured that firms consider lock-in, weakening or eliminating competition, maximizing profit, and all those other things that run counter to customer needs. Maybe I should ask if *you* work for one of those companies, because clearly you have not been involved in any strategic level interactions.