Unfortunately the leaks have consistently shown a camera bump that looks like that and Pixel phones usually leak like 6 months before release so it’s probably real :(

Hate to break it to you but people born in 2006 are turning 18 this year (and are technically considered “adults”).

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.

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.

o7

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

Ok but like let’s be real who actually fights with their wolves instead of just leaving them sitting in their base somewhere. Can the armor be dyed? That might help a bit

Add a randomizer that has a chance of resetting it back to normal every now and then for maximum chaos

Ok I was joking with the images but now that I think about it this would likely be pretty useful to have on smart watches with circular displays.

E.g. having the watch face rotating to face towards the wearer would be a pretty neat concept. Definitely something I’d want a toggle for though.

VS code is a good app in spite of using electron, not because of it. There’s no reason a simple plaintext editor needs to allocate 300MB of ram even without extensions just to launch, and there is definitely no reason a plaintext editor should require compiling chromium to build from source.

Slack is fine, but only when you exclusively use slack. Throw in an actual browser, discord, VS Code, Whatsapp, teams (?), etc. each with their own chromium instance and now your 16GB of ram are being eaten up at idle.

VS code is an electron app, there are a few others that have a simple enough purpose that they shouldn’t be using a whole dedicated chrome engine to function.

Another funny concept

Imo it’s context dependent. Obligatory “I’m only a college student/intern” out of the way.

Whenever I’m working with a project with multiple languages (e.g. split frontend+backend, different connected services, etc.) operators like that can get blurry when they aren’t consistent between lancuages. Especially when one of those languages doesn’t have runtime type enforcement or has weird boolean behavior (looking at you JS/TS) which can lead to unintended behavior

If everyone on the project is only working with that language, then your point is probably pretty close to the mark.

Something I noticed was that in this case it was mostly binary AUR programs taking up the space.

I think maybe since yay/AUR use cloned git repos, and old versions of binaries get stored in the git diff and then add up because different versions of the binary are basically like keeping multiple copies of it instead of just the changes to the source code.