That type of question could also turn people off. We already have too many discussions where people are quick to jump to conclusions and attribute intent, rather than asking basic questions.
The form stopped accepting input at five characters. I could not enter a "zip code" for my country even if I wanted to.
Even if they fixed that, there are other issues. (You pretty much need to cross-reference it with a database, which assumes said database even exists.)
In the mid-1990's, I requested information from a major multinational corporation (IBM) that had a significant presence in my country. They somehow managed to mangle the six characters of a Canadian postal code, which alternates between letters and digits, into a five digit zip code. Making it even more perplexing, the envelope was addressed by hand and came from New York state. Some Americans seem to think that the rest of the world is a mirror of them, and will go through unusual contortions to maintain that belief. (To be fair: there is another level above that which is Anglo-centric, which allows for just enough variation between English speaking nations.)
I have seen websites that more-or-less takes the author's advice though. They are country specific. They are backed by the postal system's database. They present a list of addresses that match up with the postal code. They do not work very well when a particular address does not have a postal code. And yes, that happens.
> Each block of Python or Applescript that they generate for me is a much better learning tool than a book - I'm going through the code line by line and researching everything.
I have been doing something similar. In my case, I prefer reading reference documentation (more to the point, more accurate), but I can never figure out where to start. These LLMs allow me to dive in and direct my own learning, by guiding my readings of that documentation (i.e. the authoritative source).
I think there has been too much emphasis (from both the hypesters and doomsayers) on AI doing the work, rather than looking at how we can use it as a learning tool.
Couldn't agree more. On a large and open ended feature I sometimes struggle with where to start and end up researching something tangential. Cool learning, but not efficient.
Claude Code gives me a directory, usually something that works, and then I research the heck out of it. In that way I am more of an editor, which seems to be my stronger skill.
I agree with your post, but I wanted to point out one thing:
> People bill it as making a ton of usability compromises in the name of security, but that doesn't match my experience.
When you are talking about something like GrapheneOS, most of the people who are talking about usability compromises aren't worth listening to since they are looking for something that is pretty much the exact opposite of what GrapheneOS is trying to provide. While there are likely some legitimate criticisms in the mix, the compromises required for "works by default, for everyone" are pretty much the opposite of what GrapheneOS is.
> GrapheneOS always strikes me as "perfect is the enemy of good".
GrapheneOS, as it ships, is rather bleak but you also need to consider that it is addressing the concerns of a very broad audience. That ranges from people who want to completely get rid of data leaking apps to those who want the apps but expect them to be sandboxed. Shipping two different versions won't really help them. It would only make more work on their end, with the results only reflecting two extremes. You are going to have some people willing to put up with some apps, but not others. You are going to have some people wanting some of those apps feeding fake data, but not others.
It's probably best to think of GrapheneOS as a base system that you build up to serve your personal needs, rather than thinking of them shipping it in a "perfect" state. While a handful of people will be happy with it in its default state, many will install something like F-Droid along with a collection of privacy preserving apps. Many others will install the Google Play Store along with a personally curated list of apps that reflect their needs, providing or denying access to their data as they see fit.
I believe the "build up" approach is the only viable way to handle this situation since we are talking about a group of users who are actively seeking out a third-party OS since they are particular about their needs. This isn't the typical consumer who will (gleefully or begrudgingly) put up with whatever the device vendor feeds them.
Our approach is why we have a partnership with Motorola where we're working with Motorola and Qualcomm on improving security of the devices to meet our requirements. It takes longer to get things done the way we want but that's part of the purpose of GrapheneOS. For example, it took us longer to have our own network-based location and geocoding but now we have great implementations of both. Our network-based location currently closely matches iOS but is going to have full offline support developed for it. We're working on our own local model text-to-speech at the moment too, although our focus is currently Android 16 QPR3 related work as a higher priority which delayed it. We do plan to overhaul or replace all the legacy AOSP apps, but our priority has been working on things people can't simply replace by installing more apps.
> I just have not yet been convinced I should actually care.
I'm not out to convince you since my reasons are unlikely to apply to you. There are some of us who want privacy for privacy's sake. We respect the social boundaries of other people, and find those who don't respect our social boundaries creepy. We don't much care one way or the other if those people are out to exploit us or to harm us. It is the act itself that we consider violating.
> We still have CBC radio that broadcast weather reports, and whether reports are still available on the internet.
Commercial radio/television broadcasts are not the same thing since they do not offer continuous weather broadcasts. Getting weather information from the Internet is better in most respects, but it is not always the best medium to receive such information. I am a regular user of the Weatheradio service during the summer months, and have been through one situation where it most likely saved lives.
> I think we have to not maintain things that are older tech and unused and focus on things that are the future.
The problem is that we are ditching older tech without finding a viable replacement. I find it difficult to associate that approach with focusing on the future. I find it easier to associate it with forgetting lessons we learned the hard way.
> I use proprietary stuff like Apple for these parts of my life. A new Apple device is usually a non-event: charge it, authenticate, wait for the back to restore while you go about your business.
Most of the author's criticisms were centered on avoiding account creation and third-party apps. I'm not sure I would give Apple the benefit of the doubt here since the motivations are different: Apple is far more interested in locking customers into their own ecosystem. On the Android front, that isn't all that different from getting a Pixel. Of course, getting an Android based Samsung adds an extra company who wants to do the same as well as selling space to third parties.
While Android being more open does add complexity, it is mostly limited to those who buy devices produced by another vendor or those who choose to exercise their freedom (e.g. by choosing to install a third-party version of Android, or installing a third-party "app store", or developing their own software).
that isn't all that different from getting a Pixel.
Paradox is, that with Pixel device you can get most freedom and security togather. Installation of GrapheneOS is easiest custom ROM installation that could possibly be.
I tried it, Graphene isn't really a good alternative because the built in apps are so bad that you end up needing to install the Pixel/Google versions anyway.
If I have to install Google Messages for RCS, Google Calendar, Google Contacts, Pixel Camera (which forces you to use Google Photos for basic functionality), … where is the benefit?
If I have to turn Graphene into a Pixel to make it usable, and I did, there’s not much point. And the apps are 90% of the time very noticeably better on iOS, so overall turns into a very bad trade.
You still get much better privacy with GrapheneOS even if you install Google apps since they are sandboxed; they don't have access to unique device identifiers and you can control what Google can access by adjusting its permissions, as opposed to having full reign to do whatever it wants. Also you don't have to use all the Google apps, plenty of open source and/or privacy respecting alternatives out there.
Pixel Camera only needs Google Photos for the photo previewer, everything else works without it or you can install gcam services provider to use any gallery you want
> If I have to install Google Messages for RCS, Google Calendar, Google Contacts, Pixel Camera (which forces you to use Google Photos for basic functionality), … where is the benefit?
I am not sure why would you have to install messages has nobody uses RCS these days.
As for calendars and contacts, I am struggling to see the added value over the fossify alternatives, hence I don't have them anymore on my smartphones.
Pixel camera and google photos are nice to get the most out of tye pixel camera but thanksfully grapheneOS lets you use them without access to network. Stock Pixel rom doesn't allow you to do that. That is a major difference imho.
> Pixel Camera (which forces you to use Google Photos for basic functionality)
I disabled Google Photos but I didn't notice any issues with Camera except for not being able to open the photo just taken from the camera interface. Am I missing something else?
Which one if I may ask? I'm looking for one to get out of RCS reminders and also to avoid receiving emergency messages which come through even if I turn them off in Google messages. The local authorities overuse it, I get several per month now.
I think it's because they got blamed for not warning everyone with the Valencia floods last year but it's really ridiculous now. Now they blow up everyone's phone just when there's going to be a bit of wind.
and you get absolutely nothing in return. Yeah you will have root access sometimes. But other than that, android is not opensource anymore.
I mean, it never was because you had hundreds (no exaggeration [1]) closed-binary blobs running (not to mention a whole OS on things like radio and camera, running on their own SoC), but now you cannot get even close to a proper of the userspace since google already anounced they will not be mainlining anything back to AOSP
> and you get absolutely nothing in return. Yeah you will have root access sometimes.
You get improved privacy and security, at least on some fronts. By default, GrapheneOS does not provide root access and recommends against rooting the device. Is there a trade-off? Certainly. Security and privacy are always at conflict with what a completely open platform can provide. Given the amount of access to personal information that goes through our devices and the number of bad actors out there (both behaving legally and illicitly), some people believe
it is worth the price. At least GrapheneOS offers more transparency than Android or iOS.
The bit about clamping down on open source, that is very much disappointing. I doubt that it is going to go away entirely in Android. On the other hand, hopefully it will provide incentives for companies to explore developing more open alternatives and consumers to explore buying more open alternatives. It won't be a huge market, but many of us have avoided growing so dependent upon the current platforms that we couldn't simply walk away.
You can actually use most Apple devices without signing in. There are obviously a lot of benefits to the ecosystem but you can enjoy the hardware etc. without signing especially on Mac. For iPhone you'd need to learn to side load apps but it's doable.
You don't need an Apple account to back up an entire iPhone and restore it onto a new one, keeping almost all settings. They've kept the local iTunes method working from day 1. Idk how you do this in Android, sounds like most people sync everything to Google.
Getting downvoted for speaking the truth. HN loves to twist its nose every time someone praises a closed-source solution but falls head over heels for anyone claiming to work for a FAANG. Hypocrisy thy name is HN.
I've used Android phones for a long time. A couple of years ago I got an iPad to run an app only available on iOS. Getting that iPad running was more painful and frustrating than any of the dozen Android devices I've set up over the years.
That sounds like Linux users complaining about Windows Server or vice versa. iPad is trivial to get running but it is not the same as an Android tablet, and if you try to use your Android experience you will have issues.
Not so trivial that I didn't struggle with it for an hour. I'm not an Android power user. (I think?) I'm not even particularly a fan of Android. It's just the (hot take) least bad option I've tried.
More to the point, it seems reasonable to design for onboarding brand new users. That was never a strength of Linux, which most Linux fans would probably acknowledge. What ever happened to "it just works".
> That was never a strength of Linux, which most Linux fans would probably acknowledge.
If you are comparing apples-to-apples (e.g. setting up pre-installed Linux verses pre-installed Windows, or installing Linux to installing Windows), I would argue that Linux has been in the lead for many years. Setting up a reasonable desktop distribution (Fedora, Ubuntu, etc.) is no more and no less technical. Linux distributions won't encourage you to create online accounts, try to upsell you online services, or bombard you with questions about privacy settings.
From my last experience with macOS: on a technical front, macOS is simpler to reinstall. The online account setup and upselling is far less intrusive (perhaps to the point where you can legitimately consider it as a beneficial setup step for the end user). Perhaps macOS has the lead, but it is a marginal one.
Believe me, I wish I had documented it. I didn't realize that this would be surprising or controversial until I described the experience later to others. Some people basically didn't believe me.
The basic flavor was that I spent at least an hour getting a working apple account and getting signed into it, and I used at least two other devices to achieve that.
I do vividly recall that whenever I performed the final successful account verification, rather than seeing a success message, I saw a page or webview that just had a huge XML document in it. I only knew that attempt worked after I just tried logging in again. But that was one papercut out of dozens from my hazy recollection.
If I ever set up another Apple thing, I'll take photos, but it will probably work perfectly then. Oh well.
I don't understand why the author is intent on pinning the ever changing orientation of the letters on architects. Wright's intent would have been in the architectural drawings. Everything after that, including the original installation, would be the responsibility of the person who installed the lettering. I've seen much more obvious errors (e.g. spelling errors) occur during the installation of similar signage ... things that would not have made it to the final architectural drawings.
reply