That isn’t what the article is about (despite its title)
458 karma · joined March 26, 2023
That isn’t what the article is about (despite its title)
Hoping that this is an oversight and that they will open-source the core platform in the next few months/years. It would be so awesome to hack/build on this platform
I imagine it would incur a non trivial latency and cost penalty. The memory modules are placed pretty close to the compute die right now. Cooling would also have to change (the memory modules produce a lot of heat).
But there is also no reason for any of the GPU manufacturers to do this. A skew with twice as much memory can go for a lot more than the difference in memory cost alone
(I'd love to be wrong though and see a real use case for some cool feedback loop of commands)
That is surprisingly greedy & selfish to be boasting about in their own blog.
Unless I am reading this wrong, I think all values between 0 and 1 have an equal probability (of 0).
The probability that a random uniform variable will equal any number between 0 and 1 is zero. It seems to follow that the probability of the difference between two uniform variables equaling any exact value would also be 0.
Have I missed something obvious? If zero really is the correct answer, that is pretty tricky.
If the compiler has defined behavior (and you have unit tests for that behavior) on all of these platforms, I don't think it is a huge deal. (Ideally you wouldn't... but sometimes its an accident or unavoidable)
As an example, while struct padding (problem 1) might not technically be in the spec, it is a cornerstone of FFI and every new compiler (that supports C FFI) has a way to compile structs with the same padding.
To my original point, if the article had instead given examples of compilers + architectures that produced different answers, I might feel differently. However, just saying mentioning that these weird edge cases are undefined (in the spec) doesn't mean much to me.
1) 8
2) 0
3) 160
4) 1 (both clang and gcc output a warning)
5) 2 (only clang outputs a warning)
While I like the idea of this quiz, I think it would be more powerful if it provided examples of compilers / architectures where these are not the correct answers. (I also think thorough unit tests would catch most of these errors)
EDIT: However, it is strange that the foundation has a totally different site.
Seems like an unavoidable consequence of how modern software is built
In my experience, they’ve improved massively over the last few years.
Most of the time, the docs directly explain how to solve some problem I have while also giving good context. I recently was messing with my boot loader and the docs were perfect
Do you have recommendations for a different framework for training? Accelerate seems fantastic for scaling up once I need to
> That said, who knows what the future holds. Maybe Wayland will manage to get a decent HDR solution that outstrips what's currently available on Xorg (i.e. nothing). There's a protocol in the works for this which has been in development hell at least.
As a side note, I wanted to go see what code was generated (and check the quality) but I couldn't find a docs.rs or github for the rust example (did I miss it?). I ended up having to look it up on docs.rs and was surprised that there were no comments there.
Do you have plans to add language-level documentation for the generated code?
Normally fine, but around my majority-mac coworkers, it stands out quite a bit. Silent 90% of the time though.
By that logic, if humans were actually intelligent, social engineering wouldn't exist.
Though, I still like the flexibility of adding additional fields to `Action1`. In golang I end up with fields that are conditionally populated based on the state of an Enum which is less than ideal and leads to lots of error checking (though this is relatively rare).
It doesn't have to be one or the other though. A bit more polishing on the Rust-style enums (perhaps in a different language) could lead to pretty ergonomic code.
I have an IPv6 address but haven't bothered memorizing it or giving it out because it would just be more hassle.