owroomexorcist

Some magick belief systems call this state "gnosis".

Fair point. But if we're talking about a protocol not meant for the mainstream, is it really an attack vector to worry about?

What's wrong with not having TLS? If it's just for hobbiests to share text documents, why include a TLS layer?

No proof to suggest this is true, but I assume they were lying through their teeth.

> The Light Phone II uses a technology called "electronic paper," also commonly called E-Ink. It was made popular by e-reader devices like the Kindle. The screen is characterized by its low power requirements, high visibility & contrast, and wide viewing angle. When viewing the screen, there is no backlight like you would find on a smartphone.

4chan has better moderation that YouTube.

And guess who just bought another expensive IBM solution for payment management?

Another commenter summed up my feelings on PL/SQL. It's not that it's inherently bad, it's the bad practices that seem to follow.

Modernization to me (specifically in the context of the GC) means refactoring/rewriting systems to follow modern industry standards and practices. Things like proper version control, automated testing, automated/semi-automated deployments, and monitoring and logging.

I think there are major benefits in adopting these practices for both the Canadian public and the developers building/maintaining the solutions. Unfortunately, getting a budget to move the source code from a shared network drive to Git is next to impossible. And God forbid you want to spend time adding any sort of testing.

I work on one of the systems called out in the article. It's a fabulous disaster. I don't think it'll keel over and die anytime soon, but it absolutely should be phased out.

The problem is these big projects, like modernizing core social service systems, are given big budgets and big expectations. Then they start a big team to work on it, with short deadlines and not enough direction. At some point it is discovered that the legacy systems business logic is mostly undocumented/baked into a mainframe/functioning through sheer luck/nothing but PL/SQL and DB triggers. Then the several contacting companies are brought in to try and sort out the mess, solutions are purchased from billion dollar private companies (all of which have screwed over the Government of Canada one way or another), and project management is shuffled around as fast as HR can fill out the forms. After three years the money runs out, the project dies, and then we try again in two years.

The solution is never a slow and steady modernization. It's never small, focused teams working on improving or rebuilding individual components. It's never upgrading infrastructure, or moving to modern best practices.

It's always all or nothing. Solve the problems, without fixing them.