"Boeing's much-maligned 737 Max jet could be cleared to fly again in just a few weeks," reports SFGate, adding that one U.S. airline plans to carry passengers "as early as December." Although the Federal Aviation Administration has not disclosed a public timeline for the Max's return to service, approval to lift the grounding could come as early as mid-November, according to Reuters. Boeing executives said they expect to gain FAA recertification before the end of the year. The company will also need to get approval from the European Union Aviation Safety Agency and Transport Canada, which are conducting their own respective reviews...

American Airlines said it plans to operate one daily Boeing 737 Max roundtrip from Dec. 29 through Jan. 4 between its Miami hub and New York's LaGuardia Airport. If it takes off, American will be the first US carrier to bring back the Max...

Other U.S. airlines operating the Max are taking a wait-and-see approach before assigning the fleet type to flights.

According to Phoronix, a Dell privacy driver is is being prepared for the Linux kernel. From the report: Beginning in Dell's 2021 laptop models they are providing hardware-based "privacy buttons" to disable microphone and camera support. These new Dell privacy buttons are basically hardware kill switches for the microphone and web camera video stream. The Dell privacy driver sent out on Tuesday for the Linux kernel is about manipulating the relevant LEDs and tracking the status of the hardware-based controls where as the actual toggling of the audio/video support is handled by the hardware.

The Dell privacy driver in its current form is talked about for the camera and microphone support but the patch does also note a "PRIVACY_SCREEN_STATUS" bit as well. Presumably they will be extending this privacy driver as well for privacy screen handling around reducing the horizontal/vertical viewing angles of the display. The dell-privacy Linux driver in its initial form can be found via the kernel mailing list. It's great seeing Dell working on this driver punctually for Linux ahead of their next-gen laptops.

AmiMoJo writes: As we roll into 2021 the Free Software Foundation is looking to update its high priority free software projects list. These are the software projects that should be incorporating "the most important threats, and most critical opportunities, that free software faces in the modern computing landscape." For now the FSF is looking for help deciding what to include. The FSF high priority projects list is what once included PowerVR reverse engineering as being very important albeit never happened prior to PowerVR graphics becoming less common. In fact, many FSF high priority projects never panned out as they weren't contributing much in the way of resources to the causes but just calling attention to them. PDF support was among their high priority projects as well as another example as well as the likes of an open-source Skype replacement and reverse-engineering other popular technologies.

They overhauled the list in 2017 after forming a committee to maintain the list while now as 2021 is just around the corner they are looking to revise their high priority projects focus once more. They have issued a call for input to share with the High Priority Free Software Projects committee what you feel should belong on the list. Feedback is being collected through early January. Currently on the list are different "areas" they feel are high priority for free software as opposed to previously focusing on particular projects.

In preparation for next year's Xe HPG graphics cards, Intel's open-source developers have begun publishing their patches enabling their "ANC" Vulkan Linux driver to support Vulkan ray-tracing. Phoronix reports: Jason Ekstrand as the lead developer originally on the Intel ANV driver has posted today the initial ray-tracing code for ANV in order to support VK_KHR_ray_tracing for their forthcoming hardware. Today is the first time Intel has approved of this open-source code being published and more is on the way. The code today isn't enough for Vulkan ray-tracing but more is on the way and based against the latest internal Khronos ray-tracing specification. At the moment they are not focusing on the former NVIDIA-specific ray-tracing extension but may handle it in the future if game vendors continue targeting it rather than the forthcoming finalized KHR version.

Among other big ticket items still to come in the near-term includes extending the ANV driver to support compiling and dispatching OpenCL kernels, new SPIR-V capabilities, and generic pointer support. Also needed is the actual support for compiling ray-tracing pipelines, managing acceleration structures, dispatching rays, and the platform support. The actual exposing of the support won't come until after The Khronos Group has firmed up their VK_KHR_ray_tracing extension. Some of this Intel-specific Vulkan ray-tracing code may prove useful to Mesa's Radeon Vulkan "RADV" driver as well. Intel engineers have been testing their latest ray-tracing support with ANV internally on Xe HPG.

