It shouldn't. I'd say this channel is the best fit.

Maybe also #C03RZRRMP.

Out of the curiosity, what is this photo? game of life?

Not sure what they are trying to evoke or reference with the image.

I bet the DALL-E generative art derpartment were miffed that they chose that image over all the millions of DALL-E images that have been generated.

Anyone planning to go to the event or watch it online? SamA has said they won’t be announcing GPT 4.5 or GPT 5.

I’m planning on watching — on several levels. Their AGI quest could spoil things in lots of ways. The “perfect” always destroys the useful and parodies itself.

You were a cute little lamb-da back then!

Yes, I guess I was!

That’s fun.

Mine from 2014. Someone may miss the emacs session, but the stacktrace is unmistakable 🤪

I like the fancy shoes

this is interesting! seems like a lot of the documentation is missing code blocks, which makes reading it a little hard.

I am definitively sure you got something too! May I ask why you assumed something had broken. I don't think "idiot" can explain it.😜 (you don't have to answer, I am just out of curiosity, and want to ask a "socratic method" question.

I had lost the ability to connect to a shadow-cljs repl, normally in vs code my workflow would be to open vs code terminal, and then run sudo shadow-cljs watch app. Browse to localhost:8080, Then click on REPL in Vscode and select connect to a running repl in your project and select shadow-cljs, select :app and I'd have a working repl. Yay! I was trying to do this, but now my option to select shadow-cljs had disappeared. Instead I could select shadow-cljs only when I select connect to a running repl outside your repl, but this wasn't working and wouldn't connect. I had forgot that I had opened VS code one folder up in my structure a few days ago to work on some release script, and from then had just re-opened vs code and continued working, not realising I was in the wrong folder. Now, I don't know why I was able to run my sudo shadow-cljs watch app, one folder up and have it work! I guess terminal remembers the folder it was in (one level down), last time it was opened, rather than open in the folder vscode has opened, and this maybe was further misleading me. Annoying if so.

Yes, probably the terminal was in the right directory. I’ve done things like that many times. It can get a bit dangerous. It’s the only downside I see with the integrated terminals, which I otherwise am a big fan of.

> sudo shadow-cljs watch app Why sudo?..

It's complicated.... In this project I'm using a react component, but it needs built. So I had to install and get webpack working, and i build the js part and the cljs part separately. It took hours to get it all working, and the only way I eventually got it working was to run all the js side stuff with sudo. But now I have to run shadow-cljs with sudo now too, else it doesn't work. I don't like it, but the webpack stuff was such a headache that I just put up with it now, as I don't want to go through all that again. I just tried to find the command I ran to get it all working, but I've forgotten to take note of it, which is going to be a headache at some point, figuring it out again 😞

Sounds terribly dangerous. Chances are, you intentionally or accidentally used sudo once in that project and now some webpack or npm-related stuff doesn't work because it can't write to some file. I would strongly suggest fixing it at the earliest because running npm-related stuff with sudo is basically handing out free footguns that are targeted only at your feet, at all times. Oh, and by keeping using sudo in that manner you will likely make other things impossible to run without sudo as well - again, just because something created some file that some other process might need to write to or delete.

> I was trying to do this, but now my option to select shadow-cljs had disappeared. Instead I could select shadow-cljs only when I select connect to a running repl outside your repl, but this wasn't working and wouldn't connect. I am still curious about this part. Did this make you believe the calva went wrong? What do you think this make you believe that? (I guess I would make the same assumption supposing the plugin would update automatically) Could others share your thoughts on this situation? how would you debug and realise the folder issue?