1,239 karma · joined August 9, 2016
Are there other major reasons not to roll your own crypto besides "you might do it wrong"? Wouldn't a fuzz tester (comparing your implementation to a known good one) be well adapted to making sure you didn't do it wrong?
It all comes and it all goes. Let it come. Let it go.
What do you have against .org websites?
I've heard stories of cases where development orgs were given the option of changing a line of code or re designing the hardware. They of course redesigned the hardware.
Some things are near universal and always useful. Documenting by creating a full working example with minimal dependencies will stand the test of time.
I'm not saying don't document. Even a list of notes, clearly marked as such, can be helpful.
When it's a staffing limit the question becomes less arbitrary.
And I agree about yank! I just think you could implement multiple reasonable solutions here
And it's not really arbitrary. You can count the dependency tree of every package and get the P99, exclude joke packages and get the max of the rest. Set the limit around there with an error message to open a bug if you need more, grandfathering legit old large packages with some kind of admin-level exception.
The number of people actually needing more will be incredibly tiny. Service those folks individually to avoid pain.
I guess the real answer is because it's a lot of work to maintain packages and versioning and there is space for multiple solutions.
https://github.com/civboot/civboot/blob/main/blog/0012-dev-l...
Mine will be slightly more than key/value. My index file will support indexes of arbitrary record fields as well as the index of all items in loam, but it's effectively the same idea.
Note you could keep a live instance running to handle live writes, which uses an in-memory hash for recent writes and updates the hash index as-needed. Because the index can be rebuilt from the data there is no concern about data loss.
https://paulbourke.net/dataformats/hershey/
It seems to describe a "pen" which draws the character. It is indeed pretty cool!
For example, there's lots of little places where aligning keywords helps clarify code
https://github.com/civboot/civlua/blob/main/ds/ds.lua#L89
Formatters HATE putting multiple statements on a single line, but when they go it makes it so much easier to parse (for a person)
Writing code that you love is like crafting it. You align subjects and data in beautiful flows of if/else or case/switch. You put multiple statements on a line if they encompass one "thought"
Try writing without a formatter when you are the sole author.
As for syntax highlighting I agree. You can get 80% of the way there with a vim regex of keywords, but it's one of the main things I'm solving by writing my own editor.
This isn't Doctorow. I went and searched, here's the article I think you're referencing
https://doctorow.medium.com/web-apps-could-de-monopolize-mob...