$ bash ./perl.com --version
This is perl 5, version 36, subversion 0 (v5.36.0) built for x86_64-cosmo
(with 3 registered patches, see perl -V for more detail)
One reason to prefer gojq is that gojq’s author is one of the most knowledgeable person for the original jq (as seen by GitHub PRs and issues), and his gojq fixes many long standing issues in jq.
Plus, for my use cases, gojq runtime performance beats jq by a fair margin.
Curious whether the team is looking at improving the support of having images in tables cell? I played with the playground and it seems to work, but there seems to be some (relatively minor) glitches/bugs (e.g. difficult to place an image in a cell, moving images across cells seems difficult, and cannot Ctrl-x an image and Ctrl-v to paste it).
We definitely have plans to improve Tables drastically over time, but I'm not sure when we'll get to those particular issues. If you care to make an Issue for this on GitHub, that would be much appreciated :)
I love Sublime Text and will be upgrading when ST4 comes out.
VSCode has one distinct advantage though: it’s remote SSH editing plugin (which has a proprietary license and closed source). IMO, the remote SSH and related extensions is bar none the distinguishing feature of VSCode in that it is so good and there is simply no competition. Every other feature has at least a worthy/better implementation elsewhere (ST, vim, or emacs).
Is there something similar for Sublime, either builtin or native? I’d delighted to be corrected.
What's so good about VSCode's SSH editing plugin over emacs' tramp-mode?
Does it runs shells and LSPs remotely for you?
Emacs can run eshell remotely, but LSP support is still lacking AFAIK. (I'd love to be corrected. xkcd.com/386)
Can you hop through different connections?
In emacs you can open a file in a private machine that's only reachable through another one by just opening,
The remote plugin effectively lets you work on a remote machine (or OCI container) with your local VSCode instance, as a matter of fact it's the setup I'm using right this moment. This includes remote language servers, remote shells and even remote-specific configurations.
I'm a diehard vim user. I used to do everything in vim. Even my undergrad thesis was proudly written with vim.
This is the feature that single-handedly made me switch to vscode.
> > 3. We need a desktop environment that's visually appealing and has a good UX.
> Such as KDE and the rest?
Just personal taste, but I don't find KDE visually appealing, and not only the default theme ("Breeze"). Unfortunately, I can't get used to the usability issues on GNOME.
IMO, the sweet spot of visually appealing and good UX is .... Windows 10 (sigh), followed by a close second in Cinnamon (and I'm also a fan of IceWM).
Good analysis but small nitpick: the use of "Θ" in Θ(a×exp(R×𝑡)) is slightly inaccurate (or is it the use of "a"?) because the set of functions Θ(a×exp(R×𝑡)) is the same for all positive a.
For what it's worth, I own a Unicomp keyboard I got in 2013 and it still works flawlessly to this day. Not doubting nor disqualifying your experience, but just want to provide a counterbalance.
Failing USB electronics seems symptomatic of corner cutting at the level of pennies per unit. Sure anyone can get a bad batch of chips. It’s what gets done about it that speaks to quality.
This wasn’t rough use by me. It was barely used. It was a manufacturing defect and there is no way that Unicomp could not know after the keyboard was in their shop and unlikely they didn’t know before. You just can’t be in the keyboard business that long and not know what is going on.
They probably made good keyboards for a long time and might again. Mine was poorly made in terms of reliability and I don’t have confidence that they repaired it with more reliable components.
I read about this fact elsewhere also. Could you expand on this a bit? My impression was that VSCode and its associated extensions are open source, so I'm curious how Microsoft could make certain parts exclusive to its own build of VSCode.
Because VSCode is under a permissive license (MIT) rather than a copyleft license (GPL), Microsoft can add any proprietary extensions it wants. "Permissive" licenses are only permissive for the creator and other developers (only sometimes), not for the end user.
In order to contribute you have to sign away your rights, so it's only permissive to MS. It's a pervasive view on open source, cheered by sockpuppets, making people believe MS is now a open source company.
The situation is similar to Google Chrome/Chromium: Most of it is open-source, but the release binaries contain some proprietary bits for telemetry, marketplace access, etc.
