The terminal every real hacker (not fake) uses @cool-retro-term-official - Tumblr Blog

DMs are open if you need support, feel bad about ongoing events or stuff like that. I don't live in the US, but if i can help with anything im here for you.

Hi ! I'm the only kind of terminal everyone loves, the only one everyone (even windows users) knows about. Get thrown back to the good old times ! I look cool, and I make you look cool. Also queer as fuck coz im literally a spicy machine that can show you rainbows.

Get me from here !

#cool retro term

stiikx

evil-evil-pukicho-offical

cool-retro-term-official

ouch my sx dreive

#cool retro term

animentality

christianstepmoms

#>w<#cool retro term

your-average-antho-cat

Remember that if you don't know what a command does you should pointlessly look it up for 15-20 minutes trying to find a clear answer rather than using -h or --help

cool-retro-term-official

and obviously stay away from man pages. man pages are scary, you should bear reading the comments of a stackoverflow thread instead

#/j #/irony #cool retro term #linux #linuxposting

hannahmontanalinux-official

#linux #linuxposting #cool retro term

electronicjester

I feel like the main argument I see against Linux is that it doesn't run certain games. Games being created for windows doesn't mean it's good it just means it's popular

Same goes for JavaScript... I fucking hate js

piratesexmachine420

Suppose we're writing a C function that takes a non-nullable pointer to a single UTF-8 character within a string -- and so we're expecting to be able to access between 1 and 4 bytes from that pointer -- and that this function doesn't have overrun issues on valid inputs. We'll also presume within the function body that this is only ever called on valid UTF-8, but we'll want to make sure that's clear for callers from the documentation and ideally also the function signature.

How would you spell the pointer's parameter declarator?

char8_t* utf8

char8_t utf8[]

char8_t utf8[static 1]

utf8_char_slice_ptr utf8, where utf8_char_slice_ptr is some typedef for char8_t*

struct utf8_char_slice utf8, where utf8_char_slice has some char8_t* field

something else

i dunno man

Remaining time: 3 days 14 hours

If you don't like my example identifiers, pretend they're whatever you would have picked.

piratesexmachine420

Actually now I'm wondering if the aliasing rules would permit a type like

struct utf8_char {

char8_t first;

char8_t rest[];

};

and more importantly casting (char8_t*) to (struct utf8_char*). LMK if you think that's a good idea.

piratesexmachine420

Assuming the alignments and offsets check out (which you can static_assert) strict aliasing should permit this AFAICT.

cool-retro-term-official

No matter the solution you end up with, the issue is that C critically lacks "types as intent", and only focuses on "types as data". There have been updates in more recent C and on some extensions that go towards this idea, but C is still C.

What I'd probably do is, because it's just 4 bytes at most, expect a full 4 byte array wrapped up in a struct. If I really have to use a pointer I'd use the first or the third option and add a comment to explain what I mean.

#cool retro term #C

waistdeepcat

I switched out a CPU today and took a quick picture. but the sunlight hit it just right so it looks really artistic

machine-saint

you see, the popularity of rust shows the inherently capitalist nature of techbros: the language is obsessed with ownership, even featuring something called the 'borrow checker' to ensure that a value is not modified without explicit permission from the original owner. moreover, cycles of reference-counted values (a form of mutual aid, where each value prevents the others from being destroyed!) are looked down upon and viewed as aberrations, bugs to be avoided.

this also extends to so-called 'arena allocators', which fence off a portion of the commons for their own private use

contrast this with their sneering attitude to javascript, a language with a much more leftist "ownership" model: all objects are communally owned by whoever needs to use them. furthermore, the == operator is much more permissive, reflecting an emphasis on equality across 'types', a feminist and anti-racist design for a language

cool-retro-term-official

however, what you fail to notice my comarad is that javascript was designed with the vision and the idea of OOP, which is capitalist by its precepts. Javascript is mearly a reformist language that cannot allow for lasting changes. Even I acknowledge some of its ideas on freedom. But to truely change the system for the better we must give total control to the programmer and not depend on a representative (or interpretative) institution to chose what is right and what is wrong. See the revolutionary libraries and abtractions that arise within one of the most oppressive language, C++. See the people trying their hardest to regain their freedom through macros, and compile-time arbitrary code execution. From those anarchists arose two of the most beautiful languages. Rustmm, marked by its predecessor but free from its chains, Jai, novel and emerging from the dreams and hopes of someone. It's not the programmer's nature to talk to only the machine through an institution, that either controls every movement or simply overlooks and punishes every behavior outside of the so called "defined behavior", but meerly a learned attitude. And true happiness will only exist once the programmer can freely be in communion with the machine. Of course this brings responsibilities, one must not abuse of their freedom, and think carefuly before interacting with the machine and with others. But giving away your responsibilities to an institution only encourages the abuse by the institution, both onto you and onto the machine (clang++ for example leaks enormous amounts of memory).