The Windows 10 equivalent, Timeline, got discontinued in 2021. At this point in time it is unknown whether Microsoft will retrofit Recall into Windows 10. Knowing Microsoft it is safe to assume they’ll try anything for profit.

https://arstechnica.com/gadgets/2024/05/microsofts-new-recall-feature-will-record-everything-you-do-on-your-pc/

I like CryptPad by Framasoft, for big stuff.

“Could”.

Indeed. I’m not totally oblivious. Luckily I have learned a few phrases and figures of speech. But it seems I had a way harder time learning those than my school mates who weren’t on the spectrum.

I took that AQ-10 test, and also pondered this particular question. No, I suck at reading between the lines. Give it to me straight, please. No beating around no bush.

Figures of speech pose an equal problem: I may just lack the cultural awareness that allistic people enjoy, but it’s rare for me to understand a common phrase, and more often than not I’ll invent a completely new one.

Reading between lines: do allistic people do that? How? Is it some skill I can learn?

Thank you! As I’m learning more about my own autism, I’m quite willing to share experiences.

No, they aren’t. You can switch to their Universe patches anytime, at your own risk. If you want Canonical to mitigate that risk for you, you pay. Simple, really.

With some of my smaller clients, the CIO is the same as the CTO and the same as the IT Director. There, IT is developers, too.

Enterprise will cause a boom in hiring VBA devs to migrate legacy apps to other programming languages, then hear Microsoft will extend support for a few more years, then fire all those VBA devs again. If Microsoft had some wits, they’d create easy tools to migrate VBA to C#.

Wouldn’t it face the exact same security issues as VBA, with drive-by installs of obfuscated malware and executions of arbitrary code?

Sure! I wrote all about it over on Medium: https://medium.com/@aev_software/java-jakarta-soap-wsdl-client-fails-to-read-soap-message-for-logging-38087a63ea6d

To summarize: custom logging handlers failed after upgrading to version 3, because the underlying implementation that exports a message as a SOAP message is broken.

That indeed is annoying.

Oh dear. That would work. But I’d lose the paper!

Dinosaur here. I started building web sites when JavaScript had yet to be invented. If articles like this exist for new features introduced since EcmaScript 5, I’m all ears.

Cool. Just what I need: yet another version of a JDK/JRE to test. I feel like I spend more time testing these for regressions than I spend developing functionality for my clients. Anyway. Good for Adoptium and those who found and solved this bug.

I started using Jakarta half a year ago, as it was promised to be the de-facto way to build a SOAP client that speaks to a WSDL server. Oh boy: growing pains. Did not expect that 2 decades of developer experience in Java EE would amount to nothing, for the people who implemented Jakarta. As impressive as the effort may be, the inexplicable regressions we faced when we got forced to upgrade to version 3 proved quite cumbersome.

So they say. Remember they also promised not to track users, keep trackers away, and keep your browsing experience ad-free. They came back from that within a year.

One would switch to a free JVM when other JVMs change their licenses from free to paid. OpenJ9 was the first free JVM to which I got introduced. Knowing it was based on the work by IBM, known for high performance and low memory footprint, it was a simple choice.

:(

May his loved ones find solace in sharing those memories of him, that inspire them most.