Microsoft Releases WTL To SourceForge

prostoalex writes "Microsoft's WTL (Windows Template Library) toolkit source code has been released to SourceForge.net [also part of OSDN, like Slashdot.] InternetNews explains that the toolkit allows a Windows developer to create quick GUIs in C++. According to the project page, WTL extends ATL (Active Template Library) and provides a set of classes for controls, dialogs, frame windows, GDI objects, and more. WTL is licensed under CPL, which is the license Microsoft chose for the SourceForge release of the WiX installer."

Comments

Interesting Observation

[RucasRiot]

Microsoft denounces OS yet they contribute... Odd.

Re:Interesting Observation

[LostCluster]

Microsoft denounces OS yet they contribute... Odd.

If they can't kill it, then they have to resort to "embrace and extend"...

Re:Interesting Observation

[LBArrettAnderson]

they may have opened the source, but it is not anywhere near what you OSS developers like.

they will almost certainly NOT accept source from other people; (although they may take suggestions, i'm sure).

the purpose of this is not to make their product better by allowing the community to help, but rather to allow people to customize their own toolkits or to at least better understand what they're using.

Re:Interesting Observation

[dasmegabyte]

Microsoft denounces Linux, which is a competing operating system. They don't necessarily denounce open source software in general (at least, not that I've heard of.) That would be sort of foolish...I mean, you have to denounce a rival's products, that's obvious. But to denounce the way he makes them when other world class software vendors are considering them would be shooting yourself in the foot.

Re:Interesting Observation

[leshert]

Yes, it does. Unlike Sun, Microsoft chose an existing OSDN-approved license.

It's the same license, for example, that Eclipse uses.

Re:Interesting Observation

[lkaos]

they will almost certainly NOT accept source from other people; (although they may take suggestions, i'm sure).

That doesn't matter. It's out there now. You are free to take it, re-release it as OpenWTL, and make all the changes you want. This is the beauty of Open Source. The community now has equal say in the future of this code as Microsoft does.

If they never touched this project again, that would be fine. All they're obligated to do is release the code once. As long as they keep releasing their changes, they are doing well.

Open Source works because people contribute what they want/need. That's all Microsoft has to do to be a good member of the community (yes, Microsoft *can* become a good member of the community).

In fact, I'll go as far as this, Microsoft has submitted to codebases to the community now. How many people can stand up here and claim to have submitted more than Microsoft has? In many ways, Microsoft is a better member of the community than a lot of people reading this right now.

Kind of crazy eh?

Re:Interesting Observation

[Frizzle Fry]

The "OSS is an insecure virus" campaign

Did they really claim this? I'm too lazy to dig up old articles, but I thought the objection was to the GPL in particular. And for projects like this, they are specifically avoiding the GPL, which is consistent with their earlier claims.

Re:Interesting Observation

[Dalcius]

I agree.

But remember, after years of dealing with what we feel is a horrible interface and being strongarmed into this and that, and let down by focus on money and not product, we have a very strong right to be skeptical about anything that Microsoft does.

To this point in Microsoft's history, they have done NOTHING that I can think of out of the kindness of their hearts. Everything can be written up as enough to get by with as much money as they can take from customers and carry to the bank.

A little too much MS bashing? Sure. A lot of misfounded MS bashing? Yup. A little too serious of an attitude towards MS? Oh yeah. But with that said, MS deserves a lot of skepticism and concern and if you want to avoid skepticism and concern (which isn't what you said, don't mean to put words in your mouth) I humbly suggest that you avoid websites filled with people who ran screaming from the Microsoft house.

Cheers :)

Re:Interesting Observation

[Ryosen]

I wouldn't be so gung-ho for Microsoft to jump into the OSS foray.

An alternate scenario:

1) Slowly, start testing the waters of the OSS community by offering up small, insignificant components.
2) Build support and confidence within the OSS community
3) Maintain your market share and increase your ability to push against your rivals (notably *nix/BSD)

