Not to be that guy ;-) , but the diameter of the golf ball dimples is ~4 mm or about 4,000 μm, whilst the diameter of the spheres is 38-53 μm, or about 0.04 mm.
Diameter-to-diameter seems like about 100x or two orders of magnitude?
Similarly, 200 μm is the golf ball dimple depth (oops, just noticed I dropped that key word), and they didn't give us a measurement of the depth of the dents caused by the spheres or sandblasting, but it would likely be significantly less than half the radius of the spheres?
Sorry about misleading with dropping the "depth" word.
Easy code is much easier in f#, a lot of the time. Hard code is usually easier in f# due to the type system helping a lot. F# is also a lot more concise.
And yes, you can combine them, but afair, only in terms project boundaries. (You can include a c# project in an f# one and vice versa). There are a few cases where it's quite useful. For example, rewriting a part of a big project in f# to leverage the imperative shell - functional core architecture. Like rewriting some part that does data processing in f#, so that you can test it easier/be more confident in correctness, while not doing a complete rewrite at once.
I don't think it's a matter of the type of problem and I always found it weird how F# is being framed as being only useful for "math-heavy" problems.
What matters is what libraries you are gonna use for your solution. If most of them are C#-only and don't have an F# equivalent then you'll lose the ergonomics and conveniences that make F# so easy to work with.
All types of problems. F# can do almost anything C# can do and with less ceremony. The quote I like is that once you get comfortable with F#, switching back to C# is like "having to fill out government forms in triplicate".
It's very possible, even encouraged when you have workloads that call for it. F# is a great functional language, so it's good for parsers, compilers, etc. The support for units of measure is also really cool, making it great for scientific computing.
He's redirecting requests coming from hn to a photo of a hairy ball in an egg holder with some mildly insulting text, and setting a cookie so the redirect happens outside of hn links as well. The text even comes with a tone of the moral high ground, so you know he's not being an asshole, just "being honest".
It's fair to say he's not interested in having his views known to readers here.
No. They don't lose points for using a film production technique that was in popular use at the time (and is still in use.) The reason people say this is a well timed shot has nothing to do with the voice-over at the end of the shot.
They say it's a great shot because Burke hits his mark at the beginning of the shot, then he progresses through the shot, hits his final mark and points within half a second of ignition. All while delivering dialog. (Props to the camera operator who tracked Burke and pulled focus at the appropriate time.)
And then I think there's the thematic element of the subject matter. What you don't get by watching the final shot in that episode was the emotional impact of the Voyager launches. The space program was, at the time, continuing on from the high of the moon landings. The Pioneer probes had returned black and white images from Jupiter and Saturn but the Voyagers were going to return more colour images. They were a RETURN to space, demonstrating that the pioneer mission wasn't a fluke and that, as a people, we were capable of doing great things.
And now, as a people, we bitch in online forums about voice-overs.
One does not, as you suggest, need to deduct any points for editing the sound of an impressive bit of writing, timing, presenting and camera work.
perpetual has pejorative connotations and only started appearing in marketing speak when software rental became the new business model.
reply