tudorgirba

9 ms·

91.
Gt4atproto: A Dedicated Environment for at Protocol(lepiter.io)
5 points by tudorgirba 3y ago|3 comments
92.
by tudorgirba 3y ago
gt4atproto is an environment for AT Protocol built in Glamorous Toolkit (GT). It covers several things at different levels of abstraction such as: - Creating posts and threads from inside the knowledge management system. - Working with a
93.
by tudorgirba 4y ago
We found that the key is to distinguish between writing and reading. Writing is tied to the computation and there we want as much expression as possible, and text is often hard to replace. But whatever we write, it's just data, and dat
94.
by tudorgirba 4y ago
The low level rendering is handled through Skia and it's hosted in windows handled by Winit. But all the high level model is in Smalltalk.
95.
by tudorgirba 4y ago
In GT, the Pharo VM is like a library, not the main executable. We have two threads: one that runs the UI rendering and one that runs the Pharo image. Also, our build infrastructure is coded in Rust, and all VM libraries we create are writt
96.
by tudorgirba 4y ago
Glamorous Toolkit is based on Pharo, but it is a separate project with its own build system and even graphical stack. I am glad it works for you. Feel free to ask questions.
97.
by tudorgirba 4y ago
Indeed, I am one of the authors :). The connection to other runtimes happens through an instantiating of a more generic proxy model. The same mechanism also enables us to connect with debugging interfaces as well. So, if you have a way to g
98.
by tudorgirba 4y ago
You can already connect Glamorous Toolkit to JS and Python to work with objects exposed by their runtimes :)
99.
by tudorgirba 4y ago
Glamorous Toolkit build the VM differently from Pharo. Please give the distribution a try: https://gtoolkit.com/download/
100.
by tudorgirba 4y ago
There is indeed support for structural editing, but we start the environment from the viewing use case. There are many ways to view data (or programs) and these are much less expensive and approachable than editing. For example, the distrib
101.
by tudorgirba 4y ago
People are using it for various systems and for a variety of use cases that go well beyond programming with Pharo. For example, there are connections to JS and Python out of the box for executing, inspecting and debugging. These are mere ex
102.
by tudorgirba 4y ago
Indeed! > I find the gtoolkit interface a little clunky in a way I can't quite describe I would so love to expore with you what makes it feel clunky. Please do feel free to contact me directly https://twitter.com/gir
103.
by tudorgirba 4y ago
Very interesting question, and one that we are struggling to address :). It's those and more. It's also a programmable knowledge management system. It comes with playground snippets and debuggers for several languages, like JS and
104.
Moldable Development: Guiding Technical Decisions Without Reading Code(infoq.com)
5 points by tudorgirba 4y ago|1 comments
105.
by tudorgirba 4y ago
Key points: - Figuring systems out is the largest cost and impediment in software development, and today it relies mostly on manual work. - Moldable Development is a systematic approach for understanding systems by means of custom tools tha
106.
by tudorgirba 5y ago
The creation of tools can actually be minutes cheap. Through Moldable Development one creates such tools regularly, and most of these are thrown away after being used just once. That can sound like a waste, but it's a significant boost
107.
by tudorgirba 5y ago
Do you draw them automatically, or manually?
108.
by tudorgirba 5y ago
Do you have a link to your project?
109.
by tudorgirba 5y ago
I understand that it can feel uncomfortable to look into a system to know how to use it. However, Glamorous Toolkit is the first large case study of moldable development. To this end, there are custom little tools inside (some ~2k of them)
110.
by tudorgirba 5y ago
Yes! This is one of the areas we actively explored and validated against. For example, take a look at: https://vimeo.com/498735070
111.
by tudorgirba 5y ago
Those numbers come from a peer-reviewed paper and it refers to the data they found in their specific experiment. It is not argued that those specific numbers appear in all cases. However, that data happens to be consistent with several othe
112.
by tudorgirba 5y ago
The environment aims to make systems easier to grasp for people that want to explore their inside. This is quite different from the marketing challenge of convincing one to download a tool after a few seconds :).
113.
by tudorgirba 5y ago
Not quite. It's a motivational text for Moldable Development ( https://moldabledevelopment.com ). This is a way of programming through which programmers construct custom experiences for every single development problem. This
114.
by tudorgirba 5y ago
I very much concur with the view of programming being a projection of our understanding of something in the world (physical or otherwise) into executable code. Like you point out, much can be improved by eliminating the unnecessary dissonan
115.
by tudorgirba 5y ago
Interesting. Consider how the marketing work changed over the past decade to integrate data science. The amount of time spent on decision making might have not changed, but how the time is spent did change significantly. The article argues
116.
by tudorgirba 5y ago
Legibility is relevant. The problem is that legibility requires one to read. And one cannot read the whole code fast enough. That's why legibility is relevant in the small (~one screen). In the large, we can benefit greatly from other
117.
by tudorgirba 5y ago
Interesting. We find the situation to be quite the opposite. The older and larger the system, the more expensive figuring out is. You mention a 3-6 months. That's quite a high price. Would it be inconceivable to optimize this significa
118.
by tudorgirba 5y ago
The proposition is not a tool, but an approach (moldable development). In a way, it is like data science, but for software. The approach was validated for more than a decade in industrial settings. Indeed, there is an environment involved t
119.
by tudorgirba 5y ago
I see this perspective too often. The good news is that it does not have to be painful :). Looking inside the system can be beautiful if only we change the tools through which we look.
120.
by tudorgirba 6y ago
That was a nice demo, indeed. If you liked that one, you might want to take a look at gtoolkit.com, too.

More ›