jstrong

9 ms·

61.
by jstrong 4y ago
if masks work so well, why didn't they work? how did omicron get around the world in like two weeks flat when everyone was wearing masks on planes? at what point does covid making an utter mockery of our mitigation efforts start to den
62.
by jstrong 4y ago
in rust code, I like using `debug_assert!` to represent numerical expectations/assumptions of the implementation. later if I have a problem, I can turn on debug assertions and I will get a bunch of additional checks. but I can also tur
63.
by jstrong 4y ago
> I feel absolutely no sympathy
64.
by jstrong 4y ago
luna is way down, but there's still a luna/usd market.
65.
by jstrong 4y ago
the one of those most likely to be humming along fine is redis in my experience. once ssh'd to the redis box (ec2), which was hugely critical to business: 1 core, instance had been up for 853 days, just chilling and handling things lik
66.
by jstrong 5y ago
the reaction I had was, don't speak to your Dad with the same tone you would use in a HN thread.
67.
by jstrong 5y ago
compressed storage would bring huge performance and size-on-disk wins. I suspect the issue is the difficulty and resources needed to add compression on top of the existing design rather than a decision that the tradeoffs are not worth it.
68.
by jstrong 5y ago
sorry - you'll have to pry my model m from my cold, dead fingers
69.
by jstrong 5y ago
are there any examples of this technique used in open source projects? I'd be interested to look at the code and see what you mean in greater detail.
70.
by jstrong 5y ago
I am a very avid proponent of rust. however, here are a few places I have had difficulty in working on custom storage engines in rust: - uninitialized memory: it is tricky to get the semantics of uninitialized memory right. the ergonomics o
71.
by jstrong 5y ago
I read the article and could not believe that was their takeaway. sometimes people are determined to vindicate their technology choices, no matter what.
72.
by jstrong 5y ago
agree with your read on the article but not on your conclusion. in general, I don't think fudging the truth for strategic reasons ever turns out well in the long run, mostly because, we're not smart enough to anticipate what the l
73.
by jstrong 5y ago
what is the special hardware/setup that achieves mid-single digit number of microseconds latency for deep learning inference you referred to?
74.
by jstrong 5y ago
influxql is limited, yes, but much less verbose for time-based aggregation than the equivalent sql queries, which is why I like using it for adhoc visualization and inspectibility. (I don't like flux). to me it's great for a limit
75.
by jstrong 5y ago
> The Performance P270 slots in as the lower-performance eight-stage, dual-issue, in-order processor that supports RISC-V Vector Extension v1.0, which SiFive says makes it an ideal candidate to replace SIMD architectures. I did not under
76.
by jstrong 5y ago
this article is pretty thin gruel.
77.
by jstrong 5y ago
slightly unrelated, I used to open nytimes.com articles with a new private browswer session to avoid paywall, but this no longer works. any other ways to avoid registering/paywall to read their articles?
78.
by jstrong 5y ago
it's often not particularly crucial for timeseries data, though, and the performance tradeoffs of syncing every insert to disk are significant.
79.
by jstrong 5y ago
the design you propose is to write 10sec chunks of data to an append-only log, which will contain chunks from multiple tables/series? if so, then reading larger ranges than 10sec requires scattered reads of a bunch of small chunks inte
80.
by jstrong 5y ago
I have stored a wide manner of arbitrary data in UUIDs, and had great success with that technique.
81.
by jstrong 5y ago
> The point is that if you only need to join and aggregate data it's easier and more efficient to do it directly in SQL citation needed? I've seen plenty of cases where it would have taken the db ages to do something that panda
82.
by jstrong 5y ago
I've been coding predominantly in rust since 2018 and have never encountered a build time > 10min.
83.
by jstrong 6y ago
> There is nothing more convenient than SQLite for analyzing and transforming JSON. the example query given: select json_extract(value, '$.iso.code') as code, json_extract(value, '$.iso.number') as n
84.
by jstrong 6y ago
> We hold these truths to be self-evident, that all men are created equal, that they are endowed by their Creator with certain unalienable Rights, that among these are Life, Liberty and the pursuit of Happiness
85.
by jstrong 6y ago
also a long-time rust user, and I buy this. one of the things it took me longest to realize when writing rust is to reach for traits carefully/reluctantly. they can be amazing (e.g. serde), but I've wasted tons of time trying to m
86.
by jstrong 6y ago
rust has avoided many pitfalls that python fell into. one example is the way that rust 2015 edition code works seamlessly with rust 2018 edition code, unlike the python2 -> python3 debacle. another is cargo vs pip/poetry/this m
87.
by jstrong 6y ago
I've been primarily coding in rust since 2018. I never cared for async/await, and I've never used it. (at some point, coding event loops became very natural/comfortable for me, and I have no trouble writing "manual&
88.
by jstrong 6y ago
I disagree their judgement was right - I think it was catastrophically wrong. there are some things that you can treat this way (let it blow over), but a reporter saying the n word to a group of high school kids is not one of them. the fact
89.
by jstrong 6y ago
external services don't always have a test API, and it's not always as cut and dry as processing user payments. sometimes it's less important than that, and testing it would require replicating an external server to be able t
90.
by jstrong 6y ago
usdt/usd market at kraken holding at ~$1 https://cryptowat.ch/charts/KRAKEN:USDT-USD

More ›