They don't need to embrace and extend. They don't need to play games with licensing. They simply have to maintain market dominance on their three main products: Windows desktop, Windows server, and Office.

And please, let us not forget that there is a *huge* amount of OSS developers who are Windows-centric. They would absolutely love to be able to get their hands into MS's pie and contribute to the Windows component base.

The best thing that MS could do, from a competitive viewpoint, would be to GPL a bunch of their products. They would increase their workforce by such an order of magnitude (and for little to no cost) so as to make *nix's head spin.

Re:Interesting Observation

[Dalcius]

I'm in complete agreement with what you said. I was merely attempting to point out that Microsoft cannot kill "OSS" as a concept, technique, philosophy, whathaveyou.

What you're describing falls into the "Microsoft creates a good operating system" alternative. I honestly think it could and probably will happen once Linux eats up a little more marketshare. Microsoft is known for adapting, albeit often late, to stay alive and I think OSS will eventually become at least some part of Microsoft's daily life.

It will take time before they grow up, but it will eventually happen or the monopoly will fall. History doesn't repeat itself, but it does rhyme (Mark Twain?).

Cheers

Re:Interesting Observation

[CaptainFrito]

Well, for me, I'm sick of dumbing down my own products because of the predominance of their flawed systems. Yeah, okay, we've all heard it before. So what. We hear of murder and robbery and rape everyday too. Doesn't mean it shouldn't be spoken of each time.

Microsoft gets what it deserves. They are sneaky and underhanded.There is nothing about there actions that should be seen as anything but a cleverly veiled continuation of their need to dominate the world. Is that extreme? Probably -- maybe -- but the true danger is underestimating people like this. And if you don't think that people with the kind of money that these people have -- personally and corporately -- does not influence everything you do, then you have not yet reached adulthood.

Who knows why they are making this particular move. Maybe OSS coders are the only ones cheaper than subcontinent Asians. Maybe they don't want to have to buy out the next GUI design company. One thing's for sure though: This latest move is but another tactic in a blizzard of tactics supporting a neverchanging strategy. It's pure sleight of hand. It never pays to underestimate your foe. And it never hurts to overestimate them.

Momma always said, "never trust anyone that says 'Trust me.'"

Re:Interesting Observation

[JPriest]

There is the "Bill & Melinda Gates Foundation" and the "Microsoft charity licence" but exactly what kind act would you like to see from MS?

Re:Interesting Observation

[zerocool^]

To this point in Microsoft's history, they have done NOTHING that I can think of out of the kindness of their hearts. Everything can be written up as enough to get by with as much money as they can take from customers and carry to the bank.

I can think of two things:

1.) Supporting a $100 O.S. for 6 years with official updates and patches. Quite a deal, one that you certainly won't see from redhat.

2.) Allowing pirated copies of windows XP to install service pack 2. A clip from the article: "Microsoft group product manager Barry Goffe told ComputerTimes that [...] it was more important to keep user safe than to be 'concerned about the revenue issue.'"

~Will

Re:Interesting Observation

[justin_speers]

I can't let this post slide, insightful???

But remember, after years of dealing with what we feel is a horrible interface and being strongarmed into this and that, and let down by focus on money and not product, we have a very strong right to be skeptical about anything that Microsoft does.

Common misconception amongst everyone in the open source movement, or just anti-MS zealots in general. If Microsoft is focused on making money, they are focused on their products. They cannot, at gunpoint, force consumers to purchase their products. In order to make money, they must provide a product that appeals to the largest number of people possible. That is focusing on the product. While it may not be technically superior or as stable as other OS's (Linux, Mac OS X, name it), it still does what most people want while the other operating systems don't. That is why those OS's don't have the market share. While I think Linux's technical superiority will allow it to catch up, to say Microsoft is blatantly trying to create a crappy product in order to make more money is, at best, bizarre logic.

To this point in Microsoft's history, they have done NOTHING that I can think of out of the kindness of their hearts.

What exactly are you talking about? Are they supposed to buy everyone a teddy bear?

