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

Pharo and Squeak had a DVCS called Monticello that integrated with the system much better than git, but they abandoned it in favor of git, primarily so they could use github, expecting it would raise their profile amongst developers (also the VM was already developed there). The end result was the method-level modification history, including timestamps and authorship info, was lost, since it didn't fit into git's model of treating everything as text files or blobs.

Git is also much more confusing than Monticello.



> The end result was the method-level modification history, including timestamps and authorship info, was lost, since it didn't fit into git's model of treating everything as text files or blobs.

That seems odd, they seem easy enough to map to each other?

> Git is also much more confusing than Monticello.

Not my experience. Uni had us use Smalltalk for a bunch of courses, and Monticello was universally hated (and people caused their to-be-expected number of messes with Git too, but still got on with that much better)


> That seems odd, they seem easy enough to map to each other?

Not unless you treat every method-level modification as a separate commit.


Why not? Git should handle this just fine. And you can always make details-in-second-parent merge commits or squash them down later, if you don't like the whole history having that level of detail.




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

Search: