It's not just liking the language or eating their own dogfood.
265 karma · joined August 27, 2019
It's not just liking the language or eating their own dogfood.
It's all open source. If you want a vanilla js implementation go ahead.
The idea that you need to do something that is better before you can do something that is less, even if the cost is the same seems to imply that there is only a limited amount of energy that is expendable on these topics.
As seen from the bucketloads of comments and posts about this OLD issue (the python link is from 2018) it seems there's enough energy going around.
The idea that something can't be good, just because it is not the highest item on a list is nonproductive.
[0]: https://www.parool.nl/ps/hoofd-geschiedenis-rijksmuseum-ik-w...
The author seems to imply that the name change is all about being non-offensive to some people. Since the author doesn't find the language offensive, they conclude that name change is only political correctness or virtue signalling and a hollow gesture. I do not agree with that. Language and words are very powerful in how we perceive the world. A changing vocabulary is part of cultural change.
No. It's extremely unlikely the rules WILL change. With curfew extended for another month, there is an as good as zero chance they will drop 1.5m rules (which is what the committee has based their decision on) before March.
This is not completely accurate. Sure, koek-en-zopie stuff might be organized by local restaurants or whatever, but the Elfstedentocht itself is prepared (almost) completely every single year. There is a whole foundation with internal hierarchy that oversees the process. The whole parcourse can be constructed on a 48 hour notice. The waterschappen don't stop their pumps out of hospitality or something, it is all pretty well organized.
So it's a python-based browser. If a certain python package is installed that has bindings for the (rust-based) adblock library, then it is used.
This idea that something that is (at most) a mild inconvenience (make sure the children in your car are well-protected) equates to "safety at any cost" is plainly ridiculous. The same reasoning is at the foundation for why the US now has +200000 people dead from the COVID-19 virus.
"In the United States, 675 children 12 years old and younger died as occupants in motor vehicle crashes, 4 and nearly 116,000 were injured in 2017. Of the children 12 years old and younger who died in a crash in 2017 (for which restraint use was known), 35% were not buckled up."
https://www.cdc.gov/motorvehiclesafety/child_passenger_safet...
So about 440 children died while buckled up. Suddenly 57 doesn't seem like such a bad number.
I know people working with big consultancy companies and the recurring thing they complain about is a difference of opinion between client and provider about what exactly the terms of signed agreements mean.
First of all, let me say I'm not questioning your expertise or your good intentions. I'm a great fan of (and following closely) a few standards or proposed standards championed by the W3C, mostly related to RDF, verifiable credentials and digital identity, so a bit different from digital archiving.
To be a bit more constructive instead of my comment above, I think if the aim is rediscoverability in 100 to 1000 years, what your current proposal is missing, is semantics. Bits are just bits. Discovering what the bits mean is actually a great deal more difficult than checking if a checksum is still valid. Indeed, this gives bits a certain color. A question that you pose, is 'If I change the name of the file, is it still the same digital file?', but you do not get further into an answer. While a filename might be an arbitrary label, the color of the bits (or the intent of the creator/archiver of the file), in my opinion, might be interested for inclusion.
So OP has the option of adopting an existing (and clear) spec, with existing libraries (and and existing governance structure) and because of what feels like a not-invented-here mentality (yeah well, I can't imagine needing this complexity), OP has decided to develop a new standard, without an existing spec, without existing libraries and without existing governance structure.
All these ideas in online data sharing, semantics and interoperability are great, but I think people underestimate how much effort it actually is to create a good standard, a good spec, and how exponentially more effort it takes to keep such a standard in a shape that's working for more people.
The extensibility for OP's identifier is extremely narrow. Just look at how many hash functions and properties are currently already supported by the IPFS content id: https://ipfs.io/ipfs/QmXec1jjwzxWJoNbxQF5KffL8q6hFXm9QwUGaa3...
OP's choice of hash function is even in there.
There is a reason why IPFS is already at a second version of the spec. It is because they were using the first version and found them lacking in their use cases. Every new standard is doomed to make similar mistakes unless they explicitly account for them in their design.
There's also a difference between copyright and patent law.