Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I’m switching from VS Code to VS Codium

ruky.me

Post reply on HN
Print view View original

91–100 of 343 posts

Re: I’m switching from VS Code to VS Codium

#91

Post by q-big »

lelandfe wrote: post #9
Asraelite wrote: post #2

The last time I tried Codium, not being able to use Remote Development was a showstopper. Has the situation improved since then?

No, and don't expect it or Live Share to ever land[0]. None of the "Remote" extensions are FOSS, and they restrict usage to "validly licensed" copies of VS Code[1] – plus the server side code for it is closed source. So getting it into Codium would require a clean room implementation, essentially. [0] https://github.com/VSCodium/vscodium/wiki/Extensions-Compati... ] [1] https://marketplace.visualstudio.com/items/ms-v…

> So getting it into Codium would require a clean room implementation, essentially

... if you want to go the legal route. ;-)

Re: I’m switching from VS Code to VS Codium

#92

Post by eatbitseveryday »

> f [sic] you want to get the full open-source MIT-licensed VS Code with no cemetery [sic] tracking

I prevent telemetry tracking by blocking all network access to VSC using Little Snitch. Get it set up initially with plugins then cut it off. I don’t use VSC in ways that require network access thereafter.

Re: I’m switching from VS Code to VS Codium

#93

Post by elashri »

realusername wrote: post #51
jmyeet wrote: post #20

What I find truly bizarre is how many software engineers, who are aware of how much they earn and how long it really takes to make software, are so resistant to paying anything for tools that make their job easier and faster. It blows my mind. Take the Jetbrains IDEs. I don't mean to offend any VSC fans out there but the Jetbrains IDEs are simply better and more mature in every single way. For individual use, most of…

> Take the Jetbrains IDEs. I don't mean to offend any VSC fans out there but the Jetbrains IDEs are simply better and more mature in every single way. For individual use, most of them are They just aren't, I would not switch to Jetbrains from VSCode even if it was free. It's not a question of pricing and Jetbrains themselves started to realise it since they are building some VSC clone (forgot the name right now)

Their new VSC alternative name is fleet and I don't think they confirmed it will be free like VSCode though.

Re: I’m switching from VS Code to VS Codium

#94

Post by miracloblo »

bornfreddy wrote: post #67
mangamadaiyan wrote: post #24

Earlier quoted context omitted.

Absolutely. On a tangential note, "Your problem with vim is that you don't grok vi" continues to be a favourite read: https://gist.github.com/nifl/1178878

Thank you, I might give vi another go. Btw, for reading, raw version is better: https://gist.githubusercontent.com/nifl/1178878/raw/2a20bba8...

No post body was provided.

Re: I’m switching from VS Code to VS Codium

#95

Post by Hamcha »

cdrini wrote: post #64
blip54321 wrote: post #33

Earlier quoted context omitted.

I think most of us value our freedom more. Most people don't think of it in terms of freedom, but freedom it is. With proprietary software: - You don't know when it will disappear or be discontinued. Even your paid-for existing version stops working when the activation servers go down. - You might be forced into an "upgrade" which breaks something you rely on - That's not to mention issues like being able to fix bugs…

Most of your points also apply to open source software, and aren't strict requirements for proprietary software. - discontinued: Atom just got discontinued. It's open source. Photoshop on the other hand has withstood the test of time. - Audacity's 3.0 update removed a feature I relied on. I wasn't forced to update to it, sure, but proprietary software doesn't force updates either. - Being able to fix your own bugs is…

I'll my personal experience as someone who still prefers many proprietary softwares over open source (assuming the price is fair and the features are much much better):

- Photoshop is a market leader so definitely an exception. I personally miss apps like "Made with Mischief" which had unique features that I loved that are still not yet replicated but have completely disappeared and the only way to use them is to find shady places giving out cracked versions (even when I have a license).

- If there's enough demand for a feature, you can fork and bring it back. Waterfox is a popular example of push-back to some of Mozilla decisions (like killing XUL) and is still maintained and loved.

- I love thinkering with formats, but unless you rely on the reverse engineering community at large picking your favorite format apart, you're not gonna get far without a lot of background. I use Affinity Photo/Designer, two popular alternatives to Photoshop/Illustrator, which use their afphoto/afdesign formats and there's no published spec about them. If I ever wanted to do a tool that deals with them I'd have no starting point.

Re: I’m switching from VS Code to VS Codium

#96

Post by prmoustache »

jmyeet wrote: post #20

