jjani

They are, but they have in common that a huge portion of things written about them online in English - especially about these cultural subjects - are very outdated or otherwise unrepresentative. Like I said, most of that comment is written all the time about SK too, and they're effectively untrue. There would need to be strong evidence that such reports about Japan are any different.

My entire social circle is Korean and I've never seen a same-age couple (or one where the girl is older) use 오빠.

It does, on NYE there's huge groups of kids around going out for the first time.

Alcohol consumption in Korea among young adults has cratered over the last 10 years.

That isn't about the social hierarchy, it's about the switch. If the couple would always use 존댓말 - which is not the norm nowadays but still a large enough minority that it's not weird - then obviously it'd be a switch to 반말 that would be shocking; in fact it would sound even worse to suddenly do so during a fight.

> As an obvious foreigner, you are 100% exempt from all this. In fact, if you get it right, it'll make them feel weird and they'll try to avoid that.

Are you sure? In Korea, everyone who seriously cares about this stuff absolutely prefer it if you get all of it right. Of course, plenty of people (probably most under 30) secretly hate it and are therefore thankful if you don't get it right as it gives them a semi-out to be slightly more loose as well.

> I read a story once about someone who went to McDonalds in Japanese, and the clerk flipped the menu to the English side. The person flipped it back over, and the clerk flipped it to English again! They simply couldn't believe the foreigner could read it.

> And I've read stories of people who didn't act like a "gaijin" (foreigner) and people didn't know how to interact with them, and the person finally just accepted it and acted like they expected a gaijin to act, and then everything was fine.

Not trying to be rude but this pretty much tells me your first claim is likely wrong. Plenty of the exact same stories abound about Korea, especially online, yet they're both outdated and very cherry-picked. They're real, they happen (I've experienced them myself), but 99% of people would strongly prefer it if you were fluent in the language and followed every procedure as "normally" as possible.

Never heard someone saying 님 sounds creepy, it's very commonplace in tech companies, Kakao was far from the first to introduce this. I've worked at a place where everyone was ..님 and no one cared.

Just so you know, the system has been adjusted a while ago so that new 빠른 no longer occur.

And it wouldn't matter anyway; the changes from the top are already having their effect, elementary school kids are starting to consistently use 만 나이 with each other.

That's only viable if the quality of the outputs can be automatically graded, reliably. GP's case sounds like one where that's probably possible, but for lots of specific tasks that isn't feasible, including the other ones he names:

> write poetry, give me advice on cooking, or translate to German

Google does not expose their reasoning any more. They give "thought summaries" which provide effectively zero value. [1][2]

[1] https://ai.google.dev/gemini-api/docs/thinking#summaries [2] https://discuss.ai.google.dev/t/massive-regression-detailed-...

No clue, it very much did it for me, but given the lack of new comments since March they might have silently stopped doing that. That they never responded there nor even bothered to close the thread fits squarely with GP's experience with their non-existent customer service :)

Had no idea that this was possible on Mac either, never seen any other app do this, though commonplace on Windows.

> I don't recall if Google Cloud verified my ID in the past, though

It generally does not. No idea if there are edge cases where it does, but that's definitely not the norm for the average user.

If by reasoning you mean showing CoT, Gemini and OA are the same in this regard - neither provides it, not through the UI nor through the API. The "summaries" both provide have zero value and should be treated as non-existent.

Anthropic exposes reasoning, which has become a big reason to use them for reasoning tasks over the other two despite their pricing. Rather ironic when the other two have been pushing reasoning much harder.

Bit strange to see such new accounts already priming everyone to think this is acceptable and normal, which it isn't, hence OA having started doing this months ago and still not a single other provider has it, despite offering just as powerful models. It's not like Google and Anthropic have launched their own Worldcoin either.

OpenAI introduced this with the public availability of o3, so no.

It's also the only LLM provider which has this.

What OpenAI has that the others don't is SamA's insatiable thirst for everyone's biometric data.

GP did mention this :)

> I've never heard of that's a 'partner' of the largest AI company and Worldcoin founder

Great, then they should probably not be allowed to do business in the EU, as they're unable to do so in a legal manner.

Similarly: https://github.com/getcursor/cursor/issues/1052

It reads nothing like ChatGPT, the "on the flip" is a dead giveaway that it isn't. Strange comment.

Sure, replace "the most tax" with "the highest tax rate", as that was your sentence.

> And GGP talked about how "a minority of taxpayers finance the government".

Your reply was to GP, and it wasn't one pointing that out.

OpenAI does, by virtue of doing business in the EU.

"The top 1 percent of tax payers pays the most tax" is a tautology. GP talked about the uber wealthy.

They're talking about "facilitated by the App Store ecosystem" so it includes everything from online shopping to advertising. 1 billion iPhone users spending/generating on average $1000 on their phones per year? Seems reasonable. I think even if you just consider Amazon, the Amazons of elsewhere, supermarkets etc, Ali, it goes on and on. Their combined revenue from people buying stuff on their iPhones, iPads, Mac apps downloaded through the app store will get you a great length towards $1.3 trillion.

People are not spending $1.3 trillion per year on IAPs, it's not the game whales as the other comment suggests.

Hi, early user here :) Liking the product so far. We just started using the CLI parts for our RN app, with your cloud translations.

Few things to put on your roadmap if they aren't on it yet:

- Would like it if we could set the model per language. I'm sure you do your best trying to find the best one for each language, but in our experience some of them aren't optimal yet.

- Multiple source languages would be cool. Example: It can make sense to have JA as source for KO but EN as source for FR. Or probably better, sending both (e.g. EN + JA when doing KO).

- MCP doesn't seem to be working (we posted a log on the discord)

- We seem to have spotted cases where key names were taken into account a little too much when translating, but understand this is super hard to tune and can be fixed by improving our keys.

It is a problem with Supabase as it's a problem inherent to RLS, and Supabase pushes very hard for RLS to increase adoption by non-technical users like the person who this article is about. You're right that they give lots of warnings to mitigate the issue but the people who they're targeting with RLS are exactly those who ignore them - see this post. This is nothing new and not a consequence of vibe coding. It's the contradiction between RLS being a technology that requires much more discipline to use securely compared to its alternative (a layer inbetween client and DB), yet is marketed and most used by beginners who lack the ability to maintain this.

It doesn't have to be full fat, it can be literally anything as long as it provides a backend layer inbetween the DB and the FE. It can be a single Typescript file that uses literally whatever the LLM defaults to, probably Express given its training materials, or Hono for something more modern, or any of the 1000 other options.

Just "vibe coding" something minimal in a Cloudflare Worker, or even, ironically, a Supabase Edge Function that directly connects to the DB would 9 out of 10 times lead to something more secure than using RLS. The LLM will always default to RLS when using Supabase as that's what they promote the hardest in marketing materials, so that's what it's trained on.

It would not be surprising if half of the pre-"vibe coding" mobile apps that use Supabase have the exact same security holes. This is really nothing new, it's inherent to RLS being just the technology that sounds incredibly convenient to beginners yet comes with the right footguns they are likely to miss, despite Supabase doing its best with warnings in the UI. I think SB is a cool company that means well, but RLS will never be reliable. It takes too much discipline to use safely and reliably on any meaningful project, and at that point it's simpler to just roll an API or a few serverless functions.

If you can quote anyone well-known saying we'd be replacing programmers in 6 months back in 2019, I'd be interested to read it.

I also don't prefer them, but a clear benefit is the squatting pose being a lot healthier than the standard sitting on a Western toilet. Somewhat fixable by a squatty potty, but those aren't in public restrooms.