Kobo Sync as it's called in the documentation (https://github.com/janeczku/calibre-web/wiki/Kobo-Integratio...) works very well, and is very easily enabled (updating a single line in a config file on the ereader that appears when you mount it on your computer).
It will convert books to Kepub automatically and you can select to only sync certain shelfs.
There is no difference to a .Add() function, that's true but even for strings you wouldn't have an Add function. It would be an Append() most likely which explains much more what is happening.
And verbosity helps, forcing users verbosity helps the general level of quality. Programmers could overestimate themselves and think they are doing it correctly. Looking back in my code from a year ago I see things I should have done differently. I like languages that avoid me making real dumb mistakes
IRC has no chat history either, right. I get the simplicity of IRC but searchable history is a bonus for Discord. As long as the service is available, searching is kinda possible. With irc you have to find out which bot provides history, which is then usually split over multiple files
My client dies the logging, and I can e.g. grep decade old logs. I’m not sure if you can get same level of access to Discord logs (=export them). I guess Discord bot that logs everything as a historian is a partial solution (I guess log bot cannot catch DMs).
I usually doubt about this, am I missing out on useful tools because I like my terminal based environment. Editing is much better when you have tools that are keyboard first, I think everyone agrees about that.
My conclusion now about an integrated environment (like an IDE) versus a more handbuilt (like vim) is that a handbuilt one requires the dev to know it's tools. With an IDE you are seduced to trust the magic black box, that the box will help you. This makes it that when stuff goes different then expected (usually user error), you are lost.
With a more custom environment you are pushed to learn your tools. And while this is not a given, I like this approach more. I might miss some fancy new tools, but the tools I do use, I *know*. This could be done with an IDE but is more forced in a terminal based flow.
Never said it can't be good in an IDE. But there is something that draws people to vim, which isn't just the cool factor. IDEs often even have vim modes but vim itself is a nicer editor.
Same way an IDE is a nicer debugger, linter, profiler, test run platform...
I think the fork has to do with the following item:
> Unlike SerenityOS, Ladybird will have a relaxed NIH policy (instead of "no 3rd party code!"), and will leverage the greater OSS ecosystem.
SerenityOS wants to be an OS from scratch, to see how to do things better from existing implementations. When ladybird wants to target that OS as well, using 3rd party libraries would make it hard to stay compatible. Which is easier to do on just MacOS and Linux.
It will convert books to Kepub automatically and you can select to only sync certain shelfs.