cnity

39 ms·

571.
by cnity 6y ago
I'll give it a watch, thanks.
572.
by cnity 6y ago
This guys' articles are wonderful. I was experimenting with compiling C to WASM[0] and Surma's was really helpful. [0]: https://surma.dev/things/c-to-webassembly/index.html
573.
by cnity 6y ago
I believe you, it was only a hunch. Not backed up by evidence! I've been way off about my intuition of frequencies, especially with non-harmonic sounds like key presses :)
574.
by cnity 6y ago
If you want to compute an FFT with fewer bins you can also use STFT and configure the bin count and hop size (essentially computing many FFTs of smaller regions of the signal and computing the average). A quick side note, 16kHz is quite a l
575.
by cnity 6y ago
I don't quite understand what you mean. Do you mean that in general you don't recommend DFT for signal processing? This seems counter to most approaches in the field. Issues (aliasing, spectral leakage, etc) arising from DFT more
576.
by cnity 6y ago
Hey. I've been working on an audio recognition tool that is remarkably similar to this one, and there are a few areas I strongly recommend exploring if you want to improve the classification performance. For waveform similarity, you ma
577.
by cnity 6y ago
That's cool. Do you have a write-up of this somewhere?
578.
by cnity 6y ago
I really hope they call it `fold_first`. If they call it `reduce` I will forever be thinking "which one takes the initial arg again?"
579.
by cnity 6y ago
> That's what the web is today Are you suggesting that the web is the way it is today because benevolent governments dictated it be so? Do you have any links about this?
580.
by cnity 6y ago
How do you think the creator of the site would feel reading this comment?
581.
by cnity 6y ago
For the most part, I agree. Some things really do work better in a "borrow" type system. For instance, I'm fixing up my old bike and the sheer number of tools necessary for basic tasks is astounding. I wish there were some lo
582.
by cnity 6y ago
I regret my tone. I let cynicism get the better of me there, sorry!
583.
by cnity 6y ago
This exchange highlights the uselessness of pithy one-liner self help remarks: they're interpreted according to what people have already experienced, and they're highly contextual.
584.
by cnity 6y ago
It sounds a little like you're just learning similar languages.
585.
by cnity 6y ago
What's most interesting to me about this comment is the use of an example of a closed loop environment, despite the fact that _we're already in a closed loop environment_. We just pretend otherwise with landfill and the convenienc
586.
by cnity 6y ago
So in order to understand not only the basics of the rule, but also the underlying implementation and exactly in what way it would crash, it may require more than a paragraph. I'll concede that. But this is common in programming. As an
587.
by cnity 6y ago
I personally find these quite easy to comprehend, but I suppose I can see how it might be difficult. Edit: That was snarky, I apologise.
588.
by cnity 6y ago
What makes the fact that each hook call needs to be associated with an index so unacceptable?
589.
by cnity 6y ago
This is true, but even as a fan of hooks, I must admit that you'd be fighting a losing battle if you tried to convince your coworkers to merge your PRs with classes in them, in most places.
590.
by cnity 6y ago
So easy I can explain it in a sentence: React hooks must always be called in the same order, and the same amount. If you push me by asking "why?", I can expand that sentence by including "because each hook call is associated
591.
by cnity 6y ago
> Newline separated what? What I meant by this is that the newline character is the primary delimiter of the data, but I take your point. IMO, the best way to tackle the myriad ways of structuring data is to write parsers for them, not t
592.
by cnity 6y ago
Excellent. If there are things you notice, please feel free to raise as an issue, and pull requests are always welcome! > useful in my CI environment For sure. I've been meaning to play around with getting a docker image with the sh
593.
by cnity 6y ago
Thank you! It's pretty buggy at the moment, and maybe frustrating to use since it's missing some important shell features, but any feedback is always welcome.
594.
by cnity 6y ago
Exactly. This is common with shell scripting languages. They feel like some awful duct tape, when in fact the perfect primitive for joining separate concerns already exists (the pipe). Using a nicer language (like modern JS) to perform proc
595.
by cnity 6y ago
It doesn't have to be this black and white, in my opinion. The most common data structures I've interacted with on the command line are _newline separated_ or _JSON_. What if your shell allowed parsing of JSON natively? npm list -
596.
by cnity 6y ago
Your ideas are something I wrestled with while I was writing (a very similarly named) crsh[0]. I chose to avoid trying to reimplementing commands and instead stuck with an unstructured environment, but with the ability to parse output using
597.
by cnity 6y ago
That's one thing, but another thing that is not listed as one of the possible reasons is simply that the original email is just verbose and _bad_. Imagine a person in real life gave you that spiel, of course you'd be put off.
598.
by cnity 6y ago
That's because what they mean is that the moon appears more brightly at night, and I suspect you know this. You don't _actually_ think these people have never seen the moon during the day, surely?
599.
by cnity 6y ago
That's just not true: https://reactjs.org/docs/forwarding-refs.html
600.
by cnity 6y ago
Agreed. Just for clarity, my choice was a tongue in cheek synecdoche.

More ›