Now if it supported org files too…
Runterwählen ist kein Gegenargument.
[Verifying my cryptographic key: openpgp4fpr:941D456ED3A38A3B1DBEAB2BC8A2CCD4F1AE5C21]
Now if it supported org files too…
There is no difference other than a shiny logo and a “contract” that promises you that the random stranger will take care. I promise that I will take care too.
If you still think there is a relevant difference, please tell me. To me, it looks like you don’t fully understand what a password manager stored on other people’s computers does.
A cloud password manager is a database with your passwords hosted on a stranger’s computer. Why wouldn’t I be just as trustworthy as any other stranger on the internet?
My questions are to those of you who self-host, firstly: why?
Would you give me your password database? I promise to encrypt it!
If your goal is to ever talk to people about open source software, that’s going to create a lot of unnecessary confusion.
I guess that my definition of open source is not that uncommon, given that the terms “free software” and “libre software” exist and are rather well-established by this point.
People often use the OSI’s Open Source Definition when using the term “open source”.
Which is one of the possible definitions. Mine is “you can see the code”. Everything else falls into “free software”.
I think the new one remains closed. Sadly, not locked away.
What is “actually open source”, if “here’s the source code” is not?
You can make embarrassing mistakes in virtually any programming language that’s not too esoteric.
When I still used Python for prototyping (today, I usually use Go for that), it happened much too often that I did this:
if foo:
bar()
foobar() # syntax error
In Lisp, however, both errors are much harder to make (not even considering GNU Emacs’s superb auto-indentation - which is what most Lispers use these days, as far as I know):
(when foo) ;; <- obvious!
(bar))
(when foo
(bar)
(foobar) ;; <- still valid
(quux)) ;; <- also still valid
Dynamic typing is the source of very amazing errors, see JavaScript.
Feel free, it’s still out there!
I still write more Perl than Python these days.
Still easier to refactor than Python. ;-)
For all of those, Lisp is the more logical choice. Plus, whitespace as syntax is the worst possible design decision.
A viable alternative is Guix, which uses Scheme for its scripts and could also use the Hurd kernel instead of Linux, but works the same.
Wait until you see the Lisp community. But yes, Rust is currently in its “why are there even any other languages lol” phase. Just wait.
Friends don’t let friends use a dark mode.
I understand the reluctance but it feels to me like arguing “we should just stick with COBOL because it works.”
For those depending on COBOL code that does the job and has been doing it just well for a few decades, there are approximately zero good reasons to not stick with it.
+1 for NewsBlur. Its filtering is just plain awesome.