RenderDoc is very cool, but more of a high level debugger, I guess? It's also good to analyze performance issues, e.g. when working with QML and QSG_VISUALIZE=overdraw / batches (both very high level) don't cut it anymore, or to get a different perspective. Watching a scene getting drawn API call by API call is fun.
3 million wreaths for 30 million USD, is that correct? That's still a dubious arrangement, but a sane price and far from the unbounded greed and depravity of some usually large and public corporations.
If the price is sane, I wonder if there is a competitor looking to break into the action, hence the appearance of a piece "asking questions". A great method is to break up the original operation, insert a company that has no compunction about charging higher prices in the name of good process, and clean up.
I just went on Amazon and the wreaths there are like $20-$50. It makes sense that a bulk purchase should be less, so $10 does feel reasonable though I am no expert.
With LLMs becoming so good at coding, "just never make any mistake" is also becoming easier. I usually write my own code because I don't like the coding style of LLMs, but on more than one occasion now they have proven very useful as code reviewers and bug hunters.
We were talking about Rust issues. But yes, C should have a proper string type. But as long as it does not have a better standardized string type, it is possible to define your own (or use a library).
Unfortunately, I really doubt long rust's "forever" will last in the wake of the `time` crate controversy. I can't see like a lot of good options in that place from the perspectives of the rust-std maintainers, but it might've just been worth it to wait for a new edition or similar.
I've always found Perl just plain ugly, too clever about some things (like iterating over regex matches on stdin or something) and really dumb about other things (variable syntax, the god-awful OOP system). Python is clean and pretty in comparison and usually well thought out.
If the communities were reversed, I'd still prefer Python: I just read the documentation in 99% of cases, I very rarely need to interact with the community. Python, as the article says, is mostly not a language for fans - it's mostly for auxiliary tasks.
Just like increasing the structure size "only" decreases the likelihood of bit flips. Correcting physical unreliability with more logic may feel flimsy, but in the end, probabilities are probabilities.
Is it collateral damage if they get sky-high prices for their products instead of a smaller amount for the production equipment? The US thing seems like a convenient excuse of sorts for cartel behavior.
reply