#rust programmer

[zoeythebee]

Fuck it, I'm tired of C's bullshit. I'm gonna learn Zig.

[queenlua]

i desperately WISH that reading the phrase “[x] is among the few who understands how to write C programs with effectively zero memory bugs” didn’t instantaneously put me through a demented minor-key magical girl transformation sequence in which i became a screeching thirteen-headed cockatrice, belching fire and ichor and rust macros

but UNFORTUNATELY FOR ME i’ve looked at these fuckers’ code, so,,,,

[vizthedatum]

I'm gearing up for Advent of Code 2023 (while trying to be realistic about time constraints with self-care, work, and relationships)!

Who wants to do it with me? I'll mostly be coding in R (in base, tidyverse, and other random paradigms/package bundles), Python, Excel, and (maybe) Rust.

Let's do this work-life-programming balance. (I am a very rusty programmer since I mostly do statistical work - I have the aptitude for it but am very inefficient with optimized solutions.) I'll post my solutions here: https://github.com/pritikadasgupta/adventofcode

[404a10]

The real socks for

Crabs Everywhere Socks • $10.00

It’s my pledge that is 2023 we are going to have crabs everywhere. On your devices, on your feet, they’ll be a crab for anything and everybody.

75% Cotton, 21% Nylon, 4% Lycra

Crew Length

Fits Most Feet

Men’s Shoe Size 7 – 12

Women’s Shoe Size 6 – 11

[gracien-system]

This system has very strong opinions about programming languages it does not know how to write in.

[lostjared]

This Rust joke encapsulates the basic concept of karma through a simple program that interacts with the user by accepting input and providing output based on the given input. Here's how it aligns with the idea of karma, which often implies that the energy or actions one puts out into the world will come back to them in some form:

Input as Action: The function give() takes user input, representing an action or thought put out into the universe. This act of giving an input parallels the concept of performing an action or harboring a thought in real life.

Output as Reaction: The function get(value: String) then processes this input. If the input is "love," it returns "1," and if the input is "fear," it returns "0." For any other input, it simply returns the input itself. This mechanism is a direct metaphor for karma, where the nature of what you put out—represented here by the specific strings "love" or "fear"—determines what you get back.

Love and Fear as Metaphors: The choice of "love" and "fear" as inputs with specific outputs ("1" for love and "0" for fear) symbolizes the idea that positive actions or thoughts (love) lead to positive outcomes, while negative actions or thoughts (fear) lead to negative or less desirable outcomes. The binary nature of the outputs (1 and 0) can be seen as a nod to the binary outcomes in life: positive or negative, good or bad karma.

Looping Nature: The program's looping nature, prompting the user to continuously enter thoughts and see the karma returned, illustrates the ongoing cycle of actions and consequences, a core tenet of the karma concept. It suggests that for every action (input), there is a reaction (output), and this cycle continues indefinitely.

In essence, this Rust program is a playful representation of the karma concept, using code to illustrate the philosophical idea that the quality of what you put out into the world (your actions, thoughts, or intentions) directly influences what comes back to you.

[mostlysignssomeportents]

What kind of bubble is AI?

My latest column for Locus Magazine is "What Kind of Bubble is AI?" All economic bubbles are hugely destructive, but some of them leave behind wreckage that can be salvaged for useful purposes, while others leave nothing behind but ashes:

https://locusmag.com/2023/12/commentary-cory-doctorow-what-kind-of-bubble-is-ai/

Think about some 21st century bubbles. The dotcom bubble was a terrible tragedy, one that drained the coffers of pension funds and other institutional investors and wiped out retail investors who were gulled by Superbowl Ads. But there was a lot left behind after the dotcoms were wiped out: cheap servers, office furniture and space, but far more importantly, a generation of young people who'd been trained as web makers, leaving nontechnical degree programs to learn HTML, perl and python. This created a whole cohort of technologists from non-technical backgrounds, a first in technological history. Many of these people became the vanguard of a more inclusive and humane tech development movement, and they were able to make interesting and useful services and products in an environment where raw materials – compute, bandwidth, space and talent – were available at firesale prices.

