Notices by Nolan (nolan@toot.cafe), page 12

"It takes a Village: Lessons on Collaborative Web Development" by Harald Kirschner https://www.youtube.com/watch?v=THTONE33mD8

There is some really neat stuff coming up in the Firefox Dev Tools. Skip to 20:50 and see a really amazing demo of time-travel debugging. The moment where he adds logpoints and it prints a console.log *for previous points in time* blew my mind.

"Save-Data Usage" by Tim Kadlec https://timkadlec.com/remembers/2019-08-29-save-data-usage/

So the Save-Data header is reportedly sent in 4%-20% of page loads? Maybe I should be using this.

"The story of a V8 performance cliff in React" by Benedikt Meurer and Mathias Bynens https://v8.dev/blog/react-cliff

Interesting stuff! JavaScript engines are terribly complicated.

"Avoid Premature Optimization" by Victor Zhou https://victorzhou.com/blog/avoid-premature-optimization/

This is why I'm always skeptical of JavaScript microbenchmarks. Your hot paths are probably not array iteration. (They might be, though! Always measure.)

@halkeye I block 8.8.8.8 entirely as well as the other Google one. It forces my Chromecast to fall back to my Pi Hole's configured DNS, which is Cloudflare incidentally.

So this means that all devices in my house are forced to use the Pi Hole, including the Chromecast.

@cjd Yep, it's so incredibly unproductive that I don't know where to start. Especially when the maintainers have to waste their time talking with someone who doesn't care about their project at all and just enjoys venting to strangers on the internet.

As for "ads" in the npm install console, if you use yarn then you won't see them. Plus this is not the first project to do that. (IIRC, my console was already full of stuff from Babel, Inferno, TestCafé, and various other projects.)

Open-source sustainability is hard. I don't have anything against folks trying something new and different. As I said in a previous thread though, I'm skeptical this particular approach will work. https://toot.cafe/@nolan/102655544643844394

For the record, I use StandardJS in most of my projects, and I love it. It saves me a ton of time. It's actually an incredibly valuable thing that someone went to the trouble of defining a "standard" style on top of ESLint, and that I don't have to worry about how to configure it. Even my IDE (WebStorm) just picks it up automatically. https://standardjs.com/

- Reasonable defaults
- No bickering over stuff that doesn't matter
- No config files
- My StandardJS projects look like every other one

Found a good name for a bad pattern in the programming community: "link aggregator issue tracker outrage raids" https://lobste.rs/s/7aawbr/npm_install_funding#c_m2ruct

I.e. someone posts a GitHub issue to Hacker News, /r/programming, etc., and suddenly the thread is swamped with people who have not heard of the project until today.

"Samsung made a Giphy page of comeback GIFs to send people who diss green bubbles" by Ashley Carman https://www.theverge.com/2019/8/21/20826812/samsung-giphy-gifs-instagram-meme-makers-blue-green

I remain fascinated that this is a thing. The linked podcast episode is worth listening to.

@wohali I use OSM in my car, but I almost never drive and also the directions are so bad I'm better off just ignoring it. For bike directions GMaps has zero competition AFAICT. I like being able to see where the protected lanes are, where the uphills and downhills are, etc.

At the end of the day Google is becoming so dominant on the web that they practically *are* the web, so you either use Google products or you avoid touching a computer. I can't quit Google entirely (Chrome DevTools, GMaps, YouTube are the big ones for me).

How do you deal with something that builds amazing products but also does it in kind of a sleazy way? And maybe is becoming way too powerful? I suppose you become a tech vegan sneaking occasional bites of cheese pizza. https://nolanlawson.com/2019/05/31/tech-veganism/

I have a weird relationship with Google. I know a lot of people on the Chrome team, I regularly file bugs on Chromium to help them fix stuff, I think Chrome is generally an amazing browser, and I even think some stuff AMP is doing is pretty cool - e.g. WorkerDOM is an interesting approach to a tricky perf/ecosystem problem: https://blog.amp.dev/2019/08/21/amp-script-amp-heart-js/

OTOH outside of work I generally avoid Google products. DDG, Firefox, LineageOS, etc. I even blocked Google's DNS on my home wifi.