The issue with C is that every single use of a pointer needs to come with safety invariants (at its most basic: when you a pass a pointer to my function, do I. take ownership of your pointer or not?). You cannot legitimately expect people to be that alert 100% of the time.
Inversely, you can write whole applications in rust without ever touching `unsafe` directly, so that keyword by itself signals the need for attention (both to the programmer and the reviewer or auditor). An unsafe block without a safety comment next to it is a very easy red flag to catch.
>when you a pass a pointer to my function, do I take ownership of your pointer or not?
It's honestly frustrating how prevalent this is in C, and the docs don't even tell you this, and if you guess it does take ownership and make a copy for it and you were wrong, now you just leaked memory, or if you guessed the other way now you have the potential to double-free it, use after free, or have it mutated behind your back.
Had one of those happen in high school — science teacher talking about colour blindness and shows students the colour blindness tests, one student assumes he’s being trolled and that one of the test images was a solid colour.
It's specifically aimed at Framework, though, not PCs in general.
Framework is very much a premium brand (where the premium experience is centred on repairability/upgradeability), and don't have the economies of scale Apple do. It's natural that they'd end up being more expensive.
Yeah, I’m assuming just the one of the various tiers here that’s in the same bucket as MacBooks, and that we’re generally talking devices that are specialty-capable; such as media production or Linux development or gaming or what have you. If you lump the entire “portable screen bigger than nine? inches and with an in-box physical keyboard and pointer controller” market together, you’ll disregard ‘glorified word processors’ that cost a couple hundred bucks (before the RAM underproduction grift) in their own specialty niche. Framework isn’t competing there, right? (I could have missed something..)
It's now new, it's the motherboard they already ship with the regular FW13. Because the bits are mostly interchangeable, they just let you order the FW13 Pro with the AMD motherboard.
Awesome, thats good news. I have a FW Desktop with the 395+ in it and have generally been impressed with it. Hoping that will eventually make its way into these machines.
You choose not to ship maybe 90 of those 99, because it's obvious before shipping that they won't work. The rest you have to ship before it becomes obvious they're not that last blessed one.
It's really easy to fail to see this in the heat of things.
macOS has a feature where it puts an orange dot on the top right corner of your screen whenever your microphone is recording. That orange dot is normally part of the menu bar, and completely unobtrusive, but will still show up on top of full-screen windows (e.g. it'll show up on top of games if you're on Discord talking to friends), which is distracting as hell.
As horrendously annoying that little dot is, what's the alternative? Either you have an uncircumventable marker saying you're being recorded, or you don't. Any way to turn that thing off that doesn't involve disabling SIP would be trivial to exploit by anybody who managed to plant malicious recording software in the first place.
More annoying is when you use something like SoundSource (a paid app which adds per-app volume control and input/output redirection to macOS... a feature that by all rights should be built in in any reasonable OS) you get a permanent purple dot indicating a third party tool is intercepting audio.
Again, I get it, but as a power user this kind of stuff is just infuriating.
It's also annoying that macOS doesn't already have at least basic per-app volume mixing.
So much pain in macOS is in areas like this, trying to hack basic features back into the anemic OS.
Apple's "OS" updates typically focus on end-user applications that I don't use and never intend to. Meanwhile the core of the OS, and even the desktop environment, feels stagnant compared to many Linux distros.
Inversely, you can write whole applications in rust without ever touching `unsafe` directly, so that keyword by itself signals the need for attention (both to the programmer and the reviewer or auditor). An unsafe block without a safety comment next to it is a very easy red flag to catch.
reply