I contributed my opinion, which included highlighting a long standing pattern of problematic behavior, and labeling that behavior with a well understood classification.

To be clear, I respect Verstappen. Anyone with eyes and a brain has to. His talent is without question. But that (and rule 1) doesn’t make him immune to justifiable criticism.

Perhaps “fucking immature asshole” oversteps the words of rule 1 if you squint hard enough, but I maintain that it doesn’t violate the spirit of it.

Riveting contribution to the discussion.

Absolutely this. We saw this clearly in the lead up to his first driver’s championship. Everyone maintained we were seeing a more mature, more sportsman-like Max since then, but instead he just didn’t feel any pressure over the last few years. He still drives like a pissed off teenager and makes it clear that every time you try to pass him, he’d rather just force you out or crash into you, no matter what the circumstances.

He’s a fucking immature asshole. Always has been. Likely always will be.

deleted by creator

I’m not really a webdev, more backend or full stack at this point. I do know about C & C++ strong presence in firmware, OS, HPC, video gaming, and elsewhere.

But by the numbers there’s a lot more webdevs than any other kind out there, and that doesn’t even touch on NodeJS leaking into backend and elsewhere.

I really wonder about their methodology. JavaScript/Typescript is nearly ubiquitous in webdev, and has been making strides in the backend space for almost a decade now. No matter how you feel about it (yeah it’s terrible, I’ve been press-ganged into it this year) it’s a real force in the marketplace.

It’s super surprising to me it’s still behind C and C++.

Linkwarden and Wallabag are both excellent. Omnivore is up and coming, but might still be difficult to selfhost.

“We absolutely did everything that was meant to be done by that contract that was never signed.

“In English law, had we taken it to an English court, maybe we would have won.

“You know, that’s unjust enrichment. ‘You know, you didn’t sign the contract, but you took all this and you’re not delivering what you’re supposed to deliver.”

Pretty fucking rich. Piastri didn’t make Alpine not sign. And if they actually had their shit together they could have chosen not to give him the benefits without an unsigned contact, but instead they acted like it was signed and expected to still get the benefits?

How the fuck do they think they could have won the case? Like, if I offered a contact to Alpine that I would shit in front of their office and they would let me drive a season in F1, and then they didn’t sign, could I bring them to court after I shat on the sidewalk and demand they let me drive? Bonkers.

Ah yes, Alonso, famously good role model who tried to blackmail his employer to gain the upper hand over his co-worker.

He can fuck right off.

Max, what’s wrong? You’ve hardly touched your jar.

Real talk though: why would he ever rule out future possibilities?

I guess it depends on scale.

• FSearch

• Recoll

• TypeSense

Yeah, and to exploit it you need ring0 access in the kernel.

In other words, this isn’t an attack vector, it’s an escalation path. It escalates past the kernel, which is terrible to be sure, but if a hacker manages to get that deep in the first place, your system is already fucked.

+1 for Gitlab. As the number of developers increases the features of Gitlab will get more and more important. Only OP can say, but if they’re closer to 9 developers than 2, I think it’s a safe bet they’ll need the extra features sooner rather than later.

The Epic exclusive bullshit always stinks. Glad they are at least offering an option to get it from their website, even though the best solution is to release it everywhere.

Its dangerous to send goalposts flying around that fast, be careful or you’ll hurt yourself.

Your response is condescending, arguing from ignorance, and arguing in bad faith. I will reply this time, because once again you’re trying to build an argument on extremely shaky ground and I don’t enjoy people spreading ignorance unchallenged. However I won’t engage any further and feed whatever you think you’re getting from this.

I haven’t suggested that people should use Obsidian over OSS solutions. I was simply pointing out your argument against Obsidian’s architecture was poorly founded.

The data you’re insinuating will be lost is pure FUD. While the format isn’t standard markdown, none of the well implemented solutions are, because as you so rightly pointed out, markdown has little to no support for most of these features.

However, obsidian’s format is well documented and well understood. There are dozens of FOSS plugins and tools for converting or directly importing obsidian data to nearly every other solution. Due to obsidian’s popularity, it’s interoperability this way is often far superior to FOSS solutions’.

Content is your notes. In obsidian this is represented by markdown files in a flat filesystem. This format is already cross platform and doesn’t need to be exported.

Metadata is extracted information from your notes that makes processing the data more efficient. Tags, links, timestamp, keywords, titles, filenames, etc are metadata, stored in the metadata database. When you search for something in obsidian, or view the graph, or list files in a tag etc obsidian only opens the metadata database to process the request. It only opens the file for read/write.

Does this help?

Tell me, are you aware of the distinction between content and metadata?

Also, what do you mean, no official export? The data is already sitting on your filesystem in markdown…?

This isn’t really the case though. Obsidian uses a database for metadata, and therefore can extremely rapidly display, search, and find the correct file to open. It generally only opens a handful of files at a time.

I’ve used obsidian notes repos with hundreds of thousands of notes with no discernable performance impact. Something LogSeq certainly couldn’t do.

The complaint in the post you’ve linked is a) anecdotal and b) about the import process itself getting slow, which makes sense as obsidian is extracting the metadata.

I’ll always champion OSS software over proprietary, but claiming this is a huge failing of the obsidian design is just completely false. A metadata database fronting a flat filesystem architecture is very robust.

Edit: adding link to benchmark. https://www.goedel.io/p/interlude-obsidian-vs-100000

KobaldCPP or LocalAI will probably be the easiest way out of the box that has both image generation and LLMs.

I personally use vllm and HuggingChat, mostly because of vllm’s efficiency and speed increase.