trh88
Joined 8 years ago
Joined 8 years ago
Since when? You don't need to know JS to write CSS. You just don't. You make an architectural decision, based on what you want to create, to use css-in-js. But that's a decision that you make. You can 'do' CSS without anything but... CSS!
Well that's a conscious decision the developer makes.
You don't need to use any of this.
If, as a beginner, you just want to write an HTML doc with some styles - that still works.
However, if as a beginner you jump into a Webpack / React / CSS-in-JS setup... well you're going to have a hard time.
Complaining that "that's the way things are going" seems to pass the buck. If you don't want to go that way, then don't!
STOP. RESET. CONTINUE.
> The rest of the org probably made a schedule they know you can't meet
> Most people probably already know you'll be late, but aren't saying it out loud
> There's a good chance <your boss> already knows as you suspect.
> It's probably not new news to <the project owner> either.
Doesn't take much for one, if not all of those to be untrue. And by the time it unravels, it's too late.
How do you know deadlines are going to slip when planning the project? Makes no sense.
To be honest, for the particular use cases mentioned here - why not use the object utilities in Lodash (which is well used, familiar to many, well documented, and battle hardened)?
> we didn’t get around to implementing slices like array[1:3]
What's wrong with arr.slice(1,3)?