dude that would be so incredibly cool

your question may have become part of the training data with how much coverage there was around it. perhaps you should devise a new test :P

I suggest asking it to identify/count the number of fire hydrants, crosswalks, bridges, bicycles, cars, buses and traffic signals etc.

Pit Google against Google :D

My job may have become part of the training data with how much coverage there is around it. Perhaps another career would be a better test of LLM capabilities.

Have you ever heard of a black swan?

3.1 Pro has the same Jan 2025 knowledge cutoff as the other 3 series models. So if 3.1 has it in its training data, the other ones would have as well.

The fact it's still Jan 2025 is weird to me. Have they not have a successful pretrain in over a year?

They likely won’t have a full pretrain for awhile. Just like everyone else, the name of the game now is to finetune existing models.

Honestly at this point I have fed this image in so many times on so many models, that it also functions as a test for "Are they training on my image specifically" (they are generally, for sure, but that's along with everything else in the ocean of info people dump in).

I genuinely don't think they are. GPT-5.2 still stands by 4 legs, and OAI has been getting this image consistently for over a year. And 3.1 still fumbled with the harder prompt "How many legs does the dog have?". I needed to add the "count carefully" part to tip it off that something was amiss.

Since it did well I'll make some other "extremely far out of the norm" images to see how it fairs. A spider with 10 legs or a fish with two side fins.

Easy fix, make a new test image with six legs, and watch all the LLMs say it has five.

also wondering about this. it sure isn't in electrobuns own discord server. i'm in that one and its mostly Q&A (with Yoav doing most of the answering and a couple people like me doing most of the questioning, ha)

this is the first i'm hearing about games being built with electron / web tech too, let alone electrobun. i thought most game devs would just go for unity or godot

thank you for building electrobun!!

i'm not sure how you could have any meaningful comparison here except for comparing bun to node. everything is pretty modular so you can swap things out. i would compare webview to chromium bundle size, but that has tradeoffs too, and electrobun can use chromium (CEF) too. so that's also moot.

what kind of numbers are you looking for?

most use cases are supported out of the box. you just have to set a few env vars

and then build with "notarize: true" in your config... and it pretty much just works

i've signed and notarized things with electrobun and it's perfectly fine. it also gives you escape hatches in case you're doing something more complicated

EDIT: in case i can help you with anything there, feel free to DM me! or join the electrobun discord. i'm very active there. (im not affiliated with EB. just know the struggle of apples notarization system)

Thanks, that's great! Very generous.

they don't support mobile targets at the moment but i'm pretty sure i saw the creator saying it's a "sometime in the future" thing

very interesting, thank you for investigating

no real gotchas. JS is slightly dangerous because of JS, yes. You should never fetch things at runtime to execute if possible - instead, you install absolutely everything you need with npm or bun, and it gets inlined at build time

electrobun ships with an RPC (i think it also does some encryption?) so as long as you use that to communicate between your webview and bun "host process" you should be safe.

afaik its around 14MB but the large majority of that is the Bun runtime itself. at some point it will likely be possible to pick and choose parts of the runtime to include in the binary. thus the bundle size could get a lot smaller in the future

that said electrobun's author has published a bsdiff implementation in zig, and thats used for electrobun's updater. that means you download deltas, not the entire application bundle, every time you push an update to your users. and then it gets patched in-place.

this makes updates tiny, to the tune of a couple kB