251–260 of 526 posts
Earlier quoted context omitted.
You can use the weather widget on the lock screen, and as long as you have lock screen content when locked enabled, you can see the current area's weather just fine. Or do you want the whole app experience?
I'm a little too lazy to experiment, but it wouldn't surprise me if that widget didn't function normally until the phone is unlocked.
Earlier quoted context omitted.
Unrelatedly, I'm still trying to figure out why Apple requires me to unlock my phone to look at the weather. Is there some concern that someone could pick up my phone and learn what city it is in?
You want to be able to launch apps without unlocking your phone? Slippery slope.
Earlier quoted context omitted.
Google announced that Android contains 5 million lines of Rust last year; sounds Tier-1 to me.
Android is a bit special inside Google (also Chromium). They are managed outside the main monorepo (google3) and their policies are different. From what people inside Google have told me, they do want to introduce Rust into google3 but that work has only begun.
Earlier quoted context omitted.
Whether vibecoded Rust will be better than whatever they are doing now remains to be seen.
The question in terms of memory is, will vibe coded rust get around ownership issues by .clone()-ing everything. Maybe this has changed since I wrote Rust, but that was a classic beginner fix. Just throw memory at it.
The point of these low/zero overhead languages like Rust is you're in an environment where memory management is ultra critical. The dotnet garbage collector does more than a good enough job for a weather app, likely a much better one than vibe coded .clone() Rust
Instead of oscillating between Rust and 1 GB webview apps just ... use the excellent managed language that exists on the operating system appropriate for GUI applications?
Earlier quoted context omitted.
https://github.com/luser/keep-calm-and-call-clone "Keep calm and call clone" is a good strategy for getting things working. Don't prematurely optimize code until you know it's the bottleneck.
There's premature optimisation, where you write a whole bunch of complicated code to avoid cloning an Arc . And then there's "premature optimisation" where you skip any consideration for performance until it becomes a problem. The latter is usually what people who use the quote "premature optimisation is the root of all evil" think it means. Don't just keep calm and clone, consider what you're cloning and why, and th…
Earlier quoted context omitted.
Where did you hear that it got pushed back out? It's going strong as far as I can tell.
I was thinking of the public clash in 2025 between Christoph Hellwig which lead to the resignation of Hector Martin, lead of the Asahi Linux project. It looks like later, in December 2025, Rust was officially moved from experimental to official: https://lwn.net/Articles/1049831/
I hope announcements like this show that Rust is not a fledgling little language that moves fast and breaks things anymore. It's a mature, serious competitor to well established languages like C++ and C#. This is particularly important when trying to compare the experience of using Rust to other languages in the "better C/C++" space like Zig and Odin -- these are much newer and have more rough edges than Rust.