[sy7ar]

Unless all your work involves CSS I doubt it saves 3-4 hours / week. Also, saving 3 hours of work doesn't mean you get paid for 3 hours more. It's also a dependency that's not guaranteed to exist as long as the default browser dev tools or available on every machine.

[mnsc]

If all you do is css I doubt you have a workflow where this tool would save you 3-4 hours a week. It might even be ~20 minutes/week and 10 minutes/week stumbling while relearning your habits to use (depend on) this tool. And then a year later when you are completely dependent on this tool. Boom. It's now acquired by and part of Atom Text Editor Enterprise Ide where all those who invested too much in Atom went to die.

[methodical]

Couldn't agree with this more. It's always nice to think that some super clean UI beats making quick CSS adjustments alongside HMR or a quick build time but in my experience it probably never does. If I wanted to test different font weights of some text I wouldn't go into the CSS in my browser and adjust it, I'd just change the value in my CSS (helped more-so by CSS frameworks such as Tailwind), and see how the output changed. The upside being that if I like how it looks, I've already made the change to my code. I don't know who this would realistically save any significant amount of time a week for outside of an inexperienced developer who doesn't have a pretty good idea of how slight style differences will impact the final product.

[tilakraj_0308]

Hello everyone(edited)