Weekly developer news – March 16th 2018

So, welcome edition 23rd of developer news. Sorry there wasn’t a post last week if you were looking out for one.

There are a couple of reasons for that, but the main one is, there wasn’t really anything that I felt was worth highlighting. There was the usual kind of background news and recycling of news, comments, and opinion, but nothing that really caught my eye as something worth digging into or highlighting.

But, this week, I do have some items to share.

1 : Updating a 50 terrabyte PostgreSQL DB

First up is a medium article, from a system administrator at Ayden discussing how they dealt with updating a pretty sizeable database by anyone’s standards.

It’s a nice illustration of the thinking that has to happen when things get that big, and it does go into some detail on migration approaches and architecture.

2 : SQLite language choice

This second item, is an article that has been shared a lot both publicly and privately from the SQLite team discussing why it’s written in C. It’s not necessarily new information to many, but it’s good to see a language discussion that doesn’t revolve around purely style of syntax.

3 : Rust’s 2018 Roadmap

Next is a post from the team behind the Rust language, publishing their roadmap for the Rust language development for 2018. It’s not a language that I’m familiar with in terms of day to day usage, but I always like to monitor other language developments. I like to expose myself to different language, system designs, and like to look at differences in approach to my own, either opposing or complementary.

4 : GitHub doesn’t want to monitor your code

Finally for this week, is an article by GitHub regarding a proposed EU law which relates to the automatic monitoring of uploaded content for copyright infringement.

It’s a proposal mainly aimed at people sharing media, music, videos etc, but code would come under the same category, and many people, including GitHub don’t like that.

There lots of discussion around the web, and many different views, with some people seeing it as a positive proposal, others not liking the ‘monitoring’ side of it. GitHub obviously don’t want the overhead and complexity of having to do this. To detect copyright infringement of uploaded code automatically is a massive job, and one which is very likely to give false positives.

So, that’s it for this week.

If you have any articles, announcements, tutorials, or anything else you think should be included next week, then just drop me an email.

Leave a Reply