An anonymous reader quotes a report from Ars Technica: In recent years, the cost of solar and wind energy has declined precipitously, which has accelerated the growth of these renewable energy technologies. Increasingly, utilities are now planning for a future grid dominated by solar and wind. That will require changes in grid management and transmission upgrades as well as the addition of storage to smooth out the supply from variable generators. Grid storage is still pretty early days, but we're already seeing huge cost reductions as the industry matures. The US Energy Information Administration (EIA) highlighted this recently, showing that grid-scale battery-project costs in the United States dropped 70 percent in just a few years.

Between 2015 and 2018, average project costs decreased from $2,152 per kilowatt-hour of storage to $625. Costs will need to drop much more for grid batteries to scale, but that's a huge improvement in a short period of time. By the end of 2018, the US had 869 megawatts of battery power capacity and 1,236 megawatt-hours of energy capacity. (Power is the rate at which the batteries can supply electricity, while energy is the total amount it can supply when going from full charge to empty.) EIA also has installation data for 2019, which saw the addition of another 150 megawatts/450 megawatt-hours. And in just the first seven months of 2020, yet another 300 megawatts of power capacity were installed. EIA doesn't see this slowing down. It expects installed battery storage to increase by 6,900 megawatts "in the next few years" -- a figure ambiguous enough to allow for a rapid spike in planned projects.

An anonymous reader quotes a report from IEEE Spectrum: In April, Guoping Feng and colleagues at MIT, along with [Karl Deisseroth, a neuroscientist and bioengineer at Stanford University] demonstrated a minimally invasive optogenetic system that required drilling a small hole in the skull, then being able to control opsin-expressing neurons six millimeters deep into the brain using blue light. This approach used of a type of opsin that slowly activates neurons in a step-wise manner. In the most recent study [published in the journal Nature Biotechnology], Deisseroth and colleagues sought to instead enable both deep and fast optogenetics without surgery. The Stanford team expressed in the brain cells of mice a powerful new opsin called ChRmine (pronounced like the deep-red color "carmine"), discovered by Deisseroth's group last year in a marine organism. Then, they shined a red light outside the skull and were able to activate neural circuits in the midbrain and brainstem at depths of up to 7 millimeters. With the technique, the scientists turned on and off brain circuits with millisecond precision. "It really worked well, far better than we even expected might be possible," says Deisseroth.

The team then tested the effectiveness of the system. In one instance, they used light to quickly and precisely stop seizures in epileptic mice, and in another to turn on serotonin-producing neurons to promote social behavior in mice. Most optogenetic techniques involve injecting viruses with an opsin gene of choice directly into the brain with a needle. To avoid this, the Stanford team used a type of PHP virus developed at CalTech that can be injected in the blood. The virus then crosses the blood-brain barrier to deliver its payload, an opsin gene, to brain cells. In this case, even the delivery of the gene is noninvasive -- no needle penetrates the brain. Deisseroth's team is now testing the non-invasive technique in fish and collaborating with others to apply it to non-human primates. They're also working with the Seattle-based Allen Institute to develop mouse lines bred with ChRmine in their cells.

Phoronix ran a story this morning with this provocative headline: "It's Time To Admit It: The X.Org Server Is Abandonware." The last major release of the X.Org Server was in May 2018 but don't expect the long-awaited X.Org Server 1.21 to actually be released anytime soon. This should hardly be surprising but a prominent Intel open-source developer has conceded that the X.Org Server is pretty much "abandonware" with Wayland being the future. [Or, more specifically, that "The main worry I have is that xserver is abandonware without even regular releases from the main branch."]

This comes as X.Org Server development hits a nearly two decade low, the X.Org Server is well off its six month release regimen in not seeing a major release in over two years, and no one is stepping up to manage the 1.21 release. A year ago was a proposal to see new releases driven via continuous integration testing but even that didn't take flight and as we roll into 2021 there isn't any motivation for releasing new versions of the X.Org Server by those capable of doing so.

