george
1.6K posts


Apple approved ColumnLens for the Mac App Store. It's built with Dear ImGui and C++. Pretty sure it's one of the first ImGui apps on the store.
Wrote up what the process looked like: marchildmann.com/blog/imgui-mac…
#imgui #dearimgui #cpp #macOS #indiedev #buildinpublic
English

@iamdavidhill @opencode i use it. AIs can be kinda verbose (especially in plan mode) its nice to refer to a previous conversation point
English

@Tyriar "It's ok for us to suck because they suck too"
No wonder everything is becoming enshittified.
English

@tmikov Its going to just be for JS values that can be structuredClone right? developer.mozilla.org/en-US/docs/Glo…
English

ISerialization just landed in the static_h branch and will be out in the next stable release.
ISerialization encodes a JS value into an efficient opaque binary representation, which can then be de-serialized (deeply cloned) in one or more runtime instances.
It also optionally supports serialization with ownership transfer.
It is intended for efficient passing of values between runtimes and will be the base of message passing in our implementation of Web Workers.
English

@geooot_ Right. But that is not actually possible only through the injected interface.
English

I saw an interesting claim that Zig has eliminated the need for "function coloring" (marking functions explicitly as async) for I/O. After looking into it, I am not fully convinced.
The key problem is the ability to cooperatively suspend the state of a running function while waiting for I/O, going back to the event loop and continuing to execute other events.
There are several ways to do that:
a) Just use a thread-pool. Suspend the running function on one thread and continue execution on another.
b) Manually swap the stack (green threads).
c) Stackless coroutines.
Unless I am missing something, none of these is perfect.
a) would violate the expectations of a systems programming language by unpredictably changing the id of the executing thread. Also, thread context switching is not free.
b) is possible, but it doesn't work on all platforms (Wasm), and is generally not super robust with debuggers, profilers, crash reporting, etc. Perhaps not ideal for a low level language.
c) In order for a suspension to work, all callers must be compiled as stackless. So it is impossible without explicit function coloring (precisely the thing that has been eliminated) or without compiling everything stackless, which would be a huge regression.
AFAICT, the most practical way to do this is to assume a thread-pool eventing system - basically a). That is certainly an elegant and powerful way to do I/O.
I suspect that b) may be the one gaining popularity - after all, the problems are solvable and Wasm will eventually get stack switching. Still, I feel that it is a somewhat risky runtime model.
In practice, either a) or b) seems more like reframing thread-pool async I/O than removing function coloring altogether.
Disclaimer: I am not a Zig user, so I am looking at this purely from high level design curiosity. I don't have a stake in this, but these approaches are certainly applicable to other languages like C++.
English

@tmikov this article was a very good read on the background by it kristoff.it/blog/zig-new-a…
English

Introducing proof of concept React Imgui! The name is a joke, but it is accurate enough.
In the last few days I have been working on a prototype of React driving Dear ImGui using Static Hermes.
The result is a fully native app written almost entirely in JavaScript, using unmodified React, typed JS, plus a very small amount of glue C++ code and unmodified Dear ImGui and Sokol.
The actual renderer translating React into Dear ImGui is written entirely in typed JS using zero-cost FFI.
Of course this wouldn't be possible without React's great design and flexibility. I find it really fascinating that I was able to take literally unmodified React, write a little extra JS, and get a functional fully native app so quickly.
Of course everything is unoptimized, and prototype code quality, and who knows how buggy, but it seems to work well enough.
Please, watch the video to see it in action.
If there is interest, I will write a more detailed article.
English
george retweetledi

After years of complaining about cancel culture, the current administration has taken it to a new and dangerous level by routinely threatening regulatory action against media companies unless they muzzle or fire reporters and commentators it doesn’t like. yahoo.com/news/articles/…
English







