Is there any future in languages like #haskell where AI makes code a factor of small frequently and easily replaced glue and scraps, where whatever is most trained on and most hackable, most easily replaced/iterable is king?
Are big pieces of software that benefit from the architectural assurances Haskell brings a dead paradigm?
AI is here to stay and I feel if something was not already in or out of orbit, it may never reach escape velocity
effectfully describes #Haskell as a beautiful and amazing language. In episode 46 of #TheHaskellInterlude, Wouter Swierstra and Joachim Breitner asked effectfully about how he found a new passion for programming. Listen to the episode here: https://haskell.foundation/podcast/46/
Compatible types across programming languages are also important.
What if you could easily make universal types across the languages in your stack, at the same time?
That's what I'm hoping to achieve with DataTypeTool. Still a very early product, but we're getting there. Currently producing valid (albeit not-yet-serializable) #elmlang#haskell and #gleam
You can always try out #haskell snippets on https://play.haskell.org! Many libraries, like aeson, containers, vector, effectful, text and text-builder-linear, are readily available!
@gregorni
Editor: #neovim or Pe
Multiplexer: still figuring out: only recently realised they're useful.
Package manager: #nixPackageManager / #haikuOS pkgman
Shell: bash (sometimes zsh, never got around to finding out the difference)
Language: #haskell, #rust, #rubylang, #cpp, whatever else tickles my fancy.
Containers: none (most recently docker)
Command runner: don't you mean shell?
Terminal emulator: the default ones from #CinnamonDesktop and #haikuOS
Typed holes (in #purescript or GHC #haskell or wherever) are just too useful. I don't know how to operate in higher-order / heavily polymorphic code without them anymore. :blobfoxgooglyconfused:
Writing a new language is hard... so much to implement before I'm even willing to use it myself! 😜
QQ on the state of #haskell in #Debian -- which parser combinator library should I use for a toy/hobby REPL project. Is trifecta still the go-to, or is there something newer, or is all of that overkill, can/should I just jamb it into something like reads from prelude?
But I find such articles ridiculously hard to understand, especially system F (although I have been coding in #haskell for years).
Ironically, dependently-typed seem much simpler. In non-dependently-typed systems it's very hard to pinpoint the connections between types and terms. In dependently-typed systems, terms and types are the same thing.
I kept my twtr account for a while because brands I occasionally reach out to were still exclusively there. It’s now no longer the case so I put the account down for real :)
1/3 In today's functional programming class we covered file IO in Haskell.
I repeatedly emphasised that for small files, it is much easier to read and write whole files using a single function rather than opening the file, using the file handle, and then closing the file.