Red Hat folks have long stepped up to manage X.Org Server releases but with Fedora Workstation using Wayland by default and RHEL working that way, they haven't been eager to devote resources to new X.Org Server releases. Other major stakeholders also have resisted stepping up to ship 1.21 or commit any major resources to new xorg-server versions.

The Python programming language "is a big hit for machine learning," read a headline this week at ZDNet, adding "But now it needs to change."

Python is the top language according to IEEE Spectrum's electrical engineering audience, yet you can't run Python in a browser and you can't easily run it on a smartphone. Plus no one builds games in Python these days. To build browser applications, developers tend to go for JavaScript, Microsoft's type-safety take on it, TypeScript, Google-made Go, or even old but trusty PHP. On mobile, why would application developers use Python when there's Java, Java-compatible Kotlin, Apple's Swift, or Google's Dart? Python doesn't even support compilation to the WebAssembly runtime, a web application standard supported by Mozilla, Microsoft, Google, Apple, Intel, Fastly, RedHat and others.

These are just some of the limitations raised by Armin Ronacher, a developer with a long history in Python who 10 years ago created the popular Flask Python microframework to solve problems he had when writing web applications in Python. Austria-based Ronacher is the director of engineering at US startup Sentry — an open-source project and tech company used by engineering and product teams at GitHub, Atlassian, Reddit and others to monitor user app crashes due to glitches on the frontend, backend or in the mobile app itself... Despite Python's success as a language, Ronacher reckons it's at risk of losing its appeal as a general-purpose programming language and being relegated to a specific domain, such as Wolfram's Mathematica, which has also found a niche in data science and machine learning...

Peter Wang, co-founder and CEO of Anaconda, maker of the popular Anaconda Python distribution for data science, cringes at Python's limitations for building desktop and mobile applications. "It's an embarrassing admission, but it's incredibly awkward to use Python to build and distribute any applications that have actual graphical user interfaces," he tells ZDNet. "On desktops, Python is never the first-class language of the operating system, and it must resort to third-party frameworks like Qt or wxPython." Packaging and redistribution of Python desktop applications are also really difficult, he says.

