Slashdot Mirror

Yes.

But this isn't really any news, MS has provided custom canonical distributions for Azure deployment for years, and the image MS already provides as their recommenced/default distribution for azure VMs already contains several telemetry and remote management daemons, to facilitate better integration with Azure monitoring. The image is also configured to trust ms' own apt repo source.

The code for the telemetry daemon is even open source on github.
https://github.com/Microsoft/O...

There has been a few bugs in these daemons, most significant is the bug which starts shell scripts which doesn't terminate, i.e. the server becomes super slow after a few days due to thousands of running processes. Google on "OMSConsistencyInvoker".

From almost two years ago: "Replace React with Mithril for licensing reasons"
https://github.com/Automattic/...

That said, I still feel Mithril.js + Tachyons.css is a better way to develop web apps (see my other comment on this article).

Mithril.js emphasizes leveraging JavaScript using the HyperScript API (instead of an adhoc templating language) and automatic redrawing when your application changes via user interaction or a network event. This makes web single-page application development quite pleasant to write and maintain and is scalable. You can also test much of such vdom-based UIs without creating real DOM nodes.
https://mithril.js.org/

Check out Tachyons and similar CSS libraries which use CSS classes to essentially define inline styles efficiently and in a maintainable way across big applications. Tachyons works especially well with HyperScript, letting you can do almost all your UI styling in JavaScript.

Here is one example FOSS project I wrote in that style: https://github.com/pdfernhout/...

Of course, few web developers grok this yet because most affirm "best practices" from years ago (e.g. semantic CSS, HTML-first design, JavaScript as a progressive afterthought). Most web developers are used to coding in non-standard HTML-ish templating systems (e.g. Angular, Vue, JSX). This give them a false sense of security they can maintain more complex apps that are mostly about JavaScript. By leveraging JavaScript from the start, Mithril.js may have a slightly higher learning curve (learning more about JavaScript), but it pays off down the road with much more maintainable applications.

React has helped a lot of developers begin to move past some of that, but it has its own baggage (including JSX) from being only half-way to the new paradigm outlined above. MIT licensing improves things, but I still feel Mithril is better for technical reasons. Mithril is simpler internally because Mithril does not emphasize subtree component rendering which React does for "efficiency" but which I'd suggest in practice leads to worse designs and a less understandable core. I also feel HyperScript is a better way to write UIs than JSX by keeping all your code in standard JavaScript/TypeScript without other awkward object constructions. While you can use HyperScript with React via a third-party library, it is a bit klunky as an add on, and most of the React code examples and libraries use JSX.

Actually there's a swift-evolution project where quite a few people (including non-Apple employees) are involved with Swift language design, proposals, and evolution.

https://github.com/apple/swift...

And as there's a Swift roadmap out there, I don't think the whole "on a whim" thing has merit either.

The Ubuntu kernel for AWS also includes the ENA (Elastic Network Adapter) driver (source code: https://github.com/amzn/amzn-d...), which allows you to get 20Gbps networking on certain instance types (https://aws.amazon.com/about-aws/whats-new/2016/06/introducing-elastic-network-adapter-ena-the-next-generation-network-interface-for-ec2-instances/).

I believe RHEL 7.4 also added the ENA driver, and the Amazon Linux image has it of course.

Good tip. But that doesn't always work. And some games lack controller support entirely. In such cases, try AntiMicro.

The problem is that .NET has never had something that would be a ready fit for a cross-platform GUI framework, historically

There was Windows Forms and WPF, but both of these are Windows-specific frameworks to begin with. WinForms is so tied to Win32 concepts (window handles and messages etc) that it cannot conceivably be ported - Mono tried that, and they eventually had to resort to reusing Wine code to do so, and ditch any attempts to use platform-native look and feel. WPF can conceptually run outside of Windows by design, but the implementation has a lot of native code that's intimately tied to Direct3D, so managing that is a Sisyphean task (indeed, Microsoft hasn't even ported WPF to Direct3D 11 to date!). There's a third party project called Avalonia that tries to reimplement it from scratch, but the sheer size and scope of a full-fledged modern UI framework means that they aren't going to ship a stable version anytime soon.

