While most developers may dislike the imperial calendar, all of my bank/brokerage statements display dates using it, as do tax/pension forms. It's definitely still in heavy use for some very important data.
On a similar note, I recently requested a list of historical transactions from a brokerage and found that transaction dates continued to be annotated as Heisei all the way through Heisei 36 (2024), a full 5 years after Heisei officially ended in Heisei 31 / Reiwa 1 (2019). Late in 2024, transactions finally started being annotated Reiwa 6.
In my mind, Yamada Denki is the absolute worst. I bought a washing machine there in 2004 and, almost entirely due to the song, have been back maybe once since then. I remember at the time telling my wife I couldn't imagine what working there would do to a person.
If you enjoyed 1Q84, and haven't yet read the Wind-up Bird Chronicle, there's a little bit of a connection you might enjoy.
The first Murakami book I read was Hard-boiled Wonderland and the End of the World, and it's still one of my favourites, with a new translation by Jay Rubin coming out later this year. The book of his that's always spoken to me the most is South of the Border, West of the Sun.
If you're ever in Tokyo, consider visiting the Murakami library at Waseda University. It's got a small cafe downstairs, sometimes with live music performances, and lots of nooks and corners for sitting and relaxing with a book. There are copies of all of his books, and tons of translated copies in many languages.
Wonderous is an app we've pointed people to in the past. I believe the current iOS release on the App Store uses the newer Impeller rendering engine instead of Skia, but I could be wrong.
In Japanese it’s called both 小型月着陸実証機 (roughly: small moon lander probe) pronounced “ko-gata tsuki chakuriku jisshōki” or スリム (SLIM). It’s not uncommon to have an English name alongside the Japanese one for some scientific projects but not always the case — e.g. I don’t recall hearing the Hayabusa probe referred to by any name other than Hayabusa (which means falcon) in the news.
> not using the card purchase UI at train stations is confusing.
Agreed that the UI for Japanese train ticket machines can be confusing for first-time users such as foreign visitors, but foreign visitors aren't the primary use case. These machines are designed to be familiar and fast for the bulk of their users: residents of Japan who know how the train system works. Stations need to move massive numbers of people through these machines quickly, and this layout is incredibly efficient for that.
Older terminals used a very similar layout of two groupings [1]:
1. physical pushbuttons with prices displayed using 7-segment LEDs
2. physical pushbuttons for most common multi-passenger sets
The touchscreen terminals provide this exact same layout, which provided continuity as the changeover happened, and kept the lines at the machines moving quickly. They're also freakin' brilliant when it comes to minimising the button-presses required to buy tickets. e.g. two parents and a kid going to a station that's 400-yen from here? Press the "two adults, one kid" button, then the fare. You're done. Fare zones are listed on a large train network map usually posted right above the machines with both adult/child prices [2], but locals almost always know where they're going and how much.
Given how heavily-trafficked Japanese stations are, it's way more critical to minimise the time required to use the machines and keep the lines flowing than it is to provide an easy experience for foreign visitors. Compare to e.g. Montréal where even users familiar with the metro can spend upwards of a minute to buy a ticket or recharge an Opus card.
I know someone mentioned Lynx, another option is to set up your mailcap to view using w3m. For reference, see .config/mutt/{muttrc,mailcap} here: https://git.bracken.jp/dotfiles/files.html
Hey there - Flutter team member here. Support for integrating arbitrary non-flutter views/widgets (referred to as PlatformViews in Flutter terminology) is something we're actively working on at the moment, once we've got them landed, web views and video player support are top of our list in terms of views to add support for. We know people can't wait for this to land, and believe me, I can't wait for it to land either :)
PlatformView support is one of our top desktop priorities this year (along with multi-window support).
The process that caused the light we see as the CMB happened everywhere in the universe roughly all at once. At the time, from any given point, you'd just have seen blinding light but as things cooled, you'd see a sphere expanding around you where this light was dimming, as less and less, and finally none was being emitted around you, but due to the finite speed of light, light from outside that sphere would still continue arriving in your eyeballs. That's the situation we're in today; that sphere's just really big now.
During recombination epoch ~400,000 years after the Big Bang, this light would have been visible. Due to expansion, over time that light has stretched to longer and longer wavelengths, and we currently see it as microwaves.
Note: It's been ~30 years since I was actually studying physics & astronomy; others may be able to offer better explanations or correct me.
The conviction rate is 99.3%. By only stating this high conviction rate it is often misunderstood as too high—however, this high conviction rate drops significantly when accounting for the fact that Japanese prosecutors drop roughly half the cases they are given. If measured in the same way, the United States' conviction rate would be 99.8%.
If you take a look at how Flutter is implemented, you'll see that at the bottommost layer (dart:ui), it is imperative. On top of that, we built the rendering/painting layers (pretty imperative) and then the widgets layer (reactive).
Each of these layers is public API and follows the same breaking change process as any other part of Flutter's public API, so with a bit of effort an alternative imperative framework could conceivably be built built on top of what's there. The downside is that since the widgets layer is reactive, you'd be giving up all those shiny widgets that are part of the SDK and need to build your own (or find a way to wrap what's in the SDK).
TL;DR it's entirely possible to create an imperative framework on top of Flutter's lower layers, re-using a lot of our existing code, but (as far as I know) such a thing doesn't exist today.
Edit: for some reason I'd interpreted the question as being about cycling. Leaving in case it's useful for cyclists or motorcyclists.
I've done a lot of cycling across various bits of Japan, from shorter day trips on the order of 150km to longer 1000km+ trips. One thing to keep in mind for visiting cyclists on longer road trips: this may seem obvious but Japan is very mountainous which means a lot of narrow roads with little/no shoulder, and long (sometimes multi-kilometre) tunnels. Fortunately drivers are in general, very considerate and careful around cyclists.
For shorter day trips, many large rivers/lakes in Japan have cycling/walking paths along one or both sides and make for really nice riding. In Tokyo, the Tamagawa or in Kyoto Kamogawa and Katsuragawa have paths. Lake Biwa has a really nice cycling trail as well.
One of my favourite longer routes was along the north coast of Japan between Tsuruga and the north end of Fukui. The mountain pass along no. 8 through Takefu has some nice views but a lot of climbing and tunnels. For something shorter but pretty, follow the Tamagawa from Tokyo up to Lake Okutama. As someone else mentioned, I find travelling in rural Japan a lot nicer than cycling in/near big cities.
Reminds me a bit of using a Canadian credit card in the US and occasionally being prompted to enter your zip code. Canadian postal codes are an alternating sequence of six letters and numbers (A1A 1A1). Turns out that in most cases, you can enter just the digits from your postal code in order then right pad with zeros. Perhaps not on MetroCard machines though!
Some countries [1], [2] provide government-sanctioned medically assisted death for qualifying patients. What makes you believe these sorts of programmes can't be adopted more widely?
Japanese companies often include both a commuting allowance and a housing allowance as distinct components of your pay; neither is counted as income for the purposes of taxation. Meals at company cafeterias are typically not free (though some places are), but typically very reasonable -- e.g. 300 JPY for curry-rice etc.
Hey there. I'm an engineer working on Flutter Desktop. We're definitely aware of the macOS cursor behaviour issue and are looking at ways we can fix it. We haven't landed anything (that I'm aware of) that should improve this for 3.0, but if it helps, it's something that's actively on our radar and we've discussed potential fixes for. One potential solution is to implement a custom shader [1].
While I understand this may be a dealbreaker issue for your use-case, we've been pretty busy getting a few higher-priority (overall) issues fixed (universal binary support, CJK text input, key event APIs, etc.) prior to 3.0, but we'll get to this.
Thanks for reporting this. IME-based input is super important to me -- we only speak Japanese at home. I've filed a bug [1].
I manually tested on each of Windows, macOS, Linux, and iOS (where I've done a lot of work specific to CJK input) and was able to correctly input Japanese, Chinese, and Korean text [2], so looks like this is likely an issue specific to Flutter's web runtime. I work on Flutter's desktop embedders, but if there isn't someone who's a heavy IME user on the web team, I'll gladly give em a hand to help get this fixed.
You might be thinking of this package, authored by Google, mostly by people on the Flutter team but it's not an official Flutter project (as far as I know): https://pub.dev/packages/flutter_simple_treeview
Hey there! I work on Flutter for desktop. I'm happy to provide a little background.
We made a decision early on to focus where those of us who work on Flutter could deliver the most value, and for Desktop that meant getting the runtimes and platform integration for each of the desktop OSes in good shape (international text input, accessibility support, rendering performance, etc.) as well as core integrations like the menu bar, file chooser dialogs, etc. These are things that need to land in the runtime itself and are significantly more painful for the community to contribute, or author and publish on pub.dev.
We're working on filling in the gaps for widgets that are part of the Material spec, and I expect the community to make and publish widgets on pub.dev that continue to surprise me; I'm blown away time and time again at the beautiful widgets and the community continues to produce either in packages or as pull requests. You should be able to find community-authored packages for treeview, datagrid, and charting on pub.dev today in the meantime.
On a similar note, I recently requested a list of historical transactions from a brokerage and found that transaction dates continued to be annotated as Heisei all the way through Heisei 36 (2024), a full 5 years after Heisei officially ended in Heisei 31 / Reiwa 1 (2019). Late in 2024, transactions finally started being annotated Reiwa 6.