<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>debaserab2</author><text>This tool seems useful if you buy into the philosophy, but I&amp;#x27;m just not sold yet - component based styling leads to a lot of style duplication and makes it very easy for a developer to go &amp;quot;off the playbook&amp;quot; when it comes to enforcing a consistent styleguide throughout an app.&lt;p&gt;The idea that &amp;quot;globals&amp;quot; in CSS are bad is counter intuitive to my experience that globals in CSS encourage consistency&lt;p&gt;Maybe when you&amp;#x27;re facebook size and you have many product teams all expected to produce something that all works together - I can see how the global namespace would be impossible to manage. For your average website or app? Not even close. It&amp;#x27;ll be awhile before you run into the limitations of CSS that Facebook is running into.</text><parent_chain></parent_chain></comment><story><title>Show HN: Polished – A lightweight toolset for writing styles in JavaScript</title><url>https://github.com/styled-components/polished</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>tobltobs</author><text>The current state of the JS world is getting closer every day to the J2EE craziness about 10 years ago. As an outsider it was nearly impossible to understand for what all those frameworks with funky names were required at all. For an insider every of those new frameworks looked like the solution to a fundamental CS problem. However, those fundamental CS problems where nothing else then some shortcomings introduced by the latest framework before.</text><parent_chain></parent_chain></comment><story><title>Show HN: Polished – A lightweight toolset for writing styles in JavaScript</title><url>https://github.com/styled-components/polished</url></story>