Mastering ENVY/Developer
by Joseph Pelrine · first published 2001
11mentions
2recommended by
2HN commenters
2013–2026first – last mentioned
100% recommend
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
None whatsoever. This is the worst thing about Smalltalk (with the exception of the open-source ones) - there is almost no useful documentation freely available. I was forced to buy "Mastering ENVY/Developer" by Pelrine, Knight and Cho. It is well worth the money though.
on “Methods for Teaching the Programming Language Smalltalk (1977) [pdf]” ↗> … at best hostile… Strange that you don't mention ENVY/Developer? Method-level source-code version-control and configuration-management implemented for VisualWorks, IBM Smalltalk and Digitalk. "Mastering ENVY/Developer" https://www.google.com/books/edition/Mastering_ENVY_Develope...
on “Byte Magazine Special Issue: Smalltalk (1984)” ↗>but then came Java< Yes. >image based source control systems< "Mastering ENVY/Developer" http://books.google.com/books?id=ld6E19QIMo4C
on “Today’s Smalltalk: A Second Look At The First OO Language” ↗…"multiple, separate images" would run in the same OS process? Otherwise — [pdf] "Distributed Smalltalk" http://www.cincomsmalltalk.com/main/documentation/VisualWork... Otherwise (for source code control) — "Mastering ENVY/Developer" https://books.google.com/books?id=ld6E19QIMo4C
on “Give Me Back My Monolith” ↗…https://rmod-files.lille.inria.fr/FreeBooks/TheInteractiveProgrammingEnv/TheInteractiveProgrammingEnv.pdf Late-80s early-90s multiple developers might be using ENVY/Developer version control: https://www.google.com/books/edition/Mastering_ENVY_Developer/ld6E19QIMo4C?hl=en&gbpv=1&dq=envy+developer&printsec=frontcover
on “Pharo 10” ↗Back in the day, Morgan Stanley & JPMorgan & …, used ENVY/Developer — fine-grained Smalltalk config-map / sub-application / class / method configuration & version control in a central database. "Mastering ENVY/Developer" https://www.google.com/books/edition/Mastering_ENVY_Develope... Some folk worked as "librarians" to promote code reuse across projects.
on “An oral history of Bank Python” ↗2001 book "Mastering ENVY/Developer" https://www.google.com/books/edition/Mastering_ENVY_Develope...
on “On Learning Smalltalk” ↗There's an actual book — "Mastering ENVY/Developer" https://www.google.com/books/edition/Mastering_ENVY_Develope... The fun thing is the way people could subvert and ignore the recommended development process because it seemed inconvenient to them.
on “Trunk-Based Development: Game Changers” ↗…code in an opaque "repository" Without the scare quotes we'd call that a database. "Product Revew, Object Technology's ENVY Developer" https://www.google.com/books/edition/Mastering_ENVY_Develope... Mastering ENVY/Developer" https://www.google.com/books/edition/Mastering_ENVY_Develope...
on “An Efficient Implementation of SELF (1989) [pdf]” ↗…were integrated continuously throughout the day — "This fine granularity of components enables highly concurrent development because changes can be tracked down to the individual method level …" 2001 "Mastering ENVY/Developer". https://www.google.com/books/edition/Mastering_ENVY_Develope...
on “Ruby and Its Neighbors: Smalltalk” ↗Perhaps decades ago there was "more sophisticated versioning" for Smalltalk implementations: 2001 "Mastering ENVY/Developer". https://www.google.com/books/edition/Mastering_ENVY_Develope...
on “LT6502: A 6502-based homebrew laptop” ↗