@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
It's been long enough now that we are back to the pre-golden era world where people don't understand the risks of vendor lock-in and proprietary protocols. To me this means there's an opportunity for a new golden era, if we can get people to appreciate why the "freedom" part of FOSS is so important.
@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.
The following era saw priority shift from "freedom" to "open" throughout FOSS. Linux webapp development was primarily done on Macs and that changed how FOSS development happened overall, as devs had to adapt to homebrew libraries instead of curated packages. Dev tools changed to solve the problem of inconsistent library versions between Mac and Linux distros, which ultimately led to docker. I believe the primary reason docker was created was to serve Linux webapp development on OSX.
I'd love to see a history of FOSS in its "golden era" (early aughts) to the early teens. There was this great momentum at the time, giant advances in the Linux desktop and server, and a large focus worldwide on open standards (XMPP became, briefly, the standard chat protocol).
This progress stalled. My theory is that it's in large part due to OSX convincing FOSS developers "it's UNIX" and with FOSS devs on Macs, Linux desktop advances slowed down.
@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
Moving hard coded values into a TOML file to ingest at runtime and define the actions taken by my latest #Rust project providing a tool for my factories to determine the true source of perceived network issues. For most critical services establishment of a TCP connection is sufficient. For some of the HTTPS services a 200 is self explanatory, but for others a 400 may actually indicate success (a garbage request making it past certain checks) while a 403 is problematic.
Machine design hat on for a second: if you’re designing some structure and require fasteners exclude the Phillips head screw from consideration. In 2020 there is no reason this weak design should still be used. #thismaybetheonlythingIsayrelatedtomyactualdegreein2020
@Gina the server I'm on is pretty much silent so you and the other five people I follow are all I see. Given that I don't consume much by way of social media when I do go look for content it's usually by a search for hashtags (most often rust or podman since these are critical to my current workflows). I have no doubt that there is plenty of reprehensible content/behavior in the fediverse.
Well now that I’ve got a working POC I’m inclined to make it a bit more generic and extensible tomorrow. I see some more Box<dyn Trait> use in my future. #Rust
Time to sit down with reqwest and std::net::TcpListener for a bit. Need to hammer out a diagnostic tool to help our production facilities troubleshoot network issues. #rust
The last #IKEA bookshelf was mis-packaged. There are two right sides, and no left side. Guess I'm going to have to physically go to the store since the customer service number doesn't work and the two social media contact options are for services I don't have.
@Gina a good move!
Thanks for over 2,500 app votes so far! Already at 25% of our 10,000 vote goal!
Help fund the apps you desire with "Fund Your App":
I like to work with my hands. That may mean hammering out solutions to complex problems in #Python or #Rust, building things in my shop, or spinning yarn to knit something warm. You’ll likely see some of all of that here. By day (and sometimes night) I keep >13k nodes and services alive in the Electric Vehicle sector.
PGP: FCBF 31FD B34C 8555 027A D1AF 0AD2 E852 9F5D 85E1