Hacker News: 3836293648

New comment by 3836293648 in "Elixir v1.20: Now a gradually typed language"

3836293648 — Thu, 04 Jun 2026 14:24:42 +0000

> I've not even heard of compile times being significantly slowed by type checking.

Look at Swift. But yeah, Swift is the only language I've ever heard having compile time issues because of the type checking.

New comment by 3836293648 in "Elixir v1.20: Now a gradually typed language"

3836293648 — Thu, 04 Jun 2026 14:23:45 +0000

Types always have to be checked. Either at compile time or at runtime. And if you're weakly typed you still check them to see if you use normal or backup behaviour.

If you're statically typed you can remove the actual check from the binary. They are therefore also a performance thing.

New comment by 3836293648 in "Elixir v1.20: Now a gradually typed language"

3836293648 — Thu, 04 Jun 2026 02:32:09 +0000

Because the BEAM has much more to it than a terrible dynamic type system?

New comment by 3836293648 in "Blorp Language"

3836293648 — Mon, 01 Jun 2026 16:29:42 +0000

No, significant whitespace today is still terrible, coming from Haskell, Python and Go (newlines that break expressions unreasonably)

New comment by 3836293648 in "Zig: Build System Reworked"

3836293648 — Sat, 30 May 2026 14:51:28 +0000

You are entirely right here, you're also incredibly rude. Please don't bother replying when the only thing you're actually doing is being condescending and spreading negativity

New comment by 3836293648 in "Using AI to write better code more slowly"

3836293648 — Tue, 26 May 2026 14:44:22 +0000

If you're not shipping faster it's meaningless for the company.

And if you are, it's bad for the employee.

Is what the above comment actually said.

New comment by 3836293648 in "Project Glasswing: An Initial Update"

3836293648 — Sat, 23 May 2026 00:25:17 +0000

I hope this will never be the case. As long as we have personal vehicles they should be personally controlled. Self driving cars is such a waste of everyone's money.

Cities should all have better public transport and out in the middle of nowhere you don't need self driving anyway. (And yes, personal cars should be entirely banned from cities)

New comment by 3836293648 in "Learnings from 100K lines of Rust with AI (2025)"

3836293648 — Thu, 21 May 2026 06:53:07 +0000

It's a set of asserts that are a part of the type signature. Requires are asserts on the inputs, ensures are asserts on the outputs.

Depending on your backend you either ignore them, check them all of the time, some of the time, or have SMT-solvers prove that if you uphold the first one all else must follow.

If you're interested in the last one, have a look at Dafny[0]

[0] https://dafny.org/

New comment by 3836293648 in "Cursor Introduces Composer 2.5"

3836293648 — Tue, 19 May 2026 07:08:59 +0000

Price to performance?

New comment by 3836293648 in "Native all the way, until you need text"

3836293648 — Sun, 17 May 2026 17:36:14 +0000

The typescript compiler is a typescript app. Or was, I guess

New comment by 3836293648 in "LLM Policy for Rust Compiler"

3836293648 — Fri, 15 May 2026 18:23:43 +0000

Then don't go interact with the social club?

If you want to interact with their project, follow their rules on their terms, otherwise just grab the binaries and don't stir things up.

New comment by 3836293648 in "Reverting the incremental GC in Python 3.14 and 3.15"

3836293648 — Wed, 13 May 2026 22:56:26 +0000

> X is a terrible language because of the lack of static analysis available.

> (Mocking) Yes, that's why we should go back to Y with even worse static analysis.

Sure

New comment by 3836293648 in "Show HN: Countries where you can leave your MacBook at a random coffee shop"

3836293648 — Tue, 12 May 2026 18:18:36 +0000

That applies to everywhere except for like the Vatican or Monaco. The US is not special

New comment by 3836293648 in "Async Rust never left the MVP state"

3836293648 — Fri, 08 May 2026 13:46:30 +0000

Everyone doesn't use tokio. Almost everyone on desktop/server uses tokio, with a few macos specific things wrapping grand central dispatch. But the embedded world is full of custom runtimes.

New comment by 3836293648 in "Show HN: TRUST – Coding Rust like it's 1989"

3836293648 — Thu, 07 May 2026 14:18:59 +0000

This needs to have DOS builds available. Is it performant enough for 90s hardware? I know the rust compiler itself isn't really.

New comment by 3836293648 in "Embedded Rust or C firmware? Lessons from an industrial microcontroller use case"

3836293648 — Mon, 04 May 2026 08:29:17 +0000

Not technically. But that's not the issue. The issue is that trait resolution and imports are treated inconsistently and that is a mistake.

Compare to [this](https://play.rust-lang.org/?version=stable&mode=debug&editio...)

New comment by 3836293648 in "Brain scans reveal 3 ADHD subtypes"

3836293648 — Mon, 04 May 2026 08:22:51 +0000

Merging autism and aspergers was not a mistake. There wasn't at the time enough science to separate them.

There are separations to be made within autism, absolutely 100%, but the separations they hade made were also definitely 100% wrong.

New comment by 3836293648 in "Embedded Rust or C firmware? Lessons from an industrial microcontroller use case"

3836293648 — Mon, 04 May 2026 06:02:24 +0000

Oh, yes of course. Switching to String and it works as I expected.

I thought the builtins were defined in core and reexported by the prelude (they are defined in core, they're just implicitly in scope anyway).

But I still think expected behaviour is that builtins should have the same precedence as the prelude.

New comment by 3836293648 in "Unsigned sizes: A five year mistake"

3836293648 — Mon, 04 May 2026 05:53:28 +0000

Don't they get promoted to short?

New comment by 3836293648 in "Embedded Rust or C firmware? Lessons from an industrial microcontroller use case"

3836293648 — Sun, 03 May 2026 22:20:02 +0000

Oh, wow. I am wrong. So much of the rust community must be wrong as this is commonly mentioned when discussing breakage. This is awful.

But on the other hand, it could be a bug as the trait resolver is commonly mentioned as the buggiest part of the language. I'm scared of the breakage if they fix it though.