Hacker News: ImprobableTruth

New comment by ImprobableTruth in "Not everyone is using AI for everything"

ImprobableTruth — Sun, 14 Jun 2026 20:29:56 +0000

This is a very strange mindset. Even if you want to treat everything as sort of billable hours this doesn't really make sense because the average boss's boss's isn't paid anywhere near 144x. If a SWE spends 100 hours to save their boss's boss one hour, they're wasting a ton of money.

New comment by ImprobableTruth in "Notes on DeepSeek"

ImprobableTruth — Wed, 10 Jun 2026 15:19:19 +0000

Anthropic had to settle with authors because they literally pirated books! Their behavior regarding distillation is genuinely beyond parody.

New comment by ImprobableTruth in "LLMs are eroding my software engineering career and I don't know what to do"

ImprobableTruth — Sun, 07 Jun 2026 16:25:54 +0000

Except it's not just a tool.

It's when a woodworker, musician or painter completely outsources their work and just marks what's wrong, sending those parts back. Yes, the final art piece might be the same, but the artist definitely uses less of their "soul".

New comment by ImprobableTruth in "Nvidia is proposing a beast of a CPU system for Windows PCs"

ImprobableTruth — Sat, 06 Jun 2026 19:26:10 +0000

Shared memory of the past meant reserving a part of the memory for the GPU, which could then not be used or accessed by the CPU. If the CPU wanted to access something, it had to copy it from the GPU's section of the memory to its own. Unified memory means both just fully share the same memory.

New comment by ImprobableTruth in "Qwen3-Coder-Next"

ImprobableTruth — Tue, 03 Feb 2026 18:04:36 +0000

If that was the real reason, why wouldn't they just make it so that if you don't correctly use caching you use up more of your limit?

New comment by ImprobableTruth in "If you put Apple icons in reverse it looks like someone getting good at design"

ImprobableTruth — Sun, 18 Jan 2026 02:33:47 +0000

The quill and ink at least communicates that it's about writing. The new one is so abstract that when I first looked at it I had no idea what I was even looking at, it certainly doesn't communicate "this is like word" to me. Without comparison to the previous icon, how many people do you think would understand that the bottom line is intended to be a stroke drawn by the pen?

New comment by ImprobableTruth in "Show HN: I made a memory game to teach you to play piano by ear"

ImprobableTruth — Fri, 09 Jan 2026 20:53:30 +0000

The key thing is that you teach multiplication tables in a structured, incremental manner. Yes, it's just rote memorization, but the structure makes it way easier. You don't just dump all tables on the student at once and start quizzing them until they get it.

Imo not being able to select a subset of intervals to train heavily limits how useful this is.

New comment by ImprobableTruth in "GLM-4.7: Advancing the Coding Capability"

ImprobableTruth — Mon, 22 Dec 2025 22:16:48 +0000

How is the raw Gemini 3 CoT accessed? Isn't it hidden?

New comment by ImprobableTruth in "Reflections on AI at the End of 2025"

ImprobableTruth — Sat, 20 Dec 2025 14:21:55 +0000

They're not making money on inference alone because they blow ungodly amounts on R&D. Otherwise it'd be a very profitable business.

New comment by ImprobableTruth in "Jonathan Blow has spent the past decade designing 1,400 puzzles"

ImprobableTruth — Thu, 18 Dec 2025 10:55:14 +0000

> These games are the starting point, but the bulk of the game is new puzzles combining mechanics from different games together

Seems like the puzzles are novel, but the mechanics are not?

New comment by ImprobableTruth in "GPT-5.2"

ImprobableTruth — Thu, 11 Dec 2025 18:38:26 +0000

An almost 50% price increase. Benchmarks look nice, but 50% more nice...?

New comment by ImprobableTruth in "Open models by OpenAI"

ImprobableTruth — Tue, 05 Aug 2025 17:43:34 +0000

Unfortunately not, this model is noticeably worse. I imagine horizon is either gpt 5 nano/mini.

