Each year since 2011, Stack Overflow has asked developers about their favorite technologies, coding habits, and work preferences, as well as how they learn, share, and level up. This year represents the largest group of respondents in our history: 64,000 developers took our annual survey in January.
As the world’s largest and most trusted community of software developers, we run this survey and share these results to improve developers’ lives: We want to empower developers by providing them with rich information about themselves, their industry, and their peers. And we want to use this information to educate employers about who developers are and what they need.
We learn something new every time we run our survey. This year is no exception:
A common misconception about developers is that they’ve all been programming since childhood. In fact, we see a wide range of experience levels. Among professional developers, 11.3% got their first coding jobs within a year of first learning how to program. A further 36.9% learned to program between one and four years before beginning their careers as developers.
Only 13.1% of developers are actively looking for a job. But 75.2% of developers are interested in hearing about new job opportunities.
If you’re a programmer or techie, chances are you’ve at least heard of Docker: a helpful tool for packing, shipping, and running applications within “containers.” It’d be hard not to, with all the attention it’s getting these days — from developers and system admins alike. Even the big dogs like Google, VMware and Amazon are building services to support it.
Regardless of whether or not you have an immediate use-case in mind for Docker, I still think it’s important to understand some of the fundamental concepts around what a “container” is and how it compares to a Virtual Machine (VM). While the Internet is full of excellent usage guides for Docker, I couldn’t find many beginner-friendly conceptual guides, particularly on what a container is made up of. So, hopefully, this post will solve that problem 🙂
Let’s start by understanding what VMs and containers even are.
The Linux xargs command may not be a hugely popular command line tool, but this doesn’t take away the fact that it’s extremely useful, especially when combined with other commands like find and grep. If you are new to xargs, and want to understand its usage, you’ll be glad to know that’s exactly what we’ll be doing here.
Before we proceed, please keep in mind that all the examples presented in this tutorial have been tested on Ubuntu 14.04 LTS. Shell used is Bash, and version is 4.3.11.
NPM Inc.’s NPM Orgs tool, which has been available as a paid service for JavaScript and Node.js development teams collaborating on private code, is now available for free use by teams working on open source code.
The SaaS-based tool, which features capabilities like role-based access control, semantic versioning, and package discovery, now can be used on public code on the NPM registry, NPM Inc. said on Wednesday. Developers can transition between solo projects, public group projects, and commercial projects, and users with private registries can use Orgs to combine code from public and private packages into a single project.
Yesterday I was talking to some friends about Bash and I realized that, even though I’ve been using Bash for more than 10 years now there are still a few basic quirks about it that are not totally obvious to me. So as usual I thought I’d write a blog post.
We’ll cover
some bash basics (“how do you write a for loop”)
quirky things (“always quote your bash variables”)
and bash scripting safety tips (“always use set -u”)
If you write shell scripts and you don’t read anything else in this post, you should know that there is a shell script linter called shellcheck. Use it to make your shell scripts better!
Configuration files in general_config were separated
into feature sets (to be specified with –config
argument ) and nodes configuration (to be specified with
–nodes configuration)
Featureset files should contain only the list of flags
that enable features we want to test in the deployment,
the overcloud nodes configuration, and all that involves
their set up, should be put into nodes configuration
files.
This week in Linux and open source news, The Linux Foundation’s Hyperledger Project to help China get greener, an old Linux vulnerability surfaces, and more! Read on to stay in the OSS know!
1) IBM and Energy-Blockchain Labs announced a blockchain-based trading platform for “green assets” that’s based on Hyperledger.
3) Gates’ Radiant Earth Project hopes to “encourage the creation of more open source technologies and innovation that can help ‘solve societies’ most pressing issues.'”
Arch Linux has never been known as a user-friendly Linux distribution. In fact, the whole premise of Arch requires the end user make a certain amount of effort in understanding how the system works. Arch even goes so far as to use a package manager (aptly named, Pacman) designed specifically for the platform. That means all that apt-get and dnfknowledge you have doesn’t necessarily roll over.
Don’t get me wrong; Arch Linux is a fantastic distribution. However (and that “however” is significant), it’s certainly not a distribution for anyone even moderately new to the world of Linux. Case in point: When you boot up an ISO of Arch Linux, you wind up at a Bash prompt, where you then walk through the numerous steps (as outlined in the Installation guide) to get Arch Linux installed. In the end, you will be rewarded with a fine-tuned Linux distribution that will serve your needs well. On top of that, by the time you’ve installed Arch, you will know more about your operating system than you would have before.
But what about those who want the benefits of Arch Linux, but don’t want to have to go through the unwieldy installation? For that, you turn to a distribution like Manjaro. This take on Arch Linux makes the platform as easy to install as any operating system and equally as user-friendly to work with. Manjaro is suited for every level of user—from beginner to expert.
The big question, however, is why would you want to give Manjaro a try? With so many Linux distributions available, is there anything particularly compelling about this platform to woo you away from your current daily driver (or to simply test out what this Arch-based distribution is all about)? Let’s take a look.
32- and 64-bit friendly
While many distributions are dropping support for 32-bit architecture, Manjaro continues to support the aging platform. This means that all of your older hardware can still make use of this Arch-based operating system with the latest-greatest releases of software. This will become more crucial in the future, when more Linux distributions stop supporting 32-bit hardware.
Rolling Release
Manjaro (currently on its 17th iteration) is a rolling release distribution. What does that mean? For those that do not know, a rolling release distribution effectively means everything is updated frequently, even the core of the system, so that there is no need for point-based releases. This also means your machine will always have the latest-greatest stable software. Due to the frequency of the updates, they are also smaller. Some consider this a superior update delivery method, as there is less chance of software breakage.
Choose your desktop
At the moment, you can choose between the Xfce, KDE, or GNOME. All three editions follow similar design concepts and offer a very clean and professional look (Figure 1).
Figure 1: The Xfce version of Manjaro keeps things clean and simple.
The Net edition provides a base installation without a pre-existing display manager, desktop environment, or any desktop software. With this particular release, you can customize it to perfectly meet your needs.
There are also community editions that include spins based on the following desktops:
The Manjaro developers have done a fantastic job of making Xfce, GNOME, and KDE versions look and feel the same. The biggest difference, for me, is that both the KDE and GNOME takes on the distribution are a bit more elegant and modern than Xfce (which might sway you one way or another).
Software
Beyond Manjaro’s ability to make Arch easy, one of the most impressive aspects to be found on this desktop Linux distribution is the collection of included software. Yes, you’ll find the standard productivity software:
LibreOffice
GIMP (XFCE version only)
Inkscape and Krita (KDE version only)
File managers and other standard desktop tools
Firefox (all three versions)
Thunderbird (KDE and XFCE versions)
Evolution (GNOME version)
But beyond the basics, you’ll also find the likes of:
Avahi SSH Server and Zeroconf Browser
Steam
Bulk Rename
Catfish File Search
Clipman
HP Device Manager
Orage Calendar
Htop
GParted
Yakuake (KDE version only)
Octopi CacheCleaner (KDE version only)
Along with those packages, Manjaro offers an easy to use Add/Remove Software tool (Figure 2) that allows you to install software from a vast collection of titles.
Figure 2: The Manjaro Add/Remove Software tool.
Understand, the pre-installed package listing will vary, depending on which desktop environment you’ve chosen to install. For example, the KDE version of Manjaro will lean heavy on KDE applications and the GNOME version will lean on GNOME software. You will find, however, that all three official desktop iterations do include LibreOffice, so your productivity is covered, regardless of environment.
The package manager GUI is as simple to use as any: Open the tool, search for what you want to install, select the software, and click Apply. Updates are just as easy. When an update has arrived, you will be notified in the system tray. Click the notification and okay the installation of the upgrades.
Settings Menu
One nice touch for Xfce spin of Manjaro is the Settings menu. Click on the Main menu and then click Settings in the right side of the menu to reveal an impressive amount of options available to configure (Figure 3). Figure 3: The Manjaro Settings menu offers a wide collection of configuration options. With the KDE and GNOME flavors of Manjaro, you work with the standard tools of that particular desktop environment, for a bit more cohesive feel. If you’ve used a recent releases of either KDE or GNOME, you’ll feel right at home. The GNOME iteration also includes the Dock To Dash extension, for those that prefer a more “dock-like” approach to the desktop.
Media
I was pleasantly surprised that Manjaro was able to play MP3s out of the box with one of its media players. The Xfce edition of Manjaro ships with both Guayadeque and Parole media players. Of the two, only Guayadeque was able to play MP3 files out of the box. YouTube videos play without issue and Netflix only requires the enabling of DRM (Figure 4) and the installation of the Random Agent Spoofer extension.
Figure 4: Enabling DRM for Netflix.
Once you’ve taken care of those two issues, Netflix plays seamlessly (Figure 5).
Figure 5: Catching a little Buffy The Vampire Slayer on Netflix.
Performance
As for performance, you can opt for any of the official editions of Manjaro and expect incredible speed. Running as a VirtualBox guest with 3GB of RAM, Manjaro ran as smoothly and quickly as the host Elementary OS Loki with a remaining 13GB of RAM available. That should tell you all you need to know about the performance of Manjaro. As a whole, there is absolutely nothing to complain about with regards to Manjaro performance. It’s quick, smooth, and reliable. The GNOME, KDE, and Xfce are flawless.
Who’s it for?
In the end, I think it’s safe to say that Manjaro Linux is a distribution that is perfectly capable of pleasing any level of user wanting a reliable, always up-to-date desktop. Manjaro has been around since 2011, so it’s had plenty of time to get things right… and that’s exactly what it does. If you’ve been looking for the ideal distribution to help you give Arch a try, the latest release of Manjaro is exactly what you’re looking for.
Learn more about Linux through the free “Introduction to Linux” course from The Linux Foundation and edX.
It’s no secret that Linux dominates the cloud, whether it’s a private cloud running on OpenStack or if it’s AWS or Microsoft Azure cloud. Microsoft itself admits that one out of three machines run Linux in Azure cloud. However, as more customers were running Linux, they needed the ability to manage their Linux systems, and Windows 10 lacked Linux tools and utilities.
Microsoft tried to add UNIX capabilities to its own PowerShell, but it didn’t work out as expected. Then, they worked with Canonical to create a Windows Subsystem for Linux. This allowed users to install Linux inside Windows 10, offering native integration, which meant users would be literally running Ubuntu command-line tools in Windows.
However, not everyone uses Ubuntu. In the Linux world, different distributions use different tools, utilities and commands to perform the same task. Officially, Microsoft is sticking to Ubuntu, as it’s the dominant cloud OS. But that doesn’t mean you can’t run your choice of distro. There is an open source project on GitHub that allows users to not only install a few supported distros on Windows, but also easily switch between them.
To start, we need to install Windows Subsystem for Linux on Windows.
Install Linux Bash for Windows
First, you need to join the Insider Build program to gain access to pre-release features such as WSL. Open Update Settings and then go to ‘Advanced Windows Update option’. Follow the instructions and join the Insider Build program. It requires you to log into your Microsoft account. Once done, it will ask you to restart the system.
Once you’ve rebooted, go to Advanced Windows Update optionpage and choose the pre-release update and select the Fast option.
Then, go to Developer Settings and choose Developer mode.
Once done, open ‘turn windows features on and off’ and select Window Subsystem for Linux beta.
You may have to reboot the system. Once rebooted, type ‘bash’ in the Windows 10 search bar, and it will open the command prompt where you will install bash — just follow the on-screen instructions. It will also ask you to create a username and password for the account. Once done, you will have Ubuntu running on the system.
Now every time you open ‘bash’ from the Start Menu of Windows 10, it will open bash running on Ubuntu.
The switcher we are about to install basically extracts the tarball of your chosen Linux distribution into the home directory of WSL and then switches the current rootfs with the chosen one. You can download all desired, and supported, distributions and then easily switch between them. Once you switch the distro and open ‘bash’ from the start menu, instead of Ubuntu, you will be running that distro.
Let’s get started.
Install Windows Subsystem for Linux Distribution Switcher
It’s time to install a switcher that will help us in switching between distributions. First, we need to install the latest version of Python 3 in Windows. Then, download the switcher folder from GitHub. It’s a zip file, so extract the file in the Downloads folder. Now open PowerShell and change the directory to the WSL folder:
cd .DownloadsWSL-Distribution-Switcher-master
Run ‘ls’ command to see all the scripts available. You should see this list:
Debian 8 is now installed. Now, let’s start using Debian. If you want to use Fedora, first quit the Debian bash session, by typing exit.
Now go back to PowerShell and enter the WSL directory as explained above:
cd .DownloadsWSL-Distribution-Switcher-master
Let’s download Fedora:
py.exe .get-source.py fedora
And then install it:
py.exe .install.py fedora
When you install a distribution, the ‘bash’ automatically switches to that distribution, so if you open ‘bash’ from Start Menu, you will be logged into Fedora. Try it!
Ok! Now how do we switch between installed distributions? First, you need to quit the existing ‘bash’ and go back to PowerShell, cd to the WSL Switcher directory, and then use ‘switcher’ script to switch to the desired distribution.
py.exe .switch.py NAME_OF_INSTALLED_DISTRO
So, let’s say we want to switch to Debian
py.exe .switch.py debian
Open ‘bash’ from Start and you will be running Debian. Now you can easily switch between any of these distributions. Just bear in mind that WSL itself is a beta software; it’s not ready for production so you will come across problems. On top of that, WSL Distribution Switcher is also an “under development” software so don’t expect everything to work flawlessly.
The basic idea behind this tutorial is to get you started with it. If you have questions, head over to the GitHub page and do as we do in the Linux world: ask, suggest, and contribute.
Learn more about Linux through the free “Introduction to Linux” course from The Linux Foundation and edX.
This article is paid for by Amdocs, a Platinum-level sponsor of Open Networking Summit, to be held April 3-6, and was written by Linux.com.
Open Networking Summit 2017 kicks off next week and one major topic under discussion there will be the newly formed Open Network Automation Platform (ONAP) project. ONAP is quickly becoming the de facto standard platform for network automation, supporting network functions virtualization and software-defined networks (NFV/SDN) quick adoption, says Alla Goldner, an Amdocs Director of Technology, Strategy and Standardization and a member of the ONAP Technical Steering Committee (TSC) at The Linux Foundation.
Alla Goldner, Amdocs Director of Technology, Strategy and Standardization
“ONAP is a new open source project that combines open source ECOMP and OPEN-O into a single harmonized effort to standardize a management and automation platform for NFV and SDN,” Goldner explained.
Such a standard frees operators to potentially escape the dreaded “dumb pipes” fate so many had feared and instead innovate their way to powerful differentiators and higher profits as well as effectively deal with industry disruptors, or become disruptors themselves.
ONAP is already heavily favored by telecom titans that had initially set out on their own to achieve the same Olympian accomplishment, first through proprietary means and then through separate open source projects.
AT&T originally designed ECOMP and partnered with Amdocs to bring it to fruition. Orange and Bell Canada joined in to support it and it was supposed to become an open source project at the beginning of this year. Meanwhile, the Open-O project was backed by operators like China Mobile, China Telecom and Hong Kong Telecom, as well as several vendors including Ericsson and Intel, among others.
The end goal of these efforts was not to achieve an open networking harmonized automation standard wherein costs could be cut, resources could be smartly realigned, and innovation could be moved into overdrive. Thus the merger of these two projects, ECOMP and OPEN-O, into one joint effort, ONAP, was a logical and important outcome.
“Network management is very complex,” Goldner said, “and that complexity can’t be resolved unless there is a standard for all to work with – and ONAP is becoming the de facto standard.”
Here, Goldner gives us some additional insights into the project’s impact on NFV and SDN in advance of Open Networking Summit.
Linux.com:How does adopting ONAP as a standard help all operators and vendors to innovate?
Alla Goldner:A standard makes it faster and cheaper to innovate. The ECOMP platform consists of more than 8 million lines of code. There is a big group of vendors and operators all trying to develop and implement new innovations across a large mix of platforms, many of them proprietary, which then requires further work in the way of integration and orchestration. This is not an efficient, effective, cheap or easy way to bring innovations to market.
ONAP as a de facto standard removes all these obstacles so that operators and vendors alike can focus on creativity and innovation.
Linux.com:You said that ONAP is becoming that de facto standard. How are you measuring support for the project right now as the TSC works on merging, and developing, ONAP code?
Alla Goldner:There is significant enthusiasm and support for ONAP now. There are 23 members already, both platform vendors and Service Providers, while the list of operators contains some of the biggest names in the space, including AT&T, Bell Canada, China Mobile, China Telecom, and Orange. Given this significant momentum, critical mass is either already there or it soon will be. With critical mass comes significant commitment and investment in quickly maturing the standard and surrounding technologies.
Standardizing and automating the underlying NFV/SDN also enables the operator to make adjustments at any time. Eventually this means operators can easily escape vendor lock-in, which reduces costs and enables more flexibility in switching or replacing network hardware, software, or processes.
Open Networking Summit April 3-6 in Santa Clara, CA features over 75 sessions, workshops, and free training! Get in-depth training on up-and-coming technologies including AR/VR/IoT, orchestration, containers, and more.
Linux.com readers can register now with code LINUXRD5 for 5% off the attendee registration. Register now!
This article was sponsored by Amdocs, founding member of ONAP. Find out how Amdocs is leading ONAP early adopters and accelerating NFV/SDN service innovation here, and watch leading service providers and the Linux Foundation discuss what open network automation means for the industry.
