Got to have that high thread count, burst rate throughout. Does it have the cooled bobbin?

Well I don’t use obsidian as all. But as a matter of opening and linking notes, I use this tool because I like it, and it allows me to reference two separate vaults without issue.

obsidian.nvim

Not sure if the eye roll indicates sarcasm or real incredulity but the other girls were Italian. So I guess, when in Paris do as Romans do.

The “sneaking to steal a cookie” pose?

It looks well designed. I wonder if it will find purchase among users.

Welcome to The Grand Barkapest Hotel.

The names of the two pictured: Laurel and Yanni.

🤨

I don’t disagree. I’m just saying the distribution of workload has an impact on what looks a good idea or too hard.

Because it changes the risk benefit profile of the choice. Imagine that your backend is 70k hours of work and your interface is 1k hours. Managing two interfaces isn’t going to seem like nearly as big an ask so other variables may get a higher weight. Of course those numbers are contrived for the sake of explanation, but if you still don’t think there are any circumstances in which others may value the benefits of native applications over cross platform applications, that’s fine. My point is simply that it may not seem like the trouble of managing two frontends is as insurmountable as you may think.

But I have a hard time believing you don’t think it is possible that there are any situations where one might reasonably believe it worth it.

Sure. Bitwarden provides its own backend. So that backend represents some portion of their code base. In the case of Voyager, Lemmy provides the backend. So that backend isn’t a portion of your code. So Voyager is 100% frontend. Bitwarden is < 100% frontend.

Recognizing you as a PWA developer; and a damn fine one, I get your take. But surely you are aware there are limitations to using PWA’s or other cross platform libraries. Sometimes maintaining multiple UI’s is the right choice. Especially if very little of your code is actually the front end. For you, Voyager is pretty much 100% front end, so that’s 100% of your code. But for Bitwarden, the interface is a much smaller proportion.

While the subjective assessment that quote handling in yaml is worse than bash is understandable, it is really just two of many many cases where quotes complicate things. And for a pretty good reason. They are used to isolate strings in many languages, even prose. They, therefore, always get special handling in lexical analysis. Understanding which languages use single quotes, double quotes, backticks, heredocs, etc and when to use them is really just part of the game or the struggle I guess.

That sounds like a skill issue. Something isn’t bad because you don’t understand it. Suggesting quoting is an issue for yaml is beyond the pale; it happens to be an issue everywhere.

I agree AND I think he really stresses the conjunctions WITH far too much inflection.

While white hats are sometimes paid, it is generally in bounties. It just means being adversarial without trying to be unethical. So, find the hole but tell the person that made it rather than the crooks that will exploit it.

A red team on the other hand is a known value. They are the bad guys in a simulation. The military exercises similarly or any organization that wants to test defenses. Red team == the make believe bad guys.

Generally they do. Of course they are responsible for all the dumb shit in the world, but also most of the good and interesting.

Young people don’t get dumber as they age. They get smarter, wiser, better able to cope with adversity. Setting sore back and knees aside adults are doing alright when it comes to raising the young.

You could probably change the ssd but the memory is on the SoC.

I have no ties to Newfoundland, but I absolutely love their unique phrases. Looks pretty nice too.