Conversation

Notices

1. Embed this notice
   someodd (someodd@fosstodon.org)'s status on Sunday, 15-Dec-2024 13:22:41 JST someodd

   I've gotten good enough at Haskell to realize there's a problem in paradigms.

   There's really two types of useful programming languages and approaches.

   1. Correctness. That's Haskell. The downside of correctness is that in Haskell this often means you have to exactly what to expect at all times and know about every possible edge case. This isn't in the sense of "logical edgecase broke my code," no this is about code flexibility.

   (thread continued...)

   • Embed this notice
     someodd (someodd@fosstodon.org)'s status on Sunday, 15-Dec-2024 13:22:40 JST someodd

     in reply to

     2. Hackability. Hackable paradigms are the most flexible, they allow you to do anything, to whatever, however you want. It makes it easy to tweak and tinker with any component, because there are no real expectations on exactness or validity laid out before you. For this same reason it's harder to maintain, easier to break, more prone to bugs, but it's much easier to extend and quickly work with.

     (continued...)

     alcinnz repeated this.
   • Embed this notice
     someodd (someodd@fosstodon.org)'s status on Sunday, 15-Dec-2024 13:22:40 JST someodd

     in reply to

     An example of this philosophy divide is just think about non-exported functions in Haskell. The author made them private because he knows how the code works and why you shouldn't access them, that's very nice and correct--unless... someone out there really does have a weird case! Humans are bad at setting these boundaries!

     Or how about the ability to support some YAML keys that are user-defined? Now your magical json-to-datatype generic is moot.

     (end)