Saavedro

before long we'll all have to have to run six or seven different hyper-situational vscode forks, all incompatible with different sets of extensions, having separate subscriptions to the same underlying foundation models

You also may need to run fstrim inside WSL to make all the free space actually compactible

they cannot. they do not have persistent memory.

there's literally no way to implement this on ethereum, smart contracts can't store secrets, all of their state is public.

i mean, if you're talking about how convenient is to shop there it kind of is? Doesn't matter if I'm technically close to a place if I gotta take a long detour to actually arrive.

Our system is already structured in a way to incentivize actually reinvesting and doing stuff with that money instead of adding it to one's personal hoard -- think that but enough to actually be effective

sorry, I meant provisioned.

As far as I know (could be wrong) it doesn't even listen to any network ports until its provisioned

i don't think anyone has found a machine yet where AMT is enabled out of the box either

this requires humans to be able to generate and remember passwords with decent entropy

It's worth noting that a lot of attacks that seem hard to pull off get sooner or later packaged up in ways that people with remarkably little knowledge about computers much less computer security can use them.

An old roommate of mine had a friend that found it funny to change my wallpaper while I was out of my apartment. I didn't find it as funny so I set login passwords.

At some point it started happening again, and I eventually figured out my system had a bootkit on it that made it always accept a certain password. This wasn't a guy who knew what a bootkit was, conceptually, but managed to find one and instructions for how to install it.

Yes. A JSON Object is not an ATM Machine.

well, matter for what? For building software that seems to work, sure, no. But for being able to speak to its capabilities -- or even know what they are, especially in the case of distributed systems it's definitely important.

this is why so many of the new DB offerings have docs that are either misleading or wrong -- often the doc writers or even the devs themselves don't know what invariants their system can guarantee and assume several that it can't.

map takes a function and returns a function that takes a list and returns a list. It has a type like: (a->b) -> [a] -> [b] (I take a function from type a to type b and return a function from list of a to list of b)

define

double_list_elements = map (*2)

and

> double_list_elements [1, 2, 3, 4]

gives you [2, 4, 6, 8]

> Or is it more like you pass the multiply function the first operand (2 in this case) and it returns a function multiply-by-2 which you pass the second operand

This is exactly it. You can literally write:

multiply_by_2 = (*) 2

Wow.

[EDIT]

The responses that amounted to "You did nothing wrong!" "We don't need to talk about this!" were what made the thread heated -- outside of that it was just a couple of posters realizing they made an incorrect assumption, what need was there to _debate_ that?