4 new blog posts in April. Seems I'm getting better at sharing my long(er) form thoughts :)
The workflow I now have makes it really easy too. When I have a thread here that I think deserves a blog post, I copy the link to the first toot and paste it in https://mtr.wildeboer.net where I can get a #markdown dump that I can copy/paste in my editor and work on. My blog is #jekyll based and also uses Markdown, so it is easy to do :)
Trying out #VSCodium it's a fork of VSCode's source code, it's #FLOSS and comes without data collection and other proprietary code from Microsoft. It's avaible for Windows, Linux and MacOS :3
So far it's pretty great, it gives you a guide on how to transfer your #VSCode settings, extensions and Co. and also let's u use VSCode's Extension Marketplace if you prefer it over the #opensource one. Only thing which I miss is a way to sync 🥲, but thats fine.
I've been thinking about myself as a coder a lot. I learnt #Python through its #Anaconda variety and #SpyderIDE. The course I initially went on used those, so I use them to write #SpatialAnalysis scripts.
However, I wonder whether I should learn what #JupyterNotebooks are about and potentially another IDE like #PyCharm or #VSCode / #VSCodium, but also actual software architecture and development things. Not to mention things like #Rstats, #RustLang, or #GoLang that interest me.
Using Markdown to create slides? Why not? With presenter notes and a presenter view with preview of the next slide? Sure! https://marp.app has you covered.
I think, for me, much like EDLIN, it's pretty much always been a matter of knowing that it was the default editor available in every incarnation of #UNIX and #Linux since, ... I dunno, ... 4.2BSD or so?
Perhaps I should say vi, and in DOS I don't really recall when EDIT.COM supplanted #EDLIN, but do feel free to checkout my friend's more modern #FREDLIN in the link above. h/t to @dheadshot for creating a POSIX interpretation of that classic utility from the days when disk drives talked to you and diskettes shimmied...
Also, These #Vim memes are some of the funnest elbows to the ribs of the person sitting next to you we can all enjoy together... unless, unless, Oh my gawd am I on Drugs?
Here's another one for folks to add to their collections, for foshizzles and giggles, of course, and we all can haz #Cheezburgerz! 🍔
Kindest regards, and thank you for some of the very best cookbook style #tuts, #HowTo's, and introspectives for the UNIX / Linux / FOSS world on the Internet :)
@weirdwriter@pixelate@halisonjl@weirdwriter, that article is a fantastic resource! Please do continue to keep it up to date with your discoveries. If I had found it earlier it could have saved me work discovering things on my own - then again, I do like figuring things out so I might have done the same anyway, just with a better start point.
When I was considering my options for tools to (re)learn to use after my vision loss my primary focus was on regaining my ability to write code instead of documents as that was more central to the type of work I did at the time. While I found learning to use #VSCode effectively with a screen reader to be a very frustrating and time-consuming process, it made sense at the time, and proved well worth it to me in the long run. After (re)learning to use it to code, discovering I could use it for #markdown as well was a very nice bonus. It is very web app like and can be very difficult to use with a screen reader without learning a library worth of hotkeys/key-binding/keyboard-shortcuts. If I had not already needed to learn them for coding, I don't know that I would have tried for writing documents alone. I have been consider switching to #vscodium. Less telemetry definitely appeals to me.
Thanks again for referencing that article! I'll definitely be giving it a follow.
If you are willing to hack for a better developer ecosystem, please try #vscodium. On #Linux, there are builds for flatpaks/snaps (or from source). On #FreeBSD, there's a version of #VSCode in ports that is pre-patched and relatively easy to work with. Some #Microsoft extensions, like remote dev environments and #Jupyter Notebooks, do not work (or only partially work) and require independent extensions. Consider contributing to these projects and use them, if you can.
For the rest of us, @itsfoss has a great break down and more detailed look, at the differences between VS-Code and VS-Codium.
In basic, both are free and open source. However, Microsoft owns VS-Code, which has telemetry elements enabled by default and contains some non-open bits.
Open tech, be afraid. Be very afraid. Microsoft owns both Visual Studio Code “VSCode” and MS-GitHub, two intertwined and utterly proprietary product-service ecosystems with a bit of open-source in their core to lure us in. Because they love open source? Yeah, no.
Soon after leaving GitPod whose technology links the two, Geoffrey Hunt last year explained their strategy and what it’s doing to our open tech world, in a great and “harrowing” article, “Visual Studio Code is designed to fracture” https://ghuntley.com/fracture/
“The future of software development tooling that is being built is closed as ****, and people seem to be okay with it…”
This is why MS-GitHub is not our friend.
This is why falling for their trick, disguising MS-VSCode as a neat “free” editor, will come back and haunt and hurt us.
Vendor lock-in double-whammy. Using open source as “a financial weapon”.
“… the biggest challenge for Gitpod, GitLab, Datacoves, OpenBB, Foam, et al lies ahead - developing open language tooling for each community where Microsoft has forked the communities over to proprietary language servers…”
If we have a grain of public spirit, if we are motivated at all by the Freedom that’s supposed to be afforded by Free-Libre Open-Source Software, we must #GiveUpGithub, we must recognise the trap, we must choose truly open #FreedomTech.
This post on #vscode#github and #microsoft is pretty harrowing. I have adopted VSCode after bouncing around a number of others editors / IDEs. I see how this is going to haunt me in the future. Boo. Yet another thing to have to worry about in my tech world.
Well, s***, not even #VSCodium is free of telemetry? Wonderful. What do I use now?
#Emacs requires a user script just to enable #Rust Analyzer. You've got to be kidding me.
#Vim was designed for the limitations of a terminal from 1976. Its key bindings and behavior make zero sense on a modern keyboard, mouse, and graphical display. No, thank you.
Everything else seems to want to emulate Vim, including all that's wrong with it.
Trying again #KDE#Wayland session.
Noticed that when using #VSCodium Wayland launcher the icon for VSCodium window is some generic Wayland icon instead of correct one.
Any ideas what's wrong? #archlinux