That's pretty cool. I'd be curious to know how the node editor was architected.
AnOceanAppears
joined 1 year ago
I guess a more modern example you might run into is something like Rust's no_std environment; which strips out the standard library of the language that doesn't work on every device the language is designed to target (namely microcontrollers that don't even have an operating system on them). Or like, maybe you're writing your own operating system.
Another example comes to mind of a company, General Magic, that designed a programming language with a similar Capabilities system meant to restrict access to functions and code on their devices with the idea of copyright enforcement in mind as a primary use case. There's a documentary about the device if you're interested: https://www.generalmagicthemovie.com
There's languages designed with Capabilities in mind. Like, whatever starts the program gets to decide what functionality is exposed to the running program. It's great for situations where you might run untrusted code and want to, as an example, not allow network access, or filesystem access.
More generally there's also sandboxing techniques that runtimes provide. Webassembly for instance is designed for programs to run in their own memory space with a restricted set of functions and, again, Capabilities. This might be nice if you ever work on a cloud application that allows users to upload their own programs and you want to impose limits on those programs. Think AWS Lambda, except the programs running wouldn't necessarily even have access to the filesystem or be able to make web requests unless the user configures that.
It might be a good design space for even more esoteric areas, like device drivers. Like, why worry if your GPU drivers are also collecting telemetry on your computer if you can just turn off that capability?
There's older applications of sandboxing that are a bit further from what you're asking as well; like, iframes on a webpage; allowing code served from different servers you don't necessarily control to run without needing to worry about them reading access tokens from local storage.
Or even BSD Jails and chroot.
Good question 💖
Damn, all of this person’s art is incredible
Oh my gosh! Thank you! This one just made me really really happy reading it ☺️ Also, I'm just now seeing the watermark at the bottom 😅 Normally I'm more observant, I swear!
I love this! Is there somewhere that I can follow the artist?
Any company worth working at is going to understand your concern about your parents' health.
Definitely doing something and being consistent with it is more important than having a finished thing at the end of it; like, challenging yourself and having fun with it. Open source projects are just one way to do this, it's kinda like volunteering where you can earn bonus points with people for being invested in collective good and working collaboratively. Being able to effectively collaborate is a really valuable skill to have (and companies know it) and worth finding ways to include in whatever you're doing. There's other ways to do this. For instance there's nonprofits and local communities that look for volunteers to build websites for them.
I also recommend finding community if you can. Dunno where you live, but I've had a good time getting to know the folks at Out In Tech, which has chapters in various cities (more generically, they have a slack that anyone can sign up for).
Also, for me, finding motivation in isolation has always been hard for me; joining a company gave me that external motivation I kinda needed to get started. If your goal is to find a job I recommend not creating artificial barriers for yourself just start applying to stuff. Interviewing is a skill and you probably need to develop that by just interviewing a lot. Try setting a goal for yourself of number of companies to apply to per day (10 a days and you're cooking with gas, but at least 2 is respectable). Volume is kinda your friend until you get your foot in the door.
I hope this is helpful. You got this!
It's experience. There's no such thing as undocumented experience. Training yourself to see your experiences as valid in an of themselves is a process, one I've struggled with myself; but, it's really important as it's expected that from employers that you're not filtering out expertise you have because it "wasn't professional enough" or whatever. Running a Plex server for friends to stream from is valid experience and worth considering if you're building out time ranges on your resume (eg. N years of experience with $technology)