News for hackers. Stuff that matters.

rc00

Re:Dissecting the Apple M1 GPU, the end on Wednesday August 27, 2025 @01:22AM (#45035727)
I would hope not. That would mean that no other vendor has shipped working ARM hardware support for Linux or has upstream support in the kernel. Forget the hostile nature Apple has proven to possess when consumers dare treat their hardware as if paying for it makes it their own.

Qualcomm has been beating the marketing drum on this instead of delivering. Ampere has delivered excellent hardware but does not seem interested in the desktop segment. The "greatest Linux laptop around" can not be some unmaintained relic from a hostile hardware company.

Re:Introducing tmux-rs on Thursday July 03, 2025 @09:31PM (#44460439)
What adoption? Blog posts? Echo chambers? Rust peaked. The hype pushers don't want to believe it but that is the reality. Absolutely zero shade to Rust.
Re:Datalog in Rust on Sunday June 15, 2025 @09:05AM (#44282112)
And Rust is the perfect lingua franca to accomplish this.

The demise of both of these trends cannot come soon enough.

And Rust is the perfect lingua franca to accomplish this. The demise of both of these trends cannot come soon enough.
Re:Lazarus Release 4.0 on Sunday May 11, 2025 @01:45PM (#43955464)
> What are my options?

> I stick with Qt

These come up on search results if you combine Qt plus the language.

Go:

* https://github.com/mappu/miqt

Java:

* https://github.com/OmixVisualization/qtjambi

Nim:

* https://github.com/jerous86/nimqt

* https://github.com/seaqt/nim-seaqt

Zig:

* https://github.com/rcalixte/libqt6zig

Re:Rust Dependencies Scare Me on Friday May 09, 2025 @04:24PM (#43940573)
You should evaluate on whether it is worth insisting on Rust. Others have gone down that path and it has only ended with regret[1]. The sooner you realize that you don't have the right solution to your problem, the sooner you can start solving it correctly.

What about the crypto library affects how you would use Go to solve your problem?

1. https://deadmoney.gg/news/articles/migrating-away-from-rust

Re:Rust Dependencies Scare Me on Thursday May 08, 2025 @04:12PM (#43930805)
> Many call for adding more to the rust standard library much like Go

> So now I pose the question to you what do we do?

1. Port your application to the language/tool that fits your needs like Go.

2. Hope that a language like Zig decides to feature a standard library as good as Go.

Re:Ty: A fast Python type checker and language server on Wednesday May 07, 2025 @10:03PM (#43922425)
The timing of the recent batch of propaganda makes it hard to believe it's not coordinated. I wouldn't suggest paid actors but maybe just an attempt to counter some fairly visible and negative recent takes. The amount of "I love Rust but" comments make it hard to take the commentary seriously too.
> and then submitted here by someone

> I just don’t care about karma that much. The first 500 is the only that matters. I find it hard to say that submitting a story that people found valuable is “abuse.”

The submitting account is automated and mostly non-deterministic. Forget the fake internet points and focus on the fact that there are accounts on this site that mostly exist to spam. Isn't the value of this site that humans curate what is posted? Or is automating submissions not a form of abuse? Good to know where your ethics are.

> This was posted by its author to /r/rust and then submitted here by someone because if a post does well over there, it often does well over here. That’s not “karma abuse”.

Except the submitter account in question is actually automating submissions from what looks like Lobsters (based on the timing and posting history). The account owner only seems to post non-automated comments to spam their product. This looks an awful lot like abuse. Or is abuse okay when you perceive it to be beneficial to Rust propaganda?

Re:Reflecting on a Year of Gamedev in Zig on Friday May 02, 2025 @03:37PM (#43873856)
> It refutes the idea that the "developer joy is pretty low" either way.

https://deadmoney.gg/news/articles/migrating-away-from-rust

https://loglog.games/blog/leaving-rust-gamedev

https://www.boringcactus.com/2025/04/13/2025-survey-of-rust-...

https://gist.github.com/rtfeldman/77fb430ee57b42f5f2ca973a39...

https://medium.com/@rusty-vibes/part-4-abandoning-rust-for-c...

A pile of evidence refutes your statement. There is more if you need.

> I'm happy to revise what I said from "Rust keeps winning" to "Rust continually won"

"Rust has peaked"

Re:Reflecting on a Year of Gamedev in Zig on Friday May 02, 2025 @03:16PM (#43873678)
Your link is from 2023 and references 2022. (It is also much more of an advertisement for Rust than anything else.)

The one I shared before that is from late 2024. What are you trying to say other than Rust has peaked?

+1 for Stern especially since it only has Go dependencies whereas Kubetail does not. Ease of integration with an existing stack is a bigger addition than the lack of a web UI is a subtraction.
Re:Elixir is not owned by Big Tech on Wednesday April 30, 2025 @06:37AM (#43843300)
> I think Zig is mostly community-driven and seems to have some traction. Not Rust levels of traction but definitely relevance.

Zig already appears to have lapped Rust in areas like game development, GUIs, compilation speeds, C FFI, etc. and all that despite Zig not yet being 1.0. That means backwards compatibility is not guaranteed until then nor is the full feature set fully defined. Notwithstanding that 1.0 release, traction and relevance only seem to be a matter of time.

Re:A Visual Journey Through Async Rust on Friday April 25, 2025 @08:57AM (#43793084)
Re:Atuin Desktop: Runbooks That Run on Tuesday April 22, 2025 @08:56PM (#43767694)
What more do you need than "written in Rust"?
Re:Atuin Desktop: Runbooks That Run on Tuesday April 22, 2025 @05:56PM (#43766699)
Because it's written in Rust and this is Hacker News.
Re:Things Zig Comptime Won't Do on Sunday April 20, 2025 @03:22PM (#43745891)
> What in particular do you find cumbersome about the borrow system?

The refusal to accept code that the developer knows is correct, simply because it does not fit how the borrow checker wants to see it implemented. That kind of heavy-handed and opinionated supervision is overhead to productivity. (In recent times, others have taken to saying that Rust is less "fun.")

When the purpose of writing code is to solve a problem and not engage in some pedantic or academic exercise, there are much better tools for the job. There are also times when memory safety is not a paramount concern. That makes the overhead of Rust not only unnecessary but also unwelcome.

Re:Things Zig Comptime Won't Do on Sunday April 20, 2025 @03:10PM (#43745821)
Are you referring to static linking? Dynamic linking? Importing/inclusion? How does this translate (no pun intended) when the LLVM backend work is completed? Does this extend to reproducible builds? Hermetic builds?

And the relationship with C libraries certainly feels like a placeholder, akin to before the compiler was self-hosted. While I have seen some novel projects in Zig, there are certainly more than a few "pure Zig" rewrites of C libraries. Ultimately, this is free will. I just wonder if the Zig community is teeing up for a repeat of Rust's actix-web drama but rather than being because of the use of unsafe, it would be due to the use of C libraries instead of the all-Zig counterparts (assuming some level of maturity with the latter). While Zig's community appears healthier and more pragmatic, hype and ego have a way of ruining everything.

Re:Things Zig Comptime Won't Do on Sunday April 20, 2025 @02:26PM (#43745514)
Open source or not isn't the point. The point is the mission and the ecosystem. Some of the Zig proponents laud the C compatibility. Others are seeking out the "pure Zig" ecosystem. Curious onlookers want to know if the Zig ecosystem and community will be as hostile to the decades of C libraries as the Rust zealots have been.

To be fair, I don't believe there is a centralized and stated mission with Zig but it does feel like the story has moved beyond the "Incrementally improve your C/C++/Zig codebase" moniker.

Re:Things Zig Comptime Won't Do on Sunday April 20, 2025 @01:42PM (#43745224)
Is Zig aiming to extend C or extinguish it? The embrace story is well-established at this point but the remainder is often unclear in the messaging from the community.
Re:Four Years of Jai on Friday April 18, 2025 @08:04AM (#43727276)
I can see the appeal if there is a need for stronger metaprogramming. Not that Zig is terrible in this area, it is just that Jon's language is much more powerful in that area at this stage.

That being said, I do see an issue with globally scoped imports. It would be nice to know if imports can be locally scoped into a namespace or struct.

In all, whether it's compete or coexist (I don't believe the compiler for Jon's language can handle other languages so you might use Zig to compile any C or C++ or Zig), it will be nice to see another programming language garner some attention and hopefully quell the hype of others.

Rewrite it in Zig? You might even be able to sidestep the LLVM bottleneck entirely. https://news.ycombinator.com/item?id=43016944
Re:A 2025 Survey of Rust GUI Libraries on Tuesday April 15, 2025 @04:39PM (#43698100)
Or don't use Rust. There are better and more supported options if you don't try to force a language where it clearly doesn't belong.
> Regardless, my point was that Rust _the language_ does not provide garbage collection.

These are language features not dependencies or external libraries. Maybe the best phrasing is that Rust's garbage collection features are opt-in, similar to the same features being opt-out for Go, Nim, OCaml, and others.

GLib is an external library to C and C's standard library. Arc/Rc (and there are other types of garbage collection within Rust _the language_) are language features since they are built-in types.

The delineation is very clear here. If it is part of the language's standard features and/or standard library then it is part of the language. Using opt-in/opt-out terminology also make clear how the garbage collection features are available. In Rust, you opt into garbage collection by using specific built-in types.

Older »