Skip to content

Comment on Chime 2.0 – a Go Editor for macOSparent

Comments

For me, the lack of those features is itself a feature.

I don't have any interest in using the subpar terminals/"execute this thing" buttons included in many editors. I'd rather use a terminal that I actually like -- the one I use for everything else.

I also don't want any "magic" to happen under the hood to run a thing (looking at you, Java IDEs). I want anyone to be able to download the thing I'm working on and run it without being tied to a particular editor/IDE, and the best way to do that is to put your build/run stuff into something portable (shell script, Makefile, task file, whatever) instead of relying on a button in a GUI somewhere.

With maybe a few exceptions that I'm unaware of, all integrated terminals are optional features that can be disabled. I agree that editor-specific run configurations are over the top and bad form, however an integrated terminal is a very useful feature that I use all the time, especially when working with Go.

Edit: And that said, if I'm paying money for a product it better have features that I'm going to need, and if I don't need them it better have a way to disable them.

For me, the lack of those features is itself a feature.

For me as well. However language specific IDEs these days usually don't have much if anything on more popular editors.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.