Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The best part about this, and what's different than 2to3, is that they implement API changes in gofix first, and gofix is the tool that's used to change the main source tree.

I like that. That is really nice, and it sets a process in place which continues to keep cost of language API changes low, something that the language designers will love.

At this point in Internet history, a language that's newly created and evolving has a sort of tipping point problem -- if nobody uses it, it won't improve. On the other hand, if a few too many people start using it, then suddenly you are screwing people if you make changes.

gofix seems like it can help with that, and that's cool!



Cool! Doesn't one of the Java IDEs (either IDEA or Eclipse?) have "public refactorings" (or something like that)? The idea goes something like this:

1) Enable recording of public refactorings

2) Apply a refactor which affects the public API

3) Refactorings are described in some big honking XML file

4) When you release a new version of your library, post it alongside that XML file

5) User downloads and executes the file against their codebase




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: