This is a bit awkward since TypeScript already defines its own thing called Iterator purely for type-checking. So due to this unfortunate name clash, TypeScript needs to introduce a separate type to describe these native/built-in iterable iterators.

The extension runs a command using your shell’s interactive mode, so that version managers configured in files such as ~/.zshrc are picked up automatically. The command then exports the environment information into JSON, so that we can inject it into the NodeJS process and appropriately set the Ruby version and gem installation paths.

what is the most brain friendly working environment in our digital in our digital working area and interestingly there are as I've shown you before there are different aspects of our way of thinking I mean we are not thinking the same way throughout the day um there are phases at the day

This is great because it works in Terminal, iTerm2, Chrome, Sublime & Outlook. The alternative (Karabina) is less good because that maps "Home" to Command+LeftArrow, which actually switches windows in Terminal.

esults over the past two decades have increasinglyshown that the “optimal” trajectory and the SCC are extraordinarily sensitive3 to the precisespecification of the model (Neelin et al., 2010; Budolfson et al., 2017; Gillingham et al.,2018).

They claim that they deduplicate runtimes. I question how much can really be shared between different branches when everything is recompiled. How much has /usr changed between releases of Ubuntu? I would guess just about all of it.

Yep, we experimented with this, but what we found is that you loose most of Svelte's niceness like slots, and instead you'll pass around deeply nested objects.

that is not ideal, since for example 'Cookie' is a forbidden header name, so I have to start worrying about env in load, which is kind of contra to its design.

It’s easy to create bugs because the environment is a somewhat degenerate settings database.

companies want to promote what the technology can do, so they de-emphasize that the way in which you do it is less than ideal

It makes me happy to see people actually think about things and not just accept a shitty API.

Disk space is an issue. Resource usage is an issue. Those new packages nowadays need huge amount of storage to finally do the exact same thing as their older and lighter deb counterpart. Whatever the price of storage, it’s the opposite of a progress, it’s not optimal at all.

following equation