The number of large software systems in the world is growing steadily. Old first generation solutions are improved and made more sophisticated. Completely new areas open up for automation. More systems, more line of code. More complexity everywhere. And, inevitably, more questions about their behaviour. And, of course, more errors, from bugs in the systems themselves to malfunctioning of external dependencies and systems.
Microsoft is continuously improving its record with the open source community. First dumping massive chunks of .NET into github, then actually making very dedicated effort to clean it up and make it portable to Linux and Mac. Now comes another step, albeit smaller, in the same direction. Visual Studio 2017 will support CMake projects in a native way, without the need to generate .proj and .sln files first. This is great news, because it saves some effort for those working on cross-platform C++ products.
Again I find myself thinking about how to write as little code as possible when developing applications for various mobile platform. I do find it annoying in the extreme, that iOS, Android and Windows Phone all have mutually incompatible technologies. As if they were doing it on purpose. But maybe they just do? It helps the companies to lock in software developers as well as end users, doesn't it? Maybe they hope, that the developers won't bother to write code for all the platforms and will just stick with one.
After using Fedora Core 9 for some time I feel that I have the right to wine a little bit.
Firefox Release Candidate 1 is available for download and I decided to give it a go. My first impressions are quite positive - performance is must better on the same machine, the design has been improved and they have added quite a few usability features.
Microsoft is developing a command line environment, which they call PowerShell. I read some negative feedback, but it looks rather interesting and powerful. The main difference from traditional Unix approach is that the commands do not communicate via standard input/output channels, but rather export and consume objects with properties. These properties can be queried and eventually actioned upon.
The tool would automatically visit every link on every page and would try to click every button and so on. The tool should be configurable via some sort of script language. In the end the human user would be presented with a report.
My site exports Google Sitemap, using a module for Drupal. I find it quite amazing, that every time I add content, Google actually go and download the sitemap and then the new content! I guess it is still not very popular, so they can afford to devote quite a lot of resources for individual updates of sites with low rank.