28,704 karma · joined May 2, 2010
Interests:
* Rust
* Robots
* Machine Learning
* Cybersecurity
That's how Unicode started but nowadays Unicode expresses things that are only used because Unicode itself introduced them.
And this while many important things in the "have used text in history" category have been unfinished or not tackled at all.
Nowadays these implants must be quite common. At least I encounter people wearing ones regularly. If their life can get more convenient with an implantable version this is fantastic news.
It starts, rightfully, by pointing out risks to health and physical harm. It later goes into depth describing how automation (the nail gun example) has changed the game, and especially how dexterity is in much less demand than it used to be.
It fails to point out that the same automation has made most blue-collar jobs much safer. Where I live, the paragraphs from the beginning, where everyone knows someone with a serious injury, ring true from my childhood in the 70s and 80s, but not anymore.
That seems like an important part of the picture when comparing blue-collar work then and now.
I would argue that it is more productive for the enduser as well. Not making a decision they cannot reasonably make is better then blindly believing in a decision that is likely wrong for your usecase.
Both are kind of outside the Rust compiler's influence. Macros can be almost arbitrarily complex: you pay for what you order. Codegen is LLVM, and that's a fixed choice. You can use Cranelift to get around it, but then you pay elsewhere.
Also, generics and monomorphization regularly come up in these discussion, while common wisdom seems to be that cost for the additional static analysis over other languages like C++ is no a major contributor.
Regardless, it's nice to see performance improvements in the compiler, even if you have to cooperate to benefit from them (e.g. by keeping your macros light and use less generics).
The difference from the past is that the US has always been a melting pot, while China is pretty much a closed society. If you’d emigrated to the US, you always had a good chance of blending into that diverse society no matter where you came from. Assimilating into the homogeneous Chinese society will take generations.
For me it’ll be either the westernmost end of Europe or one of the better parts of South America, in the hope that they will prosper modestly in the shadows of the upcoming conflicts.
Unfortunately I don't remember the details. I'd be happy to learn I was right after all;-)
He exercised the 15,625 options NVIDIA told him had vested. His claim now is that all 25,000 had actually vested, but NVIDIA’s letter gave him the wrong number. The letter was informing him of NVIDIA’s calculation; it did not change the option agreement. So the question is whether being given that incorrect information in 1996 gives him a claim today, despite both the exercise deadline and the statute of limitations having passed.
That being said, it strikes me as odd how empty this quadrant is. Why?
(Could mean string too, but that'd a different story)
In theory it should be possible to change the frequency of the video signal mid screen as well, but I have a hard time to imagine switching repeatedly every frame wouldn't have driven the monitors of the time crazy. Even multi-sync monitors needed probably a couple of frames to sync, right?
Instead we turned it into a worse version of television, where you still only consume passively what is fed to you while being watched and analysed.
The discussion how to deal with transcendentals in Rust is ongoing and at some point there will be a conclusion.
The Zig core team is apparently not concerned enough about the second point to forbid transcendentals at comptime and this is something that'd be hard to take back, because I'd break existing code.
From what I understand, there is hope for sqrt but there is no consensus on transcendentals.
I'd still like to encourage you to put some energy into getting it right because this mistake is very confusing for native speakers of a language that makes the distinction.
I cannot tell you how often I was listening to someone telling me a story about the thing where I sat impatiently waiting for them telling me which particular thing or person they ment only to realize they were not talking about something particular at all.
But I noticed that native speakers deviate from this at least in two cases:
1. Use thee to emphasize the following noun
2. When searching for the noun to say, they often get it wrong because they say something like "uh, thee, thee, thee, uh, book" and never sweat it.
Source: I watched a lot of Monty Python as a kid and John Cleese does this all the time.
Other parts, like floats are harder. This is where a difference shows. Rust is like: "Sorry, since we cannot uphold our guarantees, no transcendentals for you at comptime ", whereas Zig is chill about that and let you have your transcendentals even if results may differ between comptime and runtime. Different mindsets.
It's something Rust guarantees (without me having to take care of it e.g. by manually branching) and Zig does not.