dwattttt

16 ms·

361.
by dwattttt 1y ago
The FASTA format stores nucleotides in text form... compression is used to make this tractable at genome sizes, but it's by no means perfect. Depending on what you need to represent, you can get a 4x reduction in data size without comp
362.
by dwattttt 1y ago
It's not even required for the information to be present at link time; C/C++ doesn't require the pointer to always be owned or not-owned, it's valid for that to be decided by configuration loaded at runtime. Or for it to
363.
by dwattttt 1y ago
I imagine it's (implicitly?) referring to avoiding whole-of-program analysis. For example, given a declaration int* func(int* a); What's the relationship between the return value and the input? You can't know without d
364.
by dwattttt 1y ago
> The kind of "safe Rust" where you never use `unsafe` and never call into a C library is theoretical. None of the major ports of software to Rust achieve that. An entire program ported to Rust will call into unsafe APIs in at
365.
by dwattttt 1y ago
Rust hit 1.0 in 2015, it started as a project by Graydon Hoare in 2006; those dates line up pretty well with Zig's timeline.
366.
by dwattttt 1y ago
It's amusing to see assembly considered more portable than C.
367.
by dwattttt 1y ago
> The latest AMD under full load uses the same power as M1 and is faster, thus it has better performance per watt. He also said per watt. An AMD CPU running at full power and then stopping will use less battery than an M1 with the same t
368.
by dwattttt 1y ago
Be sure to be consistent with each of the edge cases in order to be correct!
369.
by dwattttt 1y ago
Only once we convince C developers that a lack of performance isn't inherently harmful.
370.
by dwattttt 1y ago
> --option flag1,flag2 Embedding a second parse step that the first parser doesn't deal with is done, but it's a rough compromise. It feels like the difficulty in dealing with [--option [--flag1 --flag2]] Is more to d
371.
by dwattttt 1y ago
The type isn't just there to make it easy to understand when you do it, it's for you a year later when you need to make a change further inside a codebase, far from where it's validated. Or for someone else who's never e
372.
by dwattttt 1y ago
> options that depend on options What would you do for "top level option, which can be modified in two other ways"? (--option | --option-with-flag1 | --option-with-flag2 | --option-with-flag1-and-flag2) would solve inval
373.
by dwattttt 1y ago
Sibling says this with code, but to distil the advice: reflect the result of your validation in the type system. Then instead of validating a loose type & still using the loose type, you're parsing it from a loose type into a stri
374.
by dwattttt 1y ago
Given > an algorithm would randomly select an arrangement from the 52! possible decks. But no computer has enough memory to evaluate all of these possibilities It sounds more like they don't understand how a computer can shuffle som
375.
by dwattttt 1y ago
The biggest question I have around the viability of breaking changes in C++ is whether you can compile some code with a newer breaking standard, some with an older standard, and link them. Headers would be a problem given their text inclusi
376.
by dwattttt 1y ago
Surely then it's the 'use', not the 'possession' that's a criminal offence? Or is it still a criminal offence to possess it, but you're fine as long as no one finds out? Because that doesn't stop it b
377.
by dwattttt 1y ago
It's an interesting proposal. A new grammar which can express everything (legal) that C++ can, can be automatically translated, but can avoid being ambiguous ( https://stackoverflow.com/a/794083 ). You'd have a
378.
by dwattttt 1y ago
> with the growing focus on safety, you can rest assured that an implementation that wouldn’t diagnose erroneous behaviour would be soon out of the game. Unless they were incumbent and inertia keeps them in. Or they're the only choi
379.
by dwattttt 1y ago
I can't wait for autism diagnosis to be linked to psychologists & paediatricians, and their subsequent banning.
380.
by dwattttt 1y ago
If a learning a new language didn't change how you think about programming, it wasn't a language worth learning.
381.
by dwattttt 1y ago
Yes, most of the survivors will have developed immunities. There's a catch in that sentence if you read it carefully.
382.
by dwattttt 1y ago
> If a group of users of 32 bit hardware care to volunteer to support the latest kernel features, then there's no problem. It's not just the case that you need people to support 32bit/nommu; you also have to account for th
383.
by dwattttt 1y ago
You'll run into a variant of the tragedy of the commons; without any kind of regulation or provable assertions from people taking part in common communication infrastructure, it'd be quite easy to ruin it for everyone.
384.
by dwattttt 1y ago
Agreed, and I wish there were more emphasis on ensuring panic free sections of Rust code.
385.
by dwattttt 1y ago
But only if you make it look like an electrical thing
386.
by dwattttt 1y ago
I've been following Raymond Chen's recent series on writing a tracking C++ pointer class with interest. Most of the articles start with "to fix the mistake we showed at the end of the last article", and end with "bu
387.
by dwattttt 1y ago
> The XDG Base Directory Specification mentions Unix a few times but lists no carveouts for macOS or any other operating system. I could write a specification that says where files should go on macOS, and I could even get people to agree
388.
by dwattttt 1y ago
You can try to read/write the same on Windows: ReadFile (and friends) take a HANDLE. It won't make sense to try to read from all things you can get a HANDLE to on Windows either, but it's up to what created the HANDLE/ob
389.
by dwattttt 1y ago
The reminder to "never break userspace" is good, but people never bring up the other half of that statement: "we can and will break kernel APIs without warning". It illustrates that the reminder isn't "never ch
390.
by dwattttt 1y ago
There are more absurd interpretations, when you remember that his first name was William.

More ›