DougBTX

25 ms·

301.
by DougBTX 6y ago
Yes, Julia looks very impressive, a language I'd like to try at some point.
302.
by DougBTX 6y ago
Yes, that's std::env::args[0], however a higher level wrapper (I prefer structopt[1]) makes it trivial to produce nice usage output etc. [0] https://doc.rust-lang.org/std/env/fn.args.html [1] https:/&#x
303.
by DougBTX 6y ago
Lets say you have three numbers, a, b, c, and you want to add them together to get the total. Then later, "c" changes, and you'd like to re-compute the total. One option would be to re-run the full sum, a + b + c, which would
304.
by DougBTX 6y ago
> it's unclear how one might change the input parameters (or if that's even possible). Yeah, the readme is pretty dense on terminology that is unfamiliar (at least to me). It answers that question like this: > In the example
305.
by DougBTX 6y ago
It does seem tricky. On on hand, they want to stop AWS using "Elasticsearch" in a product name because it isn't in partnership with Elastic co., but on the other hand AWS's product really does contain Elasticsearch, whic
306.
by DougBTX 6y ago
They make the point in their presentation to say that their method replaces the non-differentiable step function with a differentiable sigmoid function to enable the rasterizer to be differentiable.
307.
by DougBTX 6y ago
Seems like a well worn path: either pay more for the full-featured option, pay less for the minimal-feature option, or do the research to find the cheapest option which does everything you need.
308.
by DougBTX 6y ago
> T: ‘a is T outlives ‘a; but types are not generated at runtime. Yes, that’s true, but you can make it a bit more specific by saying “all the references in T outlive ‘a”. Then it should make more sense, as references are generated at ru
309.
by DougBTX 6y ago
> These are totally different things with the same name. Another way to think about it is that “T: ‘static” restricts all references in T to be static, in the same way that “‘a: ‘static” restricts ‘a to ‘static. The case when T doesn’t c
310.
by DougBTX 6y ago
The SQLite website is a little more positive than that, but as a "quite a bit in the future" option, rather than something that can happen today: > All that said, it is possible that SQLite might one day be recoded in Rust. Rec
311.
by DougBTX 6y ago
Sorry, I meant that the behaviour is guaranteed, not that the destructor is guaranteed to be called. So in the Rc cycle example the guarantee is that the destructor won’t be called.
312.
by DougBTX 6y ago
There is no guarantee when a Java finalizer will run, whereas a C++ destructor is guaranteed to run based on the code that you write. That's a big difference which has practical implications, using something with non-guaranteed behavio
313.
by DougBTX 6y ago
Interesting, that’s the opposite of my experience. Containers allow bundling up lots of dynamic dependencies together so that they can be installed as a single unit. Static binaries can just be deployed as a single file, no need for contain
314.
by DougBTX 6y ago
There's a fair amount of truth to this. Many applications are glorified SQL generators, that effectively JIT compile the application logic to SQL. So if you want to test the application logic, then you need to run it on the runtime tha
315.
by DougBTX 6y ago
> It's no different to any other legacy refactoring project There are two approaches to a project like that, as you say, take something which works and iteratively make it better, or derive a specification from the project which wor
316.
by DougBTX 6y ago
Org mode is something that I've always thought I should look at, but never quite have. One thing I like to do with my notes is to keep a short "todo" list at the top, listed in the order that I'm planning to work on them
317.
by DougBTX 6y ago
> Also, why the need o a dual(e12, e02, e01) to represent a point when in vector it's just a (e0, e1, e2). This is just counterinuitive. It seems like it isn't needed, but it hasn't all been wrapped up into an easy to unde
318.
by DougBTX 6y ago
The dynamics change a little now that the language server protocol is becoming more popular, as it drops the cost of developing new tooling, though there's lots more work to do.
319.
by DougBTX 6y ago
From the end of the article: > Despite these benefits, you should be very cautious about using CQRS. Many information systems fit well with the notion of an information base that is updated in the same way that it's read, adding CQR
320.
by DougBTX 6y ago
> Look at Facebook, Google, Amazon. They've extracted all the blood they can and given us back scraps. Facebook and Google at least have put out a lot of open source code, have you heard of React and Angular? PyTorch and TensorFlow?
321.
by DougBTX 6y ago
There are hundreds of libraries and packages for dealing with images which can all be mixed and matched together. So maybe Instagram and Photoshop don’t participate in that open ecosystem, but that’s their choice. If you want to use the con
322.
by DougBTX 6y ago
There are experiments for a Gc<T> here: https://github.com/Manishearth/rust-gc
323.
by DougBTX 6y ago
Yes, that makes a lot of sense. The ownership would be linear: struct Graph { nodes: Vec<Node>, edges: Vec<Edge>, } but the associations between nodes would have an arbitrary structure. The article s
324.
by DougBTX 6y ago
> or modelling the problem in some completely different way that lets you skip the problems of ownership semantics for the given domain Maybe that's an interesting way to think about the article too. The obvious way to think about a
325.
by DougBTX 6y ago
It is interesting that we trust our tools so little. A git hash is a pretty robust way to know whether the code in the repo is what it is supposed to be, so a "git fetch" rather than a fresh "git clone" should be safe, b
326.
by DougBTX 6y ago
> If we're being charitable we can say that the core thrust of Taleb's point remains unchallenged, while the details he quantified are either wrong or lacking in sufficient rigor to be refuted. It seems we could put this a litt
327.
by DougBTX 6y ago
That very much depends on how good the JIT is, certainly many AOT compilers would understand this pattern and inline the callback, resulting in very similar optimised code.
328.
by DougBTX 6y ago
I see you’ve replied to quite a few of the comments in this thread, but I think the basis of the disagreement isn’t in the specifics, but because you’re using a stronger definition of “unpredictability” than they are.
329.
by DougBTX 6y ago
Yeah, it’d be interesting to see the Rust code contrasted with correct C versions. How does the C code deal with a monitor being unplugged? I wonder if it could be shuffled around to amount to an early return with an Unplugged error.
330.
by DougBTX 6y ago
Yeah, interesting reading through the list of "Removed" features. On one hand, it is nice to tidy things up, on the other hand, I'm wondering, was it really worth breaking backwards compatibility for these things?

More ›