4 ms·
There was an article about this (in New Yorker, I think...) a few years back, t how Japan has this strange relationship with software. How it is a hardware-fir
by rdtsc 11y ago
There was an article about this (in New Yorker, I think...) a few years back, t how Japan has this strange relationship with software.
How it is a hardware-first country. Many reasons were given -- cultural, how "real men build real things", infatuation with appliances, which are seen as being "hardware" in a way, perhaps the langauge barrier i.e. existing software tools using English for menus and inputs etc.
And it is kind of interesting, looking back at a country that many in the 80's feared with surpass and leave the Western world in the dust technology-wise, we haven't seen that much software produced there. Can you think of large well known software from Japan (excluding console games). Vine Linux, SoftEther VPN, TrendMicro, anything else?
One wonders if they see Western software companies and if there is any desire to catch up or try to keep up.
Maybe anyone from Japan can provide a better perspective?
- karpodiem 11y agolet me know if you can find that New Yorker article, I'd be interested in reading it.
- cma 11y agoWhy exclude console games?
- rdtsc 11y agoI guess I see it as part of the appliance. Not something you download and install or use an API to access.
- fit2rule 11y agoThe console frameworks and API's are all produced in an SDK that other developers use .. so its just as valid an example of a successful Japanese software product.
- scott_karana 11y ago> I guess I see it as part of the appliance. Not something you download and install or use an API to access. Aren't car ECUs "appliances" without API access, just like games?
- shaurz 11y agoI would say games are probably where Japan has most excelled in software, at least in the 80s and 90s. But the code is probably very bad practice by modern standards (hand coded assembly hacks, all game state in global variables). When you only have a few KB of RAM/ROM there is a lot less scope to mess up (although I have come across bugs in cartridge games myself).
- keypusher 11y agoI'm not from Japan, but I work in the US for a large Japanese company. I know that they have a large software engineering team in Japan, but if it isn't hardware related they seem to have a hard time producing quality software. They seem to have realized this, and now focus on producing hardware and have started up 3 different software teams across the US to build software for said hardware. They occasionally send some of their engineers to our offices (for 6-12 months usually) to learn about our culture. There is a clear disconnect when they send these people. They work hard, no problem with long hours, but they have a very hard time getting into the collaborative nature of our teams, and I don't think it is just the language barrier. I guess I take it for granted usually, but it made me realize how much time we spend discussing things between developers, questioning management, writing furiously on the whiteboard, arguing, trying things out, failing, trying something different, finding problems with other people's code, fixing said problems, etc. It can take a bit of thick skin to absorb such criticism and engage in this process, but I think it is crucial to good software development. Someone who just sits quietly in meetings, then waits for a task to be assigned, and works at that task until it is complete is somewhat missing the process, because sometimes it turns out the task your manager assigned doesn't make any sense, or can't be done with this framework, or that you would have to use 100 global variables to accomplish the task this way. I am merely speculating but it's possible that a very rigid social and management hierarchy where it is more important to work hard and respect your position in the company than to solve the problem the right way if it involves bucking authority, could negatively impact the ability of developers to innovate and/or produce a quality product.
- lloeki 11y ago> Can you think of large well known software from Japan Ruby.
- thescrewdriver 11y agoThat's certainly not a shining example of software quality. I also don't think it's fair to generalize about software quality for an entire country based on 1 or 2 examples.
- nitrogen 11y agoI've written some C extensions for Ruby, and its internal APIs seem decent. What makes Ruby a bad example of software quality?
- thescrewdriver 11y agoThe number of bugs, mostly referring to the older MRI versions though.