|
|
|
|
|
|
by dmose
6496 days ago
|
|
|
I had to justify it to my boss and my fellow developers because everyone has their preference. Some want to use YUI, some want to use prorotype. In the end, the boss makes the decision and the availability of an MIT license comes into play, so he's going to the homepage either way and the last thing I want him to see is some cheesy rockstar shit for a framework that's going into a massive line of business SaaS application. |
|
|
Well, the nice thing about jQuery is that it is not exclusive. But I'm really surprised that you haven't gone and talked to the other engineers on the project and come up with a unified plan. If the majority of people want to use prototype and you can't show them why they shouldn't, then you probably don't have a good argument against them.
You have to justify jQuery to other engineers, and then your boss's opinion becomes largely immaterial unless he's utterly terribly at his job.
> last thing I want him to see some cheesy rockstar shit for a framework that's going into a massive line of business SaaS application.
If you really do have to justify it to him...
The first thing you want him to see is an unbiased assessment of the library's features and capabilities (not the least of which is its ability to play nicely with other libraries). The second thing you want him to see is other engineers agreeing to use it. That way when he saw the last thing, the rockstar, his mind would probably already be made up.
You make it sound like you have 0 influence over the course of the project you're involved with. If a silly graphic has the power to derail your framework choice, you didn't do your homework in the first place.