New comment by ImprobableTruth in "Typed languages are better suited for vibecoding"

ImprobableTruth — Mon, 04 Aug 2025 01:55:51 +0000

Even near-perfect LLMs would benefit from the compiler optimizations that types allow.

However perfect LLMs would just replace compilers and programming languages above assembly completely.

New comment by ImprobableTruth in "Verified dynamic programming with Σ-types in Lean"

ImprobableTruth — Sat, 21 Jun 2025 03:36:14 +0000

This is the fault of sloppy language. In Lean, _proofs_ (equivalent to functions) and _proof objects/certificates_ (values) need to be distinguished. You can't compute proofs, only proof objects. In the above quote, replace "proof" with "certificate" and you'll see that it's a perfectly valid (if trivial - it essentially just applies a lemma) proof.

New comment by ImprobableTruth in "Verified dynamic programming with Σ-types in Lean"

ImprobableTruth — Sat, 21 Jun 2025 03:28:19 +0000

Caveat: Coercions exist in Lean, so subtypes actually can be used like the supertype, similar to other languages. This is done via essentially adding an implicit casting operation when such a usage is encountered.

New comment by ImprobableTruth in "Luxe Game Engine"

ImprobableTruth — Sat, 14 Jun 2025 02:32:10 +0000

I think the concept of a game DSL is cool, but it just feels so undercooked to me.

Like, I'm a huge fan of gradual typing, especially TypeScript's, but gdscript's is just so primitive. Not even to speak of something like intersection or union types, even something basic like an interfaces mechanism is missing. has_method is an awful substitute - in general way too much relies on strings, making even simple refactoring a headache and breaks autocompletion. Lots of things also just aren't typable e.g. because generics are missing, pushing one to Variant. These aren't deal breakers, especially for the small-ish projects I've done, but it just feels bad.

A 'fully realized' version of gdscript would probably be great, but as is I'm just really not very fond of it and progress currently isn't exactly happening at a rapid pace (which is of course understandable).

Also - and this is definitely a lot more subjective - but I find its C++ FFI pretty ugly, even for basic stuff like working with structs. In theory using gsdcript as glue and C++ for the more core things would be a great approach (like unreal with its blueprints), but in practice I just want to avoid it as much as possible.

New comment by ImprobableTruth in "Next.js 15.1 is unusable outside of Vercel"

ImprobableTruth — Thu, 12 Jun 2025 12:24:41 +0000

What's the issue with the remix -> react-router transition? As far as I can tell it's just a branding thing.

New comment by ImprobableTruth in "Careless People"

ImprobableTruth — Thu, 24 Apr 2025 12:21:04 +0000

I think the fact that all (good) LLM datasets are full with licensed/pirated material means we'll never really see a decent open source model under the strict definition. Open weight + open source code is really the best we're going to get, so I'm fine with it coopting the term open source even if it doesn't fully apply.

New comment by ImprobableTruth in "Nvidia adds native Python support to CUDA"

ImprobableTruth — Sat, 05 Apr 2025 01:56:18 +0000

No, that's a different scenario. In the one I gave there's explicitly a dependency between requests. If you use gather, the network requests would be executed in parallel. If you have dependencies they're sequential by nature because later ones depend on values of former ones.

The 'trick' for CUDA is that you declare all this using buffers as inputs/outputs rather than values and that there's automatic ordering enforcement through CUDA's stream mechanism. Marrying that with the coroutine mechanism just doesn't really make sense.

New comment by ImprobableTruth in "Nvidia adds native Python support to CUDA"

ImprobableTruth — Fri, 04 Apr 2025 18:24:02 +0000

The reason is that the usage is completely different from coroutine based async. With GPUs you want to queue _as many async operations as possible_ and only then synchronize. That is, you would have a program like this (pseudocode):

  b = foo(a)
  c = bar(b)
  d = baz(c)
  synchronize()

With coroutines/async await, something like this

  b = await foo(a)
  c = await bar(b)
  d = await baz(c)

would synchronize after every step, being much more inefficient.