712 karma · joined September 21, 2018
Especially if you watch lectures at 2x the speed, you can save A LOT of time. And I'd bet your understanding is better, since lecturers can think through problems out loud. Indispensable, IMO.
https://ocw.mit.edu/courses/15-401-finance-theory-i-fall-200...
The lectures are well structured. Class questions are good.
And best of all... these lectures were done during the 2008 financial crisis, so you see how people react in real time. Fascinating.
Is this basically an RBDMS and Kafka in one? Can I use SQL?
I understand the handwaving around programming semantics, but I'd like clearer explanations of what it actually is and how it works. Is this a big old Java app? Do you have ACID transactions? How do you handle fault tolerance?
It may be early, but I believe folks will be curious about benchmarks. And maybe, someday, Jepsen testing.
Please no buzzwords like "paradigm shift" or "platform". If diagrams are necessary, I'd love to read a post that explains clearer.
If it’s due to the language design, how will Mojo avoid a GIL, given its goal is to be a superset of Python?
Can you provide some thoughts on the benefits of doing ML on Elixir vs. Python? Is the benefit the language semantics? Is it much easier to get distributed work in Elixir ML vs Python ML? Are the tools better/smoother? Are there ML ops improvements? Perhaps there’s a blog post I missed :)
It’s extremely powerful, which is great! But I want a linter that tells me, “Hey - you’re monkeypatching that. I’m going to fail this build unless you explicitly indicate you know what you’re doing”.
I don’t know of a convincing linter that has a complete solution to this. Feel free to chime in if you know of one! I’m guessing this is possible in Rubinius, but not sure about the standard Ruby VM.
There’s an analogy with tech debt or old software here somewhere.
Not that it matters - this solution is probably the right way to go without building something into Twitter itself - but the more data/stats oriented folks may be confused or irked by calling this “A/B testing”
https://docs.github.com/en/site-policy/github-terms/github-t...
also it turns out that having more than one GH free account is against the terms of service:
https://docs.github.com/en/site-policy/github-terms/github-t...
Just not sure if that separation will hold up if you have a single GitHub account.
I had a question about this part:
> We found out that this model does not fit all data acquisition use cases, such as out-of-order data
I know the whole blog post is about how you're now able to handle out-of-order data, but I'm curious - what use cases is QuestDB best for? Can you provide some concrete examples of where customers have ordered data and need QuestDB?
I have to imagine they'll eventually have to subsidize a free version by creating a really souped-up premium version that has killer features.
Or they become an acq target by Google or something, and then things could get interesting!
For sure, but at the moment it definitely is not that, and it's going to take a long long time before we get there. People have wanted thin clients for decades!
If I wanted to burn a hole in my wallet, I'd pay for Mighty, sure. The average user won't see a big benefit to this for a long time though.
The price point is too high for cheap users and the feature set is too small for power users, IMO.
I kind of understand the price point if you're getting a whole "computer in the cloud" kind of thing, but for just a browser, it feels like a rip off.
And you're capped by internet speeds too... yeah that's rough.
I'm a bit skeptical of Rails performance with the method the author details here, given that Ruby is much, much slower than Elixir.
I'm curious if even Elixir folks deploy Live Views in consumer-facing apps. But I can totally see it being used for admin interfaces or internal applications, for sure.
Impressed with GH folks in finding this, though I wonder how many more of these types of bugs are out there in Ruby libs. It'd be nice to make this more difficult to do, a la FP languages, by making it really intentional to modify state. Maybe in Ruby 4??
I'm just curious how these changes actually make it to millions of people's browsers