undefined | Better HN

0 pointsjfoutz3y ago0 comments

not the op. I'm a hobbyist.

I've figured out stack and it's pretty great.

My editing cycle is pretty terrible. usually vim in one terminal and another terminal to run ghci or stack build. That's ok, it lets me work through my toy problems.

But compared to IntelliJ or even coq and proof-general, it's a lot rougher to loop through type in new code, run it, fix or next batch of new code.

obviously developers are going to use whatever they want, but it would be really nice to see a setup with _anything_ emacs, visual studio, atom whatever. and show how to get to that setup, and how to quickly test, analyze performance, refactor.

Refactoring is Haskell's super-power. I change things and chase compiler errors, and it works well enough. Compared to even java/eclipse 15 years ago it feels primitive. it works, I can get by. I'd like to see how "grown ups" do it.

0 pointsjfoutz3y ago0 comments

not the op. I'm a hobbyist.

I've figured out stack and it's pretty great.

My editing cycle is pretty terrible. usually vim in one terminal and another terminal to run ghci or stack build. That's ok, it lets me work through my toy problems.

But compared to IntelliJ or even coq and proof-general, it's a lot rougher to loop through type in new code, run it, fix or next batch of new code.

0 comments

3 comments · 1 top-level

tikhonj3y ago· 2 in thread

Have you tried the Haskell language server? I don't think it has project-wide automatic refactoring—maybe that's something people are working on, but also seems quite difficult—but it definitely tightens the write/compile/fix loop.

jfoutzOP3y ago

I think I did, I think I spent some time puttering around trying to get a setup to match my config.

I would suggest, a clear path in a getting started guide - if you use this editor and these tools, you will have a working system end to end. maybe a short video showing interaction with that specific toolset.

I got sort of mired in what packages to use for emacs. I don't really know how other people have their stuff set up. Not having a clear path, I just kinda winged it. And was not successful.

I understand all the parts of my current workflow.

There's nothing wrong with presenting 500 options for solutions. But it would be really nice to have a "do these 5 things and you're good to go". Any set of tools would be fine. I can compare a working system to my system and puzzle out what I need to configure.

That may already exist, and I missed it. If that's the case, make that guide more prominent. I seem to recall looking around a lot.

tikhonj3y ago

Yeah, definitely. We're working on adding a guide[1] like that to haskell.org as we speak :)

If you have a chance, you could look over the PR and tell me whether this is roughly what you're thinking of.

[1]: https://github.com/haskell-infra/www.haskell.org/pull/214

1 more reply

j / k navigate · click thread line to collapse