HNHacker News
TopNewBestAskShowJobs

William_BB

166 karma · joined September 28, 2024

submissionscomments
William_BB··on CLion Is Now Free for Non-Commercial Use
Not complaining at all! I have just heard of other people facing the same issues and assumed that this must be a well-known problem. It might also just be template heavy projects -- maybe it works great otherwise. I don't have much experience with CLion in other contexts.
William_BB··on CLion Is Now Free for Non-Commercial Use
I used to be a CLion user. Unfortunately, it could not keep up with our large and heavily templated C++ codebase. Although CLion Nova with the new ReSharper engine improved things a lot, we found our custom clangd with emacs/vim/VSCode to still be much faster and convenient.

I know CLion also has clangd, but I believe it's their own fork. I am also not sure if you can enable all clangd features since it's not the main engine. I'd be happy to hear people's thoughts about this.

William_BB··on Advanced Python Features
I enjoyed reading the article. I'm far from a Python expert, but as an observation, most of these features are actually just typing module features. In particular, I wasn't sold on Generics or Protocols as I would have just used duck typing in both cases... Does modern, production-level python code use types everywhere? Is duck typing frowned upon?
William_BB··on 21st Century C++
E.g. `std::ranges::for_each`, where lambda captures a bunch of variables by reference. Like I would hope the compiler optimizes this to be the same as a regular loop. But can I be certain, when compared to a good old for loop?
William_BB··on Everything you need to know about Python 3.13 – JIT and GIL went up the hill
Hm I get the memory safety part, but could you elaborate on the compromised VM part? I'm not sure I understand that.. Specifically I don't understand what you mean by VM here
William_BB··on Everything you need to know about Python 3.13 – JIT and GIL went up the hill
Oh wow, I haven't thought about refcounts on mutexes
William_BB··on Everything you need to know about Python 3.13 – JIT and GIL went up the hill
All the answers were good, but I think this explained it the best. Thank you
William_BB··on Everything you need to know about Python 3.13 – JIT and GIL went up the hill
This was not a gotcha, sorry if it came across that way. It was a genuine question
William_BB··on Everything you need to know about Python 3.13 – JIT and GIL went up the hill
Can someone explain this part:

> What happens if multiple threads try to access / edit the same object at the same time? Imagine one thread is trying to add to a dict while another is trying to read from it. There are two options here

Why not just ignore this fact, like C and C++? Worst case this is a datarace, best case the programmer either puts the lock or writes a thread safe dict themselves? What am I missing here?

← PreviousPage 4 of 4