nynx

44 ms·

511.
by nynx 6y ago
In a way, but wasm is designed to be a lot better at sandboxing.
512.
by nynx 6y ago
Is this saying that WSL 2.0 supports Vulkan now? Because if it just supports opengl, that's pretty meh.
513.
by nynx 6y ago
I've found that the amount I use stackoverflow is inversely proportional to the quality of the documentation and the strength of the type-system of the language I'm using.
514.
by nynx 6y ago
There was a Banksy on my street in San Francisco that had paint thrown over it. Perhaps this method could help recover the art.
515.
by nynx 6y ago
Looking at Google earth always gives me a feeling that I suspect is similar—though lesser—to what astronauts feel when they look down at earth.
516.
by nynx 6y ago
I'm not sure "risk" is the right word for it.
517.
by nynx 6y ago
It's already kind of possible to statically prevent all panics: https://crates.io/crates/no-panics-whatsoever . It's pretty hacky, but it works on no_std.
518.
by nynx 6y ago
In that case, I would think that they'd note that they weren't able to get it to work for materials with much high Tc.
519.
by nynx 6y ago
This isn't quite RTS, but it's a breakthrough step towards it. If this pressure-quenching concept can be applied to some of the more exotic high-temperature superconductors (~300K) that usually require hundreds of GPa, it might re
520.
by nynx 6y ago
It's disappointing that MCF doesn't get more attention.
521.
by nynx 6y ago
The Birth and Death of Javascript (near the end of the bottom of the iceberg) has played a big role in my life and I expect it to be relevant far into the future.
522.
Add rustc flag to disable mutable no-aliasing optimizations?(internals.rust-lang.org)
1 points by nynx 6y ago|0 comments
523.
by nynx 6y ago
This is not true. Rust is based around the idea of encapsulating unsafety within interfaces that are safe to use.
524.
by nynx 6y ago
Rust already has a "mode" that forbids allocations: no-std without the alloc crate.
525.
Observation of superluminal signaling of terahertz pulses(arxiv.org)
1 points by nynx 6y ago|0 comments
526.
by nynx 6y ago
Yes, perhaps my comment was too dramatic.
527.
by nynx 6y ago
That's probably a major reason. But, Rust is also just a really nice language that's very pleasant to use.
528.
by nynx 6y ago
Why not use a different bytecode that is already more common, in that case?
529.
by nynx 6y ago
I think the main issue is that eBPF cannot have loops. It restricts the programs you can write. Wasm does not have that property, so you cannot prove that it will complete.
530.
by nynx 6y ago
I'd prefer it to use spirv or wasm. eBPF is intentionally an extremely limited language.
531.
by nynx 6y ago
Exokernels coming back would be so cool. I wrote a prototype kernel/os [0] a few years back that ran wasm in kernel mode. I'd love to see that idea pursued further. [0]: https://github.com/nebulet/nebulet
532.
by nynx 6y ago
I generally read 3ish scifi books a week.
533.
by nynx 6y ago
Yep! That's the intention I think.
534.
by nynx 6y ago
Not recently, but they'd work fine.
535.
by nynx 6y ago
I'm not really sure how that's an argument. It's just a fact. Rust has been stable and backwards compatible since 2015.
536.
by nynx 6y ago
Rust has been stable since 2015.
537.
by nynx 6y ago
Personally, I dislike python. However, it's indisputably safer than C.
538.
by nynx 6y ago
While that's true, the likelihood of a bug like this existing in an application written in a language like python, go, or rust (heck, even C++) is orders of magnitude less than the likelihood of it being in software written in C.
539.
by nynx 6y ago
When is this madness of using unsafe languages for applications that interact with outside systems going to end?
540.
by nynx 6y ago
Okay, yeah that wouldn't go over well. Despite that, i think it makes sense to replace very dangerous sections of the kernel with a safer implementation. Parsers are very difficult to make safe in C.

More ›