Conversation
Notices
-
Embed this notice
> for non-commercial use
> to push a subscription plan
"hacker" "news" stop burying the lede challenge impossible
RE: https://mstdn.social/@hkrn/113362774098072221
- Sick Sun likes this.
-
Embed this notice
@icedquinn VSCodium is free for everything... Emacs is free-er than codium :comfy:
-
Embed this notice
@captainepoch 9/10 wrist surgeons recommend emacs
-
Embed this notice
@newt @captainepoch @gooby535 kpart yeah. they used to have some corba stuff as well.
-
Embed this notice
@gooby535 @captainepoch @icedquinn i use emacs almost for everything, except KDE stuff. QML requires launching QtCreator every once in a while.
Kate is used as a component in KDevelop. Almost all KDE things can be embedded into each other. This is how Konversation ended up with an embedded terminal for some reason, because you absolutely need it in your IRC client.
-
Embed this notice
@newt @captainepoch @icedquinn Yeah it's unfortunate, though tbh Kate has been doing everything I want it to do so far so I can't complain, only need to hop into VsCode for jupyter or such. I just wish there was actual documentation for writing extensions, because what there is right now is pretty confusing and minimal, and the fact all KDE stuff is written in C++ doesn't help honestly. I'm not sure how different KDevelop is, but afaik it shares a big part of its codebase with Kate so I assume it's mostly the same? I think I'd have been using Emacs now if its web stuff wasn't so ass.
Also hi, glad to be here :blobfox_w_:
-
Embed this notice
@gooby535 @captainepoch @icedquinn i wish kdevelop wasn't so dead
btw haaai :akkohi2:
-
Embed this notice
@captainepoch @icedquinn Kate is also free (but such a pain to modify that it's kinda not)
-
Embed this notice
@captainepoch I'm doubtful of the freeness of "vscodium", considering that has a place to download proprietary plugins from.
-
Embed this notice
@sicp Can you link to such repository agreement?
I suspect the requirement is that the plugins must be gratis and depending on the requirement, that could make all the plugins nonfree even if they are licensed under MIT expat and have full source code.
-
Embed this notice
@Suiseiseki @captainepoch It seems that VS codium uses the "Open VSX" package repository hosted by Eclipse, since only the Microsoft version can access the plugins hosted by Microsoft. However the publisher's agreement they require you to agree to in order to publish plugins doesn't appear to require that your plugins are free. Even if that were the case though and every part of it were completely free, that wouldn't help it from being garbage software!
-
Embed this notice
@captainepoch >VSCodium is free by itself.
It's hard to know for MIT expat licensed projects, as that license explicitly allows for sublicensing, which means adding proprietary software to the project is allowed and often happens.
>Plugins are something you're not forced to install, unless you want extra features.
You're kind of forced to install them if you want the ability to compile many languages.
>You could make propietary Emacs plugins
That would constitute copyright infringement and the copyright holders won't hesitate to enforce their copyright and demand that the plugin either be deleted or released as free software under a compatible license.
Note that a privately written plugin for your personal use only is trivially free and not proprietary.
-
Embed this notice
@Suiseiseki VSCodium is free by itself. Plugins are something you're not forced to install, unless you want extra features. But the editor itself is free.
You could make propietary Emacs plugins too, does that make Emacs less free itself?
-
Embed this notice
@sicp The terms require that the plugins are licensed and gratis, but there is no requirement that they are free.
It's hard to read, as it says "Non-Code Content" in the definitions, but doesn't use that term.
They also require you accept all liability and even make it a requirement that you comply with "all applicable laws", even unjust ones.
Skim-reading, it appears that despite the bad requirements, the terms don't require the software to be proprietary.
-
Embed this notice
@Suiseiseki https://www.eclipse.org/legal/documents/eclipse-openvsx-publisher-agreement.pdf
It says under section 3e that you can't require compensation for your plugins when they're distributed on the registry, but those appear to be terms for the use of the repository as a publishing service, which I think are fair. It wouldn't restrict you from publishing or charging money for them elsewhere.
Under section 4 it says that plugins must be licensed and those without a provided license will be distributed as MIT-licensed, but nothing about restrictions on the terms of the license that you choose. I could not find anything that would grant them the ability to relicense anything you've published.
-
Embed this notice
@sicp *are licensed and gratis when distributed from them.
It does not say you're no allowed to distribute it separately under different terms.
iced depresso
Adolph
:suya:
Gooby
翠星石
the_daikon_warfare
All GNU social JP content and data are available under the