matze 

@matze
52 Followers
108 Following
325 Posts
Plays software and develops bass
webhttps://bloerg.net
githubhttps://github.com/matze
@jhpratt you can hide the navigation bar by ending the advanced gestures (forgot the name) where everything is done via thumb gestures. That one took me some more getting used to.
@jhpratt no idea who decided that but it's been a long time like that. You get used to it.
Die Sponsoren des CDU-Parteitages. Sie singen das hohe Lied des Mittelstands, und nehmen Pinke von Amazon, Google und anderen Konzernen, in denen BlackRock Aktien hat. Dazu kommen Lobbyclubs wie der Verband der Automobilindustrie und der der Rauchwaren. 64 sind es ingesamt.
Und das Irre: Die Partei muss noch nicht mal angeben, wie viel dabei zusammenkommt. Denn das sind keine Spenden, sondern Sponsoring. Muss man nicht verstehen.
#cdu #parteitag
@ctietze cool tool and a dependency stack I use a lot in my own projects but … why does it mess with newlines? Carefully crafted README.md's with 80 character line lengths become an unreadable mess.
@katzenmann there is jiff and it is reasonable.
Rust on Z80: From LLVM Backend to Hello World

The journey from a working LLVM Z80 backend to actually compiling Rust code for an 8-bit processor from 1976. Includes the hardware requirements that surprised us, the creative workaround that made it

TinyComputers.io

Starting tomorrow, you will be able (on linux without cross-compilation) to install and use the Rust GCC backend directly from rustup! To do so:

rustup component add rustc-codegen-gcc

Thanks a lot to Kobzol for all their work to making it a reality!

https://github.com/rust-lang/rust/pull/151156

#rust #gcc

Add GCC and the GCC codegen backend to build-manifest and rustup by Kobzol · Pull Request #151156 · rust-lang/rust

This PR adds the GCC codegen backend, and the GCC (libgccjit) component upon which it depends, to build-manifest, and thus also to (nightly) Rustup. I added both components in a single PR, because ...

GitHub
@laund @argv_minus_one @chmod777 no one disagrees that tokio is large and complex. But, the fact of the matter is that tokio is used where it makes less sense and tend to be used synonymously with "async Rust" which at the end makes people think that's why async Rust is bad and difficult. Second, can you show me some data that proves that crates are becoming less runtime-dependent? It's not my impression.
@argv_minus_one @chmod777 the decision that every Future spawned as a tokio task requires viral Send+Sync because of its underlying work stealing concurrency model. That's the root cause for the borrowing pain and subsequent Arc<Mutex<…>> or actor bandaids you see in virtually all tokio-based async programs.
@chmod777 yes I mean embassy. Alternatives? Writing manual state machines? Sounds masochistic but each to their own.