samnardoni · HackerTrans

samnardoni

no profile record

Submissions

A Work-stealing Runtime for Rust - Aaron Todd

air.mozilla.org

1 pointsby samnardoni13 lat temu0 comments

A/B testing on StatHat

stathat.com

1 pointsby samnardoni14 lat temu0 comments

comments

6 lat temudiscuss

This is known as PNS Syndrome.

7 lat temudiscuss

sync.Map?

8 lat temudiscuss

Well, yes, that's true. But my point was that they aren't going to change the legacy nav data structure.

8 lat temudiscuss

Erm, they aren’t going to change the nav data.

8 lat temudiscuss

Maybe there’s a reason this is a “not-mentioned” point.

8 lat temudiscuss

All GPS satellites are in a geosynchronous orbit.

8 lat temudiscuss

Geosynchronous is the word you’re looking for.

8 lat temudiscuss

Error in boost/bind.hpp:768

8 lat temudiscuss

Having a pointer to a stack variable is fine, as long as the stack variable lives longer than the closure.

8 lat temudiscuss

Why should Rust “just compile this” when it’s clearly bad code?

8 lat temudiscuss

That animation clearly shows they are geosynchronous?

8 lat temudiscuss

clang-fmt?

8 lat temudiscuss

So it basically just monomorphises?

9 lat temudiscuss

You can do all that with JS too. Wasm adds nothing extra. It's perfectly sensible to imagine wasm applications targeting the DOM (which it can do via JS, and will do natively in later releases) just like JS applications do now.

9 lat temudiscuss

The point is that wasm doesn't change this; wasm won't make it 'worse'.

10 lat temudiscuss

You can write it both ways. t.method() is the same as T::method(t).

12 lat temudiscuss

Rust uses LLVM, which does all the optimisation. Go generates the machine code itself and its optimisation is pretty weak compared to LLVM.

12 lat temudiscuss

Why not profile and see where the time is actually going? Slow JSON parsing? Slow I/O?

12 lat temudiscuss

Same with the UK store.

12 lat temudiscuss

I think he/she meant the GC pauses were never longer than 100ms.