There's also Irys (from Alan Schaller). It's more open than Glass, as it's a freemium model, but it's also more closed at the same time, as it doesn't offer a web-based version. It's probably even more photographer-oriented than Glass. For something truly open, there's Pixelfed. All those platforms have their pros and cons, especially regarding the audience. Personally, I publish all my photos on my own website and syndicate them to (in order of preference): Glass, Pixelfed, Instagram, Irys.
This sounds great, especially as it's linked to the IC card. Unfortunately, I couldn't find anything similar for JR West or JR Kyushu, which I will be using in the next few weeks. Hopefully they will implement the same system in the future.
But you still have to pick up the tickets at the machine. Additionally, my mobile phone internet is not recognized as "being in Japan", so I can't access the QR code needed for the ticket without wifi. You can work around it (save the QR code when you have wifi), but it all just seems so inefficient compared to all the countries where you can _book_ your tickets using a mobile app.
Vacation is also never mentioned in those discussions or comparisons. 10 days in the US vs. 20-30 (+ 8-14 public holidays, depending on the state) in Germany is much more important for _me_ than the net income.
HTML vs. CSS is a separation of technologies. If HTML was really only about the content and the CSS was only about styling, we wouldn't have to write div soups to style our websites (.container-wrapper .container .container-inner { /* "separation" */ }) and we wouldn't have to adjust our HTML when we change the layout.
> Blames are easy. There's zero need to try to keep your tree "looking nice".
I don't care about how the tree looks like. But I do care about keeping the number of commits low _because_ it makes blames easier.
> In the future when I'm hunting down a problem I almost never care about what feature or fix this was a part of - e.g. the PR - I care entirely about the context of the developers mind when he committed that specific line of code.
I've mostly made the opposite experience. Many developers don't have the knowledge or confidence to use "amend" etc. consciously, so it leads to a mass of useless "fix error", "forgot something", "add tests" and "implement PR reviews" commits. This makes blame more difficult. I also agree: sometimes a squashed commit message doesn't help me understand the code of line I'm blaming. But not having squashed the commit mostly wouldn't help me anyway. Instead, I try to avoid this problem beforehand, by making sure that the PR itself contains all the information (via PR description and/or code comments). Recently I've reviewed a "Fix scrollbar" PR. The "what" is clear. The "why" (= "it's broken") _sounds_ sufficient, but I was missing information like "how exactly is it broken" and "why does this change fix it". That's the kind of stuff I might blame in a year from now, and now it's part of the Git history.
In 2014, I have written a just for fun plugin in about 2 hours (check out my write-up [1]). I've followed the "How to make an IntelliJ IDEA plugin in less than 30 minutes" [2] guide back then. Unfortunately, this guide seems to be outdated, but now there's an official guide [3].
Where did I apply it to everything? To falsify an argument you only need one counterexample. I'm happy with all the alternatives (as mentioned before), but I'm not happy with a claim that can be falsified with the first example.
Thanks for mentioning some alternatives, but I've just checked the first example and it does not support custom domains (which Fastmail does), so it does not "provide more".
After getting a Windows Tablet, I was looking hard for a good epub/pdf reader with annotations. To my surprise, Edge was by far the best reader out there. However, a few weeks later an update killed the annotations feature - I just couldn't save them anymore. None of the support-provided solutions has worked. I then started using Calibre to convert my epub files into azn3 and open them in the Windows Kindle app, which is also quite nice.
He also wrote an official post on Glass: https://glass.photo/highlights/remembering-om