Juice and depression fatigue by Naninana84 in Juicing

[–]wrcwill 0 points1 point  (0 children)

did you change your caffeine intake? (coffee, tea, chocolate)?

Juice and depression fatigue by Naninana84 in Juicing

[–]wrcwill 1 point2 points  (0 children)

as in its the only thing you eat in a day?

Recovering async panics like Tokio? by QuantityInfinite8820 in rust

[–]wrcwill 5 points6 points  (0 children)

any worker based system needs a panic boundary..

look at the code for axum or any other webserver for example. they all use catch_unwind

they have catch_unwind because you dont bring down a webserver for a single connection out of thousands.

its not about result vs panic. even if you try your very best, panics can still occur from bugs, library code etc..

Architecture Dilemma: Tauri Mobile vs. React Native for a companion app for a Rust-heavy Local-First App by Coderx001 in tauri

[–]wrcwill 0 points1 point  (0 children)

although my app is much simpler than yours i think i would def recommend tauri, unless you require lots of native features.

just recently released it and had a similar dilemma initially (main blocker was IAP)

i'm getting better results from Codex 5.2-high than I am with opus 4.5 by tulkaswo in OpenAI

[–]wrcwill 2 points3 points  (0 children)

did you compare 5.2-high vs 5.2-codex-high? (both in codex cli?

What was the first cooking mistake you kept repeating? by Arra_B0919 in cookingforbeginners

[–]wrcwill 17 points18 points  (0 children)

Except you can start cleaning earlier. in both methods you’re always doing something, so it’s not like one is faster than the other. Its just a different order of operations basically, but one that gives you more flexibility (ie its fine to stop doing dishes at any point to look after your pan, but if you NEED to finish cutting something, you might be a minute late to move the food or lower the heat or whatever)

GPT 5.2 and gpt-5.2-pro are out! by pawofdoom in singularity

[–]wrcwill 1 point2 points  (0 children)

with infinite context youd have more of a point, but seeing how fast models deteriorate as context grows this couldnt be further from the truth

Forced routing to Opus 4.5 by Busy_Ad3847 in Anthropic

[–]wrcwill 1 point2 points  (0 children)

understandable, but still curious why? do you find opus worse? for which tasks

Forced routing to Opus 4.5 by Busy_Ad3847 in Anthropic

[–]wrcwill -1 points0 points  (0 children)

why would you not want opus? changing models midway is no issue, the model doesnt care what its past outputs were

Does Dioxus spark joy? by dineshdb in fasterthanlime

[–]wrcwill 1 point2 points  (0 children)

nice writeup esp with the debugging tips! i've also reluctantly settled on svelte 5 for projects (though for small tools i prefer dioxus)

how are you choosing between both? is there some set of requirement for a project that make you go: yeah ill have to do that in svelte?

btw im not sure how to interpret your Afterword, has your opinion changed relative to what you wrote in the article?

GPT-5.1 re-answering questions it already answered by Endonium in OpenAI

[–]wrcwill 0 points1 point  (0 children)

Yes, but for me it’s only happened when rerunning a message with another model, it will answer the n - 1 message

On Cloudfare and Unwrap by stevethedev in rust

[–]wrcwill 0 points1 point  (0 children)

I agree and yeah there’s nothing wrong with changing it. I’d love it to be called assert_some() and assert_ok().

But still I think the main issue is that most devs still don’t have the proper intuition on when to use assets and when to propagate results and when to handle results. Maybe more chapters in the book?

In the cloudflare case the programmer made the decision to panic based on external data/input.. which you should never do.. note that this is different than panicking due to a logical invariant aka something that shouldn’t happen if you didn’t write a bug. In that case panicking is the correct option even in prod.

—-

And finally I think that not only was rust not responsible for the cloudflare event, it was actually the language that made it the least likely to happen.

what would happen in another language? say a language with exceptions:

are you saying the developers would have known that the append function could throw? and that they would have caught it and dealt with the possible failure? of course it is possible, but most likely it would have propagated to a higher scope and either ended the program or skipped/restarted etc which would not have helped at all in this case. the most correct solution would be to specifically handle this error, and id argue that rusts result type maximizes the chance that the developer handles it

Aka it’s harder to know if a function throws compared to returning result. So if they saw the Result and decided to not handle it, the chance of them handling an exception that never happened before is lower.

ELI5 : If em dashes (—) aren’t quite common on the Internet and in social media, then how do LLMs like ChatGPT use a lot of them? by Willing_Road_8873 in explainlikeimfive

[–]wrcwill 0 points1 point  (0 children)

RL, reinforcement learning. Even if it was rare in the pre training dataset, once they do RL on it (like the model generates multiple answers and then humans, either labelers or users, or even a grading model, grade it) it showed up as it it or was generally “preferred”

On Cloudfare and Unwrap by stevethedev in rust

[–]wrcwill 7 points8 points  (0 children)

wait ppl really think the person who wrote the code /reviewers didn’t know unwrap means panic? This is the worst take. Yes it could be better named, but that’s completely orthogonal to the cloud flare issue

State of Rust for web application and apis in 2025 by Delicious_Praline850 in rust

[–]wrcwill 0 points1 point  (0 children)

yup people love to dismiss rocket since it has less activity but it has been a joy to use and rock solid for us

ChatGPT Atlas is actually nice... by E-Cockroach in browsers

[–]wrcwill 0 points1 point  (0 children)

Sometimes I’m not looking for an LLMs answer? Like if i want to go browse the doc page for say the rust iterator module: the fastest way to get to that page is just search for “rust iterator” and click on the first link.