Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
afdbcreid
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
afdbcreid
6d ago
Measurement is for micro-optimizations, and it's definitely important. But you should also know the complexity.
2.
▲
by
afdbcreid
6d ago
Because complexity models that involve memory hierarchy are an active research area and are super complex. Also, "plain" complexity is still useful: despite the constant factor, at large N (and this is sometimes a real possibility
3.
▲
by
afdbcreid
6d ago
It is both amortized and average, because the map may need to grow. But the complexity without growing is average, not amortized (it's possible to build hash functions for which the probability will mean O(1) for all accesses, and hash
4.
▲
by
afdbcreid
6d ago
Allegedly, there is Rust in macOS (but maybe not in iOS), so maybe it's true even if you're using Safari.
5.
▲
by
afdbcreid
6d ago
Rust is already used in production for embedded (although only here and there). Not all places are ready, but I don't believe it's a decade away anymore.
6.
▲
by
afdbcreid
6d ago
No, after this made some waves he or some other senior (I don't remember exactly) reported that this is not an official plan.
7.
▲
by
afdbcreid
6d ago
There's an interop initiative by the Rust Foundation, there is a project goal to map the problem space, there was an effort to introduce an attribute (`#[rustc_splat]`) to allow calling overloaded functions, and there are various commu
8.
▲
by
afdbcreid
6d ago
Zig too. But this is far from being mainstream. Rust took around 5 years I think to become accepted in major companies, and those languages are harder to justify.
9.
▲
by
afdbcreid
6d ago
"Keep calm and clone" is a good advice for beginners. Then it is also a good advice for experts - because when you're an expert and you just think of cloning, that probably means it is easier than borrowing which you would
10.
▲
by
afdbcreid
6d ago
> This has also been a lot less effort than writing Rust I have never written such Go, but as an experienced Rust programmer I can tell you Rust is not hard to write after learning it. Learning it can take more time than usual (although
11.
▲
by
afdbcreid
6d ago
Android is a bit special inside Google (also Chromium). They are managed outside the main monorepo (google3) and their policies are different. From what people inside Google have told me, they do want to introduce Rust into google3 but that
12.
▲
by
afdbcreid
6d ago
It could as well be the opposite, but Rust does not need a proof of quality today, certainly not from Microsoft. Still, becoming Tier 1 in major trillion-dollar corporations (Microsoft, Meta, Amazon, and I know Google also has efforts in th
13.
▲
by
afdbcreid
6d ago
Yes, about as good as a language that is 40 years old, and was also (like Rust) 10 years old when becoming Tier 1 inside Microsoft, while there were far less alternatives. Seems pretty good to me ;) (I know you're joking).
14.
▲
by
afdbcreid
6d ago
They responded in the Zulip threads that yes, this is the plan, although they don't know if and what things will be open-source yet.
15.
▲
by
afdbcreid
6d ago
It is, with extensions (using rust-analyzer of course). I don't know what's the status inside Microsoft.
16.
▲
by
afdbcreid
11d ago
Not more than regular collections (unless you mean working on different parts with different threads, then it's still possible but harder, just like with regular collections).
17.
▲
by
afdbcreid
11d ago
Internally? No. Externally? Yes. That is the point.
18.
▲
by
afdbcreid
13d ago
Easy. https://docs.rs/intrusive-collections .
19.
▲
by
afdbcreid
15d ago
Also: > This is why most large and long-running programs have abandoned low-level programming languages. That's not true, as evidenced by the fact that this move has started before extremely sophisticated JIT compilers or garbage co
20.
▲
by
afdbcreid
15d ago
I know that. I also know that JITs cannot optimize to the same amount as LLVM due to the time limit, and that C++ and Rust are allocating much, much less than Java and even C# or Go, so a faster allocation scheme is much less needed there.
21.
▲
by
afdbcreid
15d ago
> If you trust those benchmarks then you deserve whatever you pick. I was talking about experienced experts who understand performance. Low-level languages can help your performance when the program is small and they generally hurt it wh
22.
▲
Rui Ueyama: "We are rewriting the mold linker in Rust"
(twitter.com)
6 points
by
afdbcreid
15d ago
|
7 comments
23.
▲
by
afdbcreid
16d ago
> Obviously, but that doesn't help me if the complexity in the unsafe parts is made worse, while the safety helps the parts where little help is needed. It's not like the danger in a C program is spread evenly, either. The comp
24.
▲
by
afdbcreid
17d ago
It's not really defense by obscurity (the JavaScript is public), more like defense by... being different?
25.
▲
by
afdbcreid
17d ago
So, they can interleave different tokens and get stopless access at normal price? Yes this needs to be tailored for Anubis, but that was the point: the moment it will become popular enough, scrapers will have no problems to bypass it.
26.
▲
by
afdbcreid
17d ago
But they operate from neither. You can at most sue the one renting them IP addresses. Which will do basically nothing. (Also, blocking a whole country is likely not what you do, but you probably know that).
27.
▲
by
afdbcreid
17d ago
It seems you misunderstood. It's not an explicit stability guarantee (such things is not possible), it's a debugging helper to crash the program more easily when it happens, requiring you to annotate the code.
28.
▲
by
afdbcreid
17d ago
> for instance by causing a stack overflow That's not "for instance", that's literally the only place Rust has unfixable UB on embedded (code on OS has other such things, e.g. reading/writing to `/proc/
29.
▲
by
afdbcreid
17d ago
You can in Rust! You just bundle it with a lifetime. But... This loses the reason people are using indices to begin with: because the borrow checker cannot track what they do.
30.
▲
by
afdbcreid
17d ago
Yes you need to vet touching safe code. Which is why you keep things private, encapsulate them, and extract them into reusable crates. The most important reason unsafe code is harder to write than C or C++ is that you must keep soundness, s
More ›