Changelog

Sometimes you wanna release some code, but you also don't want people getting the impression that it's any good. The GLWTPL was made for those times. The one and only term/condition: You just DO WHATEVER YOU WANT TO as long as you NEVER LEAVE A TRACE TO TRACK THE AUTHOR of the original product to blame for or held responsible.

This repository contains a step-by-step guide that teaches how to create a simple operating system (OS) kernel from scratch. I call this OS Raspberry Pi OS or just RPi OS. The RPi OS source code is largely based on Linux kernel, but the OS has very limited functionality and supports only Raspberry PI 3. 6 lessons available with 5 more on the roadmap.

Big week! KBall, Nick, and JBall (nooch) dive deep in to the 2018 Node.js user survey results. What does it all mean?! They also review Ryan Dahl's "10" regrets about Node and sound off on Microsoft's assimilatio... err... acquisition of GitHub.

One of my favorite jobs in software was when I was a Product Manager for a non-profit startup. In that role I was able to impact and touch pretty much any part of the business I wanted to, it was almost like being an entrepreneur, but doing so from within an already formed company. I also led our agile software development as Scrum Master — it was awesome. I wish I had this list of advice back then. Mike Cohn writes on the Mountain Goat Software blog: Never commit the team to anything without consulting them first — As Scrum Master, you do not have the authority to accept change requests (no matter how small) on behalf of the team. Even if you are absolutely positive that the team can fulfill a request. Always say, “I need to run this by the team before we can say yes.” And certainly don’t commit the team to deadlines, deliverables, or anything else without first talking to team members. You may not need to talk to the whole team--plenty of teams will allow some or all members to say, “Yeah, we can do that” without a whole-team meeting. But it’s still their decision, not yours. This is number 1 on the list, because you should never get this one wrong.

In this post from Casper Beyer titled The Node.js Ecosystem Is Chaotic and Insecure, he cites examples like left-pad, is-odd, is-number — and goes on to say the way to be responsible with dependencies is... ...don’t trust package managers, every dependency is written by some random developer somewhere in the world and is a potential attack vector. ... Is this being too paranoid? Perhaps, or maybe it’s the healthy amount considering the massive reach these trivial packages can have. While this focuses on Node.js, the lessons learned apply anywhere you have dependencies in your code.

Today, we are open-sourcing the code behind Changelog's infrastructure as is, and are giving you the opportunity to influence the way we continue investing our time.

WWDC 2018 is wrapping up. Use this script to grab all of the sample code in one fell swoop. Johannes Fahrenkrug has been maintaining this as a Ruby gem since 2011, but he says he's working on a Swift port. 😁 (A nice companion to this would be a script to download all of the videos. But I'm not sure how feasible that is.)

Our friends at Tidelift have joined data from GitHub and their own Libraries.io, "the largest open source software dataset in the world," — which covers over 2.8 million open source projects. They were able to combine the two datasets to gather the entire commit history of each project on GitHub to more closely examine the following questions: What exactly has been Microsoft’s role in the open source community? In which projects and ecosystems have they contributed most? Have those contributions been focused on the large Microsoft open source initiatives, or has the company also participated in projects beyond their immediate purview? They were also careful to clean the dataset of forks and duplicate packages which would misinform this analysis. So what’s the verdict? Microsoft may have a mixed history with open source, but today the company is demonstrating some impressive traction when it comes to open source community contributions. If we are to judge the company on its recent actions, the data shows what Satya Nadella said in his announcement about Microsoft being “all in on open source” is more than just words.

Does the fact that sessionStorage/localStorage is shared across tabs have you down? Don't worry, here's a strange but widely supported way to store 640kb of object data in a page's navigation state. Just wow. This little hack could go down in his·to·ry. (Also that's how its name is pronounced.)

MagiCLI was built to expand the use of npm modules. When all modules can be executed via CLI, npm becomes a source for anyone who wants to find a solution ti be run from a terminal and also for those who would like to call an existing solution written in Node.js from a program written in another language. For even more context, check out the intro post on Hacker Noon.

