• 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle

  • The problem is the Gnome team doesn’t give a flying rat’s ass about maintaining a stable api. I’ve never bothered with extensions because even the most basic stuff only works for one or two versions. The neovim team is pretty committed to backwards compatibility and following standards for interoperability like LSP these days, so it’s much easier for third parties to maintain a large set of extended functionality at this point. If they acted like the gnome team, your status bar plugin would break every other update.



  • Yes the PowerPoint ui is much better. It takes more space but it’s much easier to find features you might not use as frequently.

    I haven’t done much switching between calc and excel. Formatting issues come up when making or editing a document in libreoffice and opening it in MS office. Especially with impress, the position and sizes of objects will be very different between the two programs. This makes opening a presentation from impress with PowerPoint on a different computer impractical.


  • I think it comes down to 2 main reasons, and some members of the libreoffice suite definitely do a better job than others.

    1. Comparability with MS Office, it’s really difficult to use these programs when you can’t reliably collaborate with people using the de-facto standard office software. Impress is exceptionally bad at this.

    2. User interface clunkines, the ribbon ui Microsoft uses in modern office versions is really nice, and makes finding the actions you need really easy. This is coming from someone who used office 03 and 07, it’s not just a learning thing, it’s a better design.

    These issues are definitely a bigger deal on some parts of the suite than others. I’ve found Calc to be a solid replacement for Excel, but when I’m making spreadsheets I’m not fiddling with complex formatting at all. Impress is on the opposite end of the spectrum. It has horrible comparability with PowerPoint, and I need to get things looking just right when I make a presentation. It’s difficult to find even basic formatting options. I could probably solve the usability issues by reading a few tutorials, but the comparability issues hold me back from putting the time in, since I have no idea how a presentation will look when someone loads it in PowerPoint anyway.





  • A dedicated server is needed because something needs to keep a catalog of the smart devices available on your network and ideally be accessible to many people in one household. You could make a system that went phone -> device but you would need to set up each device on each phone you wanted to use, which isn’t a great user experience. You could also run into issues where devices would need to handle multiple conflicting commands from different users coming in at once. Since smart devices are usually trying to use as little power as possible, that extra complexity would hurt you in that department. The third reason is that having a separate server enables automated workflows that would depend on an always online server that orchestrates multiple devices. For example, let’s say you have some automatic insulating blinds, a smart thermostat. You want to raise and lower the blinds to maximize your energy efficiency. Since you have the dedicated server, that server can check the temperature set point of your thermostat, current weather, and sunrise\sunset times. If it’s sunny out, and your set point is higher than the outdoor temperature, the server can raise the blinds to let warm sunlight in, and vice versa. If only your phone could control the devices a workflow like this couldn’t work when you were out of the house.




  • I wouldn’t recommend it. The Git documentation itself doesn’t recommend rebase for more than moving a few unpushed commits to the front of a branch you are updating. Using it by default instead of merge requires you to use --force-push as part of your workflow which can lead to confusing situations when multiple developers end up commiting to the same branch, and at worst can lead to catastrophic data loss. The only benefit is a cleaner history graph, which is rarely used anyway, and you can always make the history graph easier to read with a gui without incuring any of the problems of rebase.