da_cow (she/her)

It brings me joy whenever I realise, that the folks at Espressif have another driver that does the exact same thing I was about to implement manually For those of you who dont know: esp-idf is the official development framework for the ESP32 microntrollers. The nice thing is, that it comes with a port of FreeRTOS, lots of advanced Drivers and Tools to build, flash and debug your microcontrollers, which makes developing with for the ESP32 an absolute charm. On the other hand, we got the IDF…

XP in ASCII is [0x58, 0x50] and Vista is [0x56, 0x69 0x73, 0x74, 0x61]. If we add all of them together we get 168 (0xB2 for XP and 519 (0x207) for Vista

Saying that performance doesnt matter anymore is what brought us AAA games running at 20fps on the most powerfull Consumer Hardware available at the time (yes, Im talling about you Jedi Survivor)

Working outside can be fun. At least AS long AS you dont need that good of an internet connection, have a comfy place to sit in and are at a somewhat dark spot, so you can still see on your screen. If and only if these three things are all given, than it can be quite nice to work outside.

varying quality And thats where you can See if you had caffeine or not /s

While the meme is very funny, it is technically incorrect. Linux has two major ways of terminating a process. When Linux wants a process to terminate execution (for whatever reason) it first sends the SIGTERM signal to the process, which basically "asks" the process to terminate itself. This has the advantage, that the process gets the chance to save its state in a way, that the execution can continue at another time. If the process however ignores the SIGTERM signal at some point Linux will instead forcefully terminate the execution using the SIGKILL signal. This represents what the image shows. Before someone gets mat at me: I know, that there are like 50 more Signals relevant to this, but wanted to keep it simple.

I think I'm kind of fucked. I Am forever lost in the depths of Linux. I just read the headline and thought to myself "Who the fuck pays for a Linux terminal and what does it have to do with emulators?"

turnmeintoagirl.com is a greatwebsite for all those transfems that still dont know they are trans.

UwU

Or Ducks.

Bombs are in fact quite expensive, so theres some serious money to be gained.

Linux

Conservatives saying shit like "nature intended monogamous relationships between men and women, and it is against nature to change your gender" while fucking nature is queer AS fuck. Clown fish will always end up turning into females in the course of their lives (if they dont get eaten before), male seahorses get pregnant and shimpanzes solve all of their problems with sex.

A friend of mine has a Laptop, where you can easily pull out out the hard drive while the OS is running. We once did that and it worked kinda fine. After plugging the hard drive back in it continued to run like before.

:3

Not directly. Trans men can get pregnant too (it may or may not be possible if they are on hormones but as long as the Organs are still there they should be table to get pregnant.

That was my Second thought too.

At the end after ä ö and ü

While it is 100% understandable, that the lack of a graphical task manager is annoying, you are not completely without options. If you want to terminate a process you can easily type pkill -f process_name into your console. The process name doesn't even have to be exact with the process name (as example the process name is signasignal_desktop, providing signal to the command would be enough to kill it).

I fucking hatte Lisp for its excessive use of brackets. Fuck the Person who thought that you only need one type of bracket and then have shove absolutely fucking everything into it.

And its a mistake. Hear me out, but whatever lunatics at python decided that brackets and semicolons are unnecessary, have made a catastrophic mistake with it. I start using another editor that uses different amount of spaces for tabs and suddenly my code no longer runs. Its also absolutely horrible when you chase down a bug for an hour just to realise, that one additional/missing tab changed the scope of your code and broke your entire script.

The reason I dislike the missing of semicolons and brackets is because it causes bugs (that’s more of a problem of missing braces to declare the scope of your code) and also takes away control from the programmer. Missing braces: I had more than one instance where I accidentally deleted the intendation in a python script that caused undefined behaviour in my code and it took quite a lot of time to track that down. If the programming language would have forced me to properly defined the scope of my code by introducing brackets, that bug would have never been possible. Semicolons: The main thing I like about semicolons is that it allows you to properly space out your code over multiple lines for visual clarity. E.g.: void my_function(int arg1, int arg2, int arg3){ //some code } int main(){ my_function( 1, //arg1 3, //arg2 8 //arg3 ) } Rust even allows you to leave out the semicolon on the last statement of a code scope in order to return the result of the statement: fn main() { let condition = true; let number = if condition { 5 } else { 6 }; //number turns into 5 println!("The value of number is: {number}"); } }

Okay, it may use not that much more brackets, but I really dislike the places where you have to use them and it gets even worse simply because it does only use regular brackets. Why the fuck are function declaration and definition part of the same bracket? Why is its the same for conditions?

Yeah I know, but I have no clue about that kind of stuff, simply because I hate that language so god damn much so that I never cared enough to actually learn it a single inch more than it was needed, so that I could copy paste code from StackOverflow into my Emacs config.