398 karma · joined March 15, 2016
The long-term health consequences don't feel real when you're young. It's easy to dismiss, even if you logically understand the risks.
The expense is not a problem. Utterly unimportant.
The addictive aspect is a subtle beast. It creeps up on you slowly. At first, smoking is a great, fun thing to do every once in a while. It's a great, fun thing to do with friends. Slowly, every once in a while turns into every day. Then, a few times a day. Now you need a cigarette to start the day right. You try to cut back and only then realize you're addicted.
I'd be very interested in learning about the N64's 3D API and ABI and the issues with it, if you'd like to expand on that. Or maybe you know of a blog post or article already covering the topic?
I think we should stop using these terms.
The article provides no meaningful analysis. Here’s what might have made it worth reading:
* How does the hardware, and software like the kernel, manage heat in the machine?
* Some information about CPU power states, &c, and how the kernel interacts with the hardware regarding them.
* Some analysis of how Activity Monitor works and why it ascribes a certain amount of CPU activity to kernel_task, or to any other task.
Voxels were stored in a buffer sorted in Morton order. The idea was to balance performance improvements realized by increased spatial locality against the cost of computing the Morton codes. The trade-off was only worthwhile on Intel because of the use of pdep/pext in optimized encode/decode functions.
I imagine something similar would probably apply to texture lookups in a software 3D renderer.
This is commonly accepted wisdom, but it's not entirely true. (It's only a little bit true.)
The kernel is a freestanding environment where big chunks of the standard library are missing. However, the most useful parts, like unique_ptr<T>, can be reimplemented as needed.
The kernel absolutely can support RTTI and exceptions. Porting libcxxrt is relatively simple, for example, even if implementing the entire Itanium C++ ABI is a big task. Though, the kernel should still avoid throwing and catching exceptions in sensitive code like interrupt handlers. This is not radically different from other C++ projects. The use of exceptions is typically discouraged, for example, in tight inner loops.
It is true that enabling RTTI and exceptions causes code size to explode. This is a valid concern. While memory is cheap, cache misses are not cheap. Mark functions and methods with "noexcept" as needed where this becomes a problem.
Finally, it's absolutely true that exceptions make it impossible for the kernel to make solid real-time guarantees. Fortunately, most operating systems only have soft real-time constraints, if that.
Sometimes scooters are parked on the side of the road. Sometimes scooters are parked in a ditch beside the road. Bikes rarely are.
It would be a lot easier if it were much, much easier to negotiate work-life balance while negotiating compensation. Unfortunately, I’ve never found this to be practical. Management has certain expectations set by company social norms. Any employee found violating those norms is punished in one way or another.
Not at all. Please refer to the Wikipedia page on "False advertising" for an overview of what does and does not constitute false advertising.
Glyphosate is sometimes used as a desiccant to alter the timing of wheat harvests, ensure even ripening, and to make harvesting easier. While it's not a widespread practice, it does happen in the US.
The alien in Blindsight also apparently does not care to understand such things, and may lack the capacity for this kind of thought. It runs entirely on instinct, but these instincts bake in extremely complex behaviors that are beyond human capabilities.
I'm also reminded of two other aliens from other Sci Fi series: 1) the Orkz from Warhammer 40k. Dumb as a rock, but can build devastatingly effective vehicles and weapons from salvage and garbage. God knows how. They certainly have no idea. 2) The Motie engineers from "The Mote in God's Eye." They can instinctually build and improve on machines but cannot understand, or come close to explaining, How they did it.
What about any application that cares in the slightest about performance? In this case, memory layout is incredibly important, and many (most?) of those higher level languages are immediately disqualified.
However, a major plot point in the movie is that time does not exist and that there is no such thing as causality. In the world of Arrival, there is not a lot of reason to believe that mathematics, logic, and science are capable of bringing us to a true understanding of the universe. It wouldn't work to teach human mathematics to the aliens because human mathematics is weird and wrong.
I've been spending the last few days reading through the docs and learning how to use Metal. So, I'm curious what you (and anyone else, I guess) perceive its shortcomings to be.
Why do you disagree? What specific points do you disagree with? Is that link meant to be a counter to the argument that "text formats suck?" If so then how does it demonstrate this?
If you're saying that your text protocol is good enough for your purposes then I have to wonder if maybe you aren't doing anything particularly latency sensitive.