News for hackers. Stuff that matters.
Re:Forget ChatGPT: why researchers now run small AIs on thei... by aftbit on Saturday September 21, 2024 @09:33PM (#41613971)
I dropped VSCode when I found out that the remote editing and language server extensions were both proprietary. Back to vim and sorry I strayed.
Re:Forget ChatGPT: why researchers now run small AIs on thei... by all2 on Saturday September 21, 2024 @10:49PM (#41614282)
Jetbrains is pretty ok on this front. I've been enjoying using my beefy computer to do work from my potato laptop.
Re:Forget ChatGPT: why researchers now run small AIs on thei... by prometheon1 on Sunday September 22, 2024 @07:23AM (#41616303)
The way I read it, the message you replied to was a complaint about parts of VSCode being proprietary. Do you mean to say Jetbrains is pretty ok on the "not being proprietary" front?
Re:Forget ChatGPT: why researchers now run small AIs on thei... by aftbit on Monday September 23, 2024 @01:23PM (#41628407)
Yeah, 100%. I'm not a hardcore FOSS only person, but for my core workflow, when a FOSS tool exists and works well, I am not likely to use a proprietary alternative if I can avoid it at all.

So yeah, I'll use Excel to interoperate with fancy spreadsheets, but if LibreOffice will do the job, I'll use it instead. I tried out several of the fancy proprietary editors at various times (SublimeText, VSCode, even Jetbrains), but IMO they were not better _enough_ to justify switching away from something like vim, which is both ubiquitously available and FOSS.

Re:Forget ChatGPT: why researchers now run small AIs on thei... by causal on Monday September 23, 2024 @02:56PM (#41629370)
Making the remote editing extension closed is particularly frustrating, as you have little visibility into what it's doing and it is impossible to debug obscure errors