Chronosort
ledoc.itch.io
Chronosort
1–10 of 14 posts
Re: Chronosort
#2Why do games like this have one game a day? What's preventing them randomizing it so I can keep playing? I mean I'll be honest, it's pretty frustrating given I'll likely never visit your website ever again.
Re: Chronosort
#3Does not allow me to play with different cards after a restart.
Honestly I'm unlikely to remember about it tomorrow.
Why is it explicitly for desktop? The hardware requirements are low, and people mostly use mobile for time killer games. It needs to be mobile-first.
Re: Chronosort
#4Lost all lives trying to place the 10th card :(
I liked how it made me think about prerequisites for various technologies in order to guess when they were invented.
Re: Chronosort
#5Worked fine on my android.
I like the "one game a day" style, bit I also like reading Samuel Pepys diary.
I got plenty of other things to spend my time on.
Re: Chronosort
#6I thought this was going to be a silly sorting algorithm, like bogosort.
So, here's my version of chronosort: Given a set of natural numbers, place them all on a timer, with a timeout equal to the number, and callback argument also equal to the number. The callback function simply appends its argument to the end of a shared list. At some point you will have a sorted and (eventually) complete list :)
Re: Chronosort
#7Why do games like this have one game a day? What's preventing them randomizing it so I can keep playing? I mean I'll be honest, it's pretty frustrating given I'll likely never visit your website ever again.
With wordle at least I think the appeal is that you can play it async with friends and discuss your outcomes. "Have you solved the wordle today?" "Yea it was a tough one!".
Re: Chronosort
#8I thought this was going to be a silly sorting algorithm, like bogosort. So, here's my version of chronosort: Given a set of natural numbers, place them all on a timer, with a timeout equal to the number, and callback argument also equal to the number. The callback function simply appends its argument to the end of a shared list. At some point you will have a sorted and (eventually) complete list :)
Re: Chronosort
#9I thought this was going to be a silly sorting algorithm, like bogosort. So, here's my version of chronosort: Given a set of natural numbers, place them all on a timer, with a timeout equal to the number, and callback argument also equal to the number. The callback function simply appends its argument to the end of a shared list. At some point you will have a sorted and (eventually) complete list :)
It is as silly as bogosort.
It's queue-sort. You put the elements into a priority queue, then remove them in property order and put them into a list.
Here you just use the inherent queue of a timer system, which wastes time between extracting the next element. That's silly and inefficient, and disingenuous in trying to hide the queue.
Re: Chronosort
#10I thought this was going to be a silly sorting algorithm, like bogosort. So, here's my version of chronosort: Given a set of natural numbers, place them all on a timer, with a timeout equal to the number, and callback argument also equal to the number. The callback function simply appends its argument to the end of a shared list. At some point you will have a sorted and (eventually) complete list :)
It is as silly as bogosort. It's queue-sort. You put the elements into a priority queue, then remove them in property order and put them into a list. Here you just use the inherent queue of a timer system, which wastes time between extracting the next element. That's silly and inefficient, and disingenuous in trying to hide the queue.
Chronosort is closer to radix sort, as both are O(n) if values are bounded. Queue-sort (aka heapsort) is O(n log n).