898 karma · joined February 6, 2011
Take, for example, a simple program that creates a line plot (https://docs.juliaplots.org/latest/tutorial/):
using Plots
x = 1:10
y = rand(10)
plot(x, y)
After installing the package, the first run has to precompile(?), and subsequent runs use the package cache. But ~25 s to create a simple plot is incredibly slow and frustrating to work with. $ julia --version
julia version 1.1.1
$ time julia plot.jl
julia plot.jl 73.71s user 4.45s system 110% cpu 1:11.04 total
$ time julia plot.jl
julia plot.jl 24.41s user 0.39s system 100% cpu 24.633 total
$ time julia plot.jl
julia plot.jl 23.38s user 0.36s system 100% cpu 23.519 total> # typed: true
Isn't this called a directive/pragma? A sigil is a symbol on a name.
Either way, I'm excited to see this finally out after seeing the past presentations on it.
From what I understand, Ruby is highly accessible and has a standard library that covers what's used in the book.
Does anyone know of these super long range scanners (e.g, 150 m)?
Looking through Honeywell's products, the Granit 1280i [1] claims 16.5 m, which is impressive but not the 150 m mentioned above. I'm curious how aiming is even possible with what I would assume to be an incredibly narrow field of view.
[1]: https://www.honeywellaidc.com/products/barcode-scanners/indu...
I'd really like to see zero-knowledge transactions as default in the future, just to avoid the sendee seeing your wallet's balance.
> This update:
>
> * Addresses an issue that could cause Messages conversations to temporarily be listed out of order
[1]: https://playoverwatch.com/en-us/heroes/dva/
[2]: http://batmanjs.org/
* "1.1.4 Decentralization"
Ripple controls what nodes are used on their network (validators). Can you run a validator? Sure, but note that Ripple, and thus the network, aren't going to use it anyway [validator]:
> At present, Ripple (the company) cannot recommend any validators aside from the 5 core validators run by Ripple
As I mentioned in another comment tree, this is a distributed network, not a decentralized one.
[validator]: https://ripple.com/build/rippled-setup/
[registry]: https://ripple.com/dev-blog/validator-registry/
* "6.1.2 Token Utility"
XRP current has no useful use cases. Institutions experimenting with Ripple are not using the public network but their own private RippleNet, which does not use XRP tokens [ripplenet].
[ripplenet]: https://ripple.com/files/ripplenet_brochure.pdf
* "6.2.3 Team Ownership: The team stake retained by the team is a minority scale."
Currently, 38 of the 100 billion total XRP is in circulation [marketcap]. The developers were "gifted" 80% of all XRP upon its creation [distribution]. Ripple and its owners still hold the majority of all XRP.
[marketcap]: https://coinmarketcap.com/currencies/ripple/
[distribution]: https://web.archive.org/web/20150806120942/https://www.rippl...
The typings used in the library are not listed as dependencies, so I had to manually install them. This may get fixed soon (https://github.com/apollographql/apollo-link/pull/171), though I had to install three @types packages: graphql, lodash.flowright, and zen-observable.
The ApolloProvider parameter for client is also broken: https://github.com/apollographql/apollo-client/issues/2212
Also, `data.loading` still gets stuck to true. See https://github.com/apollographql/apollo-client/issues/1186, though this issue has repeatedly been opened and closed.
[1]: https://www.amazon.com/dp/B06ZZNKX78/ [2]: https://www.animenewsnetwork.com/news/.105749