Yeah, I see the idea of using a thin client and a central repository, especially in a development environment. It's much easier to have a single repository where class/module changes could be managed as opposed to having to do the dreaded 'merge' across multiple developer's code.
Kind of diverging a bit, I work as a Smalltalk devleloper. And, yes, people do still program in Smalltalk, but it's due to have a very limited life-span. The development environment, VisualAge, uses a central repository as you described. It's great, since it makes managing releases and changes very easy.
I hope your job and work situation will work out for you. As someone that had financial troubles in the past, I think I can relate to your struggles. Best of luck to you.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
momijizukamori
no subject
Date: 2005-01-21 18:59 (UTC)Yeah, I see the idea of using a thin client and a central repository, especially in a development environment. It's much easier to have a single repository where class/module changes could be managed as opposed to having to do the dreaded 'merge' across multiple developer's code.
Kind of diverging a bit, I work as a Smalltalk devleloper. And, yes, people do still program in Smalltalk, but it's due to have a very limited life-span. The development environment, VisualAge, uses a central repository as you described. It's great, since it makes managing releases and changes very easy.
I hope your job and work situation will work out for you. As someone that had financial troubles in the past, I think I can relate to your struggles. Best of luck to you.
-- Jacob