The conversation

mapcarsHNSource author
Lessons learnedExperience excerpt · English

These ideas are great, but I don't understand how the whole Smalltalk approach can fit into modern …

These ideas are great, but I don't understand how the whole Smalltalk approach can fit into modern development environments of multiple engineers working on a project, client-server architectures, or even large codebases - TDD helps, but high level of dynamism without typechecking can't be reliable in my experience. The ability to fix things on the fly and have the whole system as your ide/debugger is nice, but that's not very practical for the end user.

Original discussionGlamorous Toolkit191 source comments · at import
2

What was this responding to?

Parent context · original excerpt

TU
tudorgirbaHN

Thank you for the comments! Moldable Development is different from programming in Smalltalk. It's not a way of advertising Smalltalk, it's a new way of programming :) Moose indeed came from academia and was focused on various kinds of analyses. Glamorous Toolkit does include a small part of it, but it is a whole environment. Thank you for the suggestion related to use cases. Today, people tend to look for specific tools that can be used out of the box for a specific set of problem. Something like gritql fits in that expectation well. The challenge we face is that Moldable Development is generic and it is applicable in a wide range of scenarios. For example, the video on the front page tries to provide an idea of classes of use cases. The GT book offers many more such case studies. All of these are accommodated uniformly in the same environment with small energy. This is novel and require…

Full original

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 2

Direct replies available in this import. Original-language excerpts.

TU
tudorgirbaHN

Interesting question. The primary goal of Glamorous Toolkit is not to be a technology for expressing systems in. Its purpose is to be an environment with which to work with systems written in various technologies. The differentiator to other environments is that here you can create contextual experiences (made out of micro tools) while you develop. That said, of course, the first language targeted is the main language in which the environment is built: Smalltalk. And you can build interesting systems with Smalltalk today. The end user does not have to see the development tools. You can just fine create web applications. Collaboration is handled through Git (all sources of GT are on GitHub). You mention TDD. Moldable Development is complementary and can be quite interesting to explore :). And more importantly, you can use GT to employ Moldable Development in your system development.

Full original
PJ
pjmlpHN

Exactly the same way as using an IDE, their genesis trace back to the various workstation environments at Xerox PARC, Smalltalk, Interlisp-D, Tajo/Xerox Development Environment (XDE) with Mesa, Mesa/Cedar, and their influence in other programming language ecosystems. The way Java IDEs work on their virtual project filesystem mimics a Smalltalk image for example.

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.