A mistake that killed Japan's software industry? (2023)

Original Article ↗ Hacker News Discussion ↗

Quality of Japanese Software and UX

  • Many commenters describe Japanese consumer and web software as clunky, ugly, and unintuitive (e.g., travel, ticketing, ATMs), especially compared to Western apps.
  • Others say some apps and systems (convenience-store software, game software, some enterprise tools) work reliably and do their job well.
  • Japanese visual communication is often very dense: posters, timetables, and websites cram in text, diagrams, and options. Some locals and visitors find this efficient; others find it overwhelming and “2005-style.”

Cultural and Organizational Factors

  • Recurrent themes: extreme hierarchy, risk aversion, face-saving, and consensus processes (e.g., nemawashi) that slow decisions and punish standing out.
  • Developers are often rotated between departments, lack formal CS background, and are treated as interchangeable factory workers; “looking busy” is valued more than outcomes.
  • Perfectionism is debated: some see it as myth outside narrow crafts; others say it’s applied to different domains (rules, behavior) rather than clean cities or tidy offices.

Keiretsu, Capital, and Policy

  • Original article’s keiretsu thesis is challenged: some see keiretsu as symptom of deeper risk aversion; others argue capital flight and better returns abroad (China, India, SK) mattered more.
  • Large conglomerates historically focused on export-facing hardware; once domestic markets dominated, inward-facing policies and keiretsu control allegedly stifled PC software.
  • Government projects like the Fifth Generation AI initiative are cited as emblematic of misdirected, inward industrial policy.

Language, Unicode, and PC Adoption

  • Several argue early PCs struggled with Japanese text input and Kanji, limiting home-business use; others counter that Kanji-capable systems existed by the 1980s.
  • Unicode’s Han unification is portrayed as especially painful for Japanese: correct glyph rendering depends on locale- and font-handling most software doesn’t fully implement.
  • Consequence claimed: Japanese software stayed longer on legacy encodings; Unicode-first open-source ecosystems are less frictionless there.

Comparisons with Other Countries and Sectors

  • South Korea and China, with similar conglomerate structures, are cited as counterexamples; replies note their different capital markets and English proficiency.
  • Japan is still strong in games, embedded/industrial software, and hardware; weaker in global-facing PC/web/software products.
  • Population aging and the relative lack of young, risk-seeking talent are mentioned as additional headwinds.