Return True to Win • Hacker News Board

Re: Return True to Win

#41

Post by junke » Fri, Aug 12, 2016, 1:08 PM UTC

ninjakeyboard wrote: post #28

I don't exactly know what I did, but it did say that I win.

A day like any other with Javascript ;-)

Re: Return True to Win

#42

Post by tomsmeding » Fri, Aug 12, 2016, 1:10 PM UTC

okket wrote: post #29

This page only shows "return true to win" on a white background in Chrome?

It loads eventually

Re: Return True to Win

#43

Post by Spoom » Fri, Aug 12, 2016, 1:18 PM UTC

Tepix wrote: post #26

It doesn't seem to work for me on Firefox and Chrome..?

I had to go into the console and type "return true" for it to start working. I thought it was intentional.

Re: Return True to Win

#44

Post by k_bx » Fri, Aug 12, 2016, 1:28 PM UTC

tomelders wrote: post #40

dou4cc wrote: post #4

The game shows us how ugly JS is.

Swift. The Javascript of tomorrow, today!

PureScript. The Swift of today. Yesterday, today and tomorrow!

Re: Return True to Win

#45

Post by unsignedqword » Fri, Aug 12, 2016, 1:30 PM UTC

Does anybody really know why JS's type system was designed the way it was? It seems so out of whack with what people want out of a language, dynamically typed or otherwise.

Re: Return True to Win

#46

Post by tomelders » Fri, Aug 12, 2016, 1:37 PM UTC

k_bx wrote: post #44

tomelders wrote: post #40

Earlier quoted context omitted.

Swift. The Javascript of tomorrow, today!

PureScript. The Swift of today. Yesterday, today and tomorrow!

But it compiles to ES5. At this rate, we'll be deploying ES5 for the rest of human history while we all pretend we're writing ES451.

And it's whitespace significant, which is something only maniacs like in a programming language.

I'm half joking, don't get too offended...

But whitespace significance is madness.

Re: Return True to Win

#47

Post by scrollaway » Fri, Aug 12, 2016, 1:37 PM UTC

tomsmeding wrote: post #42

okket wrote: post #29

This page only shows "return true to win" on a white background in Chrome?

It loads eventually

Does it?

ReturnTrue:1 Fetch API cannot load https://bigger.alf.nu/db/true/H5VmsyVCBD62113H5Slu. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://alf.nu' is therefore not allowed access. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Re: Return True to Win

#48

Post by throwanem » Fri, Aug 12, 2016, 1:53 PM UTC

apricot wrote: post #31

Find the exact combination of browser/OS that does more than show "return true to win" on a white background to win.

Use patience.

Re: Return True to Win

#49

Post by wtbob » Fri, Aug 12, 2016, 1:53 PM UTC

apricot wrote: post #31

Find the exact combination of browser/OS that does more than show "return true to win" on a white background to win.

> Find the exact combination of browser/OS that does more than show "return true to win" on a white background to win.

I see:

    return true to win
    
    (Come back in a few minutes.)

What do I win?

Re: Return True to Win

#50

Post by throwanem » Fri, Aug 12, 2016, 1:55 PM UTC

unsignedqword wrote: post #45

Does anybody really know why JS's type system was designed the way it was? It seems so out of whack with what people want out of a language, dynamically typed or otherwise.

It wasn't; the language was implemented from scratch in ten days.