This week we have yet another interesting new user interface feature to talk about. The old “What’s This?” feature has been re-worked as a shiny and …This week in KDE: Expandable tooltips and more
Because I’m struggling to come up with some longer blog posts, I thought I’d make a list of my current tools that I rely on, on Windows. Many of them are, however, cross-platform, because I tend to be a digital nomad, and having familiar tools is essential in this line of work.
I think I would love to be completely immersed in a computer ecosystem of one make or another. Systems where I can have parental controls, and email, and service sync, and MDM, and authentication, etc. I am just tired of having to cobble together disparate services and hope the integration works well.
In the case of Office Suites that also offer robust email services and generous storage, it’s really hard to beat Microsoft 365. There are lots more reasons to use it and love it, but man, sometimes it can be just a confusing mess.
Weird timeline we’re in, eh? While we all sit and hope for the best with COVID-19 taking an unprepared humanity to task, Microsoft (through GitHub) is making an interesting move.
Ultimately it seems like just another piece of the Open Source pie being consumed by corporations. While NPM is a handy tool for development in Node, I’m sure this change of ownership will prompt an exodus, as the GitHub acquisition did before it.
When it does, we’ll all be the better for it. More diverse sources allow for less single points of failure or control. I wouldn’t be surprised if the popular distributed git-forge idea spawns into a distributed NPM-analog.
Update: It was pointed out to me that there is, in fact, an alternate package repo tool/project tool: Yarn. I’m not a Node developer, but I am extremely happy that it exists and can be a stand-in for NPM.