Realistically, when GUI comes to .NET Core, it would probably be Xamarin's XWT (to remind, Xamarin is currently owned by Microsoft). Given that Xamarin still ships MonoDevelop / Xamarin Studio (now rebranded as Visual Studio for Mac for the world at large - although MonoDevelop is still there on Linux), they might have some interest in a cross-platform .NET GUI. Currently they're using Gtk# for that, and running on Mono, but it's clear that .NET Core is going to subsume Mono long term.

In the meantime, .NET Core is focused almost entirely on the server side of things. I suppose a good way to think of it is a Java-like platform that offers a similar but more powerful and more thoroughly modernized language; a more lightweight, slimmer runtime that is designed to ship self-contained with the app; and modern package-based dependency management for libraries and frameworks (instead of Java's and traditional .NET "everything and the kitchen sink" approach to stdlib). Oh, and licensing - the runtime and all the standard libraries in the stack are MIT. All development is out in the open on GitHub, too.

As far as ASP security - ASP.NET had nothing in common with ASP of old (back when it was still Active Server Pages, with "Active" being a reference to ActiveX), except for the name, because branding. ASP.NET MVC was, in turn, a near-complete replacement for the original ASP.NET, reusing some low-level bits of the stack (HTTP request handling and such). The most recent incarnation, ASP.NET Core is a complete rewrite of everything from scratch for .NET Core, but with design strongly reminiscent of MVC, with various legacy bits trimmed, and the rest simplified and made more flexible (e.g. the entire HTTP pipeline is componentized, to make it easy to swap servers etc). I'm not aware of any fundamental security issues in it - although of course, as with any framework, security depends on how you use it.

HEIF offering much better than JPG compression

HEIF doesn't offer any compression because it's just an image container format, which can also contain JPEG data.

He's expecting this change due to the planned switch-over to proof of stake:
https://www.coindesk.com/ether...
https://www.coindesk.com/ether...
https://github.com/ethereum/wi...

If proof of stake works, it will fix the fundamental scalability issues that cryptocurrencies currently struggle with. It could also implode spectacularly if people figure out how to game the system or figure out a major exploit. It makes sense that he'd be very confident in his course of action, but only time will tell whether he's right or not.

Why do none of these stories contain any information about the real reason he's so confident in his assertions?
https://www.coindesk.com/ether...
https://www.coindesk.com/ether...
https://github.com/ethereum/wi...

Etherium is going to move to a whole new way of handling transactions (proof of stake) that will blow the current methods out of the water...if it works safely. Proof of work is not particularly scalable, but proof of stake is.

As you can see from these coindesk news stories, this planned transition is old news, so I don't get why these stories aren't mentioning it.

Then how does one obtain a certificate for a domain in .test and use it on all devices on a home LAN? I thought Android 7 "Nougat" and later didn't trust user-installed root certificates unless a particular app opts into trusting user-installed root certificates through the network security config file in the application's package. Chrome for Android appears to opt in, but Firefox for Android is untested. Using cleartext HTTP is not an option because more sensitive APIs are unavailable outside secure contexts.

I can either install Skype, make an account and chat about that job I want, or I can tell them I don't have Skype and the reasons why I don't want to install it or make an account

If you have used Outlook.com or Hotmail that preceded it, you have a Microsoft account. If you have set up Windows 8 or 10 and accepted the defaults, you created a Microsoft account. And if you have a Microsoft account, a web browser, and the Pidgin IM client, you can log in to Skype for Web once with your Microsoft account credentials and then build and install Skype for Pidgin.

Java has the huge advantage of automatic garbage collection.

That may be an advantage over C, or older C++. In Modern C++ this is mostly a non-issue - assuming you use smart pointers (in the standard library) judiciously and follow the Coding Guidelines. Explicit memory allocations is essentially gone and you don't have to worry about it. No garbage, no leaks. Of course, you could be keeping to much stuff alive, but that's just as much of a problem with Java, since that memory doesn't get GCed.

So Java garbage collection is more of a hindrance than a benefit relative to Modern C++.

If you want an ISC licensed jvm, there is https://github.com/ReadyTalk/a....
IIRC avian has its own class library or it can use OpenJDK or the Android class library.

The license granted hereunder will terminate, automatically and without notice, if you (or any of your subsidiaries, corporate affiliates or agents) initiate directly or indirectly, or take a direct financial interest in, any Patent Assertion: (i) against Facebook or any of its subsidiaries or corporate affiliates, (ii) against any party if such Patent Assertion arises in whole or in part from any software, technology, product or service of Facebook or any of its subsidiaries or corporate affiliates, or (iii) against any party relating to the Software.

You're right that it reads "relating to the software", but this only applies to (iii), not (i) or (ii).

I don't think that's exactly right, Amazon wouldn't loose the license to the software (the BSD), but they would loose any Facebook patent license that ReactJs is potentially infringing, and then Facebook would sue back on those patents. Source.
Still seems a risk and I think Apache made the right choice banning this license.

Here's the actual patent clause being discussed:

https://github.com/facebook/rocksdb/blob/132013366d202dbd5d5c6463c60898bdd420055b/PATENTS

The future may be table-oriented AI (TOAI).

It uses tools and/or conventions more typical of a regular office and thus allows AI problems to be split up and analyzed in a modular team-oriented fashion. Tables are easier to relate to than traditional neural nets (without a lot of training, at least). TOAI allows compartmentalizing AI tasks to distribute to staff (tasks, sub-tasks, etc.), and encourages a kit-oriented approach (modularization).

For example, you may have 3 sub-teams: 1) pattern/test makers, 2) results examiners, and 3) coordinators.

