anp

11 ms·

91.
by anp 6y ago
> one large sponsor Where is this coming from? I’m also worried about AWS over-representation in the Rust community but they’re far from the only significant corporate sponsors at this point.
92.
by anp 6y ago
Do any other ISAs have compressed encodings in wide use? It seems a bit like a chicken and egg problem - why build all the silicon to handle decoding it if your base ISA is dense enough?
93.
by anp 6y ago
My read of the comments here is that Rust is competitive with Python for some scripting tasks from the perspective of someone who knows both. I’m not sure where you get the “arguing that Rust is a better scripting language than Python” or t
94.
by anp 6y ago
IIRC the issue I had with salsa was that there’s no way to compose multiple databases from separate libraries and have them use the same incremental storage without deep integration.
95.
by anp 6y ago
This reminds me of a hypothetical project I would take up if I still had a dog and a small yard: building a poop cleanup map from CV processing of camera footage. Stepping stone toward a Poopba, obviously.
96.
by anp 6y ago
I think seL4 didn't yet have multicore support when zircon was forked from LK, could be wrong.
97.
by anp 6y ago
I used to work in an environment not dissimilar from what's described above. The uni has some hardware details here: https://in.nau.edu/hpc/details/ . Many of my answers would be similar, although the presence
98.
by anp 6y ago
It’s wasteful if you assume it could be automated, but helping customers find things is just “service” most of the time.
99.
by anp 6y ago
Isn’t that just the (née sulong) llvm frontend? IIUC GraalVM is deeply dependent on OpenJDK internals.
100.
by anp 6y ago
IIRC V8 can now provide deterministic JIT+heap images in addition to preparsed bytecode images. EDIT: worth noting that other JS VMs like JSC have these APIs for bytecode too, but i can’t remember off hand whether they can do generated code
101.
by anp 7y ago
I bought a Vive Pro Eye specifically to try and develop eye tracking navigation for a system like this. I haven’t done any actual digging yet bc it turns out the NDAs for their SDK are...unfortunate. Definitely an opportunity for a free&#x2
102.
by anp 7y ago
What a great question! Because it's implemented as a const/codegen feature I'm not sure what it would mean to support it for proc macros. Probably gnarly design/RFC work?
103.
by anp 7y ago
Rust binary size can be pretty painful, depending on what you're doing. Also, it doesn't look like that document is receiving regular updates, so grain of salt and all.
104.
by anp 7y ago
If anything I expect MLIR to make things more confusing as Rust’s MIR is probably going to be around for the long haul.
105.
by anp 7y ago
I enjoyed this quite a bit. I had read Nikolai's comment back when it was linked in a few discussions and felt familiar with the techniques, but it's really nice to have a detailed catalog with explanations and links :D. nit re:
106.
by anp 7y ago
Hey, Richard K Morgan said he was ecstatic with the adaptation. I prefer the novels’ Envoys too but am willing to follow the authors lead overall.
107.
by anp 7y ago
In moxie, everything is procedural, as it were. The declarative syntax is a way to invoke "imperative but idempotent" functions, and the core runtime provides tools for wrangling mutability and repetition in those functions.
108.
by anp 7y ago
Familiarity. In short order it’ll be easy enough to write moxie functions without the xml macro, at which point it becomes a matter of preference.
109.
by anp 7y ago
<3
110.
by anp 7y ago
Good to know! I was incorrect to take GPs claim at face value, perhaps. (BTW I’m not sure if you remember our conversation at React EU in 2017, really enjoyed chatting!)
111.
by anp 7y ago
If moxie brings anything new to the table, it’s only because I copied liberally and shamelessly from React and other successful and interesting projects, learning and improving on them in the process. If it doesn’t bring anything new, the
112.
by anp 7y ago
> The code looks almost like it is declarative. But really it's just Dart code I need to figure out how to express this better in the future, but if you swap "Dart" for "Rust," this sentence applies to moxie as w
113.
by anp 7y ago
moxie-dom is compiled to WebAssembly, and mutates the DOM using APIs from javascript. The Rust isn’t translated into JS, but it does run alongside it. moxie-native doesn’t have anything to do with JS or HTML, aside from reusing some concept
114.
by anp 7y ago
Good idea to make a DOM example for the calculator! I'm very behind on examples. Someone recently got very close to having the moxie-native calculator working in a browser's wasm/webgl, which will be mindblowing if they get i
115.
by anp 7y ago
I'm not happy with the state of the syntax, but I'm pretty sure it'll take me farther than this attitude.
116.
by anp 7y ago
It's unkind to call someone else's work "awful," even if its meant in a very minor way (even if I agree with it!). It's a low value comment when it doesn't provide any concrete feedback on top of that. Our indu
117.
by anp 7y ago
Don't see why not, although to do so you'd need to use moxie-native which is still very new.
118.
by anp 7y ago
> And no possible declarative model can capture it. Functions can. If functions are your declarative model, what would you say?
119.
by anp 7y ago
From far down in the post: > I have described moxie a few times as "what if a React in Rust but built out of context and hooks?"
120.
by anp 7y ago
Agreed! I have some thoughts about how this can be handled but it’ll be a little bit before we can try them out.

More ›