- I had being using krypton, with the private key being on my iPhone, and am now using secretive. Never had much of an issue with not having access to my private key. We made rolling out public keys to the servers very easy by using the gitlab key file. So when I get a new Macbook I'd just need to create a new key and upload it to gitlab. We have multiple devops that can run the playbook to roll it out to the servers. And if they have a new Macbook I roll it out for them. And we don't have that many Macbook upgrades anyway.
- Yeah I've also build a Phoniebox a couple of years ago for my kid. It has physical buttons, RFID cards or chips (some hidden in plush toys) and works very much like tonies, but with much easier access to anything you want to put on it. It's all in a wooden box including speakers. I've later extended it with a powerbank.
- The article might have some points, but there is also a lot of complaining just for the sake of it.
- One the homescreen seeing the search as a clear button is useful for most users. The swipe down is just not easy to find and remember. The dots shown when swiping through homescreens is actually much clearer if you don't have so many pages.
- Same goes for the pull down search bar. It took me a long time to remember that. And then in the system settings it always took me some time to find it again. That it's the same gesture as reload in other apps made it even more confusing. Now it's right where you thumb is.
- The pulsating buttons - I haven't even seen them. And I switch during the public beta phase. Normally buttons get hidden by your thumb when you press them.
- And then yeah a lot of things look different now. We had that before when we switch to the previous design language and people were just complaining as much.
- All of the presidents are elected. The bodies electing them are always part of a democratic process. Just because it's indirect doesn't make it less democratic. the president of the commission is even covered twice at it gets nominated by the council and the elected by the parliament. The parliament we voted for, the council are the head of states who might also not come from a direct democratic process.
- Biggest problem is with the approach of doing a revolution, while evolution is possible. Reactivity is mentioned in the article and examples are given with frameworks that would need a rewrite of anything you have in react and relearning everything for the team.
But it's really not needed - you can just use signals in react with the preact-signals package (works with preact and react and standalone) which has been created 3 years ago: https://preactjs.com/blog/introducing-signals It can even skip the virtual dom and diffing.
The issue is not React per se. Just look at what the ecosystem has to offer. You can also speed up your loading times by using preact. And if you don't like a compile step use a package like htm and tagged templates for a JSXish syntax. And then move your "store" outside of react with signals etc. There is enough innovation happening, no need to always look at the other side.
- We haven't been saved by procrastination. We literally were saying "oh that's a new version, we are always behind anyway". Of course everything was still checked, but actually having the latest version on packages is almost never needed and we rather update when we have to (because version is old) instead of when there is a new version. Nothing new is that awesome.
- Yeah it could have a better explanation. I added like three bases and always just got a list of "file name" and was wondering how to add different data. Was expecting something like MS access based on markdown tables. Maybe if the documentation would have an example of how you would create a collection of documents and then have a view on that with a base it would be clearer.
- If the app is as elegant as the website I have to pass. The menubar is hidden at the start - and also when you scroll back up. FAQ and Github Stars menu items are overlapping, so you could be clicking the wrong one. The icon looks like a light/dark theme switcher, but is not. Actually there is no light theme at all on the webpage, which depending on your environment can make it hard to read. I'm assuming the app is the same. Looks like I'm too old or not the target audience or both.
Also the overwrite option was never used. You'd expect a client to copy a file, get and error if the target exists, ask user if it's ok, send same copy with overwrite flag set to true. In reality clients are doing all steps manually and delete the target before copying.
It was satisfying seeing it work at the end, but you really need to test all the clients in addition to just implementing the standard.