george

1.6K posts

george banner
george

george

@geooot_

software person @ aws

UTC-8 Katılım Ağustos 2013
777 Takip Edilen406 Takipçiler
george
george@geooot_·
so i somehow started with JSONlogic and then ended up at nix again
English
0
0
1
17
george
george@geooot_·
if you really think about it. only 20 or so years was actually good. so i guess the odds were never good anyway
English
0
0
0
17
george
george@geooot_·
@Hilti does that mean you cant distribute an app on the app store that depends on GPL dynamic libraries?
English
1
0
0
409
george
george@geooot_·
Is there a taxes skill or MCP server?
English
1
0
1
59
george
george@geooot_·
@iamdavidhill @opencode i use it. AIs can be kinda verbose (especially in plan mode) its nice to refer to a previous conversation point
English
0
0
0
35
David Hill
David Hill@iamdavidhill·
desktop users, let's talk about the message timeline... it's always been rough around the edges. we have ideas for making this better, but need your input: ① are you using this? ② if so, when and why? ③ if not, why? ④ type your own answer
David Hill tweet media
English
29
0
77
9.5K
george
george@geooot_·
@thdxr isnt that what opencode does? or is there a specific “doneness” something should get to before shipping?
English
0
0
0
59
dax
dax@thdxr·
ship something shitty fast and fix it later culture just does not produce anything great there's mountains of rationale as to why you should do that but i've never seen it work and it always turns the company into a painful place to work nothing going on right now changes this
English
115
73
1.4K
67.7K
Deleterious Appeal
Deleterious Appeal@sanggr3al·
@Tyriar "It's ok for us to suck because they suck too" No wonder everything is becoming enshittified.
English
4
0
196
13K
Daniel Imms
Daniel Imms@Tyriar·
TIL the built-in macOS terminal takes 5 seconds to paste 50kb of ascii, who's day are we going to ruin with this information?
GIF
English
75
27
1.4K
228K
Tzvetan Mikov
Tzvetan Mikov@tmikov·
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
16
9
105
12.9K
george
george@geooot_·
its giving happy thanks
English
0
0
0
55
george
george@geooot_·
@tmikov i mean its a good technique to rage bait people
george tweet media
English
0
0
1
109
Tzvetan Mikov
Tzvetan Mikov@tmikov·
@geooot_ Right. But that is not actually possible only through the injected interface.
English
1
0
1
603
Tzvetan Mikov
Tzvetan Mikov@tmikov·
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
12
4
75
9.4K
george
george@geooot_·
@tmikov honestly im not even sure i would say it eliminates function coloring since the functions would be “colored” by requiring an io instance to be passed into it
English
0
0
0
40
george
george@geooot_·
@tmikov did you have to bring your own event loop?
English
1
0
0
380
Tzvetan Mikov
Tzvetan Mikov@tmikov·
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
42
65
866
210.8K
george retweetledi
Barack Obama
Barack Obama@BarackObama·
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
50.3K
81.6K
581.7K
55.6M
george
george@geooot_·
first you think your a shawn spencer only to realize your a carlton lassiter 😫😫😫😫
English
0
0
0
86
george
george@geooot_·
i wonder if i think or do i just pattern match 🤔
English
0
0
0
86