Anybody remember Kohoutek? Exactly. If I were a comet, my strategy would be to underpromise and overdeliver. That's the best way to rally a comet's soothsayer base.
Yes, I do. I do also remember Halley's comet. Or, rather, I do remember standing on a winter beach around the time of the predicted maximum with a clear view of the southern sky without light pollution and seeing exactly nothing but stars. (Being at 54 degrees north probably didn't help, either).
If you talk about this approach, the first commet that comes to mind is Hamner-Brown. (Yeah, it's fictional. Still, it's the archetype of that strategy :)
Ha! I remember that book. I memorized several end-of-the-world survival strategies from it. Like "you can drive a jeep on railroad tracks" and "when packing for the apocalypse, don't forget liquor."
I remember it well. I drove up to Bluff Mountain tower (TN) with a couple of friends on a clear summer night. From up there it was a spectacular sight. It was much more beautiful than Hale-Bopp which I saw from Bear Mountain (NY). The only problem - and it was a big one - was that you couldn't really see Kohoutek unless you were up high where Hale-Bopp could be seen from light polluted suburbs.
It's Newtonian. People have no appreciation for how far you have come (position) or how fast you are going (speed), but they are extremely sensitive to acceleration. VCs especially so.
Amazing Fact (TM): I've been throwing right-handed for my whole life. Make me throw lefty and I throw like a girl. Something to do with an urgent need to get base runners out.
Another Amazing Fact (TM): If you play catch with an Aussie, notice their motion will be more overhanded than yours, if you are a Yank.
It's nurture not nature here. Go get a softball and try to fast pitch. I bet there's a girl nearby that could beat you.
I have been using Haskell seriously for about two years now and humorously for a bit longer. For some reason I bought the old sales pitch some time ago. Now that I have a clue about the language I would like to rewrite the sales pitch for anyone considering a move.
Here's what happens in the middle of a big Haskell project.
1) Take some existing code.
2) Refactor (Add a feature, change a record element, etc.)
3) Run ghc, then fix all the errors it reports. Repeat this
step as needed.
4) Done.
What would be different in python? For one, no compile errors means very little. How many test cases would you need? How would you find all the places the code must change?
Lesson: A tough, smart compiler can be the programmer's best friend.
Meta-lesson: There is little need to discuss laziness, purity or static typing to "sell" Haskell. They are enablers of ghc. What you need is a big, complicated code base and an urgent need to make changes to it. You won't have that until you get your feet wet.
Is Haskell perfect? No, but I'll save that for an OP that is overhyping the language.
And try mixtral on chat.groq.com