frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

alpr.watch

https://alpr.watch/
536•theamk•5h ago•268 comments

Prediction: AI will make formal verification go mainstream

https://martin.kleppmann.com/2025/12/08/ai-formal-verification.html
66•evankhoury•1h ago•28 comments

No Graphics API

https://www.sebastianaaltonen.com/blog/no-graphics-api
259•ryandrake•3h ago•40 comments

GPT Image 1.5

https://openai.com/index/new-chatgpt-images-is-here/
214•charlierguo•4h ago•117 comments

Ty: A fast Python type checker and LSP

https://astral.sh/blog/ty
76•gavide•1h ago•11 comments

MIT professor shot at his Massachusetts home dies

https://www.bbc.com/news/articles/cly08y25688o
24•mosura•33m ago•0 comments

40 percent of fMRI signals do not correspond to actual brain activity

https://www.tum.de/en/news-and-events/all-news/press-releases/details/40-percent-of-mri-signals-d...
357•geox•8h ago•156 comments

Mozilla appoints new CEO Anthony Enzor-Demeo

https://blog.mozilla.org/en/mozilla/leadership/mozillas-next-chapter-anthony-enzor-demeo-new-ceo/
359•recvonline•8h ago•526 comments

Thin desires are eating life

https://www.joanwestenberg.com/thin-desires-are-eating-your-life/
227•mitchbob•21h ago•86 comments

The World Happiness Report is beset with methodological problems

https://yaschamounk.substack.com/p/the-world-happiness-report-is-a-sham
66•thatoneengineer•22h ago•84 comments

Writing a blatant Telegram clone using Qt, QML and Rust. And C++

https://kemble.net/blog/provoke/
56•tempodox•6h ago•30 comments

GitHub will begin charging for self-hosted action runners on March 2026

https://github.blog/changelog/2025-12-16-coming-soon-simpler-pricing-and-a-better-experience-for-...
366•nklow•4h ago•147 comments

Sega Channel: VGHF Recovers over 100 Sega Channel ROMs (and More)

https://gamehistory.org/segachannel/
194•wicket•9h ago•27 comments

Chat-tails: Throwback terminal chat, built on Tailscale

https://tailscale.com/blog/chat-tails-terminal-chat
11•nulbyte•1h ago•1 comments

Nvidia Nemotron 3 Family of Models

https://research.nvidia.com/labs/nemotron/Nemotron-3/
101•ewt-nv•1d ago•12 comments

Show HN: Sqlit – A lazygit-style TUI for SQL databases

https://github.com/Maxteabag/sqlit
86•MaxTeabag•1d ago•9 comments

Artie (YC S23) Is Hiring Senior Enterprise AES

https://www.ycombinator.com/companies/artie/jobs/HyaHWUs-senior-enterprise-ae
1•j-cheong•5h ago

Context: Odin’s Most Misunderstood Feature

https://www.gingerbill.org/article/2025/12/15/odins-most-misunderstood-feature-context/
25•davikr•1d ago•0 comments

Letta Code

https://www.letta.com/blog/letta-code
15•ascorbic•1h ago•1 comments

Creating custom yellow handshake emojis with zero-width joiners

https://blog.alexbeals.com/posts/custom-yellow-handshake-emojis-with-zero-width-joiners
44•dado3212•21h ago•2 comments

Show HN: Deterministic PCIe Diagnostics for GPUs on Linux

https://github.com/parallelArchitect/gpu-pcie-diagnostic
6•gpu_systems•1h ago•1 comments

Rust GCC back end: Why and how

https://blog.guillaume-gomez.fr/articles/2025-12-15+Rust+GCC+backend%3A+Why+and+how
150•ahlCVA•8h ago•70 comments

How geometry is fundamental for chess

https://lichess.org/@/RuyLopez1000/blog/how-geometry-is-fundamental-for-chess/h31wwhUX
43•fzliu•5d ago•16 comments

30 Years of <Br> Tags

https://www.artmann.co/articles/30-years-of-br-tags
123•FragrantRiver•3d ago•25 comments

Vibe coding creates fatigue?

