I drive a 2009 Subaru Impreza Outback. We bought it used recently right before our first kid was born. It's a solid car with plenty of power but nothing all that fancy.

The reasons we went with a Subaru, besides it being well priced, were:

- AWD so we can drive to Tahoe without chains in the winter

- Extremely reliable engine

- Plenty of room and flexible storage for skis, bikes, roof rack, trailer etc.

Basically, it's a great car that we can get dirty and use to go play outside.

I'm not really talking about just handing out the code... although I suppose it could just be open sourced. That being said, I'm not opposed to the company being taken in a different direction.

Of course, I realize that by telling people to contact me on about.me there is very little chance that a discussion will happen on Hacker News and this post will probably end up buried. :|

The intent of the post is to start a conversation and to have people take another look at YUI. After using jQuery for years in both small and large projects, I took another look at YUI when 3.4 was released and I've really been impressed. I don't think it gets the credit it deserves, mostly because YUI 2 was such a beast. I realize I'm missing a lot of concrete reasoning in the post, but that's primarily because I didn't want this to be a conversation about the right and wrong ways, or simply a syntax comparison.

Then add some concrete reasoning and comparison. Do some work. Fuel the conversation. Otherwise the only thing left is the assumption that you do not understand the differences between the two tools. I'm a YUI-hater and jQ-fan, so I appreciate what you're trying to do, but it needs some substance.

edit:

I don't mean to come off dickish. I started out writing my own AJAX libs in 2002-2003, started stealing some good ideas from Prototype in 2004-5, eventually trusted my fate with jQ in 2006, and have facepalmed every time anyone recommends we use YUI since the day of its release. It's like the worst of both poles...it is neither a fluid, lightweight swiss-army knife like jQ, nor a well-constructed application framework like ember. Instead it always seemed to be a rigid set of off-the-shelf components that appealed to people who liked to talk about design patterns but not actually build anything.

A student from Georgia Tech did a fantastic job with one of these last month as well. He called it CodeBook:

http://danielchasehooper.github.com/CodeBook/

You guys might want to think about working on it together. His version includes the introspection on an item in the canvas as well as some other great things like inline, as you type JSLinting.

Thanks. It was a bit helpful. I'm mostly curious what other people do because it feels like something that has been done over and over again.

I found it a frustrating experience too...happy to share more insights directly at dusanb [at] devicemagic dot com.

From an execution standpoint, I fully agree with you. That's what I did when we first found out that the domain had been registered and saw the site he had put up. I collected information and then left it alone to focus on our March 1st launch.

Now that he is being more aggressive, it's rude and a nuisance. He setup a similar facebook group to ours with a hyphen in the name instead of a space; He is tweeting about it and it's showing up in our name searches; etc.

Also, he is offering something similar to what we are offering as a (very inexpensive) service, for free; Which is just annoying and potentially confusing.

Trying not to focus on it. Serenity Now. :)

Yeah, I started filing it this morning before writing this post. Trying to cover all of my bases. :)

trademark filing will only cover you in the US, you need to look at more options

Agreed about Lawyers. I am happy to spend money on them as necessary for the right things, but this seems like something that could be very lengthly if not approached the right way... and one thing I know about hiring lawyers is that long problems have big bills. :p

Yeah, I like this route a fair bit. I'd like to think that I'm not the only one who gets frustrated by people who would do this type of thing.

Thanks a lot for the suggestion. :)

My hesitation on something like this (and also the reason I didn't put our company in this post) is because I don't want to give him any unnecessary attention until necessary. Plan of attack being worked out now...

Keep us updated. No doubt there are people here who can help spread the word.

Thanks. I definitely will. :)