kinghajj

I'm curious, what's the use case for CUE in a WASM environment? So that web apps can compile configuration at runtime?

Didn't the law that created the PPP program have explicit language to forgive the loans if certain conditions were met?

Eh, in this case it's a tool created by Rust programmers for generating documentation for the Rust language, and has particular features for validation of Rust code snippets in said documentation. I think in this case, mentioning Rust in the description is reasonable.

The Wayback Machine has entries that look extremely similar going back to 2007, and ones mostly similar back to 2005. It might be real. Looks like the AI part was added in 2022.

It's not that uncommon.

https://en.cppreference.com/w/cpp/string/byte/memcpy

https://en.cppreference.com/w/cpp/string/byte/strncpy

https://en.wikipedia.org/wiki/X86_assembly_language#Syntax

https://en.wikipedia.org/wiki/Worse_is_better

Go is a language made by Googlers, so its design helps with Google problems. And many of Google's problems are ones of scale.

* Go is straightforward to read. Any reasonably-competent college graduate should have little trouble understanding it and be able to become productive quickly.

* Go compiles into completely static binaries. You don't have issues like "oops, the build system runs CentOS 7 but we're deploying it to Ubuntu 18.04 and their libc's aren't compatible." With containers, you can copy many Go programs into `FROM scratch` images and they will work fine, greatly reducing the attack surface area.

I used to dislike for Go for similar reasons to you and others, but after using it for a few years at $employer, I've come to appreciate its merits. Sure, it can be a bit annoying to write

    if err != nil {
        return err
    }

again and again at first, but I just type 3yy7jp to yank+paste it as needed. You could also configure some editors to detect when you type `if err` and generate it automatically. It's also not uncommon for editors to fold the lines down into a single line.

The `?` at the end of the Rust example expands into the equivalent of the Go `if err != nil` idiom.

AZs don't really help when it's AWS' own services across the entire region that break. Anecdotally, we have had customers accept outages that were out of our control without penalty.

Why not, and what problems would it cause?

AI is a great example of hyperstition in action.

Scylla has "tunable" consistency[1][2][3], so it's possible to get consistency without too much of a performance hit, and still be resilient to some failures.

[1]: https://www.scylladb.com/glossary/eventual-consistency/

[2]: https://docs.scylladb.com/stable/cql/consistency.html

[3]: https://docs.scylladb.com/stable/cql/consistency-calculator....

`amd64` is still what Debian and Kubernetes use.

This might make me finally upgrade to Windows 11.

Ha, I've tried zsh, but never got quite comfortable with it. Recently I've been using bash with starship, which has enough bells and whistles for me.

The most recent FSD beta update from a few days ago finally started using the interior camera to track driver attentiveness, according to the release notes.

Cool, now I can add this to my `~/.bashrc` and easily view the whitepaper whenever.

    btc_wp() {
            open /System/Library/Image\ Capture/Devices/VirtualScanner.app/Contents/Resources/simpledoc.pdf
    }

Why wouldn't I want my offspring to live in a world where dangerous, monotonous, degrading labor is no longer required to live?

Hashrate doesn't matter if nodes don't accept their blocks. So while you're right that a powerful government could severely strike Bitcoin by taking down miners, they can't force the community to accept invalid blocks, no matter how much hash power they could amass.

Convince the Fed to buy failed banks' loan assets at the exact price required to make depositors whole, but not a penny more. Shareholders and bondholders in those banks get hosed, but depositors at those banks (and more importantly, depositors at other banks) feel assured.

Isn't the program announced by the Fed over the weekend intended exactly to prevent the risk of this spreading to other banks?

I'm not at all the target audience for this post—I'd label myself the polar opposite of an AI doomer—so it was really striking to see such a different perspective. I mean, right off the bat, the opening line

> Some people are worried that AI will wipe out all value in the universe.

Huh? What does that even mean? Even leaving aside the hyperbolic clause "in the universe," who is saying that AI will "wipe out all value," and what are their arguments?

At least the author acknowledges the assumptions baked into the work:

> Investing in AI companies, by default, gives them more funding and more ambition, and thus accelerates AI. That’s bad, and a good reason not to invest in them. Any AI company that is a good investment and maximizing profits is not something to be encouraged. If you were purely profit maximizing and were dismissive of the risks from AI, that would be different, but these questions assume a different perspective.

It's hard to square this away with the author's other advice to continue saving for retirement, which (in the USA) pretty much means investing in the large-cap stock market, which includes the "Big Tech" companies who are already funding R&D for AI projects.

"Maybe the aliens really are coming, because they realized that we're on the verge of AGI!"

Well, the biggest roadblock to that would be securities laws and their enforcement agencies. I doubt the SEC and its analogues in other nations would just sit and watch that happen.

Maybe a black-market "corporation" like a drug-smuggling ring could try something like that, but even they would have reservations.

It's breaking $21k right now, though the market isn't deep so it's swinging wildly in the past five minutes. Exciting, nonetheless.

Even assuming that's the case, isn't the counterargument "Fine, then governments need to subsidize investment into nuclear power plants, just as we do with other green technologies."

AMD hasn't had their own fabs since they were spun off as a separate company, Global Foundries. They still use GF for some things, like the I/O dies on their recent chips.

We started seriously looking for houses to buy in April, and got a rate of 5.125% later that month. We were really hoping for something <5%, but I'm grateful that we didn't wait too much longer.

Of course, now the "worry" is that rising rates will sink the market value. So long as I keep my job or can still find another easily, that's not much of a concern; but the prospect of a recession, with layoffs and hiring freezes, is in the back of my mind.

Why stop there? Doom on the Analytical Engine!

You should look into the Mill CPU architecture.[0] Its design should make microkernels much more viable.

* Single 64-bit address space. Caches use virtual addresses.

* Because of that, the TLB is moved after the last level cache, so it's not on the critical path.

* There's instead a PLB (protection lookaside buffer), which can be searched in parallel with cache lookup. (Technically, there's three: two instruction PLBs and one data PLB.)

[0]: https://millcomputing.com/

Yeah, but it's doing that at 3.2 GHz versus 4.9+ GHz that the top-end Intel CPUs need to run at to get equivalent single-core performance.