https://www.tabulamag.com/p/too-fast-to-think-the-hidden-fatigue
118•rom16384•3h ago•118 comments

Pizlix: Memory Safe Linux from Scratch

https://fil-c.org/pizlix
55•nullbyte808•2d ago•17 comments

Purrtran – ᓚᘏᗢ – A Programming Language for Cat People

https://github.com/cmontella/purrtran
213•simonpure•3d ago•31 comments

Full Unicode Search at 50× ICU Speed with AVX‑512

https://ashvardanian.com/posts/search-utf8/
178•ashvardanian•1d ago•69 comments

Confuse some SSH bots and make botters block you

https://mirror.newsdump.org/confuse-some-ssh-bots.html
38•Bender•5d ago•14 comments

The Beauty of Dissonance

https://www.plough.com/en/topics/culture/music/the-beauty-of-dissonance
7•tintinnabula•3d ago•0 comments
Open in hackernews

Japan to revise romanization rules for first time in 70 years

https://www.japantimes.co.jp/news/2025/08/21/japan/panel-hepburn-style-romanization/
68•rgovostes•13h ago

Comments

rfarley04•13h ago
I live in Thailand and I cannot get over the fact that romanization is (seemingly?) completely unstandardized. Even government signage uses different English spelling of Thai words.
kazinator•1h ago
In the first place, "romanization" of English is unstandardized! Or was that unstandardised?
adastra22•1h ago
It tends to be standardized within a single country.
qingcharles•49m ago
Whoosh :)
merelysounds•43m ago
Standardizations can be notoriously inconsistent[1], disregarded[2] or evolve fast[3].

There’s a surprising amount of interesting articles on wikipedia about that.

[1]: https://en.wikipedia.org/wiki/Ough_(orthography)#Spelling_re...

[2]: https://en.wikipedia.org/wiki/Eye_dialect

[3]: https://en.wikipedia.org/wiki/Sensational_spelling

Stevvo•1h ago
Thailand, famously, was never colonized by European powers. Everywhere else, some colonial administrator standardized a system of romanization.
floren•33m ago
Japan was not colonized, although it was briefly occupied.
Theofrastus•13h ago
I'm honestly surprised Hepburn wasn't the official standard yet. It sounds way closer to the spoken sounds, at least to my western ears.

> The council’s recommendation also adopts Hepburn spellings for し, じ and つ as shi, ji, and tsu, compared to the Kunrei spellings of si, zi and tu.

I could imagine si, zi and tu sound closer to the spoken sounds to Mandarin speakers.

wyan•12h ago
Not closer to the spoken sounds, closer to English orthography.
Theofrastus•12h ago
Native German speaker here. It fits very well here, too
mono442•10h ago
It works better with other European languages' orthography too.
mytailorisrich•12h ago
I don't know the details history of the system's development, however I notice that with Kunrei everything spelling is neatly 2 characters while with Hepburn it may be 2 or 3 characters:

Kunrei: ki si ti ni hi mi

Hepburn: ki shi chi ni hi mi

The politics of the issue is obviously that Hepburn is older and an American system while Nihon and Kunrei are very purposely domestic (Nihon "is much more regular than Hepburn romanization, and unlike Hepburn's system, it makes no effort to make itself easier to pronounce for English-speakers" [1]). Apparently, Hepburn was later imposed by US occupying forces in 1945.

Perhaps 80 years is long enough and suitable to effect the change officially with no loss of face.

[1] https://en.wikipedia.org/wiki/Nihon-shiki

Theofrastus•12h ago
The political aspect might be a big part of why and how the systems are chosen. Didn't know about that!
jinushaun•1h ago
Politics aside, Hepburn is better. You can’t seriously say you prefer “konniti-ha” and “susi-wo tabemasu”
xigoi•1h ago
Should we also change other languages’ orthographies to make them easier to pronounce for English speakers? “Bonzhoor” instead of “Bonjour”?
QuercusMax•1h ago
If French didn't use the Roman alphabet natively, you might have a point.

At some point you might as well use Roman characters the way the Cherokee alphabet does - which is to say, uses some of the shapes without paying attention to what sounds they made in English.