No other details were shared in this tweet, but this image from the stage of WWDC says all it needs to. In a post-Microsoft + GitHub world — it has been a crazy 24 hours for GitLab. More than 2,000 people tweeted about #movingtogitlab. We imported over 100,000 repositories, and we've seen a 7x increase in orders. We went live on Bloomberg TV. And on top of that, Apple announced an Xcode integration with GitLab. Here's an interesting exchange between Emily Chang and Sid Sijbrandij on Bloomberg Technology: Emily: I spoke with Satya Nadella earlier today, and he said "he promises to put developers first." Do you not believe him, or do you think it's not possible for a company with so many objectives to really put developers first? Sid: I believe him. Microsoft has shown that it is the new Microsoft, and they've done great. The new CEO, Nat Friedman, shows he really understands developers. So I believe him when he says they are going to be good maintainers of GitHub. Emily: So, then what's so bad about GitHub? Sid: There's nothing bad about GitHub. Emily: What’s so much better about GitLab? Sid: It's a fundamentally different product. It's open core, so a lot of it is open source. You can host it yourself. But second and I think most importantly, it's not just code hosting. With GitHub you host your code. GitLab is the entire DevOps lifecycle. So all the way from planning something to rolling it out, container registries, monitoring — all in a single product. That allows you to get the whole organization on the same page. And that's why people are flocking to it. They go on to talk about being a sustainable business, financials, etc.

Node is a massive success, but that doesn't mean Ryan doesn't regret decisions he (and others) made along the way. This talk is super candid and refreshing. During the last 10 minutes or so, he reveals he's been working on a follow-up project (Deno, which I logged last week) that aims to wipe those regrets away.

Quincy Larson: Dozens of contributors worked on the new curriculum for more than a year. It features 6 new developer certifications - all of which are 100% free. This looks top notch. Great work to all involved!🥇

André Staltz: I’ve just given my third programming talk where I use only my IDE (integrated development environment) for live coding and no other presentation tool. I noticed the audiences were very pleased with these talks, and I think it’s correlated to using an IDE and not a slides program. If you've ever watched one of André's talks, you know he gives good talks regardless of whether or not he's using an IDE. But he makes a good case for their use in general and goes in to great detail* on how to do it well. *even explaining each individual editor setting and why they were selected

Zed Shaw – creator of Mongrel, Learn Python the Hard Way, and more – joined the show to talk through a recent Twitter thread from Zed where he shared his thoughts on open source, making money in open source, corporate interests and involvement, developer culture, and more.

If you haven't yet, you should watch this. It's 8 minutes long and packed with insights from Sataya himself on why Microsoft bought GitHub. We are all in on open source and that's what really brings us together with GitHub — and we're going to operate as an open platform for any language, any framework, whether it's the cloud or on the client. Nat Friedman, who's going to be the CEO of GitHub post close, came to Microsoft from Xamarin — he's someone who's a veteran of open source and he's going to lead the company. We're going to operate GitHub as an open platform, and most developers are going to judge us by our recent actions and our actions going forward — and we will have to earn the trust everyday. We're very committed to it. At the core, Microsoft is a developer tools company. This is something that comes very natural to us. Earning the trust of our customers by our actions everyday is what we live by. The most important thing is that it's not just about Azure. We welcome every cloud provider to integrate with GitHub in order to be able to reach the GitHub community — and give GitHub members a choice of any cloud, as well as any client, mobile platform, or IoT platform.

Sara Vieira is easily one of the most entertaining people we've ever had on this show. She has been working with React over the past few years and has recently been traveling around Europe and giving free workshops on React in London and at React Finland.

Congrats to Discourse on becoming significant enough to inspire clones/alternatives. Also, Nim looks like an interesting language that's picking up steam.

Tusk is an unofficial, featureful, open source, community-driven, free Evernote app used by people in more than 130 countries.

A reimplementation of TensorFlow for Ruby. This is a ground up implementation with no dependency on TensorFlow. Effort has been made to make the programming style as near to TensorFlow as possible, comes with a pure Ruby evaluator by default with support for an opencl evaluator for large models and datasets.