HN user

BinaryBullet

56 karma
Posts7
Comments55
View on HN
Material-UI 9 years ago

The docs site also just "feels" snappier to me in Firefox for some reason. I'm not sure if it's actually faster, but clicking around feels more responsive.

Not really related, but a while back I wrote a script to visualize/hear audio generation loss with different file formats:

https://github.com/skratchdot/audio-generation-loss/tree/mas...

So, mp3s add a bunch of silence to the beginning of the file, and ogg files start to "chirp". I never got around to putting this info in a consumable, easy to understand format though. The videos in these folders just continuously re-encode a source file w/ a given lossy format.

See also: https://en.wikipedia.org/wiki/Generation_loss

Thanks for sharing. I remember seeing 'glitch' posted a while back, and am glad to see they've updated it with a bunch of new features.

I wish `noscript` didn't recognize a bunch of the example links as "potential xss", but that's easy enough to fix (can't have it both ways). NOTE: the links aren't XSS, just look "codelike" for obvious reasons.

Will you post insight into the data you've collected? Obviously I don't care about IP addresses, etc, but it would be nice to know how many people have submitted data vs how many unique hashes have been collected for say the "Fingerprint using DynamicsCompressor", etc. I also haven't checked every page on the site, so the data might already be there (and I'm missing it)...

I don't know of any. I would think it would be fairly easy to create a userscript or extension to stub built-in APIs (maybe using something like testdouble.js or sinon.js to override the default global objects that you are trying to "disable"). I'm not sure what issues you'd run into on various pages if you did that though (so it'd probably need a lot of iteration- and fixing bug reports).

It might be a fun project to start though. I've been really enjoying testdouble's API (and have started using that for my unit tests).

V8 Release 5.1 10 years ago

Thanks for the link. I didn't know about Orinoco, and I'm excited about WASM.

...and performance improvements are always good!

I believe 'babel-root-import' works on windows (haven't tested myself). It's a lifesaver if you are already working w/ babel (which I am).

It really saves time when you forget what nesting level you are at, and are trying to get to some other folder. I can easily remember my absolute paths, but always forget the amount of "../../.." I need. It's also nice to be able to copy imports from your "src" folder to your "test" folder, and just have them work (which they do when using absolute paths).

This is an interesting take on that idea (using symlinks instead of transpiling).

In the root project folder (containing package.json and ./node_modules), you can run the following:

    comm -12 <(ls ./node_modules) <(curl https://gist.githubusercontent.com/azer/db27417ee84b5f34a6ea/raw/50ab7ef26dbde2d4ea52318a3590af78b2a21162/gistfile1.txt) 

It will output any of the modules that @azer unpublished yesterday (that are being used by your project).

There's an inline style on a div that states:

    margin-left: 150px !important; margin-right: 150px !important;
Changing the `150px` to `10%` seems to make the site slightly responsive while looking about the same (on my macbook with a 1440px viewport):
    margin-left: 10% !important; margin-right: 10% !important;

Haha. Yeah. That jumped out at me.

#2 - Put the customer first (except when listing our core values, then put them second).

I understand the sentiment, just a weird juxtaposition with "#2" and "first"