Programming: Node.js, Micro:bit, L4Re, Python, Go and More

• 14 Best NodeJS Frameworks for Developers in 2019

  Node.js is used to build fast, highly scalable network applications based on an event-driven non-blocking input/output model, single-threaded asynchronous programming. A web application framework is a combination of libraries, helpers, and tools that provide a way to effortlessly build and run web applications. A web framework lays out a foundation for building a web site/app. The most important aspects of a web framework are – its architecture and features (such as support for customization, flexibility, extensibility, security, compatibility with other libraries, etc..).

• Debian now got everything you need to program Micro:bit

  I am amazed and very pleased to discover that since a few days ago, everything you need to program the BBC micro:bit is available from the Debian archive. All this is thanks to the hard work of Nick Morrott and the Debian python packaging team. The micro:bit project recommend the mu-editor to program the microcomputer, as this editor will take care of all the machinery required to injekt/flash micropython alongside the program into the micro:bit, as long as the pieces are available. There are three main pieces involved. The first to enter Debian was python-uflash, which was accepted into the archive 2019-01-12. The next one was mu-editor, which showed up 2019-01-13. The final and hardest part to to into the archive was firmware-microbit-micropython, which needed to get its build system and dependencies into Debian before it was accepted 2019-01-20. The last one is already in Debian Unstable and should enter Debian Testing / Buster in three days. This all allow any user of the micro:bit to get going by simply running 'apt install mu-editor' when using Testing or Unstable, and once Buster is released as stable, all the users of Debian stable will be catered for.

• Some Ideas for 2019

  Well, after my last article moaning about having wishes and goals while ignoring the preconditions for, and contributing factors in, the realisation of such wishes and goals, I thought I might as well be constructive and post some ideas I could imagine working on this year. It would be a bonus to get paid to work on such things, but I don’t hold out too much hope in that regard. In a way, this is to make up for not writing an article summarising what I managed to look at in 2018. But then again, it can be a bit wearing to have to read through people’s catalogues of work even if I do try and make my own more approachable and not just list tons of work items, which is what one tends to see on a monthly basis in other channels. In any case, 2018 saw a fair amount of personal focus on the L4Re ecosystem, as one can tell from looking at my article history. Having dabbled with L4Re and Fiasco.OC a bit in 2017 with the MIPS Creator CI20, I finally confronted certain aspects of the software and got it working on various devices, which had been something of an ambition for at least a couple of years. I also got back into looking at PIC32 hardware and software experiments, tidying up and building on earlier work, and I keep nudging along my Python-like language and toolchain, Lichen. Anyway, here are a few ideas I have been having for supporting a general strategy of building flexible, sustainable and secure computing environments that respect the end-user. Such respect not being limited to software freedom, but also extending to things like privacy, affordability and longevity that are often disregarded in the narrow focus on only one set of end-user rights.

• 5 Best Python IDEs You Can Get in 2019

  If you’re taking Python lessons online, you will eventually need a good IDE (Integrated Development Environment) to write better code. The command line interface can only prove so useful. At Python.com you can download a native IDE called IDLE (Integrated Development and Learning Environment). However, it is rather basic in scope, and debugging can consume more time than necessary. With this in mind, here are a few of the best IDEs for Python which add to your productivity.

• Python’s Requests Library (Guide)

• Factorial one-liner using reduce and mul for Python 2 and 3

• Sample Chapters from Creating wxPython Applications Book

• Migrating from Pelican 3 to Pelican 4

• Python Software Foundation Fellow Members for Q4 2018 [Ed: Python Software Foundation has many Microsoft employees in it now. Not good. Microsoft has been using money to filtrate just about everything, including its competition. This isn't so new a strategy and many examples of it exist.]

• PyCoder’s Weekly: Issue #352 (Jan. 22, 2019)

• Why Don't People Use Formal Methods?

  Before we begin, we need to lay down some terms. There really isn’t a formal methods community so much as a few tiny bands foraging in the Steppe.1 This means different groups use terms in different ways. Very broadly, there are two domains in FM: formal specification is the study of how we write precise, unambiguous specifications, and formal verification is the study of how we prove things are correct. But “things” includes both code and abstract systems. Not only do we use separate means of specifying both things, we often use different means to verify them, too. To make things even more confusing, if somebody says they do formal specification, they usually mean they both specify and verify systems, and if somebody says they do formal verification, they usually mean mean they both specify and verify code.

  Before we begin, we need to lay down some terms. There really isn’t a formal methods community so much as a few tiny bands foraging in the Steppe.1 This means different groups use terms in different ways. Very broadly, there are two domains in FM: formal specification is the study of how we write precise, unambiguous specifications, and formal verification is the study of how we prove things are correct. But “things” includes both code and abstract systems. Not only do we use separate means of specifying both things, we often use different means to verify them, too. To make things even more confusing, if somebody says they do formal specification, they usually mean they both specify and verify systems, and if somebody says they do formal verification, they usually mean mean they both specify and verify code. For clarity purposes, I will divide verification into code verification (CV) and design verification (DV), and similarly divide specification into CS and DS. These are not terms used in the wider FM world. We’ll start by talking about CS and CV, then move on to DS and DV.

• Learning C as an uneducated hobbyist

  V=Programming, however, is conscious. It’s an activity in which you have to think in order to act. Unlearning bad practice in programming takes no energy at all apart from that spent being told that the practice is bad and coming to understand and remember it. Once you’ve done that, it’s almost impossible to make the same mistake again.

  That’s why you shouldn’t be afraid of learning “along the way”, “as you go” or “in an ad-hoc manner” because “you might learn bad practice”. If you learn the wrong thing, you can learn the right thing later. After all, you’re not a professional programmer. It doesn’t matter very much if you make a mistake; your job doesn’t depend on it.

• Demystifying Pointers in Go

  If you’ve never worked with a language that exposes pointers, it could be a little confusing. But the good news is pointers don’t need to be scary. In fact, pointers can be pretty straightforward. Here are the basics of pointers in Go:

GNOME 3.32 Desktop Environment to Launch with a "Radical New Icon Style"

Besides the slightly revamped default theme, it looks like the GNOME 3.32 desktop environment will come with a "radical new icon style," along with new guidelines for app developers to provide a more unified icon style across the GNOME ecosystem. GNOME designer Jakub Steiner writes in his latest blog article about the improvements needed for the revamped icon style to be included by default with the GNOME 3.32 release of the open-source desktop environment used by numerous Linux-based operating systems, including Ubuntu. Also: GNOME Is Making Great Progress On Overhauling Their App Icons

Dell XPS 13 9380 Developer Edition Now Available, Shipping With Ubuntu 18.04 LTS

Dell is now shipping their new XPS 13 8th gen (9380) laptop in a developer edition that comes preloaded with Ubuntu 18.04 LTS. The Dell XPS 9380 is only an incremental upgrade over the previous-generation 9370: it has the slightly newer Intel Whiskey Lake processors, moves the web camera position to the top of the display rather than at the bottom, and other minor refinements but nothing too dramatic. From the Developer Edition side, they have moved from Ubuntu 16.04 LTS to 18.04 LTS. Also: The new Dell XPS 13 developer edition now available in the US, Europe and Canada New Dell XPS 13 Laptop with Ubuntu Is Now Available in the US, Europe and Canada