06:02 <re_irc> <gauteh> Hi, are there other debugger than jlink that can do RTT?

06:06 <re_irc> <gauteh> I've written up the ocean wave buoy on hackster.io, firmware and data written in Rust: https://www.hackster.io/gaute-hope/ocean-buoy-to-measure-waves-drift-using-low-power-cellular-16ad09

06:42 <re_irc> <firefrommoonlight> I can't do it. Guys. I really am tryign with an open mind

06:43 <re_irc> <firefrommoonlight> I can't see Async in Rust as anything beyond a virus

06:43 <re_irc> <firefrommoonlight> I'm sorry

06:43 <re_irc> <firefrommoonlight> I've made an effort for the past 1-2 months

06:43 <re_irc> <firefrommoonlight> I can't

06:43 <re_irc> <firefrommoonlight> It's poison

06:43 <re_irc> <firefrommoonlight> It risks fragmenting the whole lang

06:44 <Shell> you're like 2 years late with that criticism. :p

06:44 <re_irc> <firefrommoonlight> Hah sorry I deleted

06:44 <re_irc> <firefrommoonlight> Kind of drunk atm

06:45 <re_irc> <firefrommoonlight> I stand by what I posted, but I shouldn't

06:45 <re_irc> <firefrommoonlight> I really _have_ tried

06:45 <re_irc> <firefrommoonlight> I think there's 2 futures for Rust, and I will participate in one of them

06:47 <re_irc> <firefrommoonlight> I think even if it spreads to most of the dependencies, we can continue using Rust with the part that is clean

06:48 <Shell> 2 "futures" ha ha ha

06:50 <Shell> realistically, yeah, though. I've got a mostly-sync application which uses some async stuff via block_on functions and... I can tell that's going to be a source of really weird bugs.

07:19 <cr1901> I remember reading once- from someone big into async Rust's design- that "one of the reasons Rust went so hard into async APIs was because 'that's where the funding was outside of Mozilla'".

07:20 <re_irc> <K900> Honestly, I don't think async Rust is _fundamentally_ broken

07:20 <re_irc> <K900> It's definitely kind of janky

07:21 <re_irc> <K900> But that's not really a core design issue, it's mostly a diagnostics and borrowck issue

07:22 <re_irc> <K900> The core design I think is pretty sound, and the fact that it actually works on embedded is extremely jicen

07:22 <re_irc> <K900> * nice

07:23 <cr1901> The ppl who did the design of async Rust took _a lot_ of shit over bikesheds like "postfix await". I try not to gripe too much about it (and honestly, I think "async Rust is fine").

07:34 <re_irc> <K900> Honestly, postfix await is great

07:34 <re_irc> <K900> I wasn't sold on it at first

07:34 <re_irc> <K900> But after writing some code with it, I'm 100% converted

07:36 <Shell> I thin async Rust is fine too tbh

07:36 <Shell> what I don't think is fine is that any library that vaguely touches the network for a second is now async

07:46 <re_irc> <9names (@9names:matrix.org)> gauteh: yep, any debugger can do RTT. CMSIS-DAP, STLink.

07:47 <re_irc> <9names (@9names:matrix.org)> if it can read memory, it can do RTT