jQuery and its cousins are great, and by all means use them if it
makes it easier to develop your application.
If you're developing a library on the other hand, please take a moment
to consider if you actually need jQuery as a dependency. Maybe you
can include a few lines of utility code, and forgo the requirement.
If you're only targeting more modern browsers, you might not need anything
more than what the browser ships with.
At the very least, make sure you know what jQuery is doing for you, and what it's not. Some developers believe that jQuery is
protecting us from a great demon of browser incompatibility when,
in truth, post-IE8, browsers are pretty easy to deal with on their
own; and after the Internet Explorer era, the browsers do even
more.
You might not need jQuery
Your search didn't match any comparisons.
{
Object.entries(comparisons).map(
([categoryName, category], index) => (
)}
)
)
}
{titleCase(categoryName)}
{category.alternatives && (Alternatives:
-
{Object.entries(category.alternatives).map(
([alternativeName, alternativeUrl]) => (
- {alternativeName} ) )}
{Object.entries(category.comparisons).map(
([comparisonName, comparison]) => {
const newestEngine = getNewestEngine(
Object.keys(comparison.engines)
);
return (
)}
);
}
)}
{titleCase( comparisonName.replaceAll('_', ' ') )}
{comparison.alternatives && (Alternatives:
-
{Object.entries(
comparison.alternatives
).map(
([alternativeName, alternativeUrl]) => (
- {alternativeName} ) )}
{Object.entries(comparison.engines).map(
([engineName, allCode]) => (