Microsoft made computing mainstream and gives most consumers exactly what they want. Isn't that kind enough? They're a business, what else are they supposed to do? If they weren't providing a benefit of some kind to people, they would not make money, and therefore would not exist.

Everything can be written up as enough to get by with as much money as they can take from customers and carry to the bank.

And still customers HAVE THAT OPTION. No one is threatening them at gunpoint. They are voluntarily handing over their money, Bill Gates is not mugging them.

A little too much MS bashing? Sure. A lot of misfounded MS bashing? Yup.

Couldn't agree more.

Only on /. can Microsoft contribute a product to sourceforge and be bashed for it. As long as Bill Gates isn't using all of his money to buy all the slashdot virgins blowjobs from Carmen Electra, they can't do anything right.

Re:Interesting Observation

[Roark Meets Dent]

I call bullshit on #2. They pretend they are concerned about protecting the users, but the fact of the matter is there are a LOT of CRITICAL security updates now needed just to get a virgin XP install to be able to be on the net safely. An unpatched system is a threat to the general public, and MS rightly realizes they have an obligation to correct these weaknesses in their own software to procet the public, regardless of whether an individual OS installation is licensed or not. If they withheld the patches they would very likely be exposing themselves to serious liability issues.

Re:Interesting Observation

[slycer9]

If he isn't buying /.'ers blowjobs from Carmen Elektra, who IS he buying them for?

Does this mean I should have BOUGHT WindowsXP???

Re:Interesting Observation

[mcrbids]

And still customers HAVE THAT OPTION. No one is threatening them at gunpoint. They are voluntarily handing over their money, Bill Gates is not mugging them.

You had me going until this point. I recently bought a Dell Inspiron 600m laptop. I bought this particular laptop because it had high marks for Linux compatability.

I could not get this laptop without some flavor of Windows XP. Nothing on the packaging indicated that I could return the O/S - the Windows XP product license sticker was even stuck to the bottom of the laptop when opening the box!

So, where's my option for Billy boy? I had no option - either I bought the system with the O/S, or I did not buy a system I needed.

This is where the antitrust trial had a case - a case they won and then botched badly.

As long as Bill Gates isn't using all of his money to buy all the slashdot virgins blowjobs from Carmen Electra, they can't do anything right.

...and there went your credibility.

Re:Interesting Observation

[flacco]

To this point in Microsoft's history, they have done NOTHING that I can think of out of the kindness of their hearts.

i couldn't give a rat-fuck whether or not they do something out of kindness. i DO care about the awful things they're doing in order to maintain their stifling monopoly, including perverting standards, underhanded business deals, attacks-by-proxy on F/OSS, and locking consumers who are too stupid to know any better into proprietary technology.

Re:Interesting Observation

[ThaReetLad]

I think the why is quite obvious. It is in the interests of microsoft to have people develop software for their OS, and if that means giving away free source code and wizards to help people do that then thats fine. Of course, most windows developers already have a copy of VS and thus ALT, WTL MFC etc. The major advantage to a software developer is being able to know that you have the latest, bug fixed version of this toolkit, and that we now have a clear route for submitting bug reports direct to the dev team.

Of course, WTL has never really been a product, so much as a development framework, and the licence has always been pretty open so thats not a really dramatic step, but unlike the Wix thing this is actually really useful and we've (my dev group) already learnt that there are fixes and changes in this version of WTL that we didn't know about, so thats pretty cool.

Kudos to Microsoft on this one I think.

Re:Interesting Observation

[gbjbaanb]

But remember, after years of dealing with what we feel is a horrible interface

Yeah, but Microsoft had nothing to do with Gnome. :)

Re: Interesting Observation

[gidds]

It's worse than that, and much more self-interested.

Someone who can't install vital service packs has three choices: keep using it unpatched, buy a legal copy, or switch to something else. M$ desperately wants to stop people cold-turkeying themselves off their software, and I'm sure the service pack is partly to prevent that.

Re:Interesting Observation

