but why? i have to add so much milk and sugar to mask the bitterness that, combined with the negative effects, i asked myself, why do i even bother? i might as well just drink hot milk with sugar instead. now i only drink coffee if i need the energy and waking effects and nothing else sugary is available, which happens once a year, at most.

This is not universal. I only drink espresso without sugar or milk, because I love the taste of a strong coffee.

counterpoint (don't take this to seriously):

there are to many types of bricks to sort by form. unless you have an inventory the size of a brick factory you can only sort by category or by size.

otherwise, sorting by color makes your collection aesthetically pleasing, and when you build, you usually want to use specific colors only to make your model look good.

That's why you have to group similar forms. - Bricks - Plates - Narrow Plates - Wheels - Windows/Doors - Smooth pieces - People bin

And then if you like to sort further you sort out the smallest of each bin because those always fall to the bottom when mixed together

sorting by size needs to come first. from my own experience, you can't find any small pieces if they are mixed/covered by larger ones.

There are less different forms than any normal brick enjoyer has bricks of a specific color. Therefore the lookup is faster ;)

not all technical content is the same, or has the same level of importance. this video does not introduce anything that i need to be able to replicate in my work, so i don't need to catch every detail of it, just grasp the basic concepts and reasons for doing something.

if your foreground work doesn't occupy your brain, why not?

Because I prefer not to think about the hair I'm removing from my shower drain?

you could however link to the timestamp where that particular explanation starts. i am afraid i don't have time to watch a one hour video just to satisfy my curiosity.

I've found Gemini useful in extracting timestamps for particular spots in videos. Presumably it works with transcriptions, given how fast it is.

The three answers it found were:

- Avoiding lock-in to them: http://www.youtube.com/watch?v=KKbgulTp3FE&t=1914

- Competitive advantage: http://www.youtube.com/watch?v=KKbgulTp3FE&t=1852

- Perceived Lack of Use Case: http://www.youtube.com/watch?v=KKbgulTp3FE&t=1971

Those points do actually exist in the video, I checked. If there are more, I don't know about them, as I haven't yet watched the rest of the video.

This is approximately the section in the video titled "Memory controllers hate you" (https://www.youtube.com/watch?v=KKbgulTp3FE&t=1399s), combined with the following section.

The actual explanation starts a couple minutes later, around https://youtu.be/KKbgulTp3FE?t=1553. The short explanation is performance (essentially load balancing against multiple RAM banks for large sequential RAM accesses), combined with a security-via-obscurity layer of defense against rowhammer.

what's your motivation for posting this?

I have none. I just find it interesting - like the rest of the things I post if you check my comment and submission history.

What's on your mind?

another thread about the same topic: https://news.ycombinator.com/item?id=47700460

i would do free venues only. usually restaurants are free because you consume food. if that is not an option, it depends on the cost. i have seen events where people were asked to contribute something when they arrive. you can usually announce the cost of the venue and ask everyone to contribute appropriately. if you fall short then next time ask people to contribute more. or keep a running tally during the event until the venue cost is met. from my personal feeling, if it costs more than $1-2 per person the venue is too expensive. find a cheaper one.

i heard mention of 100 megabit. they downloaded 50GB of data the night after the flyby. they probably keep downloading as much as they can. and they still need to sift through all that to find the pictures worth publishing. they could do a data dump, but that's not interesting for the general public. the stuff is coming. slowly.

if you hash locally isn't that effectively like using private/public keys but less secure? might as well use the real thing then.

There's no effectively using private/public keys whatsoever.

The communication with the server must be secure, the extra hash only provides the ability for the server's data getting leaked without compromising the password through server logs. The usual setup I'd say is to salt the password in the server and store (salt, hash(pw+salt)), but that still handles text-plain password that might get logged by mistake.

i meant in term of complexity, if i hash the key on the client, but don't want the hash to become the password then i have to do some dance with sharing a secret or something that is as or more complex than using private/public keys outright.