css_apologist

i remember making the switch from atom to vscode felt so cold

i can’t explain what, it wasn’t just the colour scheme

atom was objectively worse on performance and a few other things i forget, but it felt so good to use

> last 3+ decades realistically, I'm around 35

ah yes, the formative years of 5-15 spent in 1-1 with my manager has drastically shaped my life & experience /s

holy shit that automatic colour scheme example is amazing

also didn't know about the more options in color-mix, it worked 90% of the time in a project i was using, but looked terrible a few times. I think with a different colour space and some adjustments to the specific colours it might have been fine? will definitely try it again, because its such a massive win when it works

I've used these things. IME, nowadays it's not worth the bundle size to bring in these libraries. map/filter seems quite optimized, {...obj} is fast since its only shallow. Yes it does come down to practices vs better libraries, but in practice, it's fine IME

One thing to note, i was very excited that we have a bunch of lazy methods on Iterator protocol, but they are slow as shit as of earlier this year.

I wrote a parser a year ago with extreme use of .map (every step of processing was cloning the tokens), and i thought, let's migrate it to lazy iterator - it got ~10x slower :(. The compile time was fine for my use cases, so i didn't give immutable-js a try, but it was a surprise

I did some benchmarks on map+filter vs mutable for of + push, and on firefox up to 200-300 elements map+filter is actually faster (unforunately not on chrome).

Of course, its not the best, but my experience is that modern js engines are fast enough for most use cases to not have to bring in any libraries anymore

although this article does get me thinking of documenting the “patterns” i use, and why.

this site reads like its 2017

its low quality, breadth but no depth

more important is to deeply understand the basics of working with immutable data. try writing applications with no for loops or forEach (and actually use the array methods as they are intended), no cloneDeep hacks and obviously no direct property mutation, always create a new object.

in real world you still use for loops plenty, but as a junior its good to see what its like to live without it for a while.

a lot of these are misleading, or ungrounded

see the prototype, and observable pattern

they explain the basic concept, but in the only way you would never use it in real life

Similar to knowing when to call it quits as a director, i see lifespan the same

I much prefer a beautiful arc to a drawn out, translucent life

your comment reeks of fear of fear of death, a yearning for permanent enlightenment, and an inability to feel the every day pain of life

HUGE

- finally can style <select>

- generalized attr()

- if() & function

- can open dialog & popover w/o js

CSS is having it's ES6 moment rn