8,995 karma · joined November 4, 2008
tokyo more broadly: it's improving, but yeah, it's nowhere close to 100%. obviously i won't disagree with you there.
and i didn't mean to come off as too harsh. but i imagined someone reading your comment and being deeply discouraged (as i might have been, many years younger) when in reality tokyo has possibly one of the best and most accessible subway systems in the world.
it's not all roses, but outside of the US, most of the world is not so wheelchair-friendly (in my experience and talking to disabled folks, at least). (and don't get me started on NYC, which is just wheelchair-hostile.)
on the staff support: i don't really see any problem here at all. in fact, i think the service that the staff provides is truly excellent. most lines have nearly level train-to-platform gaps, but if i feel like i need a ramp, i can ask the attendant at the gate, and they will arrange for someone to quickly unfold a portable ramp when the train arrives, and for someone to do the same at the destination, exactly where i arrive. (coming from the US, can i imagine this level of service at any US city? uh, yeah, no.)
(i use a wheelchair.)
Model: business data
View: on-screen representation of Model; reacts to changes in Model to re-draw accordingly
Controller: maps user input to changes in Model; may need to interact with Views, and may pass control through a hierarchy of Controllers, to determine the Model being manipulated
in other words, user-input data flows as: C -> M, and M -> V. i see a Controller modifying a View (rather than just querying it) as impure MVC, and i normally strive to avoid it, even though that's essentially impossible if you're forced to use a platform's GUI toolkit.
i don't think of MVC as having "gone wrong," but rather that the name has been co-opted and the pattern corrupted by so many different people, in many different ways, as to make the original name extremely confusing. iOS' concept of "MVC" drives me crazy. i think it's probably fair to call it MVP (Model-View-Presenter), the difference being that the Presenter can indeed do some of the work of modifying the View. but i still mostly think of this as a hack: the more work that gets shoved into the Presenter, the more complicated it gets.
it is a false equivalency to say that materialism is false and that it is impossible to build strong AI. if the material world alone can be described by laws of causality, then we should expect to be able to simulate some significant part of it. if it cannot, and if extra-material forces impact the material world, then we may have no hope. but existence of extra-material stuff (which i call "qualia") may or may not assert a force that affects the material world.
are one-way dataflow constraints really any different from the observer pattern? i avoid cycles exactly because i implement it myself, and don't even have a solver, per se. even KVO seems not to handle cycles. and when e.g. i am using auto-layout in IB, even then i am careful to avoid over-constrainedness, even though the solver can settle on a "solution."
I'm a little too paranoid to say exactly what I did, but I will say that I'm glad I was given that advice. (I was younger, and had much less money saved at the time; obviously that amount would affect any similar decision now.)
The advice I was given (not by the CU): either withdraw all my money from the account and put it in a safe deposit box, or wire it to a (very) close relative ASAP -- before the lien is officially issued.