What I find truly bizarre is how many software engineers, who are aware of how much they earn and how long it really takes to make software, are so resistant to paying anything for tools that make their job easier and faster. It blows my mind. Take the Jetbrains IDEs. I don't mean to offend any VSC fans out there but the Jetbrains IDEs are simply better and more mature in every single way. For individual use, most of…

> What I find truly bizarre is how many software engineers, [...] are so resistant to paying anything for tools that make their job easier and faster. It blows my mind.

What I find truly bizarre is why you bring this up in this discussion. The mentionned link is about a developper who switch from one proprietary to an open source software, both being free as in free beer.

The rest of your post is about being a fanboy of Jetbrains. Sure you may like it and are free to do so but I don't see what is difficult to understand that other people may have different preferences.

> The amount of time I saw people spend on tuning, fixing, tinkering, debugging and otherwise modifying their .vim or .emacs files

Are you making things up?

I only tinker with my neovim init file whem I want to add a plugin, which is adding one vim-plug line and command and don't take much more time than adding a plugin for another IDE.

Most people have their preferred settings that they migrate from one machine to another. I used an example vim init file from someone else and only did a handful of changes that took me probably less than 10-15 minutes over as many years.

Re: I’m switching from VS Code to VS Codium

#97

Post by cmrdporcupine »

jmyeet wrote: post #20

What I find truly bizarre is how many software engineers, who are aware of how much they earn and how long it really takes to make software, are so resistant to paying anything for tools that make their job easier and faster. It blows my mind. Take the Jetbrains IDEs. I don't mean to offend any VSC fans out there but the Jetbrains IDEs are simply better and more mature in every single way. For individual use, most of…

I love the Jetbrains IDEs and have used them for years and they'll pry CLion from my cold dead hands. I pay for a license for it. I've tried VSCode many times and always come back to CLion.

However.

JetBrains needs to consider rebuilding on something other than Java/Swing. The UI is relatively laggy. It fights with many window managers on Linux. It feels clunky compared to VS Code, from a UI POV.

Re: I’m switching from VS Code to VS Codium

#98

Post by jollofricepeas »

jmyeet wrote: post #20

What I find truly bizarre is how many software engineers, who are aware of how much they earn and how long it really takes to make software, are so resistant to paying anything for tools that make their job easier and faster. It blows my mind. Take the Jetbrains IDEs. I don't mean to offend any VSC fans out there but the Jetbrains IDEs are simply better and more mature in every single way. For individual use, most of…

You’re 100% right.

Developers are no different than other humans. Lazy, indifferent, unappreciative, self-absorbed…

Sublime Text is a perfect example.

It’s a travesty with as popular as that editor was that developers would literally use it for work and for personal projects but refuse to pay for what everyone agreed at the time was the best tool for those not using IDE’s.

It pissed me off to the point that anytime I paired with someone and the SublimeText popup showed, I’d ask them to pay the $40 or whatever was being asked.

Re: I’m switching from VS Code to VS Codium

#99

Post by Beltalowda »

azemetre wrote: post #78
cageface wrote: post #7

If you're really that concerned about using propriety software why not help build the emacs or vim ecosystem instead?

As someone who has been using vim for 5 years and neovim for 2 years, what sort of learning material (books, videos) would you recommend to learn about vim internals and subsequently neovim internals? I would love to contribute but I'm mostly a webdev, but I'd love to take a year or so to learn and hopefully contribute throughout the rest of my life. It's just so hard to start or learn. The material doesn't even have…

Depends what you want to do.

The editor itself is in C; I don't think there's any "learning materials" available for the (Neo)Vim internals specifically, so you just gotta learn C. Overall, it's not that hard IMO: I'm not a very experienced C programmer, and I managed to get some patches into Vim. Neovim also uses Lua in various parts for its internals, but I'm not very familiar with Neovim.

If you want to work on things like language support (syntax files, some completions) then most of that is in VimScript; "Learn VimScript the hard way" is a good place to get started.

Re: I’m switching from VS Code to VS Codium

#100

Post by krab »

refulgentis wrote: post #52
blip54321 wrote: post #33

Earlier quoted context omitted.

I think most of us value our freedom more. Most people don't think of it in terms of freedom, but freedom it is. With proprietary software: - You don't know when it will disappear or be discontinued. Even your paid-for existing version stops working when the activation servers go down. - You might be forced into an "upgrade" which breaks something you rely on - That's not to mention issues like being able to fix bugs…

Devs don't pay for tooling because it might be discontinued or have a paid upgrade? That seems short-sighted and perhaps an argument in search of a proponent.

The parent post argues that if you invest in learning or tweaking open source tools, they're useful to you over a longer period of time than the commercial counterparts in general. I don't read it as absolute. Just an explanation of their preference.
Post reply on HN