Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)JA
Posts
0
Comments
108
Joined
2 yr. ago

  • Matrix is open protocol, everybody is free to build their own clients. Maintainers of any one implementation are free to choose code to include in their project. And people can fork Element if they don't like the way it is going.

    Maybe Element developers are not great in including external contribution… but still nothing else seems to implement Matrix that well.

    No other client seems feature-complete. I wish I could use NeoChat instead of Matrix, but it still cannot even handle encrypted conversations properly. Are they rejecting contributions too?

  • Differences between 2.4 and 2.6 were quite big, I don't think there was another such big change in kernel releases any time later. But that was also the time when Linux was transitioning from being a hobby project (already useful for serious stuff) to being a serious professional operating system – the last moment for major refactoring.

    Linux kernel is still changing and being constantly refactored, but now the changes tend to be more gradual and version numbers matter much less.

  • Then my recent research was wrong - I tried to make it work and failed. Then read somewhere it is not supported. But it can be that it is valid EFI configuration, but not supported by Windows and some firmware implementations.
    I don't think I have ever seen an EFI firmware which was not broken in one way or another.

  • On EFI systems all bootloaders are supposed to reside on a single partition. EFI does not support multiple 'EFI system partitions', so operating systems have to share a single one. And this is usually not a problem if it is the one Windows choose. The problem most often is broken EFI firmware which fails to correctly handle adding and removing boot entries. Or Windows, which fails to boot if anything changes (disk order and such), even though everything is still available.

  • Jira was ok until they dropped self-hosting option. Why should I keep internal development data at third party server?

    Other Atlassian software, though... oh, what a mess. And it only was getting worse with any new release. I am glad we have dumped it all.

  • And a lot of users' frustration, especially on more niche platforms (Linux, ARM, etc.) - things look much better on release when the code have been regularly compiled and, hopefully tested, on all platforms, not just the one the lead developer uses.

  • Every major distro uses systemd, because before that it was nearly impossible to properly implement things that distros have to provide.
    Most startup scripts were incredible set of hacks to make services behave. Those were very inefficient (they could not be efficient being shell scripts calling other commands for various simple repetitive tasks) and would often break when circumstances were different from ideal.

    Systemd just makes building Linux distribution much easier, and the resulting system is more reliable, more consistent and more flexible. Why would distro developers chose anything else?

  • That depends on tree species and damage.
    Willow tree would probably survive that without a problem, most other trees won't. Some could be saved with appropriate protective measures, like trimming the roots.