Contrast this with the crypto bubble. It, too, destroyed the fortunes of institutional and individual investors through fraud and Superbowl Ads. It, too, lured in nontechnical people to learn esoteric disciplines at investor expense. But apart from a smattering of Rust programmers, the main residue of crypto is bad digital art and worse Austrian economics.

Or think of Worldcom vs Enron. Both bubbles were built on pure fraud, but Enron's fraud left nothing behind but a string of suspicious deaths. By contrast, Worldcom's fraud was a Big Store con that required laying a ton of fiber that is still in the ground to this day, and is being bought and used at pennies on the dollar.

AI is definitely a bubble. As I write in the column, if you fly into SFO and rent a car and drive north to San Francisco or south to Silicon Valley, every single billboard is advertising an "AI" startup, many of which are not even using anything that can be remotely characterized as AI. That's amazing, considering what a meaningless buzzword AI already is.

So which kind of bubble is AI? When it pops, will something useful be left behind, or will it go away altogether? To be sure, there's a legion of technologists who are learning Tensorflow and Pytorch. These nominally open source tools are bound, respectively, to Google and Facebook's AI environments:

https://pluralistic.net/2023/08/18/openwashing/#you-keep-using-that-word-i-do-not-think-it-means-what-you-think-it-means

But if those environments go away, those programming skills become a lot less useful. Live, large-scale Big Tech AI projects are shockingly expensive to run. Some of their costs are fixed – collecting, labeling and processing training data – but the running costs for each query are prodigious. There's a massive primary energy bill for the servers, a nearly as large energy bill for the chillers, and a titanic wage bill for the specialized technical staff involved.

Once investor subsidies dry up, will the real-world, non-hyperbolic applications for AI be enough to cover these running costs? AI applications can be plotted on a 2X2 grid whose axes are "value" (how much customers will pay for them) and "risk tolerance" (how perfect the product needs to be).

Charging teenaged D&D players $10 month for an image generator that creates epic illustrations of their characters fighting monsters is low value and very risk tolerant (teenagers aren't overly worried about six-fingered swordspeople with three pupils in each eye). Charging scammy spamfarms $500/month for a text generator that spits out dull, search-algorithm-pleasing narratives to appear over recipes is likewise low-value and highly risk tolerant (your customer doesn't care if the text is nonsense). Charging visually impaired people $100 month for an app that plays a text-to-speech description of anything they point their cameras at is low-value and moderately risk tolerant ("that's your blue shirt" when it's green is not a big deal, while "the street is safe to cross" when it's not is a much bigger one).

Morganstanley doesn't talk about the trillions the AI industry will be worth some day because of these applications. These are just spinoffs from the main event, a collection of extremely high-value applications. Think of self-driving cars or radiology bots that analyze chest x-rays and characterize masses as cancerous or noncancerous.

These are high value – but only if they are also risk-tolerant. The pitch for self-driving cars is "fire most drivers and replace them with 'humans in the loop' who intervene at critical junctures." That's the risk-tolerant version of self-driving cars, and it's a failure. More than $100b has been incinerated chasing self-driving cars, and cars are nowhere near driving themselves:

https://pluralistic.net/2022/10/09/herbies-revenge/#100-billion-here-100-billion-there-pretty-soon-youre-talking-real-money

Quite the reverse, in fact. Cruise was just forced to quit the field after one of their cars maimed a woman – a pedestrian who had not opted into being part of a high-risk AI experiment – and dragged her body 20 feet through the streets of San Francisco. Afterwards, it emerged that Cruise had replaced the single low-waged driver who would normally be paid to operate a taxi with 1.5 high-waged skilled technicians who remotely oversaw each of its vehicles:

https://www.nytimes.com/2023/11/03/technology/cruise-general-motors-self-driving-cars.html

The self-driving pitch isn't that your car will correct your own human errors (like an alarm that sounds when you activate your turn signal while someone is in your blind-spot). Self-driving isn't about using automation to augment human skill – it's about replacing humans. There's no business case for spending hundreds of billions on better safety systems for cars (there's a human case for it, though!). The only way the price-tag justifies itself is if paid drivers can be fired and replaced with software that costs less than their wages.

What about radiologists? Radiologists certainly make mistakes from time to time, and if there's a computer vision system that makes different mistakes than the sort that humans make, they could be a cheap way of generating second opinions that trigger re-examination by a human radiologist. But no AI investor thinks their return will come from selling hospitals that reduce the number of X-rays each radiologist processes every day, as a second-opinion-generating system would. Rather, the value of AI radiologists comes from firing most of your human radiologists and replacing them with software whose judgments are cursorily double-checked by a human whose "automation blindness" will turn them into an OK-button-mashing automaton:

https://pluralistic.net/2023/08/23/automation-blindness/#humans-in-the-loop

The profit-generating pitch for high-value AI applications lies in creating "reverse centaurs": humans who serve as appendages for automation that operates at a speed and scale that is unrelated to the capacity or needs of the worker:

https://pluralistic.net/2022/04/17/revenge-of-the-chickenized-reverse-centaurs/

But unless these high-value applications are intrinsically risk-tolerant, they are poor candidates for automation. Cruise was able to nonconsensually enlist the population of San Francisco in an experimental murderbot development program thanks to the vast sums of money sloshing around the industry. Some of this money funds the inevitabilist narrative that self-driving cars are coming, it's only a matter of when, not if, and so SF had better get in the autonomous vehicle or get run over by the forces of history.

Once the bubble pops (all bubbles pop), AI applications will have to rise or fall on their actual merits, not their promise. The odds are stacked against the long-term survival of high-value, risk-intolerant AI applications.

The problem for AI is that while there are a lot of risk-tolerant applications, they're almost all low-value; while nearly all the high-value applications are risk-intolerant. Once AI has to be profitable – once investors withdraw their subsidies from money-losing ventures – the risk-tolerant applications need to be sufficient to run those tremendously expensive servers in those brutally expensive data-centers tended by exceptionally expensive technical workers.

If they aren't, then the business case for running those servers goes away, and so do the servers – and so do all those risk-tolerant, low-value applications. It doesn't matter if helping blind people make sense of their surroundings is socially beneficial. It doesn't matter if teenaged gamers love their epic character art. It doesn't even matter how horny scammers are for generating AI nonsense SEO websites:

https://twitter.com/jakezward/status/1728032634037567509

These applications are all riding on the coattails of the big AI models that are being built and operated at a loss in order to be profitable. If they remain unprofitable long enough, the private sector will no longer pay to operate them.

Now, there are smaller models, models that stand alone and run on commodity hardware. These would persist even after the AI bubble bursts, because most of their costs are setup costs that have already been borne by the well-funded companies who created them. These models are limited, of course, though the communities that have formed around them have pushed those limits in surprising ways, far beyond their original manufacturers' beliefs about their capacity. These communities will continue to push those limits for as long as they find the models useful.

These standalone, "toy" models are derived from the big models, though. When the AI bubble bursts and the private sector no longer subsidizes mass-scale model creation, it will cease to spin out more sophisticated models that run on commodity hardware (it's possible that Federated learning and other techniques for spreading out the work of making large-scale models will fill the gap).

So what kind of bubble is the AI bubble? What will we salvage from its wreckage? Perhaps the communities who've invested in becoming experts in Pytorch and Tensorflow will wrestle them away from their corporate masters and make them generally useful. Certainly, a lot of people will have gained skills in applying statistical techniques.

But there will also be a lot of unsalvageable wreckage. As big AI models get integrated into the processes of the productive economy, AI becomes a source of systemic risk. The only thing worse than having an automated process that is rendered dangerous or erratic based on AI integration is to have that process fail entirely because the AI suddenly disappeared, a collapse that is too precipitous for former AI customers to engineer a soft landing for their systems.

This is a blind spot in our policymakers debates about AI. The smart policymakers are asking questions about fairness, algorithmic bias, and fraud. The foolish policymakers are ensnared in fantasies about "AI safety," AKA "Will the chatbot become a superintelligence that turns the whole human race into paperclips?"

https://pluralistic.net/2023/11/27/10-types-of-people/#taking-up-a-lot-of-space

But no one is asking, "What will we do if" – when – "the AI bubble pops and most of this stuff disappears overnight?"

If you'd like an essay-formatted version of this post to read or share, here's a link to it on pluralistic.net, my surveillance-free, ad-free, tracker-free blog:

https://pluralistic.net/2023/12/19/bubblenomics/#pop

Image: Cryteria (modified) https://commons.wikimedia.org/wiki/File:HAL9000.svg

CC BY 3.0 https://creativecommons.org/licenses/by/3.0/deed.en

--

tom_bullock (modified) https://www.flickr.com/photos/tombullock/25173469495/

CC BY 2.0 https://creativecommons.org/licenses/by/2.0/

[clockworkprism]

Lots of people talking in general but to your specific point, if you are new to programming in general I would stick to only one and since you're taking a class that will use Python, learn Python. You will be able to pick up c# very quickly later.

If you know programming generally, sure learn both languages at the same time. They're so different I don't imagine any confusion, especially because one is static typed with semicolons and the other is an absolute garbage language that I desperately want to abandon but my industry adopted it dynamically typed with enforced white space so visually it will be easy to center yourself in one vs the other. At least that's true for me when I switch between them.

Question regarding languages: Python & C#

Is it possible to learn both languages at the same time? Or will it be easy to get confused between the two? I thought I would come to the lovely codeblr people who have a vast amount of experience for advice. C# is something I *want* to learn, but I *have* to learn Python for for my course that starts in January...I just want to see if it is plausible to learn both at the same time or if it will mess up my learning if I try and learn both. I'd love to hear about your experiences and what your first languages were when you first started out in the world of coding!!

[eightyonekilograms]

C is now illegal by order of President Biden; all C programmers report to the nearest FEMA camp for your mandatory thigh-highs and estrogen injections as you begin your new life as a Rust developer.

[ayeforscotland]

Ad | Humble Bundle April 2024

Hi folks, here's a few bundles that some of you might be interested in this month.

For the inspiring programmers - the Code like a Pro bundle supports Girls Who Code.

If you lean more towards 3D modelling and design then Blender Core Skills bundle has loads of resources on Mesh modelling, rigging, shading and lighting. It also raises money for One Tree Planted.

I know a bunch of you love a good TTRPG, there's a solid Pathfinder Second Edition - Guns of Alkenstar Bundle available. A portion of the money goes towards Endometriosis UK - a charity very close to my heart.

[confusedbyinterface]

so I'm reading Gankra's "Learn Rust With Entirely Too Many Linked Lists" and the introduction feels like

STOP USING LINKED LISTS

DATA ELEMENTS WERE NOT SUPPOSED TO BE GIVEN POINTERS

YEARS OF COMPUTER SCIENCE yet NO REAL-WORLD USE FOUND for using anything other than Vec

Want to add and remove elements from the front and back just for a laugh? We have a tool for that: It's called "VecDeq"

"It might take a long time to look at any element but I'll make it up with all the merges, inserts, and splits I'll be doing" - Statements dreamed up by the utterly Deranged

LOOK at what Functional Programmers have been demanding your Respect for all this time, with all the LISP machines & tape readers we built for them (This is REAL Computer Science, done by REAL Computer Scientists)

???????????

"Hello I would like element.next.next.next.next.next.next.next.next please"

They have played us for absolute fools

[blathannabeaga]

.☽༊˚ one-word prompts; coffee

jim street x reader

feat. uniformed!reader, s5-ish swat academy instructor!street, references and brief descriptions of gun violence and injury (not to reader or street), hurt/comfort, mutual pining

Loud as the ER’s waiting room is this late into the evening, the furore only barely reaches your ears above the blood still rushing through your head. It’s an all-consuming, dementing noise that no amount of deep breaths or kneading at your aching temples to do away with - and your only break from it is the series of three, succinct shots that your mind has been playing on loop for the last hour. 

After the first, your hand is flying to your duty belt and wrenching your sidearm loose as you bolt backwards from the passenger door of the car and find cover at the rear of your adjacent squad car. The second, and despite your shouts at him Eric is dropping from sight on the driver’s side as the engine revs back to life.

The third and the car is tearing off down the empty street, kicking up gravel in its wake as you roar the plate number into your radio before your voice dies in your throat at the sight of Eric strewn back against the pavement. The burst of darkness spreads alarmingly fast across his side, visible even under the flickering streetlamps, blood pooling on the ground and soaking into the knees of your pants by the time you lurch over to him and drop to his side. 

The accursed sequence replays once, twice, ten times over as you haunt the hospital halls in wait of news. People come and go - a sweet nurse, tending to the scratches on your palms and uttering assurances that fall on unhearing ears, your watch commander who offers only a tight squeeze of your shoulder before heading away to begin the hunt for the assailant. What’s immovable is, for all your half-hysterical scrubbing, the dried, rust-coloured stains sunken into the beds of your nails and the grooves of your palms - and the persistent churning of your stomach as more and more time passes with no news.

The thought of Eric beyond those sterile double doors only sickens you further, and you hang your head in your hands as guilt floods you anew. The only partner you’ve known since you made it out of the TO programme, the man who took you on as a pseudo-little sibling after about a fortnight of knowing you. Eric, whose most deceptive action in all the time you’ve known him has probably been sending off your application for SWAT behind your back after months of indecision and self-doubt. Eric, who had you had to beg to give in and stop the Sedan with license plates that didn’t match the tags just to give one of your last shifts together some excitement.

And what if that’s what led you here? If your self-obsessed overthinking your performances in CQB drills and a certain set of dimples, and a stupid want to bid your patrol days goodbye with a bang had distracted you from what was really important? Distracted you from piquing the desperation behind the man’s eyes, the disjointed way he spat oddly pre-prepared answers back to Eric’s routine questions, the glint of the pistol barrel under the indifferent streetlights above-

A set of heavy boot treads coming in your direction disrupts your agonising. You fear it’s someone from your station coming to commiserate or lay blame, neither of which you’re ready to contend with - until a hand wearing a familiar watch comes patiently into view, pushing a warm paper cup of coffee into your hesitant grasp in lieu of a greeting.

Steam ebbs up through the plastic lid and brings with it the fragrant scent of fresh, sweet coffee as Street takes a seat beside you. The warm press of his thigh against yours is more grounding than you’d like to admit, but you don’t have to - he doesn’t press you for so much as an acknowledgement of his presence, and instead just sits quietly alongside you for you’re not quite sure how long. When the silence is finally broken, it’s unexpectedly by you - which takes both you and Street by surprise.

“Azzura’s.” Your voice is ragged from having not spoken in so long, but seeing the name of your favourite coffee shop emblazoned across the side of the cup’s green sleeve has you speaking before you realise it. 

“I do listen to your nonsense, sometimes.” That smug waver to his voice that you’ve grown so fond of is still present, if subdued somewhat for the circumstances. He bumps his shoulder softly with yours, and takes a sip from his own cup before rolling it idly between his hands. “M’still hoping that one day you’ll return the favour, but I’m not holding my breath.”

At the sound of your quiet chuckle, he looks over at you and cracks a smile of his own. “Yeah, I wouldn’t.” 

Your voice cracks on the last word, and you hastily look away. It’s probably a good thing, because the earnest sympathy behind Street’s eyes would probably be your last straw.

“He’ll be okay.” Street knows how hollow it sounds, but it’s all he can think to say because he truly believes it. Leaning down, he places his cup on the floor at your feet and folds his hands together as more staff bustle past you. “From everything you’ve told me about him, I can tell he’s not the kind of guy who’ll go down easy.”

“A center-mass shot and another to the vest might have something to say about that.” It spits out meaner than you intend, but the venom isn’t meant for Street and he understands that. Coffee splashes inside the cup as your hand trembles, and he quietly takes it from you to join his before reaching to the side of his chair. 

“I grabbed your go-bag from your locker.” He sets your backpack down at your feet, and you realise you’d not given a thought to your soiled uniform all evening. You murmur your thanks but before you can speak any more, a stretcher surrounded by staff swings a corner beside you and Street lugs another bag out of their way, spiking your anxiety markedly.

“Did you clean out my whole damn locker while you were at it?” Though you laugh as you say it, nervousness is written all over your face and voice. Christ, have you been kicked out of the Academy like that? And like this, no less- 

“You wish. Luca’s not gonna let you go anywhere until he gets a rematch to prove his arm-wrestling skills aren’t so easily shown up by a rook.” Street waves off your thinly-veiled concerns, mercifully with only a small grin, before turning the bag around to show his name printed in thick letters across the front. “That one’s mine.”

Confusion pulls at your features, and you soothe a still-shaking hand over your face.

“Eric’s a damn fine cop, but you don’t know him.” You tell Street, propping your elbow on your thigh as you look over to him with your head rested in your hand. You’re looking for an ulterior motive, a betrayal of his eyes or twitch of his lips to tell you what the endgame is here, but when you don’t find it you press on with a shrug. “Why would you post up here in the middle of the night to wait on him?”

“You’re right, I don’t.” He nods in agreement, but meets your eyes and you find that there isn’t a scrap of insincerity to be found. “But I know you, and I know how important he is to you.”

Something between a laugh and a noise of surprise breaks from your lips, but there’s no malice behind it. You turn your smile to the floor and wring your hands into your lap, but knock your knee against his as you speak. “When you said we could spend time together outside of HQ, I had kind of envisioned it being under better circumstances.”

“That mean you want me to leave?” He asks, moving in closer but lowering his timbre to convey a level of seriousness you find disjointed with who you so far know him to be.

“Not even remotely.” You tell him, and you mean it so truthfully it almost hurts - and his hand is already enveloping yours by the time the double doors at the end of the hall open, and a grave-faced surgeon emerges calling your name.

[wojenka]

i need more mutuals who are into coding and engineering!! more info under the cut!!

I planned to become an electrical engineer like my stepdad but then I decided to change my path to programming. I'm currently studying at technikum (<- wikipedia link so I don't have to explain the whole polish learning system), programmer major.

this year I have exams from web development (10th Jan - theory, 16th Jan - practical exams) and next year I have exams from App development (both mobile and desktop).

I know C family languages, Java, Python and those ones I am currently using. I also know a bit of Kotlin and I think I will continue learning it.

For web dev I know HTML and CSS ofc but also PHP and JS.

Planning on learning more languages I can use for App and operating system development as well as just to know them cause I want to after this year's exams!

my learning list:

Lua (I heard it's easy but I can't really get myself to read anything about this atm idk why)

Ruby

Assembly

Rust

As for electrical engineering I don't know much tbh but I would like to learn! I just used CAD programs for technical drawings (dad taught me some basic things when I was still thinking about going his path) helped my dad fix things on his Solar farm, houses of our neighbors and I made a few very simple circuits for fun a few years ago. Now I'm mostly focused on programming but since I learned most of the things I need for exams I have more time to do whatever I want now!

I'd like to get to know more people so I can share and mostly learn new things since even though I'm coding for years I consider myself a beginner and I am a total beginner when it comes to electrical engineering.

I'm willing to be friends or at least mutuals with anyone who codes or makes websites or is in STEM! no matter what your specialty/interest is exactly and no matter if you are a total beginner or a professional ^__^

I'd also like to have some mutuals who are into old web development and retro computing!!!!!!!!

edit: I forgot but I'm also interested in physics and quantum physics

[favorite-music-tourney]

Round 1 match ups

Deny Defend Depose by Joe Devito - Todos Juntos by Los Jaivas

Union Maid by the Almanac Singers - Color in your Cheeks by the Mountain Goats

II: The road Giveth by RENT STRIKE - Two Headed Boy by Neutral Milk Hotel

For What It’s Worth by Buffalo Springfield - I'm not a good person by Pat the Bunny

I ain't Marching Anymore by Phil Ochs - Ballad of a Wobbly by David Rovics

Do you believe in magic by the lovin spoonful - Let the Mystery Be by Iris Demont

California Dreamin by the Mama's and the Papa's - I'm a Believer by The Monkees

Hallelujah by Leonard Cohen - A Song for a Computer Programmer by Cricket!

Blackbird by the Beatles - The Gambler by Kenny Rogers

Feed the Machine by Poor Man's Poison - Curses by the Crane Wives

Big Rock Candy Mountain by Harry McClintock - Pure Obsession by Mirabai Kukathas

Closer to Fine by the Indigo Girls - I want wind to blow, the microphones

War isn't Murder by Jesse Welles - Delta Dawn by Tanya Tucker

Place to Be by Nick Drake - The Wrote and Writ by Johnny Flynn

Time in a Bottle By Jim Croce - Ohio by Neil Young

Little Lion Man by Mumford and Sons - Space Girl by Shirley Collins

A Horse with No Name by America - Fuck it by Days N Daze

The Galway Girl by Sharon Shannon and Steve Earle - The Chain by Fleetwood Mac

Heave Away by the Fables - Stick Season by Noah Kahan

Rule #4 Fish in a Birdcage by Fish in a Birdcage - Your Heart is a Muscle the Size Of Your fist by Ramshackle Glory

War on the Workers by Anne Feeney - The Funeral by Band of Horses

Blister in the Sun by the Violent Femmes - Lyndon Johnson Told the Nation by Tom Paxton

Season of the Witch by Donovan - I’m against the government by Defiance, Ohio

Everybody's Talkin' by Harry Nilsson - Kill the Boy Band by She/Her/Hers

Me and my Bobby Mcgee by Janis Joplin - O Valencia by the Decemberists

Wayward Prodigal by Cora Reef - The War Racket by Buffy Sainte-Marie

The Times they are a changing by Bob Dylan - Miracle of Life by Bright eyes

At Seventeen by Janis Ian - Little Boxes by Malvina Reynolds

I am a Union Woman by Bobbie McGee - Electricity by Sister Wife Sex Strike

Annie's Song by John Denver - Roll On, Columbia, Roll On by the Highway Men

Puff the Magic Dragon by Peter Paul and Mary - Solidarity Forever by Utah Phillipps

I'm Gonna Be an Engineer by Peggy Seegar - Follow Me up to Carlow by the Young Dubliners

Take Me to Church By Hozier - 32 Flavors by Ani Difranco

Fast Car by Tracy Chapman - Murder in the City by the Avett Brother

Mrs. Robinson By Simon and Garfunkel - The Chemical Worker's Song by Great Big Sea

The Fox by Nickel Creek - Oak & Ash & Thorn by The Longest Johns

The Wreck of the Edmund Fitzgerald By Gordon Lightfoot - Strangers by Apes of the State

American Pie by Don McLean - Our House by Crosby, Stills, Nash, And Young

Everything I own by Bread - Fire and Rain by James Taylor

The Trolley Problem by Windborne - Brown Eyed Girl by Van Morrison

Where have all the flowers gone by Pete Seeger - Dream a Little Dream of Me by Cass Elliot

Glad to be Gay by Tom Robinson Band - The Battle of New Orleans by Johnny Horton

Vienna by Billy Joel - Cats in the Cradle by Harry Chapman

One Kind of People by Amigo the Devil - Brave as a Noun by AJJ

Every Town will Celebrate by Mischief Brew - Wild World by Cat Stevens

Plastic Jesus by Tia Blake - Ho Hey by the Lumineers

Ballad of Ho Chi Min by Ewan MacColl - City of New Orleans by Arlo Guthrie

Loose Lips by Kimya Dawson - Excursion Around the Bay by Great Big Sea

Who would Jesus Bomb by Jordan Snart - Rhododendron Honey by Leslie Fish

Hungry Dog on the street by the Taxpayers - The Night They Drove Old Dixie Down by The Band

Mr. Tambourine Man by the Byrds - Nebraska by Bruce Springsteen

You're So Vain by Carly Simon - Ooh La La by the Faces

Budapest by George Ezra - Paradise by John Prine

Tear the Facists Down by Woody Guthrie - House of the Rising Sun by the Animals

One Great City by the Weakerathans - Diamonds and Rust by Joan Baez

Bread and Roses by Judy Collins - Angel From Montgomery by Bonnie Raitt

March of the Jobless Corps by Daniel Kahn - There is Power in a Union by Billy Bragg

What a time to be alive by Matt Press - Rhinestone Cowboy by Glen Campbell

Sixteen Tons by Tennessee Ernie Ford - All The Trees of the Field Will Clap Their Hands by Sufjan Stevens?

Not Yet/Love Run by the Amazing Devil - Ain't No Sunshine by Bill Withers

Tom's Diner by Suzanne Vega - It's too Late by Carole King

Hurt by Johnny Cash - Big Yellow Taxi by Joni Mitchell

Jolene by Dolly Parton - Have you ever seen the rain by Creedence Clearwater Revival

I'd work for Free by Blake Rouse - You're Dead by Norma Tanega

[queenlua]

lmao (from this CTF writeup):

The final step, emitting the target language, which is nowadays often NOT C, is our greatest weakness in 2024. A new generation of engineers and systems folk have discovered the fruits of Chris Lattner's labor and staked their claim on today's software landscape. Unfortunately for reverse engineers, we continue to deal with the Cambrian explosion in binary diversity without commensurate improvements in tools. We eat shit reading worsening pseudo-C approximations of things that are not C. This problem will probably not get solved in the near future. There is no market for a high-quality Rust decompiler. First, no one writes exploits or malware in languages like Rust or Haskell. Unlike C/C++/Obj-C, the Rust/Haskell/etc ecosystems are predominantly open-source further decreasing the need for reverse engineering. Lastly, improved source control and ready availability of managed enterprise services (i.e. GitHub) make first-party loss of source code much rarer nowadays. So like, no one really cares about decompiling Rust other than unfortunate CTF players. Golang is a notable exception. Golang is like, the language for writing malware--great standard library, good cross-platform support, brain-dead easy concurrency, easy cross-compilation, fully static linking, and design with junior programmers in mind. You could shit out a Golang SSH worm in like 200 LoC crushing carts and ketamine no problem. People worry about AGI Skynet hacking the Pentagon to trigger a nuclear holocaust but really it's more gonna be like eastern European dudes rippin' it with some hella gang weed ChatGPT ransomware. So maybe we'll get a good Golang decompiler first?

[transtrucks]

me when I'm a Rust programmer