or

"Sounds great! Let's fly our Cirrus SF50 Vision and hand deliver to Andrew Kelley."

kdb is mentioned. Possible it was added after your comment in the last 30 mins, but the article is about open source not proprietary.

I control-F'ed and didn't find it before I wrote that comment. I searched for KDB and APL, but found nothing.

EDIT: yeah that sentence is new. I think some of the sentences around Influx being the "first" have been adjusted too now saying it is the first "mainstream" and called other db's niche. it's also a little off. KDB+ is more popular in large banks and trading firms than HFT places.

You'll enjoy set theory then. Just call the first set aleph-null.

Interesting. The date at the bottom of the article shows 06/05/2024, which is this one? https://github.com/microsoft/vscode-docs/blob/main/docs/devc... renamed from your link in 2022.

All of this to say, I wish articles were upfront on original publication date.

> It is implemented locally

I am afraid nothing Microsoft works on is local anymore.

Not trusting Microsoft when they something runs locally probably means you shouldn't be using Windows, period.

Shadow of Yserbius anyone?

might want to check the status page [1]. As of writing this, it has a 27% uptime calculation. I realize this is probably a young upstart and it could be something simple as changing something on the API backend that is causing the status page to fail, but something to consider.

1. https://ntfy.statuspage.io

After reading the article, a fun thought popped into my head. Who has the right to determine if a project like this is dead or EOL'd? Is it the original author to make that declaration or when it is under BSD license, wide community-use, and support -- when does a project like this truly become dead or EOL'd?

Well EOL usually means something like “end of official support, active development, and security patches” so the owner/creator/foundation usually chooses when.

“Dead” is usually a colloquialism, so if enough people call it dead, it is.

The corollary is that if you didn't have any support to begin with, as is the case with most open source projects, EOL is pretty meaningless concept.

The OSS analogue would be “unmaintained” I guess.

Whoever owns the canonical repo (also, any relevant trademarks) has a lot of power in this situation. The community can certainly fork it, but then you start asking if the fork is a new project.

The article backs on the claim in the title, making the title kind of clickbait:

"Is YARA really dead? Despite the dramatic title of this post, YARA is not actually dead. I’m aware that many people and organizations rely on YARA to get important work done, and I don’t want to let them down.

YARA is still being maintained, and future releases will include bug fixes and minor features. However, don’t expect new large features or modules. All efforts to enhance YARA, including the addition of new modules, will now focus on YARA-X."

The official maintainers say they won't be maintaining the repo any more. Anyone else is always welcome to fork and form their own project to continue to maintain the software.

"By observing the trees and their embodied experience of time, I have been able to see the inadequacy of my wristwatch"

Until you're are late for your next teams or zoom call.