[jaguarul]

If I recall correcly, WTL was never a Microsoft product. Nor is their name mentioned anywhere on the sourceforge site. WTL has been provided on the Platform SDK as an example, or something like that. It is the result of mainly one person (nenad) who, encoureged by the quick adoption by a lot of developers, continued to develop it. He is a Microsoft employee though, so he probabily needed some kind of "approval" from MS for this move, but I don't think it denotes anything more from MS's part.

Re:Interesting Observation

[EvilAlien]

You can't reason with them. Anti-Microsoft bigotry is as irrational as any other prejudice. It is in vogue to criticize companyies that are very successful at what they do, just as those who excel at FPS games get branded as "Cheater", those who do very well in school are "nerds", and those who aren't afraid to communicate with their bosses are "kiss-asses".

The blatant and awful mistakes that Microsoft makes and the people who can't recognize good behavior from the object of their prejudice all are explained by the Stupid People Theory. Whenever you are trying to figure out why people do what they do, refer to the Theory. Its a really simple Theory, so I won't bother explaining it ;)

Re:Interesting Observation

[devnull17]

This is indeed mostly attributable to Microsoft.

It's pretty well-known that electronics hardware manufacturers of all kinds (including PC OEM's) operate on razor-thin margins. Because of this, most of the profit on computer systems comes from markup on the bundled OS.

Microsoft offers copies of Windows to members of its OEM program at a very deep discount. Without this discount, manufacturers would find it very difficult to remain competitive on price. Naturally, MS is very aware of the amount of control over OEM's that this puts in their hands, and they use it liberally. (coughabuse of monopoly powercough) If you piss off Microsoft, you risk being dropped from their partner program, at which point you're basically dead. That's why you see so few Linux desktops from major manufacturers--they're scared shitless of Microsoft.

So, yeah, Dell might be the one forcing you to accept a copy of WinXP with your computer, but it's really Microsoft's fault. The fact that these circumstances do not apply to any other OS developer is exactly what makes MS a monopoly in the first place.

Don't feel bad, though. If you weren't paying for an OEM copy of XP, your hardware costs would probably increase significantly anyway, since OEM's need to make money somewhere. So I guess it's a wash.

So, how long until...

[Anonymous Coward]

Microsoft buys OSDN (and Sourceforge, Slashdot, etc)?

Re:So, how long until...