The first group focuses on making the individual tests (patterns or "factors"), the second group focuses on determining which tests are most or least useful for given situations, and the 3rd group be the coordinators who split up the problems and/or AI decision flow between groups and/or template sets (filters).

^^^
This really needs modding up. I am surprised the advertisers are even slightly concerned about cookies anymore when browser fingerprinting is a far more insidious and (currently) difficult to overcome privacy invasion for the end-user.

Since Google has persuaded almost everyone and their kid brother to run adsense code on the page, they have a canvas-fingerprint-trackable record of clickstream from page-to-page/site-to-site.

Tools like panopticlick and ipduh can give you an immediate sense of the problem, but trying to reduce it is tricky.

To sidestep fingerprinting pretty much means running the Tor browser or Firefox with Random Agent Spoofer, Decentraleyes, and a custom user.js set up with something like pyllyukko's prefs.

in this totally safe PDF?

Yes, Postscript is a turing complete language
(you can even write a ray tracer in it).

BUT

postscript can only output to the document (or screen), and can't read input from the internet.

Thus, as long as there isn't a critical bug in the displaying software...
- (Adobe Acrobat reader, I'm looking at you right now !),
...and as long as there isn't some asinine extra feature implemented...
- (you can bet that someone at microsoft on the outlook team would dream of a document viewer that can automatically extract attachments embed inside PDF files and execute them)
...there isn't an actual risk in opening random PDF files, except that some might take a few hours to render.

(And other can generate 1000 - worth of pages on the printer with only a few lines of code, if you're so stupid to send a raw post-script to the printer without even looking at it).

I have no problem rendering unicode on my terminals. Unicode doesn't have to do with text/binary.

While it isn't the hugest challenge in security, unicode at the string level is not easy to get right. You have to do the right thing at the ends of strings when hanging combining codepoints are present. And just recently, suddenly a standard change allows certain combiners to appear before their target base character rather than after. Tons of combiners can be piled up on a character. There are plenty of icky corners where bad code could crash the stack on a poor implementation. There are 4 times as many whitespace characters, text that has different column directions, weird newline and hyphenation rules... just tons of detail-oriented work.

As an example, check out the Perl6 test suite sections that deal with unicode... not even including a bunch scattered around in other areas of the test suite.

(Really, email itself needs to just die... there just aren't any viable replacements... it's all corporate walled gardens or fractious gaggles of underfueled attempts at distributed social networking. Turtles all the way down.)

I have no problem rendering unicode on my terminals. Unicode doesn't have to do with text/binary.

While it isn't the hugest challenge in security, unicode at the string level is not easy to get right. You have to do the right thing at the ends of strings when hanging combining codepoints are present. And just recently, suddenly a standard change allows certain combiners to appear before their target base character rather than after. Tons of combiners can be piled up on a character. There are plenty of icky corners where bad code could crash the stack on a poor implementation. There are 4 times as many whitespace characters, text that has different column directions, weird newline and hyphenation rules... just tons of detail-oriented work.

As an example, check out the Perl6 test suite sections that deal with unicode... not even including a bunch scattered around in other areas of the test suite.

(Really, email itself needs to just die... there just aren't any viable replacements... it's all corporate walled gardens or fractious gaggles of underfueled attempts at distributed social networking. Turtles all the way down.)

I have no problem rendering unicode on my terminals. Unicode doesn't have to do with text/binary.

While it isn't the hugest challenge in security, unicode at the string level is not easy to get right. You have to do the right thing at the ends of strings when hanging combining codepoints are present. And just recently, suddenly a standard change allows certain combiners to appear before their target base character rather than after. Tons of combiners can be piled up on a character. There are plenty of icky corners where bad code could crash the stack on a poor implementation. There are 4 times as many whitespace characters, text that has different column directions, weird newline and hyphenation rules... just tons of detail-oriented work.

As an example, check out the Perl6 test suite sections that deal with unicode... not even including a bunch scattered around in other areas of the test suite.

(Really, email itself needs to just die... there just aren't any viable replacements... it's all corporate walled gardens or fractious gaggles of underfueled attempts at distributed social networking. Turtles all the way down.)

I have no problem rendering unicode on my terminals. Unicode doesn't have to do with text/binary.

While it isn't the hugest challenge in security, unicode at the string level is not easy to get right. You have to do the right thing at the ends of strings when hanging combining codepoints are present. And just recently, suddenly a standard change allows certain combiners to appear before their target base character rather than after. Tons of combiners can be piled up on a character. There are plenty of icky corners where bad code could crash the stack on a poor implementation. There are 4 times as many whitespace characters, text that has different column directions, weird newline and hyphenation rules... just tons of detail-oriented work.

As an example, check out the Perl6 test suite sections that deal with unicode... not even including a bunch scattered around in other areas of the test suite.

(Really, email itself needs to just die... there just aren't any viable replacements... it's all corporate walled gardens or fractious gaggles of underfueled attempts at distributed social networking. Turtles all the way down.)

I have no problem rendering unicode on my terminals. Unicode doesn't have to do with text/binary.

While it isn't the hugest challenge in security, unicode at the string level is not easy to get right. You have to do the right thing at the ends of strings when hanging combining codepoints are present. And just recently, suddenly a standard change allows certain combiners to appear before their target base character rather than after. Tons of combiners can be piled up on a character. There are plenty of icky corners where bad code could crash the stack on a poor implementation. There are 4 times as many whitespace characters, text that has different column directions, weird newline and hyphenation rules... just tons of detail-oriented work.

As an example, check out the Perl6 test suite sections that deal with unicode... not even including a bunch scattered around in other areas of the test suite.

(Really, email itself needs to just die... there just aren't any viable replacements... it's all corporate walled gardens or fractious gaggles of underfueled attempts at distributed social networking. Turtles all the way down.)

I use Feedly to monitor around 100 RSS feeds. Every morning I peruse the headlines and read any stories of interest, the way people used to read the morning newspaper. There isn't really any reasonable alternative.....

There is a good alternative.

https://www.commafeed.com/

+ you can host on your own server

https://github.com/Athou/comma...

It turns out Stylish is now spyware, the new maintainer of Stylish made some deal with some analytics vermin called SimilarWeb.

https://www.ghacks.net/2017/01/04/major-stylish-add-on-changes-in-regards-to-privacy/

I'll be switching to Stylus, instead. An open source fork maintained on github. And already updated for FF 57 - which is good, because the web would suck even more if it wasn't possible to fix the worst of the CSS abominations perpetrated by web designers with little CSS overrides and mark them " !important;".

https://addons.mozilla.org/en-US/firefox/addon/styl-us/

https://github.com/openstyles/stylus

Stylus is also available for chromium.

uMatrix, Stylish

There's a WebExtensions version of uMatrix in the works. There's a WebExtensions fork of Stylish, so I imagine there will eventually be an official port of Stylish to WebExtensions for Firefox.

Grease Monkey too

TamperMonkey is a WebExtensions add-on similar to GreaseMonkey.

I'm a 40-year old on disability, you insensitive clod and FB and Twitter have a place alongside Slashdot and Digg to keep me connected to the world. I am consuming more and more and trying to get my parents out of the 20th century. I am working to get off disability, though. http://hackwrench.tripod.com/ and http://github.com/hackwrench

Source right here:
https://github.com/ms-iot/virt...

Example video:
https://www.youtube.com/watch?...

And they look equally good at any resolution, instead of superior at one res and absolute crap at any other (minus anything with sufficiently high PPI).

I would have said equally bad, rather than equally good. CRTs are still phosphor-based just like LCDs, which is to say that they still very much have a fixed native resolution, and everything else is fuzzy. It's just analog-fuzzy (bleed) instead of digitally-resampled-fuzzy, which means it looks better than a sufficiently bad scaler algorithm.

8-bit game consoles look like rubbish on anything else

To the extent that certain games look like rubbish, I would argue that it's because they actually look like rubbish, not because the CRT is somehow better. That said, at this point, it should be possible to trivially do an adequate transformation with any moderately powerful GPU. Who wants to hack a smart TV? :-)

and games using light guns only work with CRTs.

There are hardware hacks that can make them work now, but unmodded, that's true.

Part of the reason of switching to webextensions is to get a massive performance boost while at the same time limiting the damage that plugins cause such as lockups and memory leaks.

At the cost of losing my data. Sometimes when reaching for Ctrl+W or Ctrl+Tab, I accidentally press the adjacent Ctrl+Q. This activates the Quit or Exit command, which closes all tabs in Firefox for Linux. When I reopen the browser and click Restore Previous Session, the tabs come back, but data entered into unsubmitted forms is lost. I haven't tried it for every site in existence, but it never restores a comment form in a Slashdot D2 page correctly.

In the old days of Jetpack extensions, the Keybinder extension was useful for disabling Ctrl+Q. But Keybinder will not be ported to WebExtensions, and the comparable WebExtension Disable Ctrl-Q and Cmd-Q doesn't work in Linux because of bug 1325692, which will not be fixed in time for Firefox 57.

there will be 2 tab bars (the native horizontal one + crappy always-broken javascripty injected vertical one); no context menus on tabs

Both hiding the native tab strip and context menus are being worked on for Tree Style Tab. Your fears are unfounded.

tree style tab extension

Tree Style Tab will work with Firefox 57.

privacy

NoScript, Ghostery, uBlock Origin, etc. work with Firefox 57. So don't worry, be happy.

just add this to your hosts file...

I have a lot of respect for DJB. And he's pointed out theoretical attacks, and a few points where it's easy to make implementation mistakes when developing crypto code. The thing with theoretical attacks is that they seldom are practical. Most of the issues he brings up are pitfalls specific to the algorithms, and good implementations don't fall into them.

DJB also found weaknesses in AES; that doesn't mean it's likely to ever have a practical break. DJB is a researcher, and is always looking for better solutions. If we ever get around to replacing ECDSA, his research will be a valuable resource -- assuming that Quantum computing is the reason we're replacing ECDSA.

Implementation issues don't necessitate that ECDSA is weak; ECDSA is at the heart of most modern TLS certificates, including many of Google's, as well as being central to BitCoin.

U2F is a wrapper around OpenPGP in one direction. It could have easily been a wrapper around OpenPGP in its entire, but it's not.

I'm unable to find anything regarding OpenPGP in the FIDO U2F specifications Everything points to it being a cryptographic authentication. The communication protocol is utterly unlike OpenPGP.

All the way down to the hardware level, including open-source U2F token designs. (The link can do U2F, but has zero OpenPGP capability)

As far as I've been able to research (and I'm implementing FIDO U2F for my employer), U2F is entirely separate from OpenPGP.

If you have anything that says otherwise, I'd appreciate it.

Google used to offer revision control under the name Google Code. It no longer does. So which service do you recommend for hosting a private distributed revision control repository? Is $108 per year (source) a good deal?

Private paid Github works nicely if you aren't concerned about using someone else's machines. It's not very expensive and it works alright. I keep my local git repos in a Google drive for enhanced irony.

This just in: remote filesystems are not as good as distributed revisions control systems at being a distributed revision control systems. Film at 11.

Google used to offer revision control under the name Google Code. It no longer does. So which service do you recommend for hosting a private distributed revision control repository? Is $108 per year (source) a good deal?

And how well do popular distributed revision control systems handle things other than the relatively small, diff-friendly plain text files that make up computer program source code? Examples include design documents made with LibreOffice or large graphics files made with GIMP.

Greasemonkey is being worked on but it required a rewrite from scratch, so it may be a while.

• NoScript is migrating to the WebExtensions API.
• DownThemAll is, rather famously, not moving to WebExtensions API and is calling it quits.
• GreaseMonkey appears to be a migration-in-progress, although it doesn't look great; meanwhile TaperMonkey can be used as a work-around.
• Nuke Anything was last updated in 2014 and appears to be abandonware
• VideoDownloadHelper believes they will be able to migrate to WebExtension API by FF57
• Status-4-Ever might migrate to WebExtensions eventually, but probably not by FF57. Details here.
• Classic Theme Restorer is not migrating and will eventually die.
• UnMHT appears to be a big fat question mark - which is to say that my Google-fu has failed me.

Others?

And with the current situation where the users of a device is prevented from doing the changes they like to their devices including downgrading the OS the interest in Android goes down.

It's a sour situation right now when you aren't in control of the device you have bought. I can understand that there may be some constraints to at least prevent malware but the owner of the device shall be able to be in control of the device and not risk it being bricked.

A major reason for having more control over your device is to get rid of bloatware that the manufacturers have a habit of installing. Some bloatware is also a security risk for various reasons.

Only buy a phone that's supported by LineageOS. Then you get updated builds every Thursday. My phone, a Oneplus 2, only officially has Marshmallow. Thanks to LineageOS, I'm running Nougat. It's also more responsive, I get better battery life and I only had to install the bare minimum of Google apps needed for Play (mostly use APKUpdater and F-Droid anyway). Then I just root it with Magisk and still pass SafetyNet (I only care about Pokemon Go).

TL;DR: buy a LineageOS supported phone or an iPhone if you want regular updates.

Search on "oncologists would not have chemotherapy".

Boosting the bodies own defenses against cancer in various ways (including nutrition, intermittent fasting, immune-system tuning, etc.) is another approach at least generally without negative side effects -- wonder if Watson has been fed enough alternative data to recommend it (especially for prevention)?

Example: https://www.drfuhrman.com/lear...
"Cancer screening is promoted as preventive health, and while this may detect early forms of cancer so it can be treated earlier, it does not prevent the development of cancer and has minimal effects on reducing cancer deaths. A Nutritarian diet has the power to repair defects that can lead to cancer, detoxify carcinogens, cause cancer cell death, cut off blood supplies to growing tumors , and stimulate the immune system to recognize, repair abnormalities, and even fight and kill cancer cells. The vitamins, minerals, phytochemicals, and antioxidants found in a diet rich in vegetables, fruits, beans, nuts, and seeds is the key to prevention and even can play an important role in the treatment of various cancers."

Good luck with your own health care choices. It is hard to wade through all the conflicting information and conflict-of-interest. I wanted to make free software to help people make sense of conflicting health information -- but just not enough time given a need to earn money in other ways. What I could do with Watson hardware and that project's budget... (When I was at IBM Research around 2000 I proposed making an interactive display wall powered by an AI-like system to help people make complex decisions and better designs -- but as a contractor the idea did not go that far beyond a proof-of-concept with nine old Thinkpads that looked a lot like a Jeopardy screen, made when my supervisor went on a long vacation...)
https://web.archive.org/web/20...
https://github.com/pdfernhout/...

BootStomp's code:
https://github.com/ucsb-seclab...

UCSB's team site:
https://seclab.cs.ucsb.edu/aca...

Firefox works faster because when I accidentally press Ctrl+Q instead of Ctrl+Tab or Ctrl+W, it ends up using zero CPU because it quits, taking unsubmitted form data with it. I had used the Keybinder extension, but that will not be ported to WebExtensions. I would use the Disable Ctrl-Q and Cmd-Q extension, but bug 1325692 makes the Disable Ctrl-Q and Cmd-Q extension do nothing on either of my machines (Xubuntu 16.04 at work, Debian 9 at home).

The impression that I get is "We just rewrote our extension in Jetpack months ago. If you require us to now rewrite our Jetpack extension in WebExtensions, we quit."

From Keybinder README:

SORRY GUYS, BUT I'M AFRAID THIS IS THE END OF THE LINE.

I wanted to release a last update to address a couple bugs, and mkz's locale but I'm afraid this will be the last update to Keybinder. Mozilla's self-destruct course wth Firefox (coupled with not even having adopted all WebExtensions APIs yet) makes this addon impossible to maintain (and sadly, soon to cease working at all). Already many commands will not work (especially new ones) as XUL is being deprecated, and XUL keysets was the foundation this add-on relied on. I'm probably going to move to Vivaldi or something, I guess. Way to go, Mozilla.

Your other link was probably intended to be this site. They also have a GitHub page. The code itself is written in PHP in a procedural style, which in 2017 is offensively poor practice. No one should ever use that code under any circumstances, and in a just world the author would be legally enjoined from pursuing this profession.

He specifically mentioned a reason: Pentadactyl.

They've known for two years that the new API was coming. Have they built a WebExtensions version or not? Tridactyl is at least giving it a go.

He specifically mentioned a reason: Pentadactyl.

They've known for two years that the new API was coming. Have they built a WebExtensions version or not? Tridactyl is at least giving it a go.

Two versions of Firefox from now, they will jettison what made their browser great: the extensions.

Prove it. The extensions API is changing, that's all. I'm using the WebExtensions version of uBlock Origin (version 1.14.4) in Firefox 56 beta and it works fine. Tree Style Tab is another add-on people like and the WebExtensions version is in development.

Add-ons will either migrate to the new API or they won't. If WebExtensions APIs to support your pet add-on are missing, then get involved and add them. Mozilla wants you to.

What about following a development model like the Rust programming language has?

They have a variety of teams that work on various parts of the language and its ecosystem. One of the most important teams is the Rust Moderation Team, which enforces the Rust Code of Conduct. This code of conduct ensures a tolerant environment for all. Anyone who doesn't show tolerance is excluded.

They also make heavy use of GitHub, which is where they track the over 2,700 open issues that currently affect Rust. This also provides a collaborative environment for Rust's extremely diverse development team, which mainly consists of white males in their 20s, to work together on Rust.

It's also important to make sure that the language gets a lot of attention at places like Reddit, Hacker News and Stack Overflow. But remember, if anybody says anything critical about the language then those comments must be modded down. It's intolerant to say anything bad about Rust.

Java has been around a long time, and perhaps it's time for it to adopt a modern programming language development methodology like we've seen created by the Rust community. This approach has already worked well for Rust, causing it to become such a widely used language. It will surely work well for a language like Java, too.