tantalic

If they win, the US government collected taxes they shouldn't and those would be returned. Saying the "US taxpayer will pay for it" is equivalent to saying the US taxpayer pays for your tax refund. (And also, Nintendo is a "US taxpayer.")

Twenty years ago, I was strongly anti IDE and pro text editor. In the last ~10 years or so text editors have gained features previously only found in IDEs and IDEs have improved their performance and brought in features from text editors. I would argue the distinction between text editors and IDEs at this point is academic.

There's an old saying in Tennessee - I know it's in Texas, probably in Tennessee...

I'm (still) very interested about this project. Two years ago, I came across this when setting up a Raspberry Pi based "home lab" Kubernetes cluster (https://github.com/tantalic/shaving-yaks). I ran into some issues (I believe all Raspberry Pi specific) and ended up going with k0s. While I am happy with k0s, I do wish Kairos worked out for me and I might have to give it a try again soon.

They had me at "4 months of work just to make a stupid pun."

I have been a happy Base user since 2011. I don't use it all that often, but anytime I need to explore a database file or take a CSV and turn it into a database for some investigation it is the first tool I turn to. Happy to be able to be able to pay for an upgrade after this long!

FINALLY

Being cool and getting a lot of views/clicks should not be confused.

I am a bit surprised the proposal doesn't suggest using a hash (such as SHA-2) rather than directly passing the email address.

Parse (https://parseplatform.org)

As someone who almost always has a text editor open, I have paid for many over the years. In particular multiple versions of TextMate and multiple versions of Sublime Text. I have also been responsible for getting licenses for my team(s) at work.

I now find that the editor I am happiest with is VS Code, not because it's free but because of the extensibility and community support it brings. I'd happily pay for it - but I think the nature of it being free is what has brought so much community support to it.

While that is true, it requires a very specific understanding of both intellectual property law and the inner workings of development tooling that is pretty rare in practice. As such, companies are generally conservative in such decisions. Most organizations have a single list of licenses allowed for use rather than getting into specific use cases for specific licenses. These types of environments will generally limit uptake of copyleft tools.

All that said, I'm not convinced the licensing is the issue here (although I wish them the best). We are in a world that has grown accustom to free development tools and building a commercially viable business in tooling is incredibly difficult. I'm always amazed by how many developers I know who make a living by creating software yet are unwilling to pay for software themselves.

Is there any way to trial the self hosted version? I'm rather interested, partially as someone who doesn't like the idea of putting such data "in the cloud." (For products with less sensitive data I would try the monthly subscription first.) I'm assuming not, and that the self hosted is probably a small percentage of your customer base. But worth asking!

This is problem of misaligned incentives: if you are making a security scanner the last thing you want to do is miss a vulnerability. The result is many false positives.

Becoming a standard requires independent, working implementations. So this is very much part of the process.

https://www.w3.org/2021/Process-20211102/#implementation-exp....

At what point do we ask if training from “datasets crawled from the internet” is itself the greater poison?

It's interesting seeing the general consensus that it understands the structure/style/form of jokes but not humor. I suspect anyone with kids will recognize this phase of human development.

The sad part is that my initial reaction is: "only 57?"

> and unlike SQLite, we do not substitute it with an unclear alternative

This portion of the statement is harsh, and I think the project could do better by stating what they are doing and why, rather than focusing on what SQLite is doing and why it is bad.

I would say that it seems feasible (to me) that SQLite's "Code Of Ethics" works for a small team, open-source, closed-contribution model but wouldn't work for the open-contribution model that libSQL is trying to achieve.

From a quick look at the repository: his last comment on an issue was 8 hours ago and his last commit was in July.

I suspect you may know this, but for the sake of others reading the comments, this "version" of NetNewsWire started from the original developer of NetNewsWire (Brent Simmons). NetNewsWire had passed through two other owners and the final owner (BlackPixel) returned the brand back to Brent Simmons who had already started a new, open source RSS reader which has since been known as NetNewsWire 5 (but doesn't share code with the previous versions).

If you're interested in the full history you can find the details here: https://netnewswire.com/history

Almost???

The infotainment screen can be used with or without touch. This allows them to remove a chip without loosing functionality.

For some of their enthusiast focused models many BMW drivers prefer the non-touch interface. I have had a BMW with a touch screen for 11.5 months now and a finger hasn’t touched the screen yet.

On the other hand, would you be surprised to learn the .NET runtime includes a ringtone?

I think it's fair to say that a few years ago GitLab was very much inspired by Github's design. However the project has had a focus on adding additional, tightly-integrated features and I'd say in the last couple of years Github has been more inspired by GitLab than the other way around.

Noms has gone pretty quiet since the acquisition. Dolt is based on noms (not sure how much is has diverged) and much more active: https://github.com/liquidata-inc/dolt

Based on their job listing it looks like native apps for each platform: https://quill.chat/jobs/

The technique used here currently has a known issue with iOS 13: https://github.com/caddyserver/caddy/issues/2771

If you loose control of the private key it limits the time an attacker could use it.