xxs

You can't use a fire extinguisher for one to put it down. Li-Ion effectively self-sustain when ignited.

The only version of putting it down is letting it burn out.

Morealso diesel is hard to ignite on its own, hence the ICE use compression not spark

>North Korea or pre-unified East Germany, you know the difference

Most of the East side of the Wall was like that, it's just less known.

there are no socketed laptop CPUs x86 in particular. To get a socketed laptop CPU it'd be a desktop one, which are not exactly efficient.

Effectively there are no socketed CPUs for laptops, though, for way more than a decade already. Saying that as I'd fully support modular components, as in desktops.

RAM uses a different process than the logic nodes you describe. RAM uses tons of capacitors, along with the the transistors.

Then there is the HBM which is an expensive process to mount on the chip.

Yes, of course. It says - ball grid (array) in the article. Doing it by hand, e.g. with just hot air is proper hard. It's not hard with specialized equipment (that cost way more than the laptop, itself). Sourcing the chips is not easy either.

As for the videos and the Macs, you can see the same people (likely) soldering RAM as well.

Random Identifiers -> UUIDs are (mostly) randomness, especially the v4 one. V7 leaks the time component, so you can hash that part (and randomize it again), of course in that case you'd need to have an explicit mapping and then lookup, but once you get to the internal identity you dont have to worry either.

As for the worries, most SHA family is good.

You can be much simpler, you can always one-way-hash your primary keys (along with any pepper), if you wish to hide them. Still, use UUIDs freely.

serialized ids are in most cases a mistake from business point of view revealing the amount of entities created, e.g. the amount of new user registrations each day. Just create a new user to sample.

Some of the bottle neck of having a central system issuing them one by one can be alleviated by high-low schemes (multiple the received seq. by a number, e.g. 1000 and use a local counter), still unnecessary effort.

UUID are amazing and should be the default primary key for pretty much anything. They can be independently generated and require no central shared location.

Until you have any reason to believe UUIDs (and not bugs or misunderstanding as the blog post) are the critical component in the system, just use them. Look at the odds for collision with a proper setup (ntp + any modern cpus) then look at odds for anything else being an issue.

personally, I disregard and ignore cross-language benchmarks. Benchmarks are hard, benchmarks in managed languages are extra hard.

And then the person writing the code has to be an expert in all languages involved to make it even half fair, instead of just a sound-bite/click-bait.

> is there any knock-your-socks-off dish

you need an example of what you consider such a dish.

Rabbits are pretty decent, as a kid we used to have quite a few of them at the village (along with all other kind of animals, incl. lambs, pigs, and goats). Either way it's rather easy to tell the meat apart and most meat(s) can be prepared to be delicious.

How is that even possible? It's a great movie (ah well watched in the period), done by people who were outcast to work on it - similar to the folks sent to the terrace in "Silicon Valley"

At least in the EU an account knowing filing tax evasion reports would lose their license and can be criminally charged.

I don't know the state law there but it's not uncommon for an account to be liable (and need to notify authorities in cases of tax evasion)

> stuff to German users, are you doing business in Germany

Yes, and the VAT must be paid. You'd need to have some EU member state registration to do so (and still pay the correct VAT-rate, it's different per country). If it's business-to-business it'd be somewhat different.

>but still ship there

The local folks will have to customs-clear it themselves, pay the import tax AND the VAT. It's doable but very consumer unfriendly and likely won't be doing much business at all.

With the regards to topic - the tax is still very much paid.

Under normal conditions the code gets jitted after some use... and the VM is free to deoptimize it when it reaches its max allowed generated cache.

The only code in danger is the one from libraries (e.g. zlib)

For JIT languages most of the code is dynamically generated, not available to be loaded back from the disk. Morealso, the allocations do happen at large chucks where the oom_killer also happens, so it's significantly less of an issue.

ref counting is expensive in multi-threaded applications. Overall it would have worse performance. When it comes to predictability: deallocating a linked list (for instance) would have to deallocate all of the elements. Dealing with reference cycles is also not simple, either.

For GC enabled languages swap is universally bad. Some gc-pauses are indistinguishable from a system crash. It's a side effect on not having tightly specified memory limits.

I'd rather have applications be oom_killed than having them swap out, the former is rather obvious and demands action.

>to en-US would see the American site even if they live somewhere else.

Instead we have google that would serve the pages based off the local ip (and switch any time possible) which is a "horrific" experience travelling through Europe. You get a different language every day. Totally ignoring the accept-language header.

It's even funnier as the roaming would result in having the host mobile network IP regardless where a person resides - still ignoring the lang header, of course.

...oddly enough:

  - it notifies if your kids (or spouse) have left the door open.
  - you can use as a tool to check if the power company (or the road maintenance one!) has managed to reconnect the power back (or cut it, as in literally)

  - Other than that not so much.

It's just this good.

On a more realistic note: few years back, I've added zstd compression to our log subsystem (hand written direct buffers, native code, in-process, java). For the same CPU utilization if provides twice dense compression compared to regular [-6] gzip (the topic in the title). Zstd is =much= faster on decompression as well, and it this case - unparalleledly better as it uses twice less disk.

zstd is 'silicon valley' (the tv show) - life imitates fiction, except entirely open source

> Windows users should use 7-Zip

Please no - no native zstd support. NanaZip is the better option (it's a different build of 7-zip) and it's available at windows store.

> Better compression format, unpacks more kinds of archives

winrar has supported zstd for 5 years[0]

In short - Everyone should be using zstd, and 7-zip does not support it.

[0]: https://www.win-rar.com/singlenewsview.html?&L=0&tx_ttnews%5...

Not sure this is what I meant. Password is still stored, along will all the keypass stuff. If you have the option to login with the keypass... or the password - possibly sending you a link (or code) to the email, in case the device/browser has not been seen, yet.

What prevents passkey being used alongside password (+ email 2fa)?

Slavery is a weird one. It has been there for longer than any written history exists. In ancient times (Greece, Rome), slaves didn't have rights at all. A horrific injustice but it'd be not be a theft. Then you get the serfdom in the middle ages. Up to recent times humans have been brutally exploited.

The copy part was a recognized right, then taken away.

>...the vast majority of software was written in garbage collected language

and even then recently it costed (us) quite a few months to blame JVM and later the default glibc memory allocator for running out native (not java heap memory) - had to exclude all possible native libs (zlib, zstd via jna), direct buffers, sockets, thread stacks and so on. Changing the malloc to jemalloc solved the issue, even though initially it was done for its debugging capabilities.

It's just a great memory allocator.

I sounded all legit until the comma after "solutioned". I suspect that might be a fake.

All of the examples read like: "The dude abides", except in a grotesque/parody way.