yayoohooyahoo

That's exactly what the article says... so yes apparently that's what it is

I guess you stopped reading there and missed that part:

> Yes, we see the irony! We encourage you to inspect our installer first. That's the whole point of vet. You can read the installer's source code install.sh

Interesting that one of the top comments is so negative. Do you guys not like your job at all? I've done that all my life, I love it, and I still have plenty of time to enjoy life and do other stuff.

Is it not the same as a hard link (which I believe are supported on Mac too)?

> - there is no way to store preferences (such as: don't put comments in code)

There is by using custom instructions in settings.

Joplin for permanent retention of information and large notes, and handwritten notebook for daily to-dos.

If anything needs to be done another day I move it to a to-do in Joplin

I wish backward compatibility was a thing in js library development but clearly there's nothing fun in keeping things working, so developers break API all the time for no reasons.

I don't how many time I was dealing with a breaking changes for trivial things like making an API prettier, renaming a few functions, a few parameters here and there because it suits the author's aesthetic sensibilities.

They're of course perfectly free to do this and being open source they don't owe anything to anybody, but I still wish that there was some degree of responsibility towards the end user. Or else why even release the code publicly? End users don't care *at all* how pretty the API is, we just want things to work.

Modern apps these days often end up needing to render complex layouts and rich text, so you end up needing QWebview anyway. At least that's been my experience creating desktop apps lately.

The title implies they fixed a method in Ruby itself which would have been a lot more interesting than this article.

The point is that this website is not applicable to anyone, anywhere, since the core message is strictly US-only.

If the authors were aware of this, they may have focused their message on, eg the children's age, which should be more universal.

You'd think they'd do a quick check on the name before committing to it. I remember using Lingo with Macromedia Director, it was a nice little language

I quit ST over poor typescript support - did it get any better in recent versions?