|
Authored by: Anonymous on Friday, May 25 2012 @ 05:44 PM EDT |
What's interesting is an author that writes about MS seems surprised at
this.
Perhaps that's an indication that a "microsoft guy" has had
sufficient exposure to other business models that he's begining to realize the
Microsoft "pay us to lock you in" behavior.
Open source development
is similarly disadvantaged. Consider a project such as the server-side
JavaScript platform Node.js. Node.js was originally developed for UNIX-like
platforms, but its developers have worked hard to make it a first-class citizen
on Windows (including some small contributions made by me).
Ahh...
so it seems he has been dabbling in the FLOSS ecosystem. Looks like he's just
getting his feet wet in the realm most of us are so familiar with:
Standard
Microsoft anti-competitive behavioral patterns.
RAS[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Friday, May 25 2012 @ 06:49 PM EDT |
Haven't done Winders in a long time, but don't remember Visual Studio as being
free... [ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Friday, May 25 2012 @ 07:53 PM EDT |
I have been developing software on the Windows
platform for 20 years,
since Windows 3.1 However, I have no enthusiasm
whatsoever to target
Windows 8. For most of my career, there was no free
compiler available,
and I have never used one. The first free version I
believe was VS2005,
and I don't think you could do GUI development with
it.
Complaining about lack of a free compiler for Windows
8 is a red
herring, when there are so many other things to
complain about.
Anyhow, Windows 8 will bomb, then Microsoft will
change it's mind.
I have no interest in supporting Windows 8 with my
talents and skills. I
will stick to Windows 7 for many years to come, like
most will, then look
around at all the options when it becomes time to
move on.[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Saturday, May 26 2012 @ 01:55 AM EDT |
While this might be "bad" from the perspective of people who want to
learn to use Microsoft's tool chain, it's not really that big a deal from the
perspective of open source development. Just use an open source compiler that
has been ported to MS Windows. Simples.
To use Python as an example, they do use the Microsoft compiler for their MS
Windows versions. That is for the convenience of users writing custom C
extensions who want to use MS Visual Studio to write the extensions. If this
becomes a real problem for the users, then the Python developers could simply
drop the use of the Microsoft compiler and use GCC for all versions. If
anything, this would actually make life easier for Python developers as it would
eliminate the need to support two different compilers. Most Python programmers
don't write C extensions, so they wouldn't notice the difference anyway.
If any response is required from the open source world, it would be to make it
easier to set up a working build system for GCC on MS Windows.
To re-iterate, the problem here is for people who want to use proprietary
software. Depending on Microsoft being willing to give away a version of their
products is foolish. [ Reply to This | Parent | # ]
|
|
Authored by: tiger99 on Saturday, May 26 2012 @ 05:10 AM EDT |
Fewer free tools means fewer developers, which means fewer apps, which means
less compulsion to use Windoze, which will accelerate the decline of M$,
which is immensely good. Looks like, having used it extensively, Ellison has
sold the Footgun™® to Ballmer. [ Reply to This | Parent | # ]
|
|
|
|
|