Microsoft Sponsors Apache Software Foundation
gbjbaanb writes "Ars Technica reports that Microsoft is to sponsor the Apache Foundation to the tune of $100k. From the article: 'I asked him if this could possibly be the beginning of a broader initiative by Microsoft to increase Apache compatibility with .NET web development technologies, but he says it's still too early to guess Microsoft's future plans for Apache participation. ... He doesn't anticipate a confrontational response from the developers working on individual Apache projects ... The response of the broader open source software community, however, is harder to predict.' (In related news, MS also intends to participate in the RubySpec project.)"
p0st
--pyro_dude
Would, "It's a trap", be too cliche?
A better sponsorship would be to quit developing IIS and focus all of its development staff on Apache for Windows, and Apache in general. Apache already dominates, make it better.
Colin Dean Go a year without DRM
Could it be that they would like to quit supporting IIS? Make Apache do the dirty webserver stuff, but keep all the content creation in a dll or something. Maybe the 100k is for working on Windows API's and such?
That is the only logical conclusion, as nobody just gives money to the competitor. Right?
No comprende? Let me type that a little slower for you...
Okay, I have to admit this confuses me. There are a lot of possibilities where MS could make investments or try to push markets, but this seems business backwards. I can't tell if it is a magic trick or the real thing.
And for the subject reference:
A magician works on a cruise ship and entertains the audience with his show. The only problem is that the captainâ(TM)s parrot has figured out all his tricks and tells them during the show. âoeAaarrr, itâ(TM)s in his sleeve, itâ(TM)s in his sleeve, Aaarrrâ âoeAaarrr, itâ(TM)s under his hat, itâ(TM)s under his hat, Aaarrrâ
One night the parrot starts again to tell trick. The magician pulls out a gun and shoots at the parrot. The parrot dodged the bullet; it hit a propane tank and blew the ship into a million pieces. The only two survivors are the magician and the parrot floating on a piece of wood in the middle of the ocean.
The parrot looks around, looks at the magician and say: âoeAaarrr, ok, you got me. Where is the ship?â
B) Eliminate all the stupid users. This is frowned upon by society.
Based on Ballmers history, I'd say this is inroads by which to "divide and conquer". So; with the check, what was on the document saying what they wanted in return. Microsoft never gives anything away and usually takes everything it wants?
All content in this message is copyright (c) 2008. All rights reserved. RIAA is prohibited here.
Embrace
to see Microsoft embracing Apache, oh no, wait a minute I know how this is going ....
Apache 2.4 release notes
new modules:
mod_drm
mod_ooxml
mod_reject-firefox
take this with an Everest sized pile of salt!
GENERATION 24: The first time you see this, copy it into your sig on any forum and add 1 to the generation. Social exper
Steve Ballmer is either:
1) Trying to appear more "open" (what with all the lawsuits in Europe & the oh-so-enthusiastic reception of OOXML), so they can have more influence in the real standards body.
2) Simply trying that old trick (to pretend suck up to developers) & then turn around & do something else.
Eitherway, its a PR stunt because it's hard to believe Microsoft wants to change its definition of "industry standards" from "something we came up with" to---wait for it---"industry standards". Unless I'm missing something
Suspicious, wary.
and rightly so too. look at what happened to all those who got affiliated with microsoft in any way.
microsoft has huge negative karma to alleviate.
Read radical news here
pls. you know its very funny, even if youre a microsoft fanboi.
Read radical news here
See this warning about divide and conquer. M$ has not brought much to the table. In return their marketing department is going to pretend there is community support for OOXML and other proprietary formats.
The broader M$ goal is to have people pay M$ if they want to use free software. They want you to use Windoze and taxed versions of GNU/Linux. Until they shut up about patents it is best to have nothing to do with them.
Friends don't help friends install M$ junk.
Apache has sold out. We must fork their code now and abandon their Microsoft-backed versions, no matter what the cost. Look at what Microsoft did to Novell and openSUSE - the same thing is going to happen to Apache. Tell everyone you know to stop using Microsoft-backed products. Friends don't let friends use Apache.
He believes that this move is based on a legitimate desire by Microsoft to foster collaborative development of Apache technologies that implement Microsoft standards.
If that's true, then we have a grave situation. M$ can make apache compatible with M$'s home-grown standards and then claim that the standards themselves are open standards. Since the percentage of IT people who mistake an open-source implementation as an open standard is almost 100%, M$ can even be very successful at this. Since the standards themselves are not open, all web servers, except Apache and M$-IIS, will soon die out. Finally M$ withdraws support for Apache and thus giving it a final blow. Now M$-IIS becomes the king. I know that I'm sounding like a conspiracy theorist. But we have seen enough instances of this Embrace-Extend-Extinguish policy.
The largest prime factor of my UID is 263267.
All your software are belong to us
Microsoft may have a different perspective based on their judgement of the enviroment, and whether it's a Zero-Sum Game or not.
Non Zero-Sum Game = contribute to everyone; grow entire pie; so your own little percentage yields a high profit.
Zero-Sum Game = control hardware, software, and even services; shrink entire pie; so that you own a large piece that yields more profit relative to others' profit.
If you believe contributing to Appache would be good for everyone, and hence good for you, then you support them. (Google, Microsoft, Yahoo)
If you believe contributing to Appache would be good for everyone, and hence not good for you, then you don't support them. (Apple)
Q: What do you get when you cross Microsoft and Apache?
A: Microsoft.
I really wouldn't mind having better ASP support on Apache (that doesn't hurt anyone), but this talk about "interoperability" between Microsoft and the ASF just brings back into my memory what happened to Novell.
/HAS/ (triple emphasis!) to keep their usual levels of strictness when it comes to outside contributors, specially Microsoft in this case.
The Apache Software Foundation
I hope they don't let their guard down. I'm quite concerned, honestly. I do have some hope that the ASF will handle this properly, and not let such a great project succumb to Corporate America.
When I heard about this at OSCON, I had the same disbelief as anyone on slashdot. But then I thought.. what if it's true? What if MSFT isn't going to fold up and die a relic of the days of propriatry software? I wanted to see that, and I'm sure I'm not alone. But they have new management and can see how the software world is shifting just like everyone else. The "enemy" might be infected with "good", and we might get a powerful new ally instead of a vanquished foe. (What if this happend to the MPAA?)
But for now, I'm going to watch out for boar aviators and do what I can to slow the pace of infernal cooling.
M$ has not brought much to the table. In return their marketing department is going to pretend there is community support for OOXML and other proprietary formats.
thats probably the thing they are going for.
Read radical news here
So why will their investors support this move?
Twinstiq, game news
A lot of us like permissions better than "Read, Write, Execute". Also, ACLs without dynamic inheritance are a nightmare waiting to happen. And lastly, userspace support for ACLs is still woeful on *nix - while getfacl/setfacl work well enough, GUI support is poor, archiver support is thin at best and many end-user apps still think it's OK to meddle with your permissions and inevitably screw it up because they only copy your permissions, not your ACLs (this happens more than you might expect, even word processors do it).
I strongly advise not using ACLs on Linux unless you're really sure they're the only option you have to get the results you want (and then make sure your intended results are worth the penalty). On Windows, use them as much as possible because runas is a piss-poor substitute for su/sudo.
Incidentally, this is the same reason you shouldn't use symlinks (junctions) on Windows unless you're really sure. While it's technically supported at the low level, the upper levels are basically oblivious and will carry on as though they were normal files and therefore fuck your system up one way or another (such as getting lost in a loop, backing up the same files multiple times, crossing filesystems, etc.).
Opportunity knocks. Karma hunts you down.
Apache is dying. Seriously, I'm considering dumping Apache in the future. It's a matter about trust. I simply cannot trust MS.