It’s a thing! Sadly it won’t rewrite Haskell codebases for you, though.
Rose here. Also @umbraroze for non-kbin stuff.
It’s a thing! Sadly it won’t rewrite Haskell codebases for you, though.
Reminds me of another old joke: “My doctor said I have the lungs of a little old lady. The upside is that I know that little old ladies never die.”
The difference between wolves and dogs: wolves eat the grandma, dogs eat everything else in the house except the grandma
Switch to Chrome? Never! I take my chances with the gargantuan planet humping fire elemental vulpine.
Technically, SQL is case-insensitive.
Practically, you want to capitalise the commands anyway.
It gives your code some gravitas. Always remember that when you’re writing SQL statements you’re speaking Ancient Words of Power.
Does that JavaScript framework that got invented 2 weeks ago by some snot-nosed kid need Words of Power? No. Does the database that has been chugging on for decades upon decades need Words of Power? Yes. Words of Power and all the due respect.
God clearly failed, then. George W. Bush kept bombing places that he couldn’t pronounce.
Almost every situation can be made hell by introducing an enthusiastic sales person with lots of options to market to you
In Ruby, the convention is usually that things are duck-typed (the actual types of your inputs don’t matter as long as they implement whatever you’re expecting of them, if not, we throw an exception). Type hinting could be possible, but it basically runs contrary to the idea.
Now, Ruby on Rails developers are expecting some kind of magic conversion happening at the interfaces. For example, ActiveRecord maps the database datatypes to Ruby classes and will perform automated conversions on, say, date/time values. But from the developer perspective it doesn’t generally matter how this conversion actually happens, as long as there’s something between the layers to do the thing.
/serious Well, yes, most APIs are meant for system-to-system interaction, that’s kind of a given. But since this particular API is clearly meant for human-to-system interaction, returning a human-readable response is adequate. Yes, a better design would probably allow the client to specify additional parameters about the desired response.
/back-to-jokes Yeah, well this kind of sums up most of my job applications. I send an application and the recruiting people are all like “OK”.
Yeah, the thing is, “a monad is a monoid in the category of endofunctors” is kind of a meme among non-Haskell developers. Personally, I think Haskell is a very interesting language. The mathematical jargon, however, is impenetrable, and this particular expression is kind of the poster child. I’mma go look at Erlang if I want my functional language fix without making my head hurt, thank ye very much.