The list in the above comment isn’t a summary — it’s a precise definition. It can and must be carefully explained with lots of examples, contrasts with other languages, etc., but the precise definition itself must figure prominently, and examples and intuition should relate back to it transparently.
Is NVIDIA's JIT-based approach here similar JAX's, except targeting CUDA directly rather than XLA? Would like to know how these different JIT compilers relate to one another.
Number of job posts itself seems like a better measure of the state of the job market than mentions or mention-density. What aspects might mentions capture that number of postings wouldn’t?
There's also the popularity of HN itself and the popularity of posting jobs on HN that's an important factor.
You could both normalize the figures and include a separate graph for job posting density per month or something like that. Total posts on HN monthly would also be interesting to visualize. Is it trending up or down?
There's also the popularity for HN based upon the particular language.
It's possible there's skew where rust becomes more popular say, and gets the bulk of the new posts, but python or java aren't super interesting anymore. So those people stop showing up to HN.
I'd like to see the popularity of posts by language. I bet we'd see a lot fewer Java and Python posts compared to Rust.
The article does not claim that smoking determines outcomes for any individual. It gives statistical evidence that outcomes (measured brain activity while performing certain tasks) for weed smokers are worse than for non-smokers __on average__, and that this pattern persists in various subpopulations determined by demographic and lifestyle factors.
Cryptanalysis relies on deep conjectural heuristics in analytic number theory. These conjectures becoming theorems wouldn't affect cryptanalysis at all, because their validity is already baked in. If, however, any of these conjectures turn out to be false, there would be ramifications.
Correct. HTMX doesn’t deal with client-side state and updating UI in response to client-side interactions. React, on the other hand, is all about that stuff.
One example where it's leaky is when you want to memoize something, and now you need to memoize all its dependencies, recursively, and you end up with a 30 file PR.
I say this as a big fan of React, and I'm hoping the compiler turns out a success.
Well, they're part of the effects abstraction. And they are leaking because you have to manually track them. You are already using the dependency variables inside the hook function. And now you need to duplicate them into an array and keep the array updated as your effect hook changes. This is leaky.
