tudorpavel

The one phrase that irks me as overly dramatic and both GPT and Claude use it a lot is "__ is the real smoking gun!"

I'm a non-native English speaker, so maybe it's a really common idiom to use when debugging?

For me it was available today on one laptop, but not the other. Both logged into the same account with Plus.

Ruby's Integer type works like BigInteger under the hood.

If you aren't, try using the Firefox Beta version, or Firefox Nightly which I'm using to be on the bleeding edge.

Most of the steaming platforms use HTTP Live Streaming (HLS) because it avoids all the networking NAT headaches that come with p2p connections and it handles variable quality better because each client fetches the best quality for their bandwidth. As far as I know, with WebRTC the sender degrades quality to satisfy the slowest peer.

That said, the downsides of HLS are potentially higher infrastructure costs required to transcode video to the different qualities and somewhat related is the higher latency to live. With proper tweaking you might get 2-3 seconds of latency, but it might be too much for your use case.

If there is voice interaction between the yoga instructor and their students the HLS delay will certainly be noticeable.

+1 to self code reviews, I almost always find stuff I've missed or could have done better.

Could you expand on the Ruby part? I'm not sure if you hate all programming or programming in anything other than Ruby.

DRY is good but like any abstraction it has tradeoffs. It might give you a warm feeling to do the refactor, but you might end up with code that's harder to understand and harder to replace.

Not really and Dan didn't invent React, he is currently on the core team. Just ignore trolls such as GP, it ain't worth it.

For me AoC was perfect while learning a bit of Rust last year, but tread carefully if you want to have 2 mutable references to the same value like a circular or doubly linked list.

Good luck and have fun with it!

I'm so excited! I discovered AoC in 2017 and I've participated last year as well. In 2017 I used it as an excuse to practice my JavaScript chops using ES2015 classes. Last year I learned me some Rust while doing the problems, at least up until I had to implement a doubly linked list and gave up on using Rust for the rest of the problems.

Hopefully this year I can make it past day 14. It's strange, but I got stuck or tired on day 15 both years. We'll see how it goes, I'm planning on learning Clojure this year with AoC. I've only started learning the language a bit these past 2 weeks, but I'm sure I'll have fun with it.

To all participants this year: remember to have fun!