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.

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.

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

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

Anything that touches the internet can be scraped. Mastodon DMs aren’t encrypted, and public posts are obviously public. There’s nothing stopping someone from using the API or any web crawler to harvest data on mastodon users anyway.

Not arguing for/against threads, tbh I don’t even use mastodon much because I don’t really like the idea of microblogging to begin with

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.

Exactly this. I’d rather use TypeScript than regular JS, but I enjoy using almost any other statically-typed language more (except maybe C++) because TS has the potential to be just as bad as JS for codebases where it isn’t being used correctly (this is true for other languages as well but it’s usually a lot more obvious).

Not that it isn’t possible to have good typescript code, but rather that code becomes a lot harder to maintain because of problems that could’ve been prevented at a language level (truthy/falsey logic, ‘any’ type being allowed by default rather than ‘unknown,’ etc)

In theory I’m a fan of the inferred but static typing systems that most modern languages use (kotlin, rust, TS, etc.) where most local variable types can be inferred and only return types/object fields/parameters need explicit types.

I just despise typescript because it feels more like someone put a bandaid over JavaScript and all of its oddities instead of making a properly fleshed out language, and allowing the option for an ‘any’ type to be used freely by default emphasizes that.

If I had the willpower or time to go through a multi-thousand line (not including the html templates) legacy Angular 6 codebase where almost every property is typed ‘any’ then I assure you I would have, it’s driving me insane 🙃, also why I prefer backend

Nevermind then, that’s good to hear! I enjoyed but I eventually had to switch back to Jerboa because it was the only client at the time with proper spoiler support.

Fair warning: Liftoff may not be actively maintained, as the GitHub repo hasn’t had a commit in about 2 months now

Here’s the link for those curious: https://github.com/liftoff-app/liftoff

JavaScript: They were so focused on whether or not they could that they forgot to consider whether or not they should