Subtly, not by pushing it on them directly. Instead, I share links to topics that might interest them. Show people the value.
This is a secondary account. My main account is listed below. The main will have a list of all the accounts that I use.
Personal website:
Subtly, not by pushing it on them directly. Instead, I share links to topics that might interest them. Show people the value.
Happy Birthday! I get random downvotes all the time. Don’t take assholes personally.
Love Lua. I just wish the ecosystem wasn’t a choice between a fast JIT implementation and a traditional one that’s compatible with the latest version of the language.
I don’t care for Rust because I like writing unsafe code. It’s fun. However, I would value the assurances it provides using software written in Rust.
It’s not the fanciest solution, but if you’re really not sure what you’re doing, not wiping out your Windows in the first place could be the best option.
I don’t think it’s realistic to expect a rewrite of code that works. Maybe over time we can start implementing pieces in safer languages.
I used to have a ball, but I got rid of it because I heard reports that it can be dangerous and may not be very effective. It made me paranoid enough to just watch my equipment better.
Faith in standards temporarily restored
Arm:
Somehow, the kernel has been loaded and we have transferred control into it.
Four kinds of blue in that graph.
Please. I hate all the incompatibility when trying to build a custom kernel.
Gentleman and scholar
Thanks for the tip! Will definitely consider this when I need to edit some audio.
It is really awesome. Note however that there are some gaps, like if you want accurate floating point or full syscall coverage. I’ve hit issues in some scientific applications.
I’m a little out of the loop, but I recall Audacity took a massive nose dive a while ago. Have they recovered from this?
In particular, the cloud features doesn’t pass the smell test for me. Is this one of those apps where you download the old version?
The top self-selects for the skill of climbing ladders.
In my mind, it’s more like a library of scripts. Scripts are powerful and could potentially do anything, and it would be wise to not run these scripts arbitrarily without reviewing them first or having some other trust basis you can rely upon.
For example, I don’t think you’re expected to review all open source software on your system. It’s much easier to instead trust a group of people with high visibility, such as the core Debian developers, and proceed to exercise graduated caution according to the likelihood that the code has been reviewed. You probably don’t need to review the Linux kernel. When it comes to random widgets and themes off the internet, it’s easy to encounter code that has never been reviewed.
I think there is such a thing as a risk tolerance. You can’t build a completely trust-free computer. For practical and economic reasons, you’re going to have to trust somebody. I think the optimal strategy is to be smart about who you’re trusting and where you’re focusing your limited resources to review. Popular Debian packages? Probably safe. Widget by person you’ve never heard of that nobody else uses? Probably risky.
If this makes you feel uncomfortable, I suggest that a person takes a few moments to review their threat model. What kinds of attacks are you worried about? What costs are you willing to pay to mitigate these attacks?
Not mine, but while I was an intern for a lab I enjoyed using a very normal-looking desktop with a casual 4TB of DDR4 and no SSD or HD, dual Xeon configuration. Rather, it did network boot and pivot root into an in-memory filesystem. It had a UPS and typically ran for months entirely from volatile storage and was used to run experimental photo and video processing. This was about ten years ago.
Note: Android kernel has had this since 12 because FUSE is used to enforce permissions and to emulate legacy storage types.
https://source.android.com/docs/core/storage/fuse-passthrough
From the patch back in 2016:
There is also a significant cpu/power savings that is achieved which is really important on embedded systems that use fuse for I/O.
Sometimes, easy accessibility is a bad thing. Nobody profits off a large user base here. We should instead focus on having good users and a platform that serves those users.