(#huts53q) @shinyoukai@neko.laidback.moe But I thought Alpine was one of the good distroâs left. đą Whatâs it doing wrong?
#deggq7a
If this user/feed is violating this Pod's (yarn.meff.me) community guidelines as set out in the Abuse Policy, please report them immediately!
You are also free to Unfollow or Mute this user or feed. Muting will also remove that user/feed's content from your view and you will no longer see content from that user/feed anywhere.
@vain does not follow you (they may not see your replies!)
(#huts53q) @shinyoukai@neko.laidback.moe But I thought Alpine was one of the good distroâs left. đą Whatâs it doing wrong?
(#dddn3ja) @kiwu@twtxt.net Assembly is usually the most low-level programming language that you can get. Typical programming languages like Python or Go are a thick layer of abstraction over what the CPU actually does, but with Assembler you get to see it all and you get full control. (With lots of caveats and footnotes. đ )
Iâm interested in the boot process, i.e. what exactly happens when you turn on your computer. In that area, using Assembler is a must, because you really need that fine-grained control here.
(#knxgcuq) @kiwu@twtxt.net Finally doing some Assembler again. đ Just a tiny little bit at least.
(#iaunzca) @lyse@lyse.isobeef.org Yeah, well, given that I didnât need this for such a long time, itâs probably not an essential tool. đ
Iâve often wanted to have an outline of text documents, though, and tagbar/ctags can do that as well:
https://movq.de/v/3c6d1a13d6/tagbar-md.png
https://movq.de/v/abc58e6d66/tagbar-latex.png
This isnât as powerful as the âNavigatorâ tool in StarOffice/LibreOffice (which can be used to rearrange the document), but still pretty useful:
https://www.uninformativ.de/blog/postings/2024-05-23/0/so31.mp4
(#7sw2ifq) @lyse@lyse.isobeef.org Awww, 03.jpg. đ Yeah, we also had a nice sunset. I was on the road, though, so no photos.
(#iaunzca) Ooooooooooh! If your .vimrc is as messy as mine, youâll be pleased to learn that Tagbar can show a sorted list of all key mappings:
https://movq.de/v/0f37d13a01/s.png
đ€Ż
(#ftqfrta) @prologic@twtxt.net It is, yes.
(#ftqfrta) I rewrote all my solutions in Rust (except for day 10 part 2) and these are the runtimes on my i7-3770 from 2013 (this measures CLOCK_PROCESS_CPUTIME_ID, not wallclock):
day01/1 [ 00.000501311] Result: 1066
day01/2 [ 00.000400298] Result: 6223
day02/1 [ 00.000358848] Result: 12586854255
day02/2 [ 00.000750711] Result: 17298174201
day03/1 [ 00.000106537] Result: 17405
day03/2 [ 00.000404632] Result: 171990312704598
day04/1 [ 00.000257517] Result: 1626
day04/2 [ 00.007495342] Result: 9173
day05/1 [ 00.000237212] Result: 505
day05/2 [ 00.000142731] Result: 344423158480189
day06/1 [ 00.000229629] Result: 4076006202939
day06/2 [ 00.000279552] Result: 7903168391557
day07/1 [ 00.000204422] Result: 1622
day07/2 [ 00.000283816] Result: 10357305916520
day08/1 [ 00.029427421] Result: 84968
day08/2 [ 00.028089859] Result: 8663467782
day09/1 [ 00.000310304] Result: 4764078684
day09/2 [ 00.015512554] Result: 1652344888
day10/1 [ 00.000796663] Result: 375
day10/2 [ --.---------] Result: 15377 (Z3)
day11/1 [ 00.000416804] Result: 753
day11/2 [ 00.000660528] Result: 450854305019580
day12/1 [ 00.000336081] Result: 577
day12/2 [ 00.000000695] Result: no part 2
A little under 90 ms total.
On my Samsung NC10 netbook from 2011 with its Intel Atom N455 at 1.6 GHz:
day01/1 [ 00.003771326] Result: 1066
day01/2 [ 00.003267317] Result: 6223
day02/1 [ 00.003902698] Result: 12586854255
day02/2 [ 00.006659479] Result: 17298174201
day03/1 [ 00.000747544] Result: 17405
day03/2 [ 00.002737587] Result: 171990312704598
day04/1 [ 00.001263892] Result: 1626
day04/2 [ 00.044985301] Result: 9173
day05/1 [ 00.001696761] Result: 505
day05/2 [ 00.000978962] Result: 344423158480189
day06/1 [ 00.001387660] Result: 4076006202939
day06/2 [ 00.001734248] Result: 7903168391557
day07/1 [ 00.001295528] Result: 1622
day07/2 [ 00.001809659] Result: 10357305916520
day08/1 [ 00.277251443] Result: 84968
day08/2 [ 00.284359332] Result: 8663467782
day09/1 [ 00.003152407] Result: 4764078684
day09/2 [ 00.071123459] Result: 1652344888
day10/1 [ 00.005279527] Result: 375
day10/2 [ --.---------] Result: 15377 (Z3)
day11/1 [ 00.003273342] Result: 753
day11/2 [ 00.005139719] Result: 450854305019580
day12/1 [ 00.002857552] Result: 577
day12/2 [ 00.000004421] Result: no part 2
A little over 700 ms total.
I like this. You get performance thatâs more or less in the ballpark of C, but without the footguns.
If your very popular project with lots of stars on GitHub is over 10 years old, and youâre still at a pre-1.0 version because youâre using SemVer and a 1.0 would mean making some kind of commitment and thatâs somehow not desirable for you, then I think youâre doing something wrong. đ€
Got a nice conspiracy theory for you:
https://mastodon.social/@mcc/115670290552252848
Actually wait I just thought about this and realized that the precise timing of the ACTUAL GitHub seed bank, by which I mean the Arctic Code Vault, on 2020-02-02, makes it more or less a perfect snapshot of pre-Copilot GitHub. Also precisely timed before we all got brain damage from COVID. This is the only remaining archive of source code by people with a fully working sense of smell
(Bonus points because the Arctic World Archive is located in Svaldbard and thatâs the name of the AI in Stacey Kadeâs âCold Eternityâ.)
(#fqh5rnq) @prologic@twtxt.net How on earth did you do that so quickly, especially day 10? People were struggling with this a lot. đ€Ż
(#fqh5rnq) @prologic@twtxt.net Jesus, that was quick. đ
(#te6p5oa) @prologic@twtxt.net How did you optimize that? đ€
H⊠Ho⊠How have I not heard about vim-tagbar before? đł
(#4bg5k7a) Bought more cheap slot plates (with bad reviews and people complaining about the pin order, because I couldânt find a product without such reviews), but those are simply correct now and just work. đ€Ș
(#qtm4cqq) (Well, one part late in the calendar might need floats, depending on how you solve it âŠ)
(#qtm4cqq) @prologic@twtxt.net You wonât need floats, but 64 bit integers are mandatory. đ
(#ruoopea) @prologic@twtxt.net Whoop, whoop! Nice! And welcome back. đ
Iâm seeing crashes in the 3D subsystem. (Gallium? Glamor? Whatever other Mesa thing they have? No idea.) In the logs I find this:
malloc(): unaligned tcache chunk detected
And thatâs why I still care about Rust and want to learn more about it, even though itâs giving me so much headache and Iâve given up so many times. Because Rust currently seems to be the only popular systems programming language that tries to eliminate these error classes.
And of course âthe Rust experimentâ in the Linux kernel has recently been concluded as âsuccessfulâ, so that alone is reason enough for me:
(#ftqfrta) Alright, Advent of Code is over:
https://www.uninformativ.de/blog/postings/2025-12-12/0/POSTING-en.html
Itâs been quite the time sink, especially with the DOS games on top, but it was fun. đ„ł
In case youâre wondering: All puzzles (except for part 2 of day 10) were doable in Python 1 on SuSE Linux 6.4 and ran in a finite time on the Pentium 133. Puzzle 10/2 might have been doable as well if I had better education. đ€Ł