@theKashey I'm working on a side project, Inventar, which (among other things) can manage CSS variables with a JS config (best of both worlds kinda!)
By using it in build time (Webpack plugin version is in the works) one could get truly static CSS vars where it fits
https://t.co/0129PPUXtV
This is a friendly reminder that 𝗴𝗶𝘁-𝗿𝗲𝗳𝗹𝗼𝗴 exists and that it can save you from seemingly unsolvable git accidents.
https://t.co/RFEez3fIPO
#git#DEV#developers
@tennikim (1) To save on verbose class code when only needing a few states/lifecycle effects.
(2) to follow the paradigms my workplace decided to use.
Other than that, hooks behave weird, are not intuitive, dictate code that's hard to navigate... I'd rather use other approaches if I can.
Performance tip: Make your website smaller by replacing every <div> tag with <i> tags
You’ll just have to reset the italics with “body { transform: rotate(-15deg) }”
A friend told me that she gets twice the job offers since switching to my CV template. Here you'd find it, as well as several tips and tricks to make your resume better.
https://t.co/4ZEek5zNfM
#resume#programming#techjobs#cv#jobsearch#developer#techcareers
const Component = (props, addHook) => {
const [count, setCount] = addHook(setState)(0)
...
}
Wouldn't that make @reactjs hooks seem so much less black-box-y and functional?
@FBE #react#javascript#webdev#webdevelopment
TIL that, in @reactjs, you can't return in a component before using ALL of your hooks. Yet another non-native #js constraint introduced by #hooks, yet another step in making #react a very black box, and yet another reason not to like this direction.