It’s again been a while since my last article, but today I had big news. I had previously teased the project, but I hadn’t announced it officially.

As announced previously, I am working on a Software Store at https://store.janishutz.com.

TL;DR;

I will be adding privacy preserving product analytics (P3A) to my websites over the coming months. These analytics will not allow me to uniquely identify you. You can see my revised privacy policy here and my old one here.

I haven’t written any blog posts in over a month. This is because I have taken some time off from coding to focus on my finals exams and to prepare for my studies, which, if everything goes according to plan, should start this September.

A couple of weeks ago, Apple announced that they are going to open up iOS. As somebody who develops apps for iOS this proposition seemed really nice at first glance, but when you dive into what they actually did, things are significantly worse than what they already were.

VSCode and its requirements to have an official build by Microsoft to use certain extensions

Recently, whilst starting to learn to do ML stuff, I noticed that I didn’t get any code suggestions for Python in VSCodium, which is a tracker-less build of VSCode. As Visual Studio Code is open source, it should therefore be possible to build your own version of the software and being able to use it however you like to. At least this is what the MIT license would imply, under which VSCode is licensed. But as Micro$oft is Micro$oft, they had to have their strings attached and make all FOSS builds of VSCode basically worthless as they are excluded from the extensions store by default. Yes, there are workarounds which do work, but some Extensions made my Micro$oft have checks in them that prevent it from running in unofficial builds.