[Haskell-cafe] What features should an (fictitious) IDE for Haskell have?

Joachim Durchholz jo at durchholz.org
Tue Dec 1 08:34:33 UTC 2020


All IDEs mentioned have good, sometimes excellent support for 
declarative languages like HTML, CSS, SQL, XML, you name it.

Sure, some things won't transfer easily. E.g. Haskell needs different 
debugging tools, and different performance investigation tools.

But at the coding & code inspection level, Haskell isn't any different. 
You code, you look up modules, you transform and refactor code. Modern 
IDEs tend to struggle with dynamic languages where the lack of type 
information makes them misidentify a lot of things, but Haskell isn't 
one of these (type inference is easy to do on the fly with a modern CPU).

Am 01.12.20 um 07:53 schrieb YueCompl via Haskell-Cafe:
> Typically, you programming with procedural mindset in an imperative 
> language, but programming with mathematical mindset in a functional 
> language. The difference in methodology would require difference in 
> choices of methods / tactics.
> 
>> On 2020-12-01, at 09:13, Gregory Guthrie <guthrie at miu.edu 
>> <mailto:guthrie at miu.edu>> wrote:
>>
>> Sem like there are **many** standard examples around, IntelliJ, 
>> Eclipse, Netbeans, etc.
>> Are there specific reasons that a Haskell IDE would be different in 
>> features??
>> Is there something lacking in use of (say) the standard IntelliJ IDE 
>> for Haskell?
>> Dr. Gregory Guthrie
>> Maharishi International University
>> ----------------------------------------------------------------
>> *From:*Haskell-Cafe <haskell-cafe-bounces at haskell.org 
>> <mailto:haskell-cafe-bounces at haskell.org>>*On Behalf Of*MarLinn
>> *Sent:*Monday, November 30, 2020 7:01 PM
>> *To:*haskell-cafe at haskell.org <mailto:haskell-cafe at haskell.org>
>> *Subject:*Re: [Haskell-cafe] What features should an (fictitious) IDE 
>> for Haskell have?
>>
>> Most importantly: A good IDE is not a text editor, but an AST editor. 
>> If the AST happens to be presented as text, that's a choice of 
>> visualisation, nothing more. Better to start with a graph-like 
>> visualisation to free the mind, then think through the possible 
>> interactions. Maybe add the typical text-like visualisation later. But 
>> don't start there or you'll just re-invent notepad for the nth time.
>>
>> Maybe don't even/store/the code as ascii text.
>>
>> _______________________________________________
>> Haskell-Cafe mailing list
>> To (un)subscribe, modify options or view archives go to:
>> http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
>> Only members subscribed via the mailman list are allowed to post.
> 
> 
> _______________________________________________
> Haskell-Cafe mailing list
> To (un)subscribe, modify options or view archives go to:
> http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
> Only members subscribed via the mailman list are allowed to post.
> 



More information about the Haskell-Cafe mailing list