fool

joined 3 years ago
 

Dear Linux community,

In these shite times, we need to remember to see the human in all of us. So I address the humans of this community:

  1. To the Stallmanites. SCREW CORPORATE YEAHHHHH! Each day humanity grows smarter, no matter how many iPad kids or mass media diatribes there are, so celebrate how far we've fucking come. Look at your oldest machine. You're a million times better. My old Slackware was full of SHIT! FUCK YEAH

  2. To the pragmatists. Linux doesn't get in your way. People get in each others' ways all the time. But most importantly, don't get in your own way. If you're feeling like shit -- the human capacity to hope beats everything to a pulp. You know what we do when shit fucks? We submit a fucking pull request. FUCK YEAH

  3. To the hobbyists. Life is a bundle of fun so feel every moment. When you're old, and you'll be old as fuck, you'll be like "fuck yeah I lived every moment of my life up to now." So fuck another segfault up. Learn C, and call C the best language. Then learn Rust and call Rust the best language. Make a homelab then call homelab the best language. FUCK YAML HOLY SHIIIIIIIT

Flaming hot wishes,

Your fellow fucking human.

 
 

edit: fixed title

Journalist and self-proclaimed Freedom of Information Act nerd Ken Klippenstein claims to have released Mangione's manifesto. He also believes that some news sources are withholding it.

Manifesto (source: Klippenstein)

To the Feds, I'll keep this short, because I do respect what you do for our country. To save you a lengthy investigation, I state plainly that I wasn't working with anyone. This was fairly trivial: some elementary social engineering, basic CAD, a lot of patience. The spiral notebook, if present, has some straggling notes and To Do lists that illuminate the gist of it. My tech is pretty locked down because I work in engineering so probably not much info there. I do apologize for any strife of traumas but it had to be done. Frankly, these parasites simply had it coming. A reminder: the US has the #1 most expensive healthcare system in the world, yet we rank roughly #42 in life expectancy. United is the [indecipherable] largest company in the US by market cap, behind only Apple, Google, Walmart. It has grown and grown, but as our life expectancy? No the reality is, these [indecipherable] have simply gotten too powerful, and they continue to abuse our country for immense profit because the American public has allwed them to get away with it. Obviously the problem is more complex, but I do not have space, and frankly I do not pretend to be the most qualified person to lay out the full argument. But many have illuminated the corruption and greed (e.g.: Rosenthal, Moore), decades ago and the problems simply remain. It is not an issue of awareness at this point, but clearly power games at play. Evidently I am the first to face it with such brutal honesty.

0
submitted 2 years ago* (last edited 2 years ago) by fool@programming.dev to c/linux@lemmy.ml
 

I had a teeny pet project using GNU assembly that was going to target two platforms.

Instead of keeping my handwritten worst-practices Makefile I decided to try GNU Autotools for the educated reasons of:

  • Text scrolling by looks pretty
  • Vague memories of ./configure make make install tarballs

I got hit with mysterious macro errors, recompile with -fPIE errors (didn't need this before?), autotools trying to run gcc on a .o file w/ the same options as an .s file, "no rule for all:", and other things a noob would run into. (I don't need a bugfix, since my handspun Makefile is "working on my machine" with uname -m.) So there's a bit of a learning curve here, inhibited by old documentation ~and~ ~more~ ~quietly,~ ~genAI~ ~being~ ~shittier~ ~than~ ~normal~ ~in~ ~this~ ~department~

With this I ask:

Do people still use Autotools for non-legacy stuff? If not, what do people choose for a new project's build system and why?

edit: trimmed an aside

[–] fool@programming.dev -1 points 2 years ago

duck girl

i haven't drawn a person since grade school but this post has given me the courage

1
kdesu (programming.dev)
submitted 2 years ago* (last edited 2 years ago) by fool@programming.dev to c/linuxmemes@lemmy.world
 
 
[–] fool@programming.dev 0 points 2 years ago* (last edited 2 years ago)

Obligatory Linux comment (Lemmy moment):

Windows is used often for its compatibility and defaultness but Linux is interesting in the sense that everything is patchable, everything is tinkerable and configurable. The low resistance to tinkering makes lots of Linux users tinkerers -- including tinkering via code.

I'm not saying wipe your hard drive or even dual-boot. Maybe an older computer or VM could help, depending on what you have. But just in the past week I've screwed around in low-to-medium-difficulty Linux projects that configured my lockscreen with C, that implemented mildly usable desktop GUIs with TypeScript, among others -- just not-too-committal stuff that has a return value I literally see every time I lock my computer.

Windows equivalent projects can be harsher on the beginning-to-intermediate curve (back when I first tried out Linux Mint, I'd been struggling to make a bookmark inspector in Visual Studio -- ended up Pythoning it instead) -- not to say that Windows fun is by any means out-of-reach.

[–] fool@programming.dev 0 points 2 years ago

It probably is, but I think their main point is the protest against the age-old delineation into "GUI vs CLI" camps. I'm not saying that you're elitist, even if your statement might be interpreted as such (it's hard to communicate tone online but the quotations around "their workflow" could appear mocking), but regarding the structure of your statement, I had a "Windows users are all button-presser noobs" phase and would've typed something similar about the Git CLI if time was decently rewound (sans the kindness of a "use what you like" statement). They could be interpreting your statement as a propagation of the anti-GUI stereotyping.

Evidently they prefer GUI but can effectively use the CLI -- no one disagrees that the CLI is more functional.

 

Git cheat sheets are a dime-a-dozen but I think this one is awfully concise for its scope.

  • Visually covers branching (WITH the commands -- rebasing the current branch can be confusing for the unfamiliar)
  • Covers reflog
  • Literally almost identical to how I use git (most sheets are either Too Much or Too Little)