emil (Slashdot reader #695) shares an article from Linux Journal re-visiting the saga of the btrfs file system (initially designed at Oracle in 2007): The btrfs filesystem has taunted the Linux community for years, offering a stunning array of features and capability, but never earning universal acclaim. Btrfs is perhaps more deserving of patience, as its promised capabilities dwarf all peers, earning it vocal proponents with great influence. Still, [while] none can argue that btrfs is unfinished, many features are very new, and stability concerns remain for common functions.

Most of the intended goals of btrfs have been met. However, Red Hat famously cut continued btrfs support from their 7.4 release, and has allowed the code to stagnate in their backported kernel since that time. The Fedora project announced their intention to adopt btrfs as the default filesystem for variants of their distribution, in a seeming juxtaposition. SUSE has maintained btrfs support for their own distribution and the greater community for many years.

For users, the most desirable features of btrfs are transparent compression and snapshots; these features are stable, and relatively easy to add as a veneer to stock CentOS (and its peers). Administrators are further compelled by adjustable checksums, scrubs, and the ability to enlarge as well as (surprisingly) shrink filesystem images, while some advanced btrfs topics (i.e. deduplication, RAID, ext4 conversion) aren't really germane for minimal loopback usage. The systemd init package also has dependencies upon btrfs, among them machinectl and systemd-nspawn . Despite these features, there are many usage patterns that are not directly appropriate for use with btrfs. It is hostile to most databases and many other programs with incompatible I/O, and should be approached with some care.
The original submission drew reactions from three disgruntled btrfs users. But the article goes on to explore providers of CentOS-compatible btrfs-enabled kernels, ultimately opining that "There are many 'rough edges' that are uncovered above with btrfs capabilities and implementations, especially with the measures taken to enable it for CentOS. Still, this is far better than ext2/3/4 and XFS, discarding all the desirable btrfs features, in that errors can be known because all filesystem content is checksummed." It would be helpful if the developers of btrfs and ZFS could work together to create a single kernel module, with maximal sharing of "cleanroom" code, that implemented both filesystems... Oracle is itself unwilling to settle these questions with either a GPL or BSD license release of ZFS. Oracle also delivers a btrfs implementation that is lacking in features, with inapplicable documentation, and out-of-date support tools (for CentOS 8 conversion). Oracle is the impediment, and a community effort to purge ZFS source of Oracle's contributions and unify it with btrfs seems the most straightforward option... It would also be helpful if other parties refrained from new filesystem efforts that lack the extensive btrfs functionality and feature set (i.e. Microsoft ReFS).

Until such a day that an advanced filesystem becomes a ubiquitous commodity as Linux is as an OS, the user community will continue to be torn between questionable support, lack of features, and workarounds in a fragmented btrfs community. This is an uncomfortable place to be, and we would do well to remember the parties responsible for keeping us here.
So how do Slashdot's readers feel about btrfs?

The Linux 5.10 kernel's XFS file-system will have two new on-disk meta-data capabilities, reports Phoronix: 1. The size of inode btrees in the allocation group is now recorded. This is for increasing redundancy checks and also allowing faster mount times.

2. Support for timestamps now until the year 2486.

This "big timestamps" feature is the refactoring of their timestamp and inode encoding functions to handle timestamps as a 64-bit nanosecond counter and bit shifting to increase the effective size. This now allows XFS to run well past the Year 2038 problem (where storing the time since 1970 in seconds will no longer fit in a signed 32-bit integer and thus wraparound) to now the Year 2486. Making a new XFS file-system with bigtime enabled allows a timestamp range from December 1901 to July 2486 rather than December 1901 to January 2038. For preserving backwards compatibility, the big timestamps feature is not currently enabled by default.

The official public repository for CUPS, an Apple open-source project widely used for printing on Linux, is all-but dormant since the lead developer left Apple at the end of 2019. From a report: Apple adopted CUPS for Mac OS X in 2002, and hired its author Michael Sweet in 2007, with Cupertino also acquiring the CUPS source code. Sweet continued to work on printing technology at Apple, including CUPS, until December 2019 when he left to start a new company. Asked at the time about the future of CUPS, he said: "CUPS is still owned and maintained by Apple. There are two other engineers still in the printing team that are responsible for CUPS development, and it will continue to have new bug fix releases (at least) for the foreseeable future." Despite this statement, Linux watcher Michael Larabel noted earlier this week that "the open-source CUPS code-base is now at a stand-still. There was just one commit to the CUPS Git repository for all of 2020." This contrasts with 355 commits in 2019, when Sweet still worked at Apple, and 348 the previous year. We asked Apple about its plans for CUPS and have yet to hear back.

KDE's Plasma 5.20 is now available, bringing a bunch of refinements as well as some larger features. Some of the KDE Plasma 5.20 highlights include (via Phoronix): - Numerous fixes to the KWin window manager / compositor including a number of Wayland fixes. Among the Wayland work in Plasma 5.20 includes Klipper support and middle-click paste, mouse and touchpad support nearly on par to X11, window thumbnails in the task manager, crash fixes, and more.

- Improved notifications.

- Different redesigns and additions to the KDE System Settings from SMART monitoring to better looking interfaces.

- Redesigned on-screen displays.

- Various tack manager and system tray improvements. More information about KDE 5.20 is available here.

An anonymous reader quotes a report from Motherboard: Decades before Twitter threads, Reddit forums, or Facebook groups, there was Usenet: an early-internet, pre-Web discussion system where one could start and join conversations much like today's message boards. Launched in 1980, Usenet is the creation of two Duke University students who wanted to communicate between decentralized, local servers -- and it's still active today. On Usenet, people talk about everything, from nanotech science to soap operas, wine, and UFOs. Jozef Jarosciak, a systems architect based in Ontario, had his first encounter with Usenet in 2000, when he found a full-time job in Canada thanks to a job posting there.

This week, Jarosciak uploaded some of the oldest Usenet posts available to the internet. Around 2.1 million posts from between February 1981 and June 1991 from Henry Spencer's UTZOO NetNews Archive are archived at the Usenet Archive for anyone to browse. This latest archive-dump is part of an even larger project by Jarosciak. He launched the Usenet Archive site last month, as a way to host groups in a way that'd be independent of Google Groups, which also holds archives of newsgroups like Usenet. It's currently archiving 317 million posts in 10,000 unique Usenet newsgroups, according to the site -- and Jarosciak estimates it'll eventually hold close to 1 billion posts.

FSGSBASE support in Linux "has the possibility of helping Intel/AMD CPU performance especially in areas like context switching that had been hurt badly by Spectre/Meltdown and other CPU vulnerability mitigations largely on the Intel side," Phoronix wrote back in August. As it started its journey into the kernel, they provided a preview on August 10: The FSGSBASE support that was finally mainlined a few days ago for Linux 5.9 is off to providing a nice performance boost for both Intel and AMD systems... FSGSBASE support for the Linux kernel has been around a half-decade in the making and finally carried over the finish line by one of Microsoft's Linux kernel engineers...

FSGSBASE particularly helps out context switching heavy workloads like I/O and allowing user-space software to write to the x86_64 GSBASE without kernel interaction. That in turn has been of interest to Java and others...On Linux 5.9 where FSGSBASE is finally mainlined, it's enabled by default on supported CPUs. FSGSBASE can be disabled at kernel boot time via the "nofsgsbase" kernel option.
Today on the Linux kernel mailing list, Linus Torvalds announced the release of Linux 5.9: Ok, so I'll be honest - I had hoped for quite a bit fewer changes this last week, but at the same time there doesn't really seem to be anything particularly scary in here. It's just more commits and more lines changed than I would have wished for.
And Phoronix reported: Linux 5.9 has a number of exciting improvements including initial support for upcoming Radeon RX 6000 "RDNA 2" graphics cards, initial Intel Rocket Lake graphics, NVMe zoned namespaces (ZNS) support, various storage improvements, IBM's initial work on POWER10 CPU bring-up, the FSGSBASE instruction is now used, 32-bit x86 Clang build support, and more. See our Linux 5.9 feature overview for the whole scoop on the many changes to see with this kernel.

Python has reached "a new all-time high" on TIOBE's index of programming language popularity. TechRadar reports: Java's days as the world's second most popular programming language could be numbered according to Tiobe's latest programming language rankings which show Python is becoming increasingly popular among developers. The firm's Index for October 2020 shows that Java has been overtaken by C as the world's most popular programming language when compared to the same period last year. Python remains in third place but it's quickly closing the gap between it and Java. According to Tiobe CEO Paul Jensen, C and Java have held the top two spots consistently for the past two decades. However, the 25-year-old programming language Java is approaching its "all time low" in popularity as it has fallen by 4.32 percentage points when compared to where it stood in October of last year. Tiobe ranks programming languages in its popularity index based on the number of hits each language gets across 25 search engines.
RedMonk's rankings already show Python as more popular than Java — the first time since 2012 that Java isn't one of their top two most popular languages. And TIOBE's CEO says "Let's see what will happen the next few months."

Here's their October rankings for the top 10 most popular programming languages.

• C
• Java
• Python
• C++
• C#
• Visual Basic
• JavaScript
• PHP
• R
• SQL

And coming in at #11 is Perl.

A remarkable first-person story in today's Washington Post: I used to call it the "scamdemic." I thought it was an overblown media hoax. I made fun of people for wearing masks. I went all the way down the rabbit hole and fell hard on my own sword, so if you want to hate me or blame me, that's fine. I'm doing plenty of that myself.

The party was my idea. That's what I can't get over. Well, I mean, it wasn't even a party — more like a get-together. There were just six of us, OK? My parents, my partner, and my partner's parents... Some people in my family didn't necessarily share all of my views, but I pushed it. I've always been out front with my opinions. I'm gay and I'm conservative, so either way I'm used to going against the grain... I told my family: "Come on. Enough already. Let's get together and enjoy life for once." They all came for the weekend. We agreed not to do any of the distancing or worry much about it... We cooked nice meals. We watched a few movies. I played a few songs on my baby grand piano. We drove to a lake about 60 miles outside of Dallas and talked and talked. It was nothing all that special. It was great. It was normal...

I have no idea which one of us brought the virus into the house, but all six of us left with it. It kept spreading from there.... I was sweating profusely. I would wake up in a pool of sweat. I had this tingling feeling all over my body, this radiating kind of pain... Then one day I was walking up the stairs, and all of the sudden, I couldn't breathe. I screamed and fell flat on my face. I blacked out. I woke up a while later in the ER, and 10 doctors were standing around me in a circle. I was lying on the table after going through a CT scan. The doctors told me the virus had attacked my nervous system. They'd given me some medications that stopped me from having a massive stroke. They said I was minutes away.

I stayed in the hospital for three days, trying to get my mind around it. It was guilt, embarrassment, shame. I thought: "OK. Maybe now I've paid for my mistake." But it kept getting worse. Six infections turned into nine. Nine went up to 14. It spread from one family member to the next, and it was like each person caught a different strain... My father is 78, and he went to get checked out at the hospital, but for whatever reasons, he seemed to recover really fast. My father-in-law nearly died in his living room and then ended up in the same hospital as me on the exact same day. His mother was in the room right next to him because she was having trouble breathing. They were lying there on both sides of the wall, fighting the same virus, and neither of them ever knew the other one was there. She died after a few weeks. On the day of her funeral, five more family members tested positive...

They put my father-in-law on a ventilator, and he lay there on life support for six or seven weeks. There was never any goodbye. He was just gone. It's like the world swallowed him up.

We could only have 10 people at the funeral, and I didn't make that list.

California's elections include grass roots propositions that change the law directly while bypassing legislators. Uber, Lyft, and Uber-owned Postmates (as well as DoorDash and Instacart) have spent $185 million — the most ever spent — pushing a proposition that would keep ride-hail and delivery drivers as independent contractors, reports SFGate. "If it passes...gig corporations won't have to contribute to Social Security, Medicare or unemployment insurance. They won't have to offer paid sick leave, workers compensation or unemployment benefits to drivers."

But the site also investigated what happened shortly after the Uber/Lyft PAC reported an $128,000 expenditure on mailers: Political mailers masquerading as progressive voter guides and endorsing Proposition 22, the initiative backed by Uber and Lyft, are showing up in Southern California voters' mailboxes. The fine print on one mailer says it was prepared by the "Feel the Bern, Progressive Voter Guide," which is not an actual organization. Neither are the "Council of Concerned Women Voters Guide" nor the "Our Voice, Latino Voter Guide," whose mailers make the same endorsements as Feel the Bern.

Mailed political fliers typically identify the organization that paid for the literature. But that information was conspicuously absent from Feel the Bern and the other two mailers...

The measure would allow ride-hail and delivery drivers to continue to be treated as independent contractors, although with some new benefit concessions. If it fails, these employees would likely be considered workers entitled to a minimum wage, overtime pay, workers' compensation, unemployment insurance and paid sick leave.

The California Democratic Party has endorsed a "no" vote for Prop. 22.

Hobbyist developers are trying once again to get a Motorola 68000 back-end merged into the upstream LLVM compiler. Phoronix reports: The Motorola 68000 series processors have been around since the 80's thanks to the likes of the early Apple Macintosh computers. Fast forward to 2020, the Motorola 68000 is still a popular target for vintage computer enthusiasts and hobbyists. Community developers have worked on improving the Linux kernel support for M68k hardware like early Apple Powerbooks as recently as a few years ago and the compiler support is a continued target. GCC 11 due out next year was looking to drop the M68k target over its unmaintained status. Hobbyists though stepped up there so the M68k support will remain in GCC. Now developers are also looking at adding M68k support to the LLVM compiler.

This isn't the first time that M68k support for LLVM has been brought up albeit never successfully landed to date. Building off the past failures to get the Motorola 68000 series support upstreamed, developers last week sent out new patches proposing this back-end -- this time they are showing more clarity about the developers involved and being committed to supporting the code, the sustainability of the code, and responding quickly to code review comments. This patch series is the latest attempt at upstreaming Motorola 68000 series support in LLVM. Besides all the back-end specific code there is also some common LLVM code changes that fall under greater scrutiny.

University of Queensland student Germain Tobar who worked with UQ physics professor Fabio Costa on a new peer-reviewed paper "says he has mathematically proven the physical feasibility of a specific kind of time travel" without paradoxes, reports Popular Mechanics: Time travel discussion focuses on closed time-like curves, something Albert Einstein first posited. And Tobar and Costa say that as long as just two pieces of an entire scenario within a closed time-like curve are still in "causal order" when you leave, the rest is subject to local free will... In a university statement, Costa illustrates the science with an analogy


"Say you travelled in time, in an attempt to stop COVID-19's patient zero from being exposed to the virus. However if you stopped that individual from becoming infected, that would eliminate the motivation for you to go back and stop the pandemic in the first place. This is a paradox, an inconsistency that often leads people to think that time travel cannot occur in our universe. [L]ogically it's hard to accept because that would affect our freedom to make any arbitrary action. It would mean you can time travel, but you cannot do anything that would cause a paradox to occur...."


But the real truth, in terms of the mathematical outcomes, is more like another classic parable: the monkey's paw. Be careful what you wish for, and be careful what you time travel for. Tobar explains in the statement:


"In the coronavirus patient zero example, you might try and stop patient zero from becoming infected, but in doing so you would catch the virus and become patient zero, or someone else would. No matter what you did, the salient events would just recalibrate around you. Try as you might to create a paradox, the events will always adjust themselves, to avoid any inconsistency."

"To celebrate Java's 25th anniversary this year and the latest release of Java 15, JetBrains has compiled data from multiple sources to look at what the current state of the language," reports SD Times: The largest concentration of Java developers is in Asia, where 2.5 million developers use it as their primary language. JetBrains believes this may be due to the fact that it is common to hire offshore developers in countries like China and India to build Android apps. "We might have expected the USA to have a high percentage of Java users, but it also makes a lot of sense that they don't. There is a big technology stack to choose from and often a lot of the tech companies are at the forefront of that stack, so it could be that developers there don't need the power or stability of Java and are using languages that allow them to build and test quickly," JetBrains wrote in a post.
The post on JetBrains notes that the six countries with the highest percentage of developers using Java as their primary language are: China, South Korea, India, Germany, Spain, and Brazil: The reasons Java is most likely so popular in the first 6 countries include the free use of Java, governmental support, and open-source... Germany is also very high which could be attributed to Java being the most popular language in Germany for software engineers as it is used to build highly scalable applications for a multitude of industries. Most enterprise services rely on Java to power the applications that enable the day-to-day running of businesses, such as payroll, inventory management, reporting, and so on. Germany also has a big financial sector that uses Java heavily for their homegrown tech, such as trading bots, retail banking systems, and other applications that the finance industry requires in order to remain competitive...

According to the State of the Developer Ecosystem Survey 2020, more than a third of professional developers use Java as a primary language and Java remains the second primary language among professional developers after JavaScript. Expert analysis: It is not surprising to see JavaScript and Java taking the leading positions as they are kind of paired together; developers who work with Java often write their frontend and any quick scripts in JavaScript. Python is probably third place due to the spread of machine learning. In general, we expect the web to be a big part of the developer ecosystem and so JavaScript, HTML and CSS, and PHP will always have solid standing. SQL is also always going to be around as there isn't much that doesn't require databases in some capacity. C++ is also kind of a solid language in that it is used for a lot of embedded applications, so it won't be disappearing off the charts any time soon. C# though seems to be losing ground, and I guess if Java is high then C# will be low, as they are both very similar in terms of capabilities.

As to why I think Java is so high in the sphere of professional development — it's similar to what was mentioned about Germany. Most enterprise business services rely on Java to make them tick along. It's not just the IT sector either — almost every company, be it in distribution, manufacturing, or banking, has IT services as part of their infrastructure, and these services, such as payroll or inventory management, are generally built with Java in the backend. So Java is used a lot by professional developers who work for these companies.