The Internet is the most important tool in our everyday lives. It’s how we consume media, conversate with friends and family, interact with colleagues, learn new skills, and handle our finances. However, the internet that we know and love has flaws. The biggest of those flaws is that the information on it is mostly centralized. This means that the information we access every day is held on servers that are under the control of a central company.
Flutter, Google’s UI toolkit for building mobile Android and iOS applications, hit its version 1.0 release today. In addition, Google also today announced a set of new third-party integrations with the likes of Square and others, as well as a couple of new features that make it easier to integrate Flutter with existing applications.
Sources claim that Microsoft is abandoning EdgeHTML and building a Blink/Chromium based browser. This might be a good business decision for Microsoft but it is a disastrous advancement for the Web. In this short post, I will make a case for why we’re loosing the Web and how in a Blink, all we love about our Web will be owned and controlled by a single entity.
Swift and Kotlin have taken the developer community by storm, helping to increase the number of developers for both platforms. Both languages rapidly gained adoption due to their easy syntax, simple way of writing and the modern techniques and features they bring to the table.
At its core, Flutter is a standalone, binary executable; making it a game-changer not only on mobile, but on desktop as well.
Writing once and deploying natively on Android, iOS, Windows, Mac and Linux and additionally sharing all the business logic to the web (using AngularDart) is a big deal.
Let’s explore this idea!
The first area to take a look at is Haiku’s latest feature in its Beta release: packaging.
Packages (but not just packages!)
As I mentioned in the Haiku Beta review, it was the first official release to feature package management. Best I can give anyone new to Haiku a mental picture of it is this: think of PackageFS of being like (but not the same as) having the old Slax 6 modules system running, along with all the usual ‘package’ tools to go with it.
A recap of it can be summarized in five quick points (versatile command-line packaging tools (as you might expect), the HaikuDepot and software updater, package and/or system states, the PackageFS, (where all packages are mounted seamlessly and mesh at startup), and as a side effect of the FS, a gentle layer of safety to the system.)
The UNIX® system is an old operating system, possibly older than many of the readers of this post. However, despite its age, it still has not been open sourced completely. In this post, I will try to detail which parts of which UNIX systems have not yet been open sourced. I will focus on the legal situation in Germany in particular, taking it representative of European law in general – albeit that is a stretch, knowing the diversity of European jurisdictions. Please note that familiarity with basic terms of copyright law is assumed.
https://graphql.orgIn late 2016, we decided to rewrite our aging PHP legacy system using Python and React. With only four months to build an MVP in time for the 2017 festival season, we had to decide very carefully where to invest time.
One of the technologies we invested in was GraphQL. None of us had ever worked with it before, but we judged it to be crucial for delivering quickly and enabling people to work independently.
This turned out to be a great decision, so two years later we wanted to look back and share what we’ve learned since then…
At GopherCon 2017, Russ Cox officially started the thought process on the next big version of Go with his talk The Future of Go (blog post). We have called this future language informally Go 2, even though we understand now that it will arrive in incremental steps rather than with a big bang and a single major release. Still, Go 2 is a useful moniker, if only to have a way to talk about that future language, so let’s keep using it for now.