[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


File: 1783420452831.jpg (9 KB, 588x306)
9 KB JPG
>>
I had a hot idea that Codex would have an easier time using Tailwind, but as it turns out it seems to have made it more confused. So I went back to conventional css/scss.
>>
>>109775338
well if the choice is between twitter pink haired tranny faggots and jeets I would actually take jets
>>
File: Tupolev_Tu-123_in_2002.jpg (396 KB, 1024x620)
396 KB JPG
>>109776420
I would take jets as well
>>
File: 1777181770752.jpg (154 KB, 1763x992)
154 KB JPG
>>109776420
Hell yeah go jets
>>
There's no reason for it. Css allows variables and nested classes so there's barely any reason to scss anymore, let alone this mess.
>>
I'm not using anything newer than bootstrap 4, shit is bloated enough as it is.
>>
Had to work on a Rails codebase with Tailwind. It's pure horror and the worst part of it is that it's completely impossible to eradicate once introduced, it penetrates every html template with unreadable incomprehensible css class soup which reads like inline styles, but worse (because a lot more style info is contained in ever shorter class names). Refactoring is literally impossible unless you invest a year into re-writing this shit into css. Whomever invented this is the most retarded kind of of retard ever.



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.