3 ms·
Until I learned I'm behind the curve. Look, I think CSS-in-JS is a great idea. It's cool, in fact I remember suggesting something similar to my lead dev as a n
by plutonorm 7y ago
Until I learned I'm behind the curve.
Look, I think CSS-in-JS is a great idea.
It's cool, in fact I remember suggesting something similar to my lead dev as a newbie 12 years ago. He basically told me I was an idiot.
My point is you guys are getting fired up over things that are just variations on a theme. First it was mix presentation and logic. Then it was separate it all, html, css, js. Then it was put some restricted js functionality in html. Then it was f* it lets just do it js.
Just... yawn.
Think bigger.
- tomxor 7y ago> Just... yawn. Think bigger. More specifically: Think subjectively, think what's relevant to your current context... Most important, is to lose the "everything is a nail attitude" and instead find the solution that fits best for your current problem. It's very difficult to make unbiased well balanced decisions to use a solution when starting from the solutions perspective. It's better to start with the problem first and stop focusing too much on tools, methods, patterns etc. i.e be invested in your problem not some solution, you don't owe them anything. None of these ideas e.g CSS-in-JS are absolutely good or bad, they can be good in one context and bad in another, however very often the distribution is such that they are bad to generally apply - programming patterns being the worst and most often abused case of things that should not be generally applied and which are. It's ok to talk about new ideas, it's not ok to forcefully apply the latest idea to everything you touch like it's your new religion.
- ghego1 7y ago> My point is you guys are getting fired up over things that are just variations on a theme. My first thought was: how long before we see CSS-in-TS