My point wasn't that FAANG isn't exploitative (my bad if it came off that way, I didn't mean for that), it's that everywhere else is also exploitative to some degree (most probably less so than FAANG, there are definitely a few that are worse though), and that it could still be reasonable to work there for some people.

The other consideration is that pretty much every company you could work for as a software developer is going to try to take advantage of your work. Most companies are morally bad at best and morally terrible at worst. If you discourage any good person from working there, the problem will only snowball from there.

If working at FAANG gives you the resources to support things you're passionate about, and you're willing to stand up for your values when they do something bad, there isn't a problem with that IMO.

If he was counting his money in $100 bills it would still take him about 40 years,

Edit: assuming he counts 1 $100 bill per second

Among us chip bags??? GET OUT OF MY HEAD

I just want developers to consider their deployment environment and maybe generate and include more capable, POSIX BB instead of just choosing the smallest and most useless.

This is completely fair, but the only example you gave to show this was about regexp in OpenWRT, and it seems from the other comments like there are several ways to go about doing this. You mentioned half of your RAM being free, but on the flip side of that, something with half as much RAM or less would be struggling a lot more. Admittedly I don't know much about OpenWRT but routers aren't exactly known for being powerful systems, so to me this seems like a perfect use case for a leaner set of utilities.

To your other point, languages like Python and Lua might not technically be everywhere but it they are common enough and simple enough to learn that you really are holding yourself back by avoiding them. Lua in particular is used by a lot of Linux projects (e.g. Neovim and Awesome WM are the most recent that I've used but there are tons of others) because of how easy it is to embed a configuration/plugin API into existing codebases.

Tldr; you're being dissed because the only example you gave about BusyBox being overused is (on the surface at least) a valid use case with easy solutions that you seem to be intentionally ignoring.

To be fair learning lua isn't exactly a hard process, there's a reason it's embedded into so many other tools. If you're familiar with python you're like 85% of the way to writing something basic anyway.

Github contribution graphs (basically how much code you committed over time)

*Unfortunately this graph is from Google images, not my account :(

Edit: maybe I should have included a screenshot of light mode because it looks closer to the shower panels, oh well

Another interesting low-level interpreter/emulated system to look into for anyone else trying to get started with this type of thing is the CHIP-8! It's a pretty basic 8/16-bit instruction set (there are 35 opcodes, the instructions themselves are mostly simple) and there are tons of detailed guides on making one and writing roms for them.

This already exists to some degree, the Raspberry Pi 5 has 2 exposed pcie lanes and people have been (kind of hackily, since some parts of the driver depend on x86) getting AMD cards to run with the pi.

I'm not an expert on drivers so I don't know entirely how close fully functioning GPU support is but in theory there's nothing stopping that from happening eventually.

As far as I'm aware specifications/implementations that have been on PCs for ages like UEFI and PCIE are not architecture specific, but it's just that a significant amount of code needs to be rewritten since it's low-level enough that the CPU architecture makes a difference.

(If someone is more knowledgeable on this, please correct me because this is all just my understanding and I could be wrong)

Could also be referring to something like ~/.local/bin, where you remove unnecessary user-only programs vs. /use/bin where you remove system essential ones.

Is that definition not supporting your points though? It defines gender as mostly a social construct, which imo reinforces the fact that it's made up and not a tangible thing anyway.

Sometimes biological sex matters (e.g. as medical info for a doctor to understand) but other than that it's connected to gender in name only, based on made-up social rules.

To be fair, studying computer science isn't always indicative of knowing your way around tech anymore. I'm an undergrad in CS right now with some experience as a TA. The amount of people who got points off of submissions (for a 2nd year class) because they didn't know how to zip a folder correctly and submitted an empty zip file is honestly depressing.

That being said, even knowing what Linux is probably puts your tech literacy above most people so I doubt that was the case here.

o7

I somehow didn't see the top comment and deleted it but I guess not quick enough :(

Japanese manga is read right->left so presumably you would read the two tiny panels on the right side and then the bigger one on the left

Woah weird

a

See now we've got a valid argument going

Wasn't the name "soccer" originally from England?

Edit: it was, and it was used for ~100 years in England until around 1960 - https://en.m.wikipedia.org/wiki/Names_for_association_football