[Paul d'Aoust]

I think it's bizarre myself. They're kinda throwing away their advertising money by buying spots on OSDN. Let's see, we've got four different groups here:

1. Open source enthusiasts and developers, who are very dedicated to Linux or FreeBSD or what-have-you
2. Linux zealots who are fanatically dedicated to Linux
3. Platform-agnostic IT folks who use Linux, Windows, Mac OS, or maybe even DOS depending on what works best for them
4. Tech-heads who come here for information and opinion on the world of science and technology

I think that (correct me if I'm wrong) the vast majority of Slashdot readers and posters fall into the first two categories. And they're already baptised members of the open-source community, so they're not giving up the faith. The rest, who fall into the last two categories, certainly have an open mind towards Linux and are usually pretty sceptical of advertising in general.

Re:So, how long until...

[Fnkmaster]

I think you are sorely mistaken. I'd say "open source enthusiasts", or more accurately, hobbyists, make up a lot of folks on Slashdot. More people than not around here have installed a Linux distro, may have an old box they use as a Linux server or occasional desktop machine, or use some Unix flavors at work. But a lot fewer than the majority here never use Windows - I don't know the exact numbers, but I know Rob Malda has stated that the majority of page views are from Windows boxes, and I know that when I've had links in top comments and stories from Slashdot, I've seen the traffic patterns - sure, there are a lot more Linux users than the average stream of web traffic, but it's more like 10-15%.

Lots of people around here write software for a living, not just as a hobby. Unless you write web software, embedded software or other niche software, it's safe to say that you have to worry about people buying and using the software you write, which means using Windows. No, I'd say the fact that MS buys ads on OSDN indicates they understand the audience on Slashdot fairly well and in fact they want to be associated in these developers minds with the positive aspects of the Open Source community.

Anyway, I am an active Slashdot poster, and I know a fair number of other active Slashdot posters, and as far as I know, relatively few of them can say they exclusively use Linux, FreeBSD, or other Free/Open Source operating systems. I don't know if I would call myself "platform agnostic" - I'm not a zealot, and I recognize the strengths and weaknesses of Linux and Windows, but when it comes down to it, I need people to buy my software, and ignoring that fact is a fast road to being broke.

Hurry up and post, pundits

[drinkypoo]

I can't wait to find out how microsoft is screwing me today (tm).

license

[Coneasfast]

for some reason, i don't think it's a coincidence that both their sf projects are under a non GPL-compatible license.

Re:license

[sfraggle]

The ironic thing is that the CPL is almost identical to the GPL in its features (the CPL has some patent clauses which the FSF are thinking of incorporating into the next version of the GPL), including copyleft which Microsoft has been so vocal in opposing in the past.

Re:license

[0x0d0a]

Microsoft doesn't have a problem with open source per se. The GPL, however, is a threat, because it attacks two points (closed source and patents) that they use to prevent competention from popping up and going after their market. If they use GPL code, they lose a good chunk of what keeps them king of the market. They love the BSD license, because it gives them goodies for free (and they don't have to do anything in return).

Producing software that is open source but not GPL-compatible helps fragment the opne-source world and weaken the GPL (unlike the BSD license, which is different from the GPL but compatible with it).

Re:license

[lkaos]

But from that quick glance, the CPL is less "Free".

Woah. Hold your horses there pal. Quotith gnu.org:

This is a free software license but it is incompatible with the GPL.

The Common Public License is incompatible with the GPL because it has various specific requirements that are not in the GPL.

For example, it requires certain patent licenses be given that the GPL does not require. (We don't think those patent license requirements are inherently a bad idea, but nonetheless they are incompatible with the GNU GPL.)

So the FSF simply states that the CPL has extra clauses that aren't necessarily bad. The FSF is *not* shy about saying something is bad when they think it is. Fact is there are a lot of non-GPL compatible licenses out there. This is not like saying the CPL is OSI approved, but not FSF approved.

I know some of the people that worked on developing the IPL (the predecessor to the CPL). They worked very hard to make a license that would be acceptable to the community. The GPL is vague on patents. Unfortunately in the corporate world, you need to be more specific.

I applaud Microsoft for using the CPL. Keep in mind, the LGPL cannot be used with C++ code without a special clause (see libstdc++ in GCC for more info on this).

Uh-oh

[agent dero]

Guys, i'm scared, really scared.

I mean, do I download it? Do I use it? Do I trust it?

All of a sudden nothing makes sense anymore!

Glad to see MS releasing so much code

[Anonymous Coward]

First Windows 2000, now this.

What now, Slashdot?

[Anonymous Coward]

Oh the angst! Thousands of geeks struggle valiantly for a way to spin this so as to make Microsoft's release of this software for free look bad... hmmm... criticize the license terms? chant "embrace and extend"?

Oh, fuck it.

"Bill gate is a poopyhead, neener neener neener!"

It's about damned time.

[leshert]

WTL has been a bit of an embarrassment for Microsoft.

It started life as an MSDN sample app, but (to the surprise of everyone), people started actually using it. It fits nicely between the niches of MFC and ATL, supports a nice big chunk of what you need to do to get a desktop app running, and does it in a very clean, STL-friendly way. I read in an interview that some folks at MS thought it was a major mistake to release it; fortunately for them (at the time) it was pretty obscure.

There's some history of WTL at WikiWiki.

I remember way back then there were a couple of calls for Microsoft to "give it away" (in terms of control, not price--it's always been gratis), but I suppose the time hasn't been politically right within Microsoft until the recent popularity of their installer program release.

Re:It's about damned time.

[leshert]

Except that those meetings undoubtedly predated .NET. :-)

I agree--had WTL been released before MFC, or even after MFC but before 32-bit Windows, I think it would be the dominant paradigm on the Windows desktop.

But Microsoft really didn't have any incentive at all to market it, and putting it into MSDN was as good an idea (at the time) as any.

Given that Open Source is the latest business world rage, and they no longer have a huge need to prevent it from fragmenting their MFC developer base, this is a smart move (with near-zero cost) for them now, too.

Anyone who is willing to dump MFC for a better thing, and has their eyes on the future, is likely to head .NET-ward anyway.

On the bridge of the USS Linux

[Progman3K]

Sulu: Captain, it's the Borg, again. they want us to integrate their technology.

Spock: Captain, I expect they are doing this so they can still feel relevant in the future open-source, linux-dominated software world.

Kirk: Mr Sulu, set phasers to "ignore"

Sulu: Aye, Captain.

Re:On the bridge of the USS Linux

[Progman3K]

You're wrong.

My goal in switching to Linux wasn't to destroy Microsoft.

Hard to believe as you may find it, it was to become LEGIT!

There's no way I can afford to shell out for something like Windows XP every couple of years.

And now, everything I run is legit. And free. Can't forget about the freedom.

This is great news

[timecop]

WTL, which is basically a one-person project at microsoft, doesn't really get enough attention of developers.
It's a great lightweight wrapper around Win32 API, does not depend on any external DLLs (like MFC etc).
The only problem with WTL, up to including this release, is that there is absolutely no documentation - there
are a few projects documenting WTL3.0 or older exist, but they are not maintained anymore. Hopefully once this
project is on sourceforge, people will be fixing bugs *and* writing documentation. I'm very looking forward
to this.

WTL Rocks

[wandazulu]

The WTL proves that there are some *very* good people at MS: They basically took MFC and redesigned it around templates and the STL; no MFC runtime dlls and even VC6 produces tiny exes that run wickedly fast. They even wrote a VC6/7 addin so you can use the project wizard to create a boilerplate project as a starting point. And to top it off, the two developers were (are?) very active on the ATL mailing list and responded to questions/complaints/bug reports. Way to go guys!

That all said, Microsoft did practically everything they could to squash this project; it was originally installed as an "oh, by the way" in their SDK package (and not enabled by default...you had to go hunting for it) and then they removed it entirely. Official communcations always seemed to revolve around the message that "We acknowledge that it exists, we would prefer you not use it, and no we're not going to tell you why." I guess they had some fear that everyone was going to dump the millions of lines of existing MFC code for much better written code that ... has the same interface. Go figure.

Trust me from one who has used this library in apps that reached production: this is a true gem amist all the cubic zirconia that MS puts out.

Well... hm....

[paroneayea]

Interesting.... especially considering this article of past. Let me just pull off the summary from the article itself... it sums it up pretty well...

Microsoft lawyers have joined the company's campaign against open-source software, restricting how developers may use what it terms "viral software" in connection with Microsoft programming tools.

So... uh... yeah. What the heck?

always open source!

[dudifeuer]

WTL was always open source. It was distributed as a bunch of header files (along with some sample apps and visual studio wizards). The big test here will be if Nenad will accept (direct) contributions from the community, or whether the community will keep track of bugs and document stuff while Nenad will code.

Nenad is amazing and has really been the core developer of the project (he is now the project admin at sourceforge), but it will be interesting to see the OSS process at work here.

Microsoft + Sourceforge =

[imidazole2]

Microsoft + Sourceforge = The End Of The World

Re:Errata

[raehl]

chicks dig coders!

Well now we KNOW you're lying.

Re:WTL for stand-alone executables

[DrXym]

The learning curve for MFC is high too. If it weren't for the wizards, you would have to write the swathes of code just to do something simple. WTL is no worse, and the consensus from anyone who has used MFC in anger is what a baroque piece of junk it really is. It's like a dogshit covered icing and marzipan - superficially tempting but take a deep bite and see how much you like it.

Really. MFC works okay if you want stay on the path, but get off the beaten track a bit - say to implement something in OLE like an OLE message filter - and it becomes a nightmare. Half the methods are not virtual compelling you to cut and paste whole classes to change a few lines. I've literally copied huge chunks of MFC to change a function that I could not override.

And MS in their wisdom have tried to merge MFC & ATL into atlmfc with duplicate classes galore. Now they're trashing ATL by deprecating some of the tried and trusted conventions such as object maps in favour of meta info that ties ATL tightly to VC++7.x. Still, ATL is fast and produces very tight code compared to MFC.

WTL works much like ATL, and neither is particularly hard to learn assuming you've seen any STL, MFC, wxWindows etc. in your life.

Interestingly, no one has pointed out that WTL depends on ATL. The CPL'd WTL depends on the proprietary ATL. So its use is rather limited. It would be great to see MS open up MFC, ATL and WTL since it would make porting apps to Wine a lot easier. Perhaps that's why it is unlikely to ever happen.

Good on you MS (NOT)

[jonwil]

The bad thing is that this library is visual C++ only (by virtue of the fact that ATL is required and that ATL is visual C++ only)

Also, this is the exact same code that was available from MS for WTL before, its just a change of licence to the CPL

Unless microsoft opens ATL to the world also, this doesnt help anyone developing on non-MS compilers

Personally, I think they could gain a LOT of PR by open-sourcing more stuff.
Specificly, releasing (under the CPL for example) more code which is not important to M$ money making machine.

For example, open sourcing their C Runtime (the source code does come with Visual C++ but its missing some bits that only come in binary form)
Or open source the Active Template Library or MFC.
Or "open-source" the Platform SDK (i.e. all the headers and libraries)

Although I suspect that Open Sourcing things like CRT, ATL or MFC would probobly hurt MS since people would be able to use instead of to develop for those libaries.

On the other hand, there is no reason why someone cant come up with a free version of ATL or MFC or whatever that matches the published interface (there are already at least 2 free versions of the MSVCRT.DLL file, unsure exactly how complete they are, there are also free versions of the headers and libraries for talking to MSVCRT.DLL)

Actually, real story....

[raehl]

I finished school just before the tech bubble burst, and had occasion to travel out to the Silicon Valley on business to our corporate headquaters.

There have been few times in my life where I have been more amazed than I was at the number of ways a girl could work some variation of "How much money do you make?" into the first three sentences of a conversation.

I'm happy to report, however, that these women are no longer there.

In retrospect, however, I probably should have just said "A Googillion".

Get started with WTL

[klin]

I started Win32 programming with WTL. No MFC experience at all.

For those of you who may be curious about this technology, here are a couple of points:

WTL is a collection of header files with the source inlined in. Personally I find the source reasonably understandable. I have had not much trouble stepping through and debugging WTL calls.

It's a light wrapper around the Win32 API. Some people commented on the lack of documentation regarding the WTL. The truth is, MSDN's API and common controls documentation pretty much covers what you need to know. For most cases the library does little fudging between your app and the API behavior.

For the application I am coding, I use strictly STL strings, containers, and various Boost libraries. With WTL, I don't feel that I am paying for things I am not using like CStrings and such. For non-UI OS calls, I use ATL. In short, WTL, STL, & ATL let me produce efficient code without worrying about reinventing solutions.

One thing I am worried about is the future of WTL. Open-sourcing is great, but I don't know what direction the Windows API is heading. As .NET seeps deeper into the Windows Platform, I am afraid that MS is going to try to root out such a quick and painless way to whip out applications in unmanaged code. There's life in C++ yet, I just don't know if MS believes that.

What about ATL?

[AstroDrabb]

This WTL may be OSS, however it depends on the ATL, which is not OSS. So again, this looks like a little marketing PR to me. MS making the WTL OSS while depending on the non-OSS ATL is Like having the OSS Linux kernel needing some non-OSS code from SCO. It doesn't make sense, accept for PR since many people will over look the important detail of depending on the non-OSS ATL.

Also, just like the last OSS release from MS, this is not what I would call an important piece of software. In MS's new world .Net is king. So the WTL can go away. However, it is pretty clever to get a little PR out of this release instead of just letting the WTL fade away.

All MS needs to do to make a big positive change of their image, is release ONE important piece of their software as OSS and actaully let the community contribute. I am not talking about a bread-n-butter app like MS Office. Some non-revenue generating app like IE or even explorer.exe. Those two apps could use some serious fixin.

Unwanted Child

[ChaoticCoyote]

I've written a few WTL programs, and am rather fond of this lightweight wrapper over ATL. WTL allowed me to create small, tight programs without the overhead (and poor design) of MFC (which was created before templates were added to Visual C++).

WTL has always been something of a dirty little secret: it wasn't installed by default by Visual Studio, and the README files suggested that it was an internal project unsupported by management. Yet those of us who disliked MFC found WTL to be quite useful, despite Microsoft's "official" attitude.

As for Microsoft releasing this as Open Source -- MS management never valued WTL in the first place, so "giving it away" is merely a public relations move.

Re:Unwanted Child

[m00nun1t]

It seems to be that no matter what MS does, it's got evil intentions, lacks sincerity somehow, "is merely a public relations move", or whatever.

That could be true if it were a few isolated incidents, but there are things up on /. pretty much weekly which, with your cynic-coloured glasses off, are actually positive. Blogging, releasing product source, increased participation in communities, relaxing licensing restrictions, WinXP SP2, etc.

Maybe the OSS community is the big lumbering beast which is slow to change while MS is getting on with changing what needs to be changed. Each small change by itself isn't ground breaking, but a trend, well, maybe that is.

Microsoft denounced Open Source

[Nailer]

Microsoft denounces Linux, which is a competing operating system. They don't necessarily denounce open source software in general (at least, not that I've heard of.) That would be sort of foolish...I mean, you have to denounce a rival's products, that's obvious. But to denounce the way he makes them when other world class software vendors are considering them would be shooting yourself in the foot.

From http://news.com.com/2100-1001-270684.html?legacy=c net

Earlier in the year, that feature led Microsoft Chief Executive Steve Ballmer to call open-source software a "cancer" and Windows leader Jim Allchin to call it "an intellectual-property destroyer."

MS on SF

[Slapdash X. Hashbang]

I assume that Microsoft has twice chosen Sourceforge to host their OSS projects because of the visibility and credibility it lends their open source steps. However, MS certainly doesn't need SF's resources. Does anyone know if MS has made any donation -- monetary or otherwise -- to SF?

Good move by MS. Unfortunately, WTL sucks.

[master_p]

(this is not a troll: Slashdot editors mod anything with the word 'sucks' as a troll).

Although it is nice to see the software giant contribute to open source, WTL sucks. It is really no different than MFC, carrying with it all the disadvantages of it:

a) the window creation process: first you create the C++ object, then you call 'create', and then 'preCreate', 'postCreate' and other silly stuff is being called. Contrast that with QT where you simply create a C++ object...

b) message maps: it violates object-oriented programming; introduces macro hell; makes code very sensitive to changes, to the point where if something goes wrong the IDE can not parse the code any more.

c) menus and commands based on numeric ids: maintaining the list of ids is easy at first, but it grows exponentially harder as the project grows, and after a while it becomes unmanageable to the point that it needs serious manual intervention.

d) the stupid UI updating architecture: your UI elements will be updated only when there is no other message in the message loop. You don't know when your UI will be updated.

e) the classes don't make any sense. For example, there is a CMessageLoop class. For crying out loud, who would have thought to make a class out of a message loop ? only MS twisted minds.

f) more string classes.

To me, it seems that releasing WTL is all about making themselves more innocent to the open source world. They now can say "look, we are contributing to OSS, you can't blame us!".

I would have much respect for them if they released anything serious to open source...for example the .NET platform.