saltymimir

The obvious culprit here are the LLMs, but I do wonder whether Github's social features, despite its flaws, have given developers fewer reasons to ask questions on SO?

Speaking from experience, every time I hit a wall with my projects, I would instinctively visit the project's repo first, and check on the issues / discussions page. More often than not, I was able to find someone with an adjacent problem and get close enough to a solution just by looking at the resolution. If it all failed, I would fall back to asking questions on the discussion forum first before even considering to visit SO.

Pleasantly surprised that this site’s still around. I remember seeing this back in college, and it was one of the catalysts that got me into building sites and this career in the first place.

(I’m 30 btw, so this site’s quite old by internet standards.)

These are the slides that are about to be presented (or has been presented already?) by some of the TC39 committee members.

Some genuinely interesting bits about how the committee sees the entire Javascript ecosystem today and what they envision the future will (probably) look like.

Ohh boy, as someone who works on a travel booking, service serving customers in Asia, this problem hits hard. I guess the answer depends on how you plan to handle the names once they got submitted.

I happen to be handing that data over to airlines, which has some of the less forgiving, yet fragmented name requirements. If you handle this incorrectly, your customer can't fly, even after they paid for the flight. And for those who say that this doesn't matter as much: It absolutely does. People do get confused by this more frequently than you think. I've seen people losing an entire trip that they saved for, all because of unclear naming requirements.

The way I deal with this is to provide a country and locale specific name fields. You don't have to detect the geolocation or track the user for this, just let them choose whatever locale setting they want, and give them the "sensible" layout. Here are some examples:

- In Vietnam, we use last name then first name.

- In Indonesia, we use first name, then last name, but also give an option to declare that the person doesn't have a last name.

- In Singapore, we use a single field to input the first name and last name.

Even when you've handled the layout convention carefully, the 3rd party you're handing the data to, if one exists, might not give the same care and attention that you do. In my case: some airlines just haven't gotten around the idea that some people simply don't have last names. When a person with a single name wants to fly, airlines want the customer to use the name for both first and last name (e.g. If the person's name is David, then the airline expects "David David"). If you require First Name and Last Name as the input, and don't elaborate on how to fill them, the customer might simply fill the last name with a dot (".") character. The airlines / any other 3rd party won't accept that. For this, I suggest to detail out the ways in which you handle the data and go talk to your providers, if any.

All in all, it's a pretty tough challenge, and the wisdom around this isn't going to fit inside a single HN post. I do commend you for actually thinking about this problem. Good Luck.

> As with previous Macedonian snake cults, the focus of worship at the temple was on fertility. Barren women would bring offerings to Glycon in hopes of becoming pregnant. According to Lucian, Alexander had less magical ways of causing pregnancy among his flock as well.

Wondering what they are :)

I decided to take a look at the redesigned mobile app after some time not using it. Can't believe how much worse it got.

I don't appreciate their move towards "social" feed sure, but the reader has genuinely gotten worse. I remember that it used to have the options to adjust:

- Line Height

- Page Width

- Text Alignment

- Fonts beyond the defaults (for paid subscribers, which I am one).

In the new app, it was all gone. Yet, I'm still paying the same premium price for it. The web app still has those perks, but it's probably because there hasn't been any update to it for the past 2 years or so.

I haven't had any use for the app for some years now. Like what many say in this thread, it's not that hard to build a system that replaces it well enough. You just need to make it scrape links, turn them to markdown (personal preference), and index the entire content for FTS in SQLite.

Thanks to the OP for reminding me to cancel my subscription. Now I just need to find a way to export my huge pocket archive before the subscription renews.