4 ms·

Impressive, but to me, as a front-end developper that has been breathing CSS for the best part of my adult life, this solve an issue that shouldn't be an issue.

Impressive, but to me, as a front-end developper that has been breathing CSS for the best part of my adult life, this solve an issue that shouldn't be an issue. Yes, you can end up with unmanageable CSS. Yes, it is very easy to end up with a website that is hell to maintain if you have no idea what you are doing. The real solution is to hire someone who is an expert at managing CSS in enormous websites. You don't see people saying "Oh? OOP programming? That's too hard! Write all your code with this insert unconventional project instead!". That being said, this project is impressive, and I love that people are working toward making CSS better.

clessg 11y ago
Of course, anybody is able to manage a problem, but our jobs as engineers should be to fix the problem. And indeed, there is a lot that is problematic about CSS, just as there is a lot that is problematic about writing concurrent code in old versions of Java. You can deal with it if you're careful and don't let anybody touch the code, but you've solved nothing and as an engineer, that should make you feel bad.
- tracker1 11y ago
  I'm not sure that this really solves the problem better than keeping your less files next to your jsx files for component specific styles and relying on css classes, hierarchy or properties as it stands. I've gone down the path of doing similar things to this, and in the end I find it's more complex than simply using less (or scss)... While I appreciate the effort actually inheriting styles in/out of react components, based on parent/child relationships is a lot harder to manage when dealing with your react components directly imho.
  - clessg 11y ago
    Are you able to elaborate on what practical issues you ran into?
    - tracker1 11y ago
      Mainly centers around inheritance, or applying the same styles to multiple controls... it's much easier in CSS using classes, or hierarchies than it is directly in the controls... you'll usually wind up with some common js style files, and have to import/use them for reuse... and it just gets a bit weird, even compared to say bootstraps variables file.
andrewingram 11y ago
I'm a fan of technologies that let me hire people who aren't best-in-world and still produce decent maintainable code.
- Raphmedia 11y ago
  I'm more of a fan of hiring people that can make the best-in-world out of out-dated hard to use, barely documented technologies. To me, that's what is encountered the most.
Nekorosu 11y ago
> You don't see people saying "Oh? OOP programming? That's too hard! Actually we do. OOP makes a lot of things hard to implement and maintain. That's why functional programming of front-end matters and new approached emerge (reactjs/virtual-dom + immutable data).

clessg 11y ago

Of course, anybody is able to manage a problem, but our jobs as engineers should be to fix the problem. And indeed, there is a lot that is problematic about CSS, just as there is a lot that is problematic about writing concurrent code in old versions of Java. You can deal with it if you're careful and don't let anybody touch the code, but you've solved nothing and as an engineer, that should make you feel bad.

tracker1 11y ago
I'm not sure that this really solves the problem better than keeping your less files next to your jsx files for component specific styles and relying on css classes, hierarchy or properties as it stands. I've gone down the path of doing similar things to this, and in the end I find it's more complex than simply using less (or scss)... While I appreciate the effort actually inheriting styles in/out of react components, based on parent/child relationships is a lot harder to manage when dealing with your react components directly imho.
- clessg 11y ago
  Are you able to elaborate on what practical issues you ran into?
  - tracker1 11y ago
    Mainly centers around inheritance, or applying the same styles to multiple controls... it's much easier in CSS using classes, or hierarchies than it is directly in the controls... you'll usually wind up with some common js style files, and have to import/use them for reuse... and it just gets a bit weird, even compared to say bootstraps variables file.

andrewingram 11y ago

I'm a fan of technologies that let me hire people who aren't best-in-world and still produce decent maintainable code.

Raphmedia 11y ago
I'm more of a fan of hiring people that can make the best-in-world out of out-dated hard to use, barely documented technologies. To me, that's what is encountered the most.

Nekorosu 11y ago

> You don't see people saying "Oh? OOP programming? That's too hard! Actually we do. OOP makes a lot of things hard to implement and maintain. That's why functional programming of front-end matters and new approached emerge (reactjs/virtual-dom + immutable data).