hugmynutus

wait list, then it releases, and you get 10 api requests *per day*.

Until you've spend $100-150 on their platform. Then you get 250 per day until you spend $2000 and it becomes properly unlimited.

It is really annoying. I'm literally trying to pay you for a service and you won't let me.

writing a macro to implement most common integers would've been a time saving.

I also appreciate your paper/work on bf-tree, I started a hobbyist filesystem based on it.

[flagged]

There are not-for-profile municipal utility operators in California. They form NCPA (Northern California Power Agency), the largest stake holder is SVP (Silicon Valley Power) a.k.a. The City of Santa Clara.

Something a lot of transplants don't learn for years: Palo Alto, Santa Clara, and Alameda are members of NCPA, so you don't pay PG&E, amusingly PG&E pays NCPA for access to its hydro and geothermal.

> Pretty sure there was even a Need for Speed game on Frostbite

7 if wikipedia is to be trusted

blaze/bazel doesn't support incremental crate compilation. It also can't, by design, as incremental compilation depends on incremental change to local build artifacts which isn't deterministic.

So a single crate has to be as small as possible so builds are fast & cachable.

Apple puts the NAND flash controller on package, so it cooled as part of the SoC/CPU as they share an IHS. Given it is part of the fabric it only has to maintain signal coherence on millimeter to micrometer scales, while enterprise/consumer NAND PCIe have to adhere to standards which force them to signal at 800-1200mV and keep that signal stable for centimeter scale distances.

Basically, Apple gets to cheat because they shove everyone onto the same IC & make the OS that runs on this SOC.

Qwen3.8/Qwen3.6 has a weird self doubt/thinking too much problem. You can prompt it away. I would say it "approximates" Opus 4.X class models well enough especially for coding/linux problems.

The only reason I stopped using it as much is I was getting 25-35tok/s on Intel B70 (non-quant) which made some responses slow. For a long running/autonomous task, it would probably be sufficient.

If they did not use my data for training, they should permit me to run the first 1-3 layers of the model locally and send them dense hidden state vectors. In my experience these compress very nicely without much effort.

Nullius in verba

Because nobody knows.

Apple doesn't let you "pass" the GPU through to a VM like most other ARM/x86_64 processors (forwarding interrupts and PCIe memory regions). There are symbols defined to do this within the kernel (if you dump the binary) but they aren't used in retail macos.

Instead you end up creating a paravirtual device that emulates the GPU acting like a 'normal PCI device' which you give to clients. This is usually reserved (by other hardware vendors) for when you're doing multi-tenat time sharing of higher end GPUs (like Nvidia enterprise cards can do).

These paravirtualized GPUs then just have 'less features' and Apple (being Apple) states no reason why.

> I’m curious if you have an opinion on how you think this should be handled?

To "totally overcomplicate things" but do it correctly

- Binary states a list of constraints (namespace:name [<|>|>=|<=|!=] semver). - ldconf/ld.so either integrate into your package manager and/or are easier to update (I'm not writing conf files by hand and/or flakes). I should simply be able to recursively scan. - Give the runtime linker an SMT constraint solver (when <1000 this is nearly instant) - Cache known states to avoid solving NP hard problems every time you launch `cat`.

> At this point I’m just on team static linking or Windows DLL black box style. The Linux approach of dynamic libraries which function same as static is just the worst of every world.

Honestly same.

Having the package manager <-> elf runtime <-> shared libraries more-or-less be a blackbox is probably for the best (which is sort of what windows does with the install-shield/install-wizard stuff). But nobody in Linux Land really wants to "improve" userland, other then change to flavor-of-the-month display managers.

> I also blame C/C++ toolchains for being very very bad on Linux.

They honestly aren't, it is more your pacakge manager *is* your library manager. Because of the absolute bullshit of shared libraries.

If you pretend it is the 1970/80s everyone at your company has the architecture, unix version, etc. It is pretty nice. No cross compiling, multiple OSs, everything just sort of works pretty well. But like I said, "pretend".

Shared Dynamic Libraries. Not to say they aren't useful. Keeping applications small, keeping security updates simple, sub linear ram scaling, yada-yada-yada, big wins cross the board, not debating that.

The pervasive link detection structure of effectively everything on GNU/Linux assumes is (more-or-less) objectively incorrect behavior in any sane security minded context. Binaries should be able to declare the interface/contract they expect (args/types/abi/exceptions/cryptographic signatures/digests). Then the runtime linker "match" against the local system. The current system is basically 2 levels of string equality checking.

Nix goes into the right direction by getting your runtime linker/elf-runtime & package manager "integrated". But this sort of just feels like putting 'lipstick on a pig' and dancing around the core issue that `foo.exe` cannot ever realize `foobar-v1.8` and `foobar-v1.7` are both installed on the same computer. Nix just manages the environment/symlinks such that `foo.exe` doesn't realize this fact.

HN is rightly pointing out putting a model into an ASIC is kind of dumb.

HN is failing to understand that AMD knows this well.

Taalas has WO2025217724A1 pending and AMD wants that because it is immediately a function block they can sell to anyone doing FP math, since large (mostly) read only memory banks are ideally suited for that micro-code type stuff.

yellow/red tint is an extremely common problem not matter the photograph source you train on

source: work at a photograph start, even training on raw images things get tinted, it is an uphill battle