samnardoni

This is known as PNS Syndrome.

sync.Map?

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

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

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

All GPS satellites are in a geosynchronous orbit.

Geosynchronous is the word you’re looking for.

Error in boost/bind.hpp:768

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

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

That animation clearly shows they are geosynchronous?

clang-fmt?

So it basically just monomorphises?

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.

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

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

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

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

Same with the UK store.

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

And people don't do this in "real life" too?

Awful video. I could barely hear what the guy was saying. And the few hundred panning shots with peeling bananas and spreading cream cheese on bread was bizarre.

It might be a decent product though!

It doesn't have to be binary. Just use it less if you don't want to. Use it more if you want to.

> Maybe that just says something about my intelligence, or maybe the functional camp hasn't yet figured out how to write large programs in a readable way.

You make it sound like we've figured out how to write imperative large programs in a readable way.

Honest question. Why do people write posts like these?

I would never buy anything from an online stored that used this.

Why? (Genuinely curious...)

2 threads can't access the same variable in Rust without unsafe{}. I think, anyway...

If they wanted every language feature, they'd use C++

Yes.