beefhash

40 ms·

391.
by beefhash 8y ago
For an algorithm with "standard" in its name. This gets more confusing my the minute.
392.
by beefhash 8y ago
Given Rust's spotty platform support[1], I don't see that happening anytime soon. [1] https://forge.rust-lang.org/platform-support.html
393.
by beefhash 8y ago
Please keep doing that. I'm still hesitant to contribute to tech@ with code and have yet to find a fixable issue in the man pages/FAQ in my own usage. But I do appreciate that the details are oh so right very often.
394.
by beefhash 8y ago
Open core can go wrong if you're not coupling the valuable functionality tightly enough to the open core, though. This seems to be happening with BitWarden, where at least two free third party implementations of the password storage ba
395.
Ask HN: What are some examples of great documentation?
2 points by beefhash 8y ago|2 comments
396.
Celebrating 50 Years of Unix: Public Unix VMs(unix50.org)
4 points by beefhash 8y ago|0 comments
397.
by beefhash 8y ago
I assume the idea is that, on average, you'd get better results just following those five points (focus on the body, get a reasonable text size, get decent line spacing, adjust the two for 45-90 characters per line, choose a decent fon
398.
by beefhash 8y ago
To be fair, C is kind of like that, too. You could move the declarations of static functions to the top, but then you'd still have declarations that prevent you from getting to the real meat.
399.
Practical Typography(practicaltypography.com)
261 points by beefhash 8y ago|61 comments
400.
NCSA Mosaic 2.7 on OpenBSD(cryogenix.net)
1 points by beefhash 8y ago|0 comments
401.
by beefhash 8y ago
As far as I know, the Windows 2000 source code leak was incomplete, actually; or if it isn't, then not the entire thing ended up getting leaked. For example, the code to the setup program was missing. To the best of my knowledge, the m
402.
OpenBSD in Stereo with Linux VFIO: Reverse Engineering Audio Drivers(jcs.org)
1 points by beefhash 8y ago|0 comments
403.
by beefhash 8y ago
Beware the AGPL on some components, though. You may want not to make a business whose business model revolves around adding features to sr.ht.
404.
by beefhash 8y ago
Copyright has become the catch-all kind of intellectual property if nothing more specific is available. It's grotesque what it's become, but that's just how it is.
405.
by beefhash 8y ago
Yes, they are orthogonal. However, chances are POSIX can only be convinced to add one . And I'd rather they add the one that can't be misused by a programmer.
406.
by beefhash 8y ago
FILE is part of the standard, see 7.21.3 and e.g. 7.21.5.3. Section numbers as per C11 latest public draft; I don't have two hundred bucks to spend on an actual copy of the standard.
407.
by beefhash 8y ago
Oops. Edited a fix in.
408.
by beefhash 8y ago
If uint8_t exists, then I believe the following ought to be true: 1. CHAR_BITS == 8, and 2. the compiler is required to make uint8_t an alias of unsigned char. Point 2 is there so that you can cast to uint8_t safely, which some cryptograp
409.
by beefhash 8y ago
getline is POSIX, but not C. I feel like the functionality is so fundamental to writing C as securely as the language allows that it ought to be promoted to being in the C standard. arc4random is in complete POSIX limbo as far as I can tell
410.
by beefhash 8y ago
> You can use C++ as some kind of C with destructors though :P Scoped cleanup is really a nice thing.. C++ is not a strict superset of C. You actually have to cast void pointers, for example. > But then you also want templates of cour
411.
by beefhash 8y ago
Wishlist: the arc4random family (would also put up with it being in POSIX), strlcat and strlcpy (yes, glibc, just for you), getline (fgets sucks), reallocarray and recallocarray, that signed integer overflow becomes at least implementation-
412.
by beefhash 8y ago
> This is why if you're currently writing C or C++, please, please look into Rust. But please, please also look into its platform support table[1], too. If you're the slightest bit opposed to the Windows/macOS/Linux
413.
by beefhash 8y ago
Interesting, I didn't know it worked. A comment on another site by stsp@[1] suggested it doesn't. https://lobste.rs/s/ljdhug/install_openbsd_on_dedibox_with_f...
414.
by beefhash 8y ago
> Full Disk Encryption with SoftRAID It's worth noting that SoftRAID for encryption is mutually exclusive with SoftRAID for redundancy: " Note that "stacking" softraid modes (mirrored drives and encryption, for exampl
415.
by beefhash 8y ago
Work on OpenCVS started in 2004[1] and schwarze@ said last year that the project is "dormant" and in a state where "trying to use it in production revealed instabilities that were non-trivial to debug, and nobody did the work
416.
by beefhash 8y ago
I think it's somewhere inbetween, similar to the heirloom-doctools. You can interact with any live SCCS repo -- if you find any outside of BitKeeper (whose format seems to have diverged anyway). And for some reason it's in POSIX.
417.
SCCS: The Posix Standard Source Code Control System (2017)(sccs.sourceforge.net)
55 points by beefhash 8y ago|40 comments
418.
by beefhash 8y ago
stdint.h can't be reliably be premade. A compiler is completely free to, say, define sizeof(unsigned int) to anything as long as it can represent at least 65535. stdint.h has to work with the C base types, so it does have to be customi
419.
by beefhash 8y ago
> stdint.h is nearing 20 years old now, I don't think it counts as a "newfangled thing" anymore. In the world of C, it is. Custom compilers for particular embedded systems, such as MCUs, often only speak C89 and nothing el
420.
by beefhash 8y ago
I see your C and raise you a COBOL[1,2]. [1] http://www.coboloncogs.org/INDEX.HTM [2] http://adrianzandberg.pl/cobol-on-wheelchair/

More ›