mpweiher

6 ms·

91.
by mpweiher 2mo ago
> 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. Those "updates" go in the queue. When the UI gets around to updating
92.
by mpweiher 2mo ago
Many, though I have to start with this disclaimer: I still don't fully understand why Objective-C is such a sweet spot. One very important one is that, empirically, it showed how much of what we think we know about language design is .
93.
Call Stack Diffs(oskrim.github.io)
4 points by mpweiher 2mo ago|0 comments
94.
by mpweiher 2mo ago
You obviously have some very non-standard definitions at work here. apply/map/collect are just higher order operations, they have nothing to do with reification, except that you need the functions that are arguments to be first c
95.
by mpweiher 2mo ago
> Swift should have been a modernized Objective-C. It should have kept the best parts of it, which made it a joy to use, and leave the archaic and the weird things behind. That's what Objective-Smalltalk is, or rather, what it start
96.
Prevent cognitive debt by manually retyping LLM-generated code(ankursethi.com)
545 points by mpweiher 2mo ago|443 comments
97.
by mpweiher 2mo ago
> Swift should have just been a much improved syntax over that same runtime That's exactly how Objective-Smalltalk started, and it's still very good at being just that. https://blog.metaobject.com/2019/12&#
98.
by mpweiher 2mo ago
>> UI is also very much not functional, > I disagree, and I believe that the complete stagnation of GUIs is due to ignoring this. I disagree with your assessment. >Description->Pack->Apply events->Generate assets->Re
99.
by mpweiher 2mo ago
"A view is a (visual) representation of its model. It would ordinarily highlight certain attributes of the model and suppress others. It is thus acting as a presentation filter." https://web.archive.org/web/20
100.
by mpweiher 2mo ago
Yes, they don't ever openly admit mistakes. But they do quietly drop or fix them, covertly acknowledging they were mistakes. Often with this messaging: "we have this new shiny thing that is even better than the old shiny thing
101.
by mpweiher 2mo ago
Dude, what I describe is exactly MVC. Your interpretation is a common misconception, for example promulgated by Apple. It is not MVC. https://blog.metaobject.com/2015/04/model-widget-controller-... https:/&#
102.
by mpweiher 2mo ago
Yes and no. Conceptually, the UI re-renders itself completely in order to always be an accurate reflection of the model. That is the #1 job of the view: be an accurate reflection of the model. And re-rendering itself completely is a safe wa
103.
by mpweiher 2mo ago
Yep, to anybody who actually knows MVC, the whole Elm/React/SwiftUI stuff is funny. "We solved the problems of MVC by properly applying MVC". https://blog.metaobject.com/2017/03/concept-shadowin
104.
by mpweiher 2mo ago
Yeah, M-V-C are all roles, not concrete objects. The C mediates between the input devices and the model, but in practice views can and often do fulfill that role as well. Cocoa views, for example, also fulfill the C role. Different formul
105.
by mpweiher 2mo ago
I never claimed MVC is a silver bullet. Just that it solves "... incredibly easy to forget an edge case in your update logic." > UI does not re-render itself too much? Glad you asked! In my Blackbird reference architecture (
106.
by mpweiher 2mo ago
Not if you actually do MVC, so solved around 50 years ago. 1. The UI tells the model to change. 2. The model does the change and possible related changes. 3. The model notifies the UI that something has changed. 4. The UI updates itself f
107.
by mpweiher 2mo ago
This used to be different. NeXTstep and early MacOS-X were pretty much the finest platforms to develop on.
108.
by mpweiher 2mo ago
Not just complex. Also "successful for other reasons". And of course the RDF is particularly strong in Apple's case. And these are interlinked as well: they were successful in the past not just despite ignoring feedback&#
109.
by mpweiher 2mo ago
Not just does the computer not do functional. UI is also very much not functional, and in fact the lack of progress in UI the last 30-40 years can largely be traced to trying to create UI with procedural/functional programming language
110.
by mpweiher 2mo ago
Not sure how you define "success" here. Is Bonsai used much outside of Jane Street?
111.
by mpweiher 2mo ago
https://en.wikipedia.org/wiki/Poe's_law
112.
SwiftUI After 7 Years(ykvm.com)
279 points by mpweiher 2mo ago|334 comments
113.
SwiftUI After 7 Years: A Story of Mediocrity [video](youtube.com)
5 points by mpweiher 2mo ago|0 comments
114.
North American construction is back–smaller and faster–at OPG's Darlington(ans.org)
3 points by mpweiher 2mo ago|0 comments
115.
Epipe on write might mean you're doing it wrong(rachelbythebay.com)
2 points by mpweiher 2mo ago|0 comments
116.
Building Progressively Enhanced Forms Using Htmx(rafa.ee)
3 points by mpweiher 2mo ago|0 comments
117.
What Naur got wrong from The concept of mind(tssm.neocities.org)
4 points by mpweiher 2mo ago|0 comments
118.
Building Progressively Enhanced Forms Using htmx(rafa.ee)
97 points by mpweiher 2mo ago|14 comments
119.
by mpweiher 2mo ago
Have you seen the shenanigans modern C compilers are up to? If you think your compiler will respect your code's semantics, you might be in for a rude awakening. And there are certainly ways of influencing an LLM to be "more determ
120.
by mpweiher 2mo ago
"Turnabout is fair play" Or as the poster put it > When seeing the title of this post, I bet in some people's minds, the first thought was "Rust devs!". This connection is not unfounded. Exactly. The Rust commun

More ›