wewtyflakes•1h ago
English is the top language spoken in all the world; it would be lovely to facilitate better communication with that population.
QuercusMax•57m ago
And the way English generally uses the Roman alphabet (obviously excluding the zillions of irregularities) isn't that far off from how most European languages use the Roman alphabet.

I'd expect that Spanish, German and French speakers would benefit just as much as English speakers from these changes.

dragonwriter•54m ago
> And the way English generally uses the Roman alphabet (obviously excluding the zillions of irregularities) isn't that far off from how most European languages use the Roman alphabet.

Its not far off from the union of how all other European languages use the Roman alphabet, would be closer to accurate.

QuercusMax•50m ago
Sure, but the point is this isn't really making romanized Japanese more English-like. It's making it more similar to how just about every other language already uses the Roman alphabet. This isn't an Anglo-centric thing, it's just good common sense - unless your goal is to make it harder to pronounce your language properly, which seems like an obvious own-goal.
rdtsc•59m ago
> Should we also change other languages’ orthographies to make them easier to pronounce for English speakers? “Bonzhoor” instead of “Bonjour”?

Already done.

- Komen ça va? - Mo byin, mærsi.

We don't have anything against https://en.wikipedia.org/wiki/Louisiana_Creole, do we?

ronsor•58m ago
Japanese people don't read romanized Japanese. Even Japanese learners don't read romanized Japanese.

Romanization is, by and large, a thing that exists for people who already know European/Western languages.

devnullbrain•21m ago
>English

Use *h₂enǵʰ-ish please.

JuniperMesos•35m ago
"Better" depends on what you care about. _konniti-wa_ (which is the Kunrei-siki romanization of こんにちは, _konniti-ha_ is Nihon-shiki form that preserves the irregular use of は as topic-marking /wa/) and _susi-o_ (again, Kunrei-siki ignores a native script orthographic irregularity and romanizes を as _o_ not _wo_ ) are more consistent with the native phonological system of Japanese. In Japanese coronal consonants like /t/ and /s/ are regularly palatalized to /tS/ and /S/ before the vowel /i/, and there's no reason to treat _chi_ and _ti_ as meaningfully different sequences of sounds. Linguists writing about Japanese phonology use it instead of Hepburn for good reason.

Obviously, being more transparent to English-readers is also a reasonable goal a romanization system might have, and if that's your goal the Hepburn is a better system. I don't have a strong opinion about which system the Japanese government should treat as official, and realistically neither one is going to go away. But it's simply not the case that Hepburn is a better romanization scheme for every purpose.

ranger_danger•1h ago
> It sounds way closer to the spoken sounds, at least to my western ears.

That's the thing... to some other non-English language speakers, the existing/old romanization method actually is more accurate regarding how the letters would be pronounced to them, especially coming from languages that don't have the same e.g. [ch] or [ts] sounds as written with Hepburn.

The one technical downside I would say to this change is, 1:1 machine transliteration is no longer possible with Hepburn.

usrnm•1h ago
The popularity of Hepburn has a lot more to do with the English language than the Japanese language
shikon7•45m ago
You mean, if you would apply the inverse of the standard romanization of Mandarin, the resulting sound would be closer to the Japanese sound, if starting from the Kunrei spelling than if starting from the Hepburn spelling?
ChrisArchitect•5h ago
Previously in 2024 (?):

https://news.ycombinator.com/item?id=39624972

dang•2h ago
Thanks! Macroexpanded:

English-friendly Romanization system proposed for Japanese language - https://news.ycombinator.com/item?id=42606969 - Jan 2025 (23 comments)

Japan to revise official romanization rules for first time in 70 years - https://news.ycombinator.com/item?id=39624972 - March 2024 (97 comments)

kazinator•1h ago
Hepburn is poorly supported in some input methods, like on Windows. If you want to type kōen or whatever, you really have to work for that ō. It's better now on mobile devices and MacOS (what I'm using now): I just long-pressed o and picked ō from a pop-up.
adastra22•1h ago
Is that part of Hepburn? It is not mentioned in the article, nor by most explainers that I’m familiar with.
QuercusMax•43m ago
The article says the new style says that you can use either a macron or a doubled letter, but it's not clear if that's supported for keyboard input on various platforms.
Etheryte•1h ago
That's one aspect I really love about macOS. I'm from a small country so nearly no one makes hardware with our exact layout, but with macOS I can always just long press to fill in the gaps. I just wish all apps used native inputs, not some weird half-baked solution they built themselves.
bitwize•1h ago
Compose o dash. Windows doesn't have an easy way to map in the compose key (usually ralt)?

big if true, jesus christ microsoft

Lammy•58m ago
https://github.com/ell1010/wincompose is like the first thing I install on any new Windows machine.
gpvos•47m ago
Nope. When on Windows I tend to use one of the US International or the Pseudo VT320 layout from https://keyboards.jargon-file.org/ .
bryanlarsen•40m ago
Note: bitwize is talking about how to do it on Linux. Which is the best way in my biased opinion. Perhaps not the best mapping for people who use it regularly but is awesome for those who use it irregularly. We can usually guess how to do weird diacritics without having to look it up.
qingcharles•47m ago
What's the best way to type Japanese on Windows? (I have a QWERTY keyboard)

On mobile I just switch to the hiragana keyboard, but that obviously isn't a sane option on desktop unless I'm clicking all the characters with a mouse?

kazinator•14m ago
I don't know now, but for the longest time, Google made a much better Japanese IME for Windows than Microsoft ("Google Japanese Input"). I started using it when running into reliability issues, like disappearing kanji dictionary, or frozen switching between roman and hiragana.

Assuming Microsoft's Japanese IME is still a dumpster fire, and the Google one has not succumbed to Googleshitification, that would be a way to go.

To enable the Microsoft IME there are some rituals to go through like adding the Japanese language and then a Japanese keyboard under that. It will download some materials, like fonts and dictionaries. A reboot is typically not required, I think, unless you make Japanese the primary language.

Once you have the keyboard, LeftShift + LeftAlt chord goes among the input methods. Ctrl + CapsLock toggles hiragana/romaji input. I think these are the same for Google or MS input.

junar•12m ago
Using the example from the top-level comment, you would install an IME, switch to hiragana mode, start typing "kouen" and convert to kanji when you see the right suggestion.

It might sound complicated at first, but you can do it pretty fast once you get used to it.

https://learn.microsoft.com/en-us/globalization/input/japane...

johnea•11m ago
Hepburn also allows the use of the double vowel, in this case: kooen
phantasmish•42m ago
Oh no.

This is going to make finding specific Japanese game roms even more annoying.

lbotos•23m ago
Elaborate? I’m not following.
phantasmish•2m ago
For people not familiar with Japanese, finding any info about a Japanese-language game can be a pain. They may have a Japanese representation, an official romanized name, a community romanized name using a different system… plus may also go by an outright English-language name, in some circles, which may (or may not) overlap with the name of an English-language port (if it exists). Then consider that some games have pretty extreme and confusing name variants in various editions or on different platforms, and those may go by different names in different contexts.

You can see the same game go by three different names on a community forum, Wikipedia, and a catalogue of games + md5sums for a system (you might think the md5sum could act as a Rosetta Stone here… but less so than you’d think, especially in the specific context of an English speaker and Japanese games, as you sometimes need some specific, old, oddball and slightly-broken dump of a game to get the one a particular English patch requires… and god knows what name you’ll find that under, but probably not the same md5sum as a clean dump)

The only bright spot in this is that if you can find a Japanese game on Wikipedia the very first superscript-citation almost always lists the official Japanese title in Japanese script on hover. That’s a life saver. (Presumably all of this is easier if you know at least some Japanese)

Though after I posted my comment I realized they mean they’re switching to another existing system (which I think is already widely used in gaming circles? Not sure though) which isn’t so bad. At least it’s not another one being added to the mix.

qingcharles•24m ago
They need to do the same for a bunch of languages, e.g. Arabic.
WalterBright•12m ago
Please bring back Fraktur.