Ideka

Do you know how that sentence you wrote right there works? Did you create the English language?

I see a lot of talk about Vimperator here.

Vimperator's pretty good, but you people really need to check out Pentadactyl.

True, I always think the same thing. But if a wheel was rotating clockwise, it would be moving from left to right. That could be where it comes from.

Honest question: Why do people care so much about or like having the year in the title? In some situations I can see it being needed to prevent big confusions, but many times I see people put the year in the title when it doesn't really seem to matter. In this particular case for instance, I don't see why it would be needed.

I downvoted you.

You shouldn't generalize people (doing it by race is called racism; doing it by country has no fancy name that I know of but it's wrong all the same), or refer to some cultures as "better" than others.

(The following mostly applies to C#.)

> Objects containing the same values should be equal by default.

Sounds good, but it's a tricky issue. Equality must be checked between all values of both objects. This can take long, as objects can have many values and may contain references to other objects which may in turn contain references to other objects and so on. Object references might even be cyclical. Not impossible to account for but quite tricky.

And how about get/set properties? These must be checked as well, even though many will be just "mirrors" of private or protected properties, and others might be calculations based on other properties (like the area of a circle).

> Comparing objects of different types is a compile-time error.

Accounting for inheritance, I assume.

> Once created, objects and collections must be immutable.

This sounds like a terrible idea. Wouldn't objects be to even modify their own properties?

> Objects must always be initialized to a valid state. Not doing so is a compile-time error.

> No nulls allowed.

Nulls are useful. The problem here comes from not knowing whether something may be null or not. The solution would be only allowing Nullables to be null, and enforcing anything that's not a Nullable to be initialized.

A couple of problems with the API.

First, why do you have to call checkDestinationQueue after modifying the queue? It's awfully redundant. I assume this is due to some kind of limitation.

And second, goingUpIndicator and goingDownIndicator are kind of sketchy. Can you activate both at the same time? What effect would that have? There should be a single property, directionIndicator of an enum type with the possible values up, down, and none. I don't think you can make enums in javascript though, but I don't know the language very well. I'm just explaining this in terms that I know; there probably is a suitable javascript equivalent or replacement.

I'm gonna need a source on that one. I experience ASMR, and the tingling sensation definitely calms you and feels nice, but it has nothing sexual attached to it.

Hahaha. That level is so much fun to troll people in.

Someone was drawing an X on the correct exit, and I started drawing a checkmark on the one next to it. When they realized, they tried to cross it out.

No. The japanese consider 4 and sometimes 7 to be "unlucky numbers". 9 is fine.

Can you explain in detail how you achieved this? How is it that you "designed" the trip?