mbauman

16 ms·

151.
by mbauman 5y ago
~700 miles is the magic point at which charging times can be significantly extended to simply be overnight.
152.
by mbauman 5y ago
I'd love to figure out where the disconnect is — and how we can make the manual more clear. It's a pretty simple rule: the number of semicolons specifies the dimension in which you "move". I've seen two disconnect
153.
by mbauman 5y ago
See the one footnote: you can re-associate a list of 2046 numbers such that they sum to _any_ floating point number between 0 and 2^970. https://discourse.julialang.org/t/array-ordering-and-naive-s...
154.
by mbauman 5y ago
That's precisely the part that makes it so impossible to use! Sometimes it means fewer bits of accuracy than IEEE would otherwise give you; sometimes it means more. Sometimes it results in your code being interpreted in a more algebra
155.
by mbauman 5y ago
I'd love to see an update here that: * Included a graph of the resulting ordering of the two dimensional plane and some examples * Included consideration of 5- or 10-star scales.
156.
by mbauman 5y ago
The donation matches are typically not grants, but rather _other donors_ playing those games (surely in collaboration with NPR's development dept). They definitely exist.
157.
by mbauman 5y ago
The problem is twofold: the test is notoriously flakey, and the cancer is frequently not an issue. You're also absolutely right that many more men die with prostate cancer than from it — but that's most commonly _without_ treatmen
158.
by mbauman 5y ago
That exists more directly with Weave.jl — this is built for bigger things. As the README says: > If you want a small report instead of a book with numbered sections, then Weave.jl might be more suitable for your problem. http:/&#x2
159.
by mbauman 5y ago
All the dismissals here are fascinating to me — and sure seem to be exactly the overarching story of TFA. Yes, this certainly isn't the only problem here, but it's certainly the easiest to fix. And yes, the narrative of the sto
160.
by mbauman 5y ago
But they did help him. I don't see this as a huge indictment on the rep here — they _do_ deal with people who are very ignorant of tech everyday. Maybe it took a while to convince them, but I think that's just as likely a failin
161.
by mbauman 5y ago
I am really curious what his end goal here was. Apple's boxes are all very small — in what situation would a few centimeters in box size outweigh all other considerations?
162.
Mythbusting Julia's Speed(giordano.github.io)
7 points by mbauman 5y ago|0 comments
163.
by mbauman 5y ago
The rest of the internet sucked yesterday, and my understanding was it was due to a thundering herd of recursive DNS requests. Slowing down clients seems like a good thing.
164.
by mbauman 5y ago
How would've it been worse? Waiting for a timeout is a good thing as it prevents a thundering herd of refresh-smashing (both automated and manual). I don't know BGP well, but it seems easier for peers to just drop FB's pac
165.
by mbauman 5y ago
As a moderator on the primary discussion board — discourse — please do flag problematic posts and/or DM me. We don't see everything and rely on flags.
166.
by mbauman 5y ago
You can already choose different `diff` programs to use for particular filetypes. E.g., nbdime for Jupiter notebooks: https://nbdime.readthedocs.io/en/latest/vcs.html#git-integra...
167.
by mbauman 5y ago
Julia Computing: https://juliacomputing.com and https://juliahub.com Julia Computing is a company founded by all of the co-creators of the Julia Language, and we've just raised our Series A to build out our core
168.
by mbauman 5y ago
The point is simply there’s a method to the madness. It’s not randomly inaccurate. Many operations are perfectly accurate. Those that aren’t are just the closest representable value to the accurate value. Doing something like what you initi
169.
by mbauman 5y ago
Oh cool, you want to use different definitions. No matter. Point remains: the floating point representation of 1/4 is not approximate. Similarly, the closest floating point value to 1/10 also precisely defines some value: it&
170.
by mbauman 5y ago
> the other just gives you a (more) wrong number. This is a common misconception: IEEE754 floating point arithmetic is not wrong or fuzzy or inherently inexact. It is very exact; it just has limited precision.
171.
by mbauman 5y ago
That's just trading one class of bugs for another. Adding a million 10^-50s to 1.0 is far still closer to 1.0 than the next floating point number. Your algorithm would give an answer that's a million values away.
172.
by mbauman 5y ago
Whoa, retail is doing LPR now? Not surprising, but goodness. I forgot a high-value item at a checkout lane the other day, and when I returned with my receipt to ask for it, they pulled up the video of the checkout lane to confirm I hadn&#x2
173.
by mbauman 5y ago
That's not what I'm saying. Apple is required by law to report images if they have "actual knowledge" of CSAM. Courts aren't too kind about superficial technicalities like "that output label wasn't traine
174.
by mbauman 5y ago
Even without a requirement to proactively scan, Apple is surely expanding its ML stack on photos to categorize and describe photos and persons in them. Is that not the simpler explanation for this?
175.
by mbauman 5y ago
You can expose it as a CLI tool if you wish: https://github.com/fredrikekre/jlpkg
176.
by mbauman 5y ago
Folks generally don't do development in notebooks, thankfully. Instead, they generally use a Revise- or REPL- based workflow, often with VS Code.
177.
by mbauman 5y ago
I've never seen anyone say that latency is a good thing or that it's not a priority. It's a hard problem and it's being worked on and it's getting significantly better — particularly over the past three releases. I
178.
by mbauman 5y ago
When folks talk about the performance of Julia's JIT, they're generally talking about the compile-time overhead (and not the runtime speed). Type inference is one part of the compile-time overhead that enables improved runtime spe
179.
by mbauman 5y ago
There's no hidden dirty magic, but you're right: Complex numbers require `Real` components and Rationals require `Integer` numerators and denominators. Both `Real` and `Integer` are simply abstract types in the numeric type tree,
180.
by mbauman 5y ago
Yes, that's what I figured you meant, and that's precisely what that paragraph and my comment above detail. You can enter a credit card into JuliaHub and start running large scale distributed compute on CPUs and GPUs right now. Or

More ›