1,032 karma · joined April 6, 2011
https://twitter.com/wa7son
One benefit of standardisation that's not tied to async/await is that the JavaScript engines has been able to do performance optimisations not otherwise possible which benefit Promise-heavy applications
Static one page site built by hand. Nothing fancy, just a portfolio of sorts
It creates a PR for each backport you make and label them "backport", so you can easily see them all here: https://github.com/elastic/kibana/pulls?q=is%3Apr+is%3Aopen+...
I realize this is just an homage to LEGO and I'm sure they know and appreciate that. But they still need to defend their trademark. If they don't, anybody could just use their name for whatever they wanted - even things they DO NOT want to be associated with.
$ is-ci && echo "I'm running in a CI environment"
But of course that could technically be baked into ci-info. It's just more convenient to use with npx and to reason about if it's a self-contained module
The Node module actually works. If you use it, it will make all your tests pass.
When writing the code, I put the logic for detecting if code is being run on a CI server into a separate node module called is-ci[1] (which the volkswagen module then depends on). That module (later split out into ci-info[2]) turned out to be so useful for actual work, that today it's being used by both React and the npm cli.
I only found this out recently. Imagine the surprise when a tiny part of a joke project you created years ago turns out to be one of your most popular open source projects :D
[1]: https://www.npmjs.com/package/is-ci [2]: https://www.npmjs.com/package/ci-info
> We determined that access tokens for approximately 4,500 accounts could have been obtained before we acted to close this vulnerability. However, we have not found evidence that any tokens were actually obtained or used to access any npmjs.com account during this window.
Source: https://blog.npmjs.org/post/175824896885/incident-report-npm...
IPFS seems to me to be a bit over-engineered whereas dat is a lot more simple/low level - something that suits my way of working really well.
As far as I know git isn't good at storing binary data. Git depends on line breaks to be able to diff and make change sets. If you store a binary file in git and make an update to it - even though that update only changed 1 byte, the entire new version of the file is stored again. Dat uses Rabin fingerprinting to intelligently slice binary files into chunks that are less likely to change. That make dat a lot more efficient at storing, versioning, and syncing videos, images, and other large binary files.
Edit: The keys are very short (64 bytes), so they can easily be copy/pasted, tweeted and what have you :)
1) With the new version of Opbeat which will be based on Elasticsearch, you have the ability to perform any custom query you like. That should hopefully take care of that part
2+3) I'm not 100% sure what the app development plan is. But I'll make sure to tell the right people :)