nu11ptr

I wasn't sure how I would feel about my newish MBP M5 Max when they released this, but given the price increase, and the fact that I have zero interest in a better screen since I dock most of the time, I am happy I paid $2K less for the same horsepower earlier this year.

Update: The one nice thing I noticed is the weight of the 16" is only 4.1lb vs. 4.7lb from the previous model. I guess OLED is a lot lighter. THAT would be nice.

AI is the correct term because it describes "what" it is (artificial, not natural intelligence). SI describes the magnitude and is no doubt meant as marketing, which then invites different prefixes over time ("ultra intelligence", etc.), creating consumer confusion.

> Why do they insist on every new phone being bigger than the phones before them?

Folded, I get, I want it to be a "regular size", but the only reason I don't like big devices is because they are clumsy to store in my pocket and use/grab one handed. If I can use it BOTH ways, now I have a choice. One handed for quick usage, and two handed for extended sessions. For $2K, yeah, I'm going to want a full fledged computer in my pocket.

It is distracting. Just use your hands normally. It just feels a bit alien and scripted.

It is a massive accomplishment and neat tool for sure but:

1) Induces a large performance penalty

2) Introduces a GC into C code bases (higher memory requirements, performance profile changes)

3) Is x86-64 only atm I believe

An idiomatic Rust port would have none of these issues, so it would be more a stop gap measure than a long term strategy.

How are compile times compared to Rust? Zig? Go?

> It’s the language behind Kubernetes admission policies, Envoy’s RBAC rules, Google Cloud IAM conditions, and gRPC’s protovalidate

Very small nitpick, but AFAIK protovalidate comes from Buf, not Google. While protovalidate DOES work with gRPC via backward compatibility (but also Buf's ConnectRPC), saying "gRPC's protovalidate" probably makes people think it came from Google.

Disclaimer: I have no affiliation with either Buf or Google.

Agreed, I really like Rust's Result type. Go's idea is okay, but they should force you to handle the error.

Checked exceptions were actually the "right way" to do exceptions (if there is such a thing), the problem was just that developers hated them, but I think that draws the wrong conclusion. That tells me their syntax/usage was seen as too much forced boiler plate making code unwieldy, not that they didn't have benefits for correctness (something often not appreciated until years later).

Unchecked exceptions lead to unhandled exceptions at runtime. We've all seen screens with Java programs running with tons of exceptions in the log, or worse, that crash with unhandled exceptions. This is the result of the unchecked exceptions mess, which is why I won't use languages that use them for routine error handling for anything more than trivial programs.

> When I write new code in Fil-C, I just lean into the GC all the way, which makes programming in C and C++ so much nicer. I don’t ref count, I don’t use smart pointers, I don’t free and I don’t delete. It makes these languages so much nicer!

Sure, GC's are nice which is why so many langs have them, but that removes the deterministic allocation performance which most C/C++ programmers want (and many times need). Why not just use something like Go then? You have a much richer stdlib available out of the box.

I don't have a horse in this race, but to me this makes GPT-5.6 Sol Max look better. It is about half the cost for nearly the exact same performance. It just goes to show how expensive Fable really is when Opus 5 is still this expensive relative to GPT 5.6.

I've always thought it odd that we don't use ECC as a standard on all computers. I think people really downplay the impact of memory issues. They can be devastating, especially over time. They will slowly corrupt your file system, documents, binary files, code, everything. You notice when things like your compressed files start giving CRC/checksum errors or your downloads don't match SHA-512. You are then left with this "icky" feeling. What parts of your work are compromised? Obviously this is far worse with things like binary files and structures than those built on readable text. I have normally just rebuilt my system from scratch in these instances (after fixing the issue of course), but not all our files are replaceable, and you forever and always might have corrupted files you are unaware of that got written during this time. You might not find them until years later.

As someone just starting out with the JS ecosystem, how does this compare to something like SurveyJs?