File
public/uploads/rules/use-jquery-instead-of-javascript/rule.mdx
Finding
lastUpdated: 2016-11-17. The rule states "jQuery is the MUST HAVE tool" and lists cross-browser support and plugins as reasons. This recommendation is outdated: modern browsers provide native DOM APIs, and many projects use frameworks or vanilla JS.
Suggestions
- Reframe the rule to explain when jQuery remains appropriate (legacy projects) and when to prefer native DOM APIs or frameworks.
- Add examples showing native equivalents (querySelector, classList) and note performance/maintenance trade-offs.
- Recommend documenting project-specific choices and linking to migration resources where relevant.
contenthawk-run-id: 24946376720
Generated by Content Judge (Agent 2a) · ◷
File
public/uploads/rules/use-jquery-instead-of-javascript/rule.mdxFinding
lastUpdated: 2016-11-17. The rule states "jQuery is the MUST HAVE tool" and lists cross-browser support and plugins as reasons. This recommendation is outdated: modern browsers provide native DOM APIs, and many projects use frameworks or vanilla JS.
Suggestions
contenthawk-run-id: 24946376720