<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Quality-of-Code on Scholion</title><link>https://scholion.thluiz.com/tags/quality-of-code/</link><description>Recent content in Quality-of-Code on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Tue, 06 Oct 2026 17:26:29 +0100</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/quality-of-code/index.xml" rel="self" type="application/rss+xml"/><item><title>Qual é exatamente o problema com eval()</title><link>https://scholion.thluiz.com/notes/qual-e-exatamente-o-problema-com-eval/</link><pubDate>Tue, 12 Jun 2012 13:31:38 -0300</pubDate><guid>https://scholion.thluiz.com/notes/qual-e-exatamente-o-problema-com-eval/</guid><description>O texto questiona os argumentos comuns contra eval() em JavaScript, dizendo que performance e segurança costumam ser exageradas e que o problema mais sério está na qualidade do código e na dificuldade de debugar.</description></item></channel></rss>