You seems to be a Windows fan, aren't you. Yes for Windows I'm a troll but other Slashdot readers seems to like this, else I wouldn't have gotten a Karma Excellent.
But instead getting personal I'll give you the chance to explain why you think wyoGuide is wrong or what is wrong. Just tell us all why you think the Picasso Wine implementation is better and Google should keep developing that way.
I'm no expert, but to me, cross-platform development is taking a lowest common denominator approach...
I think I am a cross-platform expert and I can assure you that cross-platform doesn't mean lower that native these days. Just look into wyoGuide (http://wyoguide.sf.net/) to find out how cross-platform development is done, in many cases it's even simpler than single-platform and less error prone.
Doesn't Google employees read Slashdot? I've multiple times told what I think is the best way to develop software albeit other might think different. Yet probably everybody agrees that wyoGuide (http://wyoguide.sf.net/) is by far better than Wine. wyoGuide is IMHO the only way how to do cross-platform development and the only way for OpenSource and ClosedSource. It seems to me that it's exactly perfectly suited for Google.
On screenshots for a desktop usable by "everyone"...
wyoGuide and wyoDesktop are two separate projects, one is about applications the other about a desktop. So far I spend almost all the time for wyoGuide which leaves nothing for wyoDesktop.
The other thing is that you may want to consider switching from wxWidgets or GTK+ or whatever you're using to Qt...
It's amazing that everytime I bring up wyoGuide a QT-Fan tells its story albeit no QT-Fan seems to be willing or able to provide sample code for QT. Why?
wyoGuide can be used with any framework and no preference of QT so there's no point in switching and definitely not as long as there isn't appropriate sample code.
DDR2 has been known long enough to be considered when AMD designed socket 939. So they are either incompetent or cheaters. Either one annoys me so I probably don't stick with them any longer unless they are factors better.
Why do computer companies never understand to not annoy potential customers.
Just by following a few simple common-sense guidelines, you can drastically improve the usability of any given software:
I just read your comment because of two reasons, first it just comes after mine and second because it's just about what I had in mind when I designed wyoGuide (see http://ask.slashdot.org/comments.pl?sid=186617&cid =15399619. But the difference is you tell just common sence while I show how this common sense can be implemented into code. I invite you to look through the guideline and discover the points where common sense might be improved so at last we get better applications.
See http://wyoguide.sf.net/, it can be used with any programming language with any framework on any platform. So far it's the only guide which gives advice in a cross-platform fashion, has sample code and if you happen to use C++ a demo sample for use as your starting code base.
Microsoft has a market share of above 90%? It's no wonder that computer illiterate people think it synonym with computer understanding. Most people don't see a computer as a gadget but as a tool which helps them doing their tasks. People want to write simple letters, sometimes a full resume or to look up some information or schedules in the internet or maybe get some music or play a game. People don't want to install a system or an application and they definitely don't want to work around annoyances and bugs. So as long as Microsoft cares for these people but none of the OpenSource developers, computer literacy is synonym with knowing Microsoft.
To counter this one way behavior I've created wyoGuide (http://wyoguide.sf.net/). It just shows to developers how to code their applications so all these people can use and like them. But it only makes a sense if developers make wyoGuide conformant applications and users ask for wyoGuide conformant applications.
Well first of all OpenSource developers should code alike. Here http://wyoguide.sf.net/, any developer can see how it canbe done correctly, how it can be done efficiently on any platform.
It's not very complicate to create a CPU which sports different memory systems like DDR versus DDR2, any chipset can do it. Even the current CPU have to deal with different memories so it's quite possible the new CPUs already have this feature. So not supporting 939 is just a marketing and not a technical decision.
Before the 939 board I had 2 socket A boards, both had a 900MHz CPU now one has a 2GHz the other a 2.4GHz CPU. Then I had a socket 7 board which I upgraded a K7-II to a K7-III+ (450MHz). I don't remember the early Pentium CPUI's I had upgraded before.
Introducing a new socket (AM2) and not supporting the existing ones (939) after such a short period doesn't show much competence. I used to upgrade the CPU of any of my computer at least once during the life cycle of 4-6 years but that won't be possible with my 939 mainboard. That means at least one less CPU sell for AMD.
It will be tough for Debians to accept Ubuntu but there's no alternative. While Ubuntu has made the deb package format state of the art, it will also squash Debian out of the market. It's just a matter of time until Ubuntu will become the single most important distribution. So instead of cursing about this fact Debian developers should just go over to Ubuntu and accept it. It might not make everybody happy but that's normal in real live.
..."he considered this small group important enough to be worth more of his time than the 14,000 people who went to JavaOne"...
Im shocked,
Why are you shocked? Java has lost it's hype, isn't the only and not anymore the best solution for cross-platform and has never done anything for OpenSource. Mark did right when choosing a small but important group above some Java managers and their forced followers.
I guess you evaluated both toolkits but you have written real code only with QT. In my case I evaluated both and I have written real code only with wxWidgets, so take my bias into account.
I neither have enough QT practice to decide what's better. I've asked several QT people (including Trolltech and a leading KDE developer) to submit QT sample code for wyoGuide but so far nobody volunteered. I don't know why nobody did but it would be a nice sample for a comparison.
I agree that MFC message maps are ugly, but they are not obligatory, in fact I use none of them in my new wxCode. I have code like this in the constructors (or wherever is needed): Connect(ID_Add, wxEVT_COMMAND_BUTTON_CLICKED, wxCommandEventHandler(tparticles::OnAdd));
I don't care that much if they look ugly but I prefer to have all events concentrated in one place than to search for all "Connect" in the code.
And yes, the wxWidgets license is a GREAT advantage (one of the best licenses ever).
Yes, IMO for a cross-platform framework it's the only possible one. The LGPL is barely acceptable but the GPL isn't more useful than any closed source license.
So, my point is (for the guy with the problem): wxWidgets is a very good option (IMO much better than java if you have a C++ codebase) an you should evaluate it without any bias.
That's exactly my point as well, QT might be equally suitable, but wxWidgets is far better than any Java solution. Still one point I have to stress again, I've you want to build good cross-platform applications you have to conform to the wyoGuide guidelines. Only then can you develop on a single platform and more or less just move the code to other platforms. Only then becomes your application usable by ordinary users, only then will your application fit well with others.
As others have already asked, what environment you currently use is critical for any development strategy. Simply switching from C++ to Java will gain you nothing, what counts is what better framework you want to use. Since you only mentioned Windows I guess you just use plain MFC but since you also mentioned Java I guess you need to divert to a cross-platform solution.
In case your future environment has to produce binary applications you are IMHO best of if you switch to the wxWidgets framework (http://www.wxwidgets.org/). Since you already have C++ knowledge and wxWidgets is quite easy for Windows developer it shouldn't be a big problem to become familiar. I'm quite sure with wxWidgets you are equally efficient as with any Java framework but don't have the disavantages of Java.
You can use wxWidgets regardless of any platform consideration, if you just want to stick to Windows or to Linux or whatever, it doesn't matter. But if you also follow the guidelines of wyoGuide (http://wyoguide.sf.net/) you can move your code anytime to another supported platform and just release it. As long as you just use the features of wxWidgets there's no need to recode anything on other platforms ever.
If you want to see how well this approach works try out my samples (wyoEditor http://freshmeat.net/projects/wyoeditor/, wyoFiler http://freshmeat.net/projects/wyoeditor/) or look into Audacity. Or look out for the commercial application Xara. There's probably no alternatives for cross-platform development as if you do single-platform development as with wxWidgets/wyoGuide. And keep in mind, no Java disadvantages.
... Any or all of these might merge or die off or be made irrelevant at any time...
That's true but as long as you choose an OpenSource framework (I prefer Dojo) you can support it yourself at least long enough until you've converted all your code to a new framework. If you choose any proprietary framework (like Google's) even if it doesn't cost anything you don't have this way.
Sure anybody need good tools to produces something exceptional. But what can you do if the needed tools aren't available? What can developers do if they aren't happy with their tools or their environment?
For users the answer is easy, they simply switch to something different, but for developer it's not. You usually first have to get a lot of knowledge which needs time. But one does never get more time!
So developers have to think in advance sometimes several years. This means constantly be on the edge of the available knowledge. Tools can certainly help but nothing prevents you from getting the knowledge in advance.
Microsoft is welcomed to support cross-platform development (http://wyoguide.sf.net/) so OpenSource developers can easily port their applications to Windows but Microsoft may consider that cross-platform also works in the other direction so commercial vendors are able to port to Linux. Maybe this is a win-win solution for everybody;-)
Thank you for having enough insight to say "Wow, people aren't using this because it's somewhat difficult to use" and actually think about a solution, rather that bitching about the problem.
Thank you for voicing your agreement in public. It essential that as many people as possible knows this, to encourage anybody to work towards this goal. It's critical to start working now since development always takes its time.
Don't miss understand me, I'm not saying my way is the sole solution I only say I don't know any other and AFAIK nobody else does. I know the application's look&feel is the Achilles heel of the Linux desktop and much is lost because of this. So the minimum required action is the LXer article (http://lxer.com/module/newswire/view/54009/index. html) is discussed.
Even if you are only one of the user of Linux you could change the future of the Linux desktop. Just write to your friends and colleagues, to Slashdot, to your favorite Linux users group, to the developers of your favorite applications or who else you can think of. Only when wyoGuide gets known will people look at it, only when it's looked at people will see its advantages and its necessity. Only then will people start working towards its goal.
Sorry if this is redundant or feels like a flame, it's just I am glad that the parent was smart enough to point this out and felt like I needed to rally to him. Many Slashdot readers are jaded by the support that the anti-MS crowd gets here and they neglect to see things from a fairly obvious point of view, and it's very annoying to the rest of us.
Rallying is sometimes necessary, especially if it's about a seeming obvious point of view. It's huge work to create a usable Linux desktop and much effort is needed. It needs the help of many users who do all the advertisement and encouragement, many developers who spend their spare time, companies who support this effort. It's not an easy task and needs some time but it's doable.
I completely agree maybe since I'm a developer myself. I just built a new computer based on a Asus A8N-VM CMS (superb board), installed WindowsXP and set up my multiboot environment (XFDisk). Then I installed Ubuntu 5.10 except neither network nor graphic worked. At least the console mode was working. Okay then I tried Ubunto Dapper Beta which as a live CD works flawlessly but after installation the system didn't boot from the harddisk. So I now have to figure out why the older Ubuntu boots but not the newer. I guess the Grub boot loader is missing but still how could that happen?
I think the users just have to have the patience to go out there and find the multimedia programs.
Don't you wonder when someone rates the Linux desktop not fit for the switch because he could not find or work with the found applications? Isn't this article a clear sign which part of the Linux desktop needs our most attention? It's the application which counts most. Go and read this article at LXer.com http://lxer.com/module/newswire/view/54009/index.h tml.
I guess less than 10% of all the wordwide sold DVDs are also released in Flemish. Beside for Swiss dialects I think there aren't more than a handful. And selling DVDs isn't the same business as selling SW. Just look at the Mac which is beside the much better market than Linux, there's almost no third party SW around. Or look how difficult it is to get printer drivers even if the development costs are marginal. So any market share below 10% for Linux means it's insignificant for SW vendors.
So saying "we'll wait till you have a 10..20..30% marketshare is pure free floating horse shit.
Did I say wait? No, of course not.
Well if you think you have a better way for increasing Linux market share, just go and work for it.
The LXer article states "...to educate newcomers with respect to the importance of keeping software free" but people, especially customers, don't like to be educated of something they don't care. What would you think if the car seller wants to educate you that 60mph are more than sufficiant for any driving? Would you buy a car there or leave for another shop?
Get a market share above 10% and vendors with consider to release on Linux. Get a market share above 20% and vendors will release on Linux. Get a market share above 30% and vendors can't afford not to release on Linux!
How to get a higher market share? Fix the first top inhibitor of the Linux adoption (http://www.osdl.org/dtl/DTL_Survey_Report_Nov2005 .pdf). How to fix this inhibitor? One important action (IMHO the most important) is to declare the guidelines of wyoGuide (http://wyoguide.sf.net/) as the Linux application standard!
There might be other actions to fix this inhibitor but I don't know any. Just voice them here and now. But be sure unless this inhibitor isn't fix fast, the market share of Linux will stay low, too low for any significance.
IMHO it's essential that anybody (maybe O'Reilly) starts a Linux conference about this subject to discuss any possibility.
Slashdot Mirror
You seems to be a Windows fan, aren't you. Yes for Windows I'm a troll but other Slashdot readers seems to like this, else I wouldn't have gotten a Karma Excellent.
But instead getting personal I'll give you the chance to explain why you think wyoGuide is wrong or what is wrong. Just tell us all why you think the Picasso Wine implementation is better and Google should keep developing that way.
O. Wyss
I'm no expert, but to me, cross-platform development is taking a lowest common denominator approach...
4 08818
I think I am a cross-platform expert and I can assure you that cross-platform doesn't mean lower that native these days. Just look into wyoGuide (http://wyoguide.sf.net/) to find out how cross-platform development is done, in many cases it's even simpler than single-platform and less error prone.
See also http://slashdot.org/comments.pl?sid=186741&cid=15
O. Wyss
Doesn't Google employees read Slashdot? I've multiple times told what I think is the best way to develop software albeit other might think different. Yet probably everybody agrees that wyoGuide (http://wyoguide.sf.net/) is by far better than Wine. wyoGuide is IMHO the only way how to do cross-platform development and the only way for OpenSource and ClosedSource. It seems to me that it's exactly perfectly suited for Google.
On screenshots for a desktop usable by "everyone" ...
wyoGuide and wyoDesktop are two separate projects, one is about applications the other about a desktop. So far I spend almost all the time for wyoGuide which leaves nothing for wyoDesktop.
The other thing is that you may want to consider switching from wxWidgets or GTK+ or whatever you're using to Qt...
It's amazing that everytime I bring up wyoGuide a QT-Fan tells its story albeit no QT-Fan seems to be willing or able to provide sample code for QT. Why?
wyoGuide can be used with any framework and no preference of QT so there's no point in switching and definitely not as long as there isn't appropriate sample code.
O. Wyss
Sure, I'll see in about 2 years.
DDR2 has been known long enough to be considered when AMD designed socket 939. So they are either incompetent or cheaters. Either one annoys me so I probably don't stick with them any longer unless they are factors better.
Why do computer companies never understand to not annoy potential customers.
O. Wyss
Just by following a few simple common-sense guidelines, you can drastically improve the usability of any given software:
d =15399619. But the difference is you tell just common sence while I show how this common sense can be implemented into code. I invite you to look through the guideline and discover the points where common sense might be improved so at last we get better applications.
I just read your comment because of two reasons, first it just comes after mine and second because it's just about what I had in mind when I designed wyoGuide (see http://ask.slashdot.org/comments.pl?sid=186617&ci
O. Wyss
See http://wyoguide.sf.net/, it can be used with any programming language with any framework on any platform. So far it's the only guide which gives advice in a cross-platform fashion, has sample code and if you happen to use C++ a demo sample for use as your starting code base.
O. Wyss
Microsoft has a market share of above 90%? It's no wonder that computer illiterate people think it synonym with computer understanding. Most people don't see a computer as a gadget but as a tool which helps them doing their tasks. People want to write simple letters, sometimes a full resume or to look up some information or schedules in the internet or maybe get some music or play a game. People don't want to install a system or an application and they definitely don't want to work around annoyances and bugs. So as long as Microsoft cares for these people but none of the OpenSource developers, computer literacy is synonym with knowing Microsoft.
To counter this one way behavior I've created wyoGuide (http://wyoguide.sf.net/). It just shows to developers how to code their applications so all these people can use and like them. But it only makes a sense if developers make wyoGuide conformant applications and users ask for wyoGuide conformant applications.
O. Wyss
File Edit Blah Blah Blah Help
CTRL X
CTRL C
CTRL V
CTRL S
Well first of all OpenSource developers should code alike. Here http://wyoguide.sf.net/, any developer can see how it canbe done correctly, how it can be done efficiently on any platform.
O. Wyss
It's not very complicate to create a CPU which sports different memory systems like DDR versus DDR2, any chipset can do it. Even the current CPU have to deal with different memories so it's quite possible the new CPUs already have this feature. So not supporting 939 is just a marketing and not a technical decision.
O. Wyss
Before the 939 board I had 2 socket A boards, both had a 900MHz CPU now one has a 2GHz the other a 2.4GHz CPU. Then I had a socket 7 board which I upgraded a K7-II to a K7-III+ (450MHz). I don't remember the early Pentium CPUI's I had upgraded before.
O. Wyss
Introducing a new socket (AM2) and not supporting the existing ones (939) after such a short period doesn't show much competence. I used to upgrade the CPU of any of my computer at least once during the life cycle of 4-6 years but that won't be possible with my 939 mainboard. That means at least one less CPU sell for AMD.
O. Wyss
It will be tough for Debians to accept Ubuntu but there's no alternative. While Ubuntu has made the deb package format state of the art, it will also squash Debian out of the market. It's just a matter of time until Ubuntu will become the single most important distribution. So instead of cursing about this fact Debian developers should just go over to Ubuntu and accept it. It might not make everybody happy but that's normal in real live.
O. Wyss
..."he considered this small group important enough to be worth more of his time than the 14,000 people who went to JavaOne"...
Im shocked,
Why are you shocked? Java has lost it's hype, isn't the only and not anymore the best solution for cross-platform and has never done anything for OpenSource. Mark did right when choosing a small but important group above some Java managers and their forced followers.
O. Wyss
I guess you evaluated both toolkits but you have written real code only with QT. In my case I evaluated both and I have written real code only with wxWidgets, so take my bias into account.
I neither have enough QT practice to decide what's better. I've asked several QT people (including Trolltech and a leading KDE developer) to submit QT sample code for wyoGuide but so far nobody volunteered. I don't know why nobody did but it would be a nice sample for a comparison.
I agree that MFC message maps are ugly, but they are not obligatory, in fact I use none of them in my new wxCode. I have code like this in the constructors (or wherever is needed):
Connect(ID_Add, wxEVT_COMMAND_BUTTON_CLICKED, wxCommandEventHandler(tparticles::OnAdd));
I don't care that much if they look ugly but I prefer to have all events concentrated in one place than to search for all "Connect" in the code.
And yes, the wxWidgets license is a GREAT advantage (one of the best licenses ever).
Yes, IMO for a cross-platform framework it's the only possible one. The LGPL is barely acceptable but the GPL isn't more useful than any closed source license.
So, my point is (for the guy with the problem): wxWidgets is a very good option (IMO much better than java if you have a C++ codebase) an you should evaluate it without any bias.
That's exactly my point as well, QT might be equally suitable, but wxWidgets is far better than any Java solution. Still one point I have to stress again, I've you want to build good cross-platform applications you have to conform to the wyoGuide guidelines. Only then can you develop on a single platform and more or less just move the code to other platforms. Only then becomes your application usable by ordinary users, only then will your application fit well with others.
O. Wyss
As others have already asked, what environment you currently use is critical for any development strategy. Simply switching from C++ to Java will gain you nothing, what counts is what better framework you want to use. Since you only mentioned Windows I guess you just use plain MFC but since you also mentioned Java I guess you need to divert to a cross-platform solution.
In case your future environment has to produce binary applications you are IMHO best of if you switch to the wxWidgets framework (http://www.wxwidgets.org/). Since you already have C++ knowledge and wxWidgets is quite easy for Windows developer it shouldn't be a big problem to become familiar. I'm quite sure with wxWidgets you are equally efficient as with any Java framework but don't have the disavantages of Java.
You can use wxWidgets regardless of any platform consideration, if you just want to stick to Windows or to Linux or whatever, it doesn't matter. But if you also follow the guidelines of wyoGuide (http://wyoguide.sf.net/) you can move your code anytime to another supported platform and just release it. As long as you just use the features of wxWidgets there's no need to recode anything on other platforms ever.
If you want to see how well this approach works try out my samples (wyoEditor http://freshmeat.net/projects/wyoeditor/, wyoFiler http://freshmeat.net/projects/wyoeditor/) or look into Audacity. Or look out for the commercial application Xara. There's probably no alternatives for cross-platform development as if you do single-platform development as with wxWidgets/wyoGuide. And keep in mind, no Java disadvantages.
O. Wyss
... Any or all of these might merge or die off or be made irrelevant at any time...
That's true but as long as you choose an OpenSource framework (I prefer Dojo) you can support it yourself at least long enough until you've converted all your code to a new framework. If you choose any proprietary framework (like Google's) even if it doesn't cost anything you don't have this way.
O. Wyss
Sure anybody need good tools to produces something exceptional. But what can you do if the needed tools aren't available? What can developers do if they aren't happy with their tools or their environment?
For users the answer is easy, they simply switch to something different, but for developer it's not. You usually first have to get a lot of knowledge which needs time. But one does never get more time!
So developers have to think in advance sometimes several years. This means constantly be on the edge of the available knowledge. Tools can certainly help but nothing prevents you from getting the knowledge in advance.
O. Wyss
Microsoft is welcomed to support cross-platform development (http://wyoguide.sf.net/) so OpenSource developers can easily port their applications to Windows but Microsoft may consider that cross-platform also works in the other direction so commercial vendors are able to port to Linux. Maybe this is a win-win solution for everybody ;-)
O. Wyss
Thank you for having enough insight to say "Wow, people aren't using this because it's somewhat difficult to use" and actually think about a solution, rather that bitching about the problem.
. html) is discussed.
Thank you for voicing your agreement in public. It essential that as many people as possible knows this, to encourage anybody to work towards this goal. It's critical to start working now since development always takes its time.
Don't miss understand me, I'm not saying my way is the sole solution I only say I don't know any other and AFAIK nobody else does. I know the application's look&feel is the Achilles heel of the Linux desktop and much is lost because of this. So the minimum required action is the LXer article (http://lxer.com/module/newswire/view/54009/index
Even if you are only one of the user of Linux you could change the future of the Linux desktop. Just write to your friends and colleagues, to Slashdot, to your favorite Linux users group, to the developers of your favorite applications or who else you can think of. Only when wyoGuide gets known will people look at it, only when it's looked at people will see its advantages and its necessity. Only then will people start working towards its goal.
Sorry if this is redundant or feels like a flame, it's just I am glad that the parent was smart enough to point this out and felt like I needed to rally to him. Many Slashdot readers are jaded by the support that the anti-MS crowd gets here and they neglect to see things from a fairly obvious point of view, and it's very annoying to the rest of us.
Rallying is sometimes necessary, especially if it's about a seeming obvious point of view. It's huge work to create a usable Linux desktop and much effort is needed. It needs the help of many users who do all the advertisement and encouragement, many developers who spend their spare time, companies who support this effort. It's not an easy task and needs some time but it's doable.
O. Wyss
I completely agree maybe since I'm a developer myself. I just built a new computer based on a Asus A8N-VM CMS (superb board), installed WindowsXP and set up my multiboot environment (XFDisk). Then I installed Ubuntu 5.10 except neither network nor graphic worked. At least the console mode was working. Okay then I tried Ubunto Dapper Beta which as a live CD works flawlessly but after installation the system didn't boot from the harddisk. So I now have to figure out why the older Ubuntu boots but not the newer. I guess the Grub boot loader is missing but still how could that happen?
O. Wyss
I think the users just have to have the patience to go out there and find the multimedia programs.
h tml.
Don't you wonder when someone rates the Linux desktop not fit for the switch because he could not find or work with the found applications? Isn't this article a clear sign which part of the Linux desktop needs our most attention? It's the application which counts most. Go and read this article at LXer.com http://lxer.com/module/newswire/view/54009/index.
O. Wyss
I guess less than 10% of all the wordwide sold DVDs are also released in Flemish. Beside for Swiss dialects I think there aren't more than a handful. And selling DVDs isn't the same business as selling SW. Just look at the Mac which is beside the much better market than Linux, there's almost no third party SW around. Or look how difficult it is to get printer drivers even if the development costs are marginal. So any market share below 10% for Linux means it's insignificant for SW vendors.
So saying "we'll wait till you have a 10..20..30% marketshare is pure free floating horse shit.
Did I say wait? No, of course not.
Well if you think you have a better way for increasing Linux market share, just go and work for it.
O. Wyss
The LXer article states "...to educate newcomers with respect to the importance of keeping software free" but people, especially customers, don't like to be educated of something they don't care. What would you think if the car seller wants to educate you that 60mph are more than sufficiant for any driving? Would you buy a car there or leave for another shop?
h tml
O. Wyss
PS. See http://lxer.com/module/newswire/view/54009/index.
Get a market share above 10% and vendors with consider to release on Linux. Get a market share above 20% and vendors will release on Linux. Get a market share above 30% and vendors can't afford not to release on Linux!
5 .pdf). How to fix this inhibitor? One important action (IMHO the most important) is to declare the guidelines of wyoGuide (http://wyoguide.sf.net/) as the Linux application standard!
How to get a higher market share? Fix the first top inhibitor of the Linux adoption (http://www.osdl.org/dtl/DTL_Survey_Report_Nov200
There might be other actions to fix this inhibitor but I don't know any. Just voice them here and now. But be sure unless this inhibitor isn't fix fast, the market share of Linux will stay low, too low for any significance.
IMHO it's essential that anybody (maybe O'Reilly) starts a Linux conference about this subject to discuss any possibility.
O. Wyss