Vertical integration works really well to control quality of your platform if you have the resources to make it happen. You _could_ make the argument that System76 is too small of a company to financially make this work, but the payoff is a better product.
I would expect IPC between GUI applications to go the way of iced's Subscriptions + Commands, sending and receiving messages from a central bus or other peripheral components running as daemons.
I use the Vinegar extension for Safari which replaces the YouTube player for a simple HTML5 <video> tag and consequently removes the ads. Don't know if there's alternatives for other browsers, but worth looking into if this is all that's keeping you there.
Builds don't "have" to start from scratch. If you're building in a docker context you can mount a volume containing build artifacts (target directory). Or `sccache` if you want those artifacts stored in a remote store such as S3. I'm sure there's other solutions as well, but not clearing build artifacts in between builds would be a simpler win over maintaining separate, shared infrastructure.
Actually, yeah! One example of this is the set of the Adams Family, which famously had a ton of pinks and bright pastels despite being a supposedly gothic set specifically because those colors created the best contrast in the final medium, a black and white tv set :)
That, and I think it's also fair to acknowledge that language choice can be a serious barrier of entry to contributing to a project or using it in tandem with other technologies. Also if I'm looking to learn from real-world projects I would, personally, prefer to know ahead of time.
"Hi, my project does X, I wrote it in Y," seems a reasonable way to introduce something.
I'd be happy to hear more about this workflow you've set up for yourself. The more I do development work the more I've come to appreciate having a framework to offload mental overhead onto. I don't think I've found one that quite fits me quite yet, but hopefully soon :fingers_crossed:
You're right, the above declaration should probably be refined a bit. You should be both white and straight.
I would say it's hard to take what you've said seriously having personally known people who have left the midwest specifically due to the discrimination they faced.
Except I do have to have to take it seriously because it's a toxic attitude that belittles the struggles that people face due to discrimination by attempting to minimize their experiences.
I'd suggest picking something small that you personally want to get started. For me, I wrote Dingus (https://github.com/davidarmstronglewis/dingus), which is really just a simple CLI that reads environment variables from a file and either executes a command with those loaded or drops you into a shell. I was finding myself constantly populating my shell environment with different variables depending on various contexts and figured I would canonicalize the process and learn more about Rust in the process.
I still use the tool today (although I'm still not sure it's the most elegant solution :P), and I've taken that knowledge I picked up in the process for other projects I've since done in Rust.
If I were where you are, I'd do something similar: carve out a simple project that you could complete in a day (or two) in a language you're more familiar with, and try to do it in Rust.
I'd also recommend joining the Rust Discord channel to field any immediate questions you might have (and going to the Forums if there's something more involved you'd like opinions on).