I think that’s because the barrier to entry for a beginner is much higher than say python.
Python has a reputation for being good for beginners so it's taught to beginners so it has a reputation for being good for beginners.
Readit Newsazkalam commented on AI will make formal verification go mainstream martin.kleppmann.com/2025... · Posted by u/evakhoury
azkalam commented on Netflix to Acquire Warner Bros about.netflix.com/en/news... · Posted by u/meetpateltech
How did good movies and TV shows get made before the panopticon? How did we get Casa Blanca when there were no Nielsen ratings?
Success rate in that era was very low. There are thousands of movies from that time that no one cares about today.
I'm also in a few local leaderboards, but I'm not "really" competing, it's more of a fun group thing.
Premises:
(i) I love Advent of Code and I'm grateful for its continuing existence in whatever form its creators feel like it's best for themselves and the community;
(ii) none of what follows is a request, let alone a demand, for anything to change;
(iii) what follows is just the opinion of some random guy on the Internet.
I have a lot of experience with competitions (although more on the math side than on the programming side), and I've been involved essentially since I was in high school, as a contestant, coach, problem writer, organizer, moving tables, etc. In my opinion Advent of Code simply isn't a good competition:
- You need to be available for many days in a row for 15 minutes at a very specific time.
- The problems are too easy.
- There is no time/memory check: you can write ooga-booga code and still pass.
- Some problems require weird parsing.
- Some problems are pure implementation challenges.
- The AoC guy loves recursive descent parsers way too much.
- A lot of problems are underspecified (you can make assumptions not in the problem statement).
- Some problems require manual input inspection.
To reiterate once again: I am not saying that any of this needs to change. Many of the things that make Advent of Code a bad competition are what make it an excellent, fun, memorable "Christmas group thing". Coming back every day creates community and gives people time to discuss the problems. Problems being easy and not requiring specific time complexities to be accepted make the event accessible. Problems not being straight algorithmic challenges add welcome variety.
I like doing competitions but Advent of Code has always felt more like a cozy problem solving festival, I never cared too much for the competitive aspect, local or global.
Do you know of anything like AoC but that feels less contrived? I often spend the most time understanding the problem requirements because they are so arbitrary - like the worst kind of boardgame! Maybe I should go pick up some OSS tickets...
Opinion poll:
Python is extremely suitable for these kind of problems. C++ is also often used, especially by competitive programmers.
Which "non-mainstream" or even obscure languages are also well suited for AoC? Please list your weapon of choice and a short statement why it's well suited (not why you like it, why it's good for AoC).
Terse languages with great collection functions in the standard libraries and tail call optimization. Haskell, OCaml, F# ...
azkalam commented on Event Sourcing in Go: From Zero to Production skoredin.pro/blog/golang/... · Posted by u/tdom
Sqlite can scale CQRS to 100000 events per second on a relatively small VPS. That's 10x what the author achieves with postgres.
You can scale them independently in that you can control the rate at which your views are read and the batch size of your updates.
The whole big win wirh CQRS is it allows for very efficient batching.
But only one server can access each SQLite at a time?
azkalam commented on Event Sourcing in Go: From Zero to Production skoredin.pro/blog/golang/... · Posted by u/tdom
Please explain how you intend to use different models for reading and writing without there being some temporal separation between the two?
Most all CQRS designs have some read view or projection built off consuming the write side.
If this is not the case, and you're just writing your "read models" in the write path; where is the 'S' from CQRS (s for segregation). You wouldn't have a CQRS system here. You'd just be writing read optimised data.
- Write side is a Postgres INSERT
- Read side is a SELECT on a Postgres view
azkalam commented on Event Sourcing in Go: From Zero to Production skoredin.pro/blog/golang/... · Posted by u/tdom
I'm going to have a word with my ISP. It seems that sites SSL certificates has expired. That's not a good thing, but my ISP decided I'm an idiot and gave me a condescending message about accepting expired certificate - unacceptable in my book. VPN helped.
Too much dry code for my taste and not many remarks/explanations - that's not bad because for prose I'd recommend Martin's Fowler articles on Event processing, but _could be better_ ;-)
WRT to tech itself - personally I think Go is one of the best languages to go for Event Sourcing today (with Haskell maybe being second). I've been doing complexity analysis for ES in various languages and Go implementation was mostly free (due to Event being an interface and not a concrete structure).
> Go is one of the best languages to go for Event Sourcing toda
Can you explain this? Go has a very limited type system.
azkalam commented on Event Sourcing in Go: From Zero to Production skoredin.pro/blog/golang/... · Posted by u/tdom
How does event sourcing handle aggregates that may be larger than memory?
azkalam commented on Python 3.14 is here. How fast is it? blog.miguelgrinberg.com/p... · Posted by u/pjmlp
LOL, python is plenty fast if you make sure it calls C or Rust behind the scenes. Typical of 'professional' python people. Something too slow? just drop into C. It surely sounds weird to everyone who complains about Python being slow and the response is on these lines.
This assumes the boundary between Python and the native code is clean and rarely crossed.