Fork me on GitHub
#calva
<
2023-07-03
>
p-himik17:07:40

Had a random idea that I'd like to voice so I don't forget it, just in case it's useful. It's targeted mainly at beginners. What if every exception message had a button that would lead the user to a web page that connects them with some expert that can help them out? And the action behind that button could be available just as is, without being tied to any exceptions, to be triggered whenever. There are quite a few concerns here of course, but I don't want to get into the weeds since someone might quickly point out why this idea is dumb.

seancorfield18:07:37

Sort of like an "AI explainer" for exceptions? 🙂

p-himik18:07:04

But "NI" in this case. :) Right now a person would have to: • Think whether it's worth going to some other platform, write all the details, provide some code, etc. • Actually go there • And write all the details • And provide the code With such a button, a user would have to press it, maybe log into some service, and that's it.

p-himik18:07:40

And not just an explainer. More like "a human expert available in my IDE or elsewhere, at the press of a button".

p-himik18:07:35

I believe there is a platform (either with Clojure support or with focus on it) that lets people that are registered as expects tutor or help on a case-by-case basis people that are registered as regular users. But I couldn't find it right away. So, something similar, but with an easier access and sharing.

pez20:07:06

I like it.

bringe21:07:39

Interesting idea. Thinking about the other side of that service, I could see the experts/helpers having a lightweight app installed (maybe something that exists could be used) that would notify them when someone's requesting help. This could be similar to a ride share service notifying drivers that someone needs a ride. Rough idea of how it could work: 1. User requests help from their IDE 2. User is notified of their position in the queue (if a queue is used) and/or the expected time until helped 3. Helpers are notified 4. The first helper who hits the button to help becomes the user's helper 5. User sees the helper pop up in a video call on their screen (ideally in their IDE) The hard part of this IMO is developing a good incentive system for the helpers. Would they get paid? How much? Where does the money come from?

👍 2
pez22:07:54

Thinking out loud here… What if the IDE hosts the helper’s app too? So you would have a REPL and all Clojure IDE support at hand to experiment with whatever code you need to experiment with in order to help.

👍 1
vlad_poh21:07:43

I have a cljc file and 2 repls running. normally i’m able to toggle between the repls by clicking on the cljc/clj item in the bottom bar. Nothing happens when i click now. How do i troubleshoot?

pez21:07:04

Do you see any related errors in the developer tools (Help menu) console when you click the button?

pez06:07:19

Does it choose repl correctly for clj, and cljs files, respectively?

vlad_poh15:07:37

@U0ETXRFEW yes it does. clj for clj cljs for cljs and cljc/clj for cljc but the click on cljc/clj to toggle to cljc/cljs doesn’t happen. I just uninstalled and reinstalled calva but the same result. I’m on a mac. It works on my windows machine.

vlad_poh17:07:32

@U0ETXRFEW need to mention that the shortcut key to toggle works its just the click that doesn’t

pez17:07:20

Oh, that’s extra funny. Same Calva version works on Windows for you?

pez17:07:05

Can you try with VS Code Insiders?

vlad_poh03:07:14

@U0ETXRFEW it works with VS Code Insiders!

metal 2
pez05:07:34

Thanks for confirming! Assuming you haven’t copied all your settings and installed all the same extensions already, I think that leaves us with three possible explanations: 1. There’s some conflicting extension in play. 2. There’s a setting that somehow causes this. 3. Your VS Code install has some dirty state. 1 and 2 are pretty unlikely for this kind of error. You can confirm by installing the same extensions and copying over the settings to insiders. 3 is what I think has happened. We’ve seen strange things happening lately due to that. And then it has been three types of dirtyness: 1. Restart of VS Code helps. 2. Restart of the computer helps. 3. Complete wipe of all VS Code state on disk. I’m guessing that a restart of the computer is what it takes in this case. But if you haven’t tried restarting VS Code yet, by all means, start there.

👍 1
vlad_poh21:07:22

@U0ETXRFEW its working after the re-installation. Thanks!

metal 1
🙏 1