kikimora

This does not match my observation. Over my life I’ve seen many gifted individuals. None exhibit high sensitivity to criticism. Most were open to feedback, even not confirming their choices and actions.

How on earth I never came across this before? ChatGPD does not know about this project either. Looks very, very promising!

It is the same Xiaomi which announced 300 000 SU7 vehicles sold in a day and 6 months later reported they are struggling to hit their sales targets? Just don’t believe anything a Chinese company say, divide it by at least 2. I have nothing against China, this is a cultural thing which you should be aware reading anything coming from the country.

Prompts plus code called literate programming, have been around over 30 years.

Twitter content is trash

You can say it this way. Other way to put is optimal policy makes optimal decisions on every step as if it knows the future. If you looking for shortest distance in a graph then at every vertex it picks the right step, even if the edge is longer than other available in the vertex, as if it knows the future. This is why you cannot just build an algo implementing the policy, you have to find it with dynamic programming.

There was research showing how AI performance degrades as you go from green field into support. My guess ERP in question will break after some time as agent will add more bugs than new features. Plus recovering data will be extremely difficult.

You have n decisions to make - this is your policy. After you make one, if your remaining n-1 decisions also optimal, then you have optimal policy.

I like drag&drop way more than .pkg. just easier to deal with. If you do a CLI tool then maybe `brew install CLI` is the way to go instead of a pkg file?

>The coalescing is two-level: first, simple duplicates are weeded out. Second, if the update queue gets very full, it becomes coarser-grained, and weeds out duplicates based on that coarser grain

This is not about duplicates. For example, sync updates 100 items in a list changing their titles. Items are bound to a list in the UI. Thus, 100 unique title update events triggered.

>Events are only used in the M→V communication

I don’t understand. Button clicked -> model change -> view update -> new event triggered -> model or view updated again … This is not something one would code on purpose, but often an attempt to create relationships between view. Like a custom layout code. Might not include model at all, just views being updated in an event handler trigger more events and more updates to views.

MVC is not bad, but it is not a silver bullet. Calling MVC an ultimate solution to UI is oversimplification. Just looking at the steps you listed I can ask:

How do you collect all notifications on step 2 to fire them on step 3 such that UI does not re-render itself too much? E.g. updating a title of each item in a list of 100 items should not trigger 100 renders. Or 100 layout calculations (which I think is harder to avoid).

How do you deal with situations where on step 4 UI triggers an event that your model happens to listen and the cycle repeats while killing performance?

Because you rely on events how do you avoid “event hell”? That is, a situation when an event handler triggers a change that triggers another event handler that triggers a change and so on. Sometimes it is scrolling or typing, sometimes it is parts of the model subscribed to each other bubbling events to UI.

Famous UI = f(Model) is oversimplification that was sold in slides. Real “functional UI” frameworks implement UI = f(Model, UIState) where UIState is scroll and cursor positions, view pool for virtualization, rendering caches, etc. USState is mutable and managed by the framework and the rendering engine (e.g. React + DOM, SwiftUI + UIKit + CoreAnimation). I don’t see a problem with functional approach as in React. I do see a problem with understanding of how UIState being managed between framework, ui library and rendering engine.

No, but the project does not meet its goals around memory safety. It is usage Rust all the way down with same memory safety issues.

Yes, bonds, sometimes corporate debts, often money market participation.