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.

DF also already has an almost silly level of ambition: http://bay12games.com/dwarves/dev.html

Your post is very reminiscent of this[0], which was posted on HN a long time ago.

[0]: http://worrydream.com/ABriefRantOnTheFutureOfInteractionDesi...

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?

You raise a good point, but even if sophisticated AIs are not technically possible yet, predefined characters can still be done well without (ab)using cutscenes.

Their product is presumably not photo tagging or recording GPS data. These are just components they need for their actual product to work. When you talk about "innovating" here you are actually saying "finding way of achieving something that's different enough from the most convenient way (because someone has already thought of that)". That's no innovation at all; all that would do would be stopping them from launching their product until they figure out a way around the problem. By blocking entrepreneur's paths, patents prevent them from releasing their possibly innovative products, thus preventing innovation.

Yaguarón 1414, Montevideo, Uruguay

This is certainly a thing of beauty. See, for instance, the way the trainers are defined:

https://github.com/kanzure/pokecrystal/blob/master/trainers/...

It almost looks like a high-level language.

That's not what they mean. The usage they are discussing is more like this, I believe. In a functional context, instead of doing:

    print expensive_computation(), expensive_computation()

You can do:

    (lambda x: print x, x)(expensive_computation())

Which would be equivalent to, with an imaginary let syntax:

    (let x be expensive_computation(): print x, x)

Lisp/Scheme. Go through SICP[0] and do the exercises. Also, mandatory pg essay: http://www.paulgraham.com/avg.html

[0]: http://mitpress.mit.edu/sicp/full-text/book/book-Z-H-4.html

I always open these up in a new tab (usually can be done fast with third click, or ctrl+click), then close the tab when I'm done. It's fast, you can keep reading the original site while the image/webpage/whatever loads, and the problem you mention never happens.

Well, there's this: https://github.com/Sanqui/2048-gb

It was posted on HN but didn't really take off, sadly: https://news.ycombinator.com/item?id=7434529

Man, that's awesome. And it's written in assembly! I'm asking out of my armpit here but, is there no way to compile C/C++ for the Gameboy?

This kind of crap is exactly the reason why I don't like doing just "if var:" unless var is guaranteed to be a boolean.

I'm sure the parent was talking about HTML5. It isn't erroneous in HTML5.

Nobody thinks it's a good idea to rewrite something just to make it "newer". The idea is to rewrite (or maybe just refactor) these tools to make them better.

It's also not "fixing what's not broken", but improving something that could... well... be improved.

Really? Why do you think that is? Do you have some examples?

Can you link the originals?

Well, he jumps back a little bit in these but don't tell me you don't see the difference. It's pretty big.

I don't think so. He actually jumps back, as if trying to physically get away from the creature.

What was the old one?