Are you going to write such plugin for every possible editor? Is every newbie going to have such plugin? What about browsing code from GitHub?
A language's readability should not depend on tooling. On Mon, Aug 22, 2016 at 5:52 PM, William Bailey <b...@deepfinesse.com> wrote: > For years I coded in Java using IntelliJ. It was super easy in that IDE to > hover on any symbol, system or otherwise, and learn all about it. Or hit > ctrl-B (eg) to drill into the source. Again, worked fine for system > libraries and was really useful for seeing how the under-the-covers stuff > worked. > > When I started coding in go-lang a couple years ago, people were griping > about having to manually remove unused imports as the compiler would not > allow that. But now, most editors have plug-ins that do that automatically. > > So... I think focusing on what the core language should and should not allow > here is misguided. Just need better IDE tools. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Elm Discuss" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/elm-discuss/ydhKsvJtDZw/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > elm-discuss+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
