Probably, the reason they disappear is that this is the sort of "finished software" that Google makes it very infuriating to keep on the store. On Android you can build an APK like this and it will literally work unmodified for a decade. Google can't stand that and makes you make changes to keep up with shifting policies.
I think this idea doesn't go far enough. If it's money that's motivating slop, fine - let's make it about money. $50 to submit a bug report. If it's legitimate, we send you back $60; the judgement is on the curl maintainers' honor. If it wastes time, well, at least the curl maintainer gets a steak dinner.
Beautiful hardware. If they'd commit to GrapheneOS's hardware requirements https://grapheneos.org/faq#future-devices, I'd preorder... I'm stuck on Pixels because Graphene is so nice.
Seconded. Graphene has spoiled me. Here's to hoping graphene's future collaboration with an OEM results in a small physical keyboard device! Not holding my breath, and will choose graphene over any other feature.
Not only that, but you can also always form a normal (ptr, size) slice reference to any piece of the ring buffer, even when it wraps. This is really helpful for Eigen arrays that you need to rotate.
Yeah only the DOS façade of Windows NT is well known. Under that skin lurks some pretty wild late-1980s concepts. One of the core things to understand is that a lot of the features are based on a reverse map of GUIDs to various actions, and resolution of these map entries pervades the UI. That's why you can put {hexspew} as the name of a shortcut on the Windows desktop and have it magically become a deep link to some feature that Windows doesn't otherwise let you create a shortcut to, and also why you can just add things to the control panel which doesn't seem like it would be an intentional feature. And these actions can be named symbols inside DLLs, so they can do literally anything the OS is capable of doing. This is also why Windows has always been ground zero for malware.
>so they can do literally anything the OS is capable of doing
Yea, over the years someone thought of something they wanted to do and then did it without a systematic consideration of what that level of power meant, especially as multi-user network connectivity and untrusted data became the norm.
As far as I can tell, the drive will still be accessible, it'll just require the character equivalent to € on the other code page as a drive letter.
As long as your code page doesn't have gaps, that should be doable. It'll definitely confuse the hell out of anyone who doesn't know about this setup, though!
I don't think it works that way, the actual drive letter is a UTF-16 Unicode path. The application must be able to provide an "ANSI" string that encodes to that UTF-16 value if it uses an "ANSI" function to open the file. It's not like 8-bit systems where they just want the same 8-bit value.
You're very close to Aikin shape note heads! These help sight-read in any key, since they're always shaped according to whatever the relative major is, and so it's easy to learn the intervals between any two shapes.
This is great. Missed opportunity for a low-pass RC filter on the speaker circuit - if you know you're driving an 8kHz sample rate, you can design your filter with that cutoff, and it'll sound way better (it'll get rid of the buzzy quality).
This may be essential if you're connecting it to an audio amplifier. I learned this the hard way by burning out someone else's very expensive tweeters with 31.25kHz PWM.
reply