HNHacker News
TopNewBestAskShowJobs

samhld

7 karma · joined May 17, 2017

submissionscomments
samhld··on Most Popular Programming Languages on GitHub by OSS Insight
Interesting. I've never seen it take more than a second, or maybe two.
samhld··on Most Popular Programming Languages on GitHub by OSS Insight
The data is stored in TiDB and queried from there. Is there a reason you assumed it was dynamically loaded in full via the Github API?
samhld··on GitHub Statistics
GPT-3
samhld··on Robinhood is said to draw on bank credit lines amid tumult
The concept of "accredited investors", itself, is a great data point for why our implementation of capitalism isn't really capitalism. When opportunities are given explicitly to the rich, you don't have a free market.

I know that's not 100% relevant but it was therapeutic to write it.

samhld··on Robinhood is said to draw on bank credit lines amid tumult
Thanks for spreading the word. The DTCC portion of this sounds like they had a "liquidity problem" in the sense that they were trying to prevent one.

The portion about not having a plan for when market makers don't want their action -- and they have to instead pay to use exchanges -- seems like a pretty stupid problem they set themselves up for.

Do have this right?

samhld··on Robinhood is said to draw on bank credit lines amid tumult
I'm confused why you're bringing up "blocking people from selling". Has that ever happened? It certainly isn't happening here.

Edit: I'm guessing it's because the above comment said "only BUYING". I think that was a distinction from blocking both buying AND selling. If you block only one, it forces the market.

samhld··on ListenBrainz moves to TimescaleDB
Yep you're right -- oversight on my part. To be clear, the "not sure why you'd run a query like that" was referring to doing it the InfluxQL way (which is not the same thing)...where your results would end up being the same controlling for time range.
samhld··on ListenBrainz moves to TimescaleDB
Huh? I don't mean to come off as blaming anyone for anything. Trying to offer a work around for their problem with InfluxQL. They usually exist. They may not be good enough for some but offering them doesn't hurt. In this case, I certainly misunderstood the need though.
samhld··on ListenBrainz moves to TimescaleDB
(InfluxData solution architect here) Boolean is supported. You query it in the WHERE clause. Try `SELECT MAX(temperature) FROM ... WHERE temperature > 10`. That said, I'm not sure why you'd run a query like that in InfluxQL as it's the same as `SELECT max(temperature)`. :).
samhld··on ListenBrainz moves to TimescaleDB
(Solution architect at InfluxData here) Out of curiosity...what was the need for this DELETE? Deleting (not dropping) being somewhat of a "second class citizen" was a design choice to make room for more pressing time series needs. In my experience, `DELETE`ing is rarely necessary.