Anthony Martinez @ajmartinez@librem.one

@kyle not my laptops and desktops!

Going to look into some CI so I can automate builds to provide packages for my projects. Just to see how long it would take to ‘cargo install connchk’ on a small system, I installed the #Rust toolchain on a #beagleboneblack and checked: 69min. Cross compiling on my T460s takes 62s.

Any thoughts on which tooling to use?

After spending several hours fighting with OpenSSL variations in my array of Linux hosts, I have released v 0.2.0 of connchk to remove the OpenSSL dependency completely. TLS is now handled by rustls.

Now the project builds easily with cargo or cross on x86_64-unknown-linux-gnu, armv7-unknown-linux-gnueabihf, and x86_64-pc-windows-gnu.

https://crates.io/crates/connchk

#Rust #FOSS

@Gina if there's an "ideal" place to break down, that is definitely not it! Did you make it out yet?

@kyle @angdraug heh I remember having the FujiP out in public circa 2007 running Debian w/ XFCE and having someone want to know which Mac I had and how much it cost...

I never feel "held back" by LoTD. It's generally that I feel constrained to the point of being unproductive if I find myself in the unfortunate position of having to actually use my work laptop on Win10.

@angdraug @kyle It was circa 2.4.late/2.6.early when things were half OSS / half ALSA. The worst was having a laptop that would occasionally have the hd at /dev/hde instead of /dev/hda where was when the system was installed. Probably not actually Linux's fault, but fun anyway.

Now I never have an issue with a machine working. Debian, Ubuntu, Fedora, CentOS, Tails, Kali, whatever. My windows machine is reqd by work. I use it to change my password every 90 days.

@angdraug @kyle A good chunk of the pain 20yrs ago, IMO, was from finding one application that was great for the task you needed it to do only... it was then the ONLY app you could use that made sounds (to call back the pain of having 9000 different sound layers possible at the turn of the century). Things are much better now, and I seldom find myself deep in /proc trying to figure anything out anymore. I'm glad I had that experience for when truly outstanding problems do crop up today.

Right now my 'connchk' project is really only available if you're a #Rust user who can `cargo install connchk`.

This weekend I think I'll add some automation to at least provide binaries for x86_64-unknown-linux-gnu, armv7-unknown-linux-gnueabihf, and x86_64-pc-windows-gnu targets. Maybe later I'll package .rpm and .deb versions too.

@kyle cheers to that - the 'freedom' part is exactly why I've supported @purism with my orders this year, and why every project I've worked on in 2020 is #GPL or #MIT licensed.

I guess I did release my vim config as #unlicense "code" but... yeah

@kyle my brief period of insanity^w Mac use predates Docker nearly a decade, and indeed most of the things I needed to do that had a development flavor happened in full heavy Linux VMs (almost always Debian back then) because homebrew often made me weep.

That said my Linux use today leans pretty heavily on Podman for things like spinning test databases, test fixtures, and cross compilation.

@kyle I wonder if some of the stall wasn't also from the constant forking and fracturing of core areas different FOSS contributors couldn't agree on. That may also tie into your theory though as OSX said "you want to make sounds? do it this way", but early aughts Linux said "you want to make sounds? there are 6.02E23 ways to do that. 0 of them work together".

@stevenroose everyone I know who hits their email on the command line uses mutt/neomutt.

Updated my vim-config repo: https://github.com/anthonyjmartinez/vim-config with an important announcement: emacs is probably actually the best version of #vim once you've got EVIL installed.

I really only use EVIL because in the server (and embedded) administration game you're always going to find at least vi on your target host. Those motions will always be part of my day to day. I really only `M-x evil-mode RET` when I know I'll be in and out of remote systems all day.

Standard Emacs bindings are fine.

@codesections My suspicion is that most developers willing to go all the way to the length of writing and maintaining their own successful language are well outside the mainstream for many reasons beyond faith (or a lack thereof). If faith happens to be one of them I'm not sure how much driving power that has on the language... though given my experience with #perl and/or #ruby it does seem that prayer is often required to get the results you're looking for ;)

@Gina w00t!

Not much sleep was had last night, so I took advantage of the situation and finished another #Rust project: https://crates.io/crates/connchk

The structs defined thus far let me define what path to take for HTTPS services. Now I just need a struct that takes a one or more elements of each exiting struct so I can create them based on TOML contents. Making surprisingly fast progress. #Rust