Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jstrong
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
121.
▲
by
jstrong
6y ago
as a rust dev, much appreciated that there is a rust port of this!
122.
▲
by
jstrong
6y ago
this looks pretty promising. what I am most excited about is the way that the syntax minimizes repetition. from the examples[1], this is pandas: tips[(tips['size'] >= 5) | (tips['total_bill'] > 45)] this i
123.
▲
by
jstrong
6y ago
do you have any recommended entry points for reading dovecot's code? I opened it up on github and it's a very large library! thanks for any help you can provide.
124.
▲
by
jstrong
6y ago
agree 100%. it honestly kind of baffles me, "async" is like the programming community's white whale, and all of us get to come along for the chase. meanwhile, I long ago grew accustomed to the paradigm of an "event loop&
125.
▲
by
jstrong
6y ago
I've experienced excellent results building distributed systems where the nodes talk to each over via raw udp. often, in the context of message queues, there is much talk about delivery guarantees, but in many contexts the same goals c
126.
▲
by
jstrong
6y ago
> just macro-decorate the main function, sprinkle some async/await around, maybe add a join or a mutex somewhere, and then pretty much forget all about event loops, messaging, threads and whatnot that is ... not how I have experienc
127.
▲
by
jstrong
6y ago
are there any good articles about what has gone so, so wrong at intel in the last few years?
128.
▲
by
jstrong
6y ago
I'm a theano diehard, and I'll never get over how google came along, introduced a shittier version of theano, garnered worldwide acclaim for it, and killed the better library in the process.
129.
▲
by
jstrong
6y ago
congrats to Frank McSherry and the rest of the materialized team! very impressed by your project.
130.
▲
by
jstrong
6y ago
I've always found that when you are solving a concrete problem, like you were, it's vastly easier than the case of a general-purpose database because you can make all the tradeoffs that benefit your exact use case. but it sounds l
131.
▲
by
jstrong
6y ago
hooray for zstd compression!
132.
▲
by
jstrong
6y ago
looks interesting. is there any place to read about its design goals or how it is being used?
133.
▲
by
jstrong
6y ago
cool. interested to see the TSM library. if it's any use to you, here's an unpublished rust influx client crate I've been using for a few years. the main point of interest is an ergonomic macro to construct measurements, `mea
134.
▲
by
jstrong
6y ago
do you expect any of your work on this to end up as rust libraries that can be used on their own?
135.
▲
by
jstrong
6y ago
a millisecond is a long time in computer terms. many meaningful decisions can be made in a millisecond.
136.
▲
by
jstrong
6y ago
if you are sending data to "yourself" and performance is important, defining your own binary protocol can be very effective. every time I go to grok protobuf, thrift, et al. I end up just rolling my own format because it's so
137.
▲
by
jstrong
6y ago
my guess is it would take me a lot longer to finagle the database to do what I want, but that's me.
138.
▲
by
jstrong
6y ago
hugely impressed at the skills displayed.
139.
▲
by
jstrong
6y ago
the phrase "rearranging deck chairs on the Titanic" comes to mind...
140.
▲
by
jstrong
6y ago
caveat: I'm not familiar with the clickhouse codebase. however, usually "embedding" musl libc is about portability - it allows you to build an entirely static binary that can run on practically any box. is this different? sec
141.
▲
by
jstrong
6y ago
ah, I see what you wanted now (`max(col) > 10...` -> [true, false, true, ..]). seems like it would be pretty easy to use numerical transformations for the same thing, depending on how you were going to be using it: `select max(col) -
142.
▲
by
jstrong
6y ago
not a solution architect but, just delete by a very specific timestamp. this is not possible if you are writing at coarse time precisions, so don't do that. `delete from meas_name where time='2020-07-22T15:40:58.375506762Z'`
143.
▲
by
jstrong
6y ago
it's not that hard: `select max from (select max(temperature) from measurement_name group by time(1h)) where max > 10`
144.
▲
by
jstrong
6y ago
to each his own - I find influxdb somewhat flaky but the best part about it is not having to write the atrocious sql queries I would need to to get the same kind of windowed aggregations. `group by time(1h)` and so on is pretty handy.
145.
▲
by
jstrong
6y ago
personally I think the mistake is trying to fit both purposes into a single format or type. as you state, it's a fundamentally different data type. representing a fixed moment in time is hard. representing a "floating" time o
146.
▲
by
jstrong
6y ago
Have you written a lot of concurrent code in rust? Did your experience doing so convince you that it's something you should "fear" doing?
147.
▲
by
jstrong
6y ago
one technique that could be used (to get high compression rates on compression applied to each frame) is to train a compression "dictionary" on the first few seconds/minutes of a data stream, and then use the dictionary to co
148.
▲
by
jstrong
6y ago
God, I hate this attitude.
149.
▲
by
jstrong
6y ago
if `self.cleanup()` panics, the program crashes, though? How is a memory leak even a relevant concept in that case?
150.
▲
by
jstrong
6y ago
"This meeting is to announce we've settled on an architecture for the next gen grid optimization program: Electron UI with a Ruby on Rails app underneath the hood that calls to AWS Lambda for anything that's cpu-heavy. State
More ›