Recent submissions

Comment · 4 months ago
> user fatigue

Citation needed. What is user fatigue? Can it be empirically measured? Fatigued by what? Too much color? Lack of shape? Too much contrast? Lack of contrast?

When is the last time you were "fatigued" by icons?

Without hard facts the expression is just a wishy-washy way to promote a personal taste.

Comment · 1 year ago
Comment · 2 years ago
Thank you!

From your descriptions, it seems likely that the same system was used in the earlier games.

Comment · 2 years ago
Awesome!

Back in the day, I reverse engineered the level format of v2. I Understood the graphics and physics attributes, but never how the waypoint system worked. (in multiplayer, if you take too big of a shortcut you’ll be penalized by being “popped”)

Can you explain how the waypoint system works in v3?

Comment · 2 years ago
Comment · 2 years ago
Comment · 2 years ago
It’s a pun. Undefined (program) state(s).

Also, there are some NAN’s hidden in the palmtrees.

Comment · 2 years ago
> Taking into account how much nesting is involved in writing HTML

which is another one of its flaws.

Comment · 2 years ago
^^^ Apples to oranges:

    <DoStuff args={...}><DoMoreStuff args={...}> <DoEvenMoreStuff args={...}/> </DoMoreStuff> </DoStuff>
vs

    DoStuff(DoMoreStuff(DoEvenMoreStuff()))
Both of them you would split into indented lines when they become too long. And 1 becomes too long much faster.

Also with 2 you can do

    const todo = DoMoreStuff(DoEvenMoreStuff());  
    DoStuff(todo);
where as with 1 you cannot.
Comment · 2 years ago
... and imposes a build step, for no good reason.
Comment · 2 years ago
Please no

The {...} syntax is a non-standard extension to XML/HTML I think MS came first up with back in the day for XAML (WPF).

It's a hack to "fix" a shortcoming of the base language.

It does not compose, i.e. :

<DoStuff args={<DoMoreStuff args={...} />} />

does not work.

Comment · 2 years ago
If you know JS (or any other C family language), the syntax is not new.

It's about getting rid of a flawed syntax.

But it'll probably never happen because people are used to it and oblivious to change.

Unless of course if one of the FAANG publishes it as their New FrameWork [tm], then everybody will jump on it, and people that don't are seen as "not modern".

Comment · 2 years ago
Why would you insist to write the function name both before AND after the call?

<DoStuff> args </DoStuff>

vs

DoStuff(args)

Comment · 2 years ago
People complaining about lack of JSX, HTML angle-brackets: I don't get it.

XML gets all the hate for being overly verbose (and for good reason [1])

however with HTML syntax, which is almost the same, everybody seems to be just fine...

[1] XML is sooo nineties, the "modern" developer uses markdown. inb4 S-Expressions

</rant> (...yes I know)

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton