It took me a while to figure out the answer, but it was because the buttons disappear off the screen on a mobile device. I had to play in landscape mode.
There is also a small bug where if you swipe to flip the bits, the button state is no longer in sync
It’s working now, I wonder if it was related to the public WiFi I was using earlier. I’ll try it again next time I am there, everything else seemed to be working fine.
I'd love to use this tool with my high school CS class, but the "suggestive" numbers would, unfortunately, prevent me. Great concept and well implemented!
-specifically, some of the first few numbers are 69 and 80085
There are only three predefined numbers (69, 420, 80085). It doesn’t look to difficult to replace those in the source if you want to provide your own version.
That might not matter enough if the students start saying, “Have you seen the examples on that website loco5niner showed us? looolol”.
I also can’t help but mention that I already know the answer to this example from one of my favorite jokes in Futurama: https://youtube.com/watch?v=_4TPlwwHM8Q
Something like this could be really helpful to learn IPv4 subnetting/addressing. My aha moment in fully understanding it was learning binary, most of the resources I used at the time didn’t explain it very well.
Meh, just go left-to-right, and click the buttons, starting at the first... if it's higher than the wanted number, disable that button, and go one position to the right, and try that.
Yet another site falls victim to CSSWG’s absolutely asinine, entirely indefensible idea to make centered flexbox items in a too-small container clip and become completely inaccessible on the left side.
Anyone who says flexbox “solved” centering hasn’t been paying attention.
It blows my mind that this is the “best” (or at least most ubiquitous) layout engine in existence.
Edit: to be more constructive, can anyone offer the OP a concise, CSS-only, diff that would fix the mobile issue without changing the DOM structure or layout on larger screens? It might be possible with a min-width: fit-content, but I have no development setup available at the moment.
Wrapping is undesired, the linear presentation is critical here. And the box is the screen in this case, on a mobile one the highest order buttons are missing.
It’s sad that this had been up for so long with no real solutions. A genuine failure of the CSSWG.
You can't have >x of reasonably sized and spaced boxes on a screen horizontally without wrapping, regardless of layout engine. Besides, wrapping can be done presentationally while keeping the linearity.
In this case, I'd probably switch to an automatic grid layout with equal size boxes regardless of content size. Then it could neatly wrap into multiple rows while keeping the boxes at a constrained size.
Yes you can, it’s called scrolling. And the items on the right of the screen are indeed accessible via scrolling, it’s the items on the left of the screen that are entirely inaccesible. There is no possible justification for this design, it’s pure slop. (CSSWG’s design, not this site which is hamstringed by their incompetence)
That's the correct way... big adjustments on left-hand side until you're ready for small-adjustments on right-hand side. This game takes less than 2 minutes.
You could expand this game with much more advanced operations and tricks that people devised but I guess those would involve algorithms too. Floating point would be a good expansion and much better interactively than a textbook.
64 comments
[ 2.1 ms ] story [ 135 ms ] threadIt took me a while to figure out the answer, but it was because the buttons disappear off the screen on a mobile device. I had to play in landscape mode.
There is also a small bug where if you swipe to flip the bits, the button state is no longer in sync
I still have kind of mixed feelings about a website that does not use bit lengths that are powers of 2.
Edit: meant answer not result
Should be made mobile responsive. Difficult to use on mobile.
1) off by one errors
(in this case it comes in the annoying form of messed up floor/ceil calculations)
https://looo.lol/?x=1 (I like the “Binary math can seem hard, but it's actually quite simple.”)
https://looo.lol/?x=2
https://looo.lol/?x=4
But the number of values is just 2^n, because that includes zero.
-specifically, some of the first few numbers are 69 and 80085
I also can’t help but mention that I already know the answer to this example from one of my favorite jokes in Futurama: https://youtube.com/watch?v=_4TPlwwHM8Q
https://flippybitandtheattackofthehexadecimalsfrombase16.com...
I also play this one which I think was posted on HN a while ago: https://play.google.com/store/apps/details?id=go.lang.bintri...
Anyone who says flexbox “solved” centering hasn’t been paying attention.
It blows my mind that this is the “best” (or at least most ubiquitous) layout engine in existence.
Edit: to be more constructive, can anyone offer the OP a concise, CSS-only, diff that would fix the mobile issue without changing the DOM structure or layout on larger screens? It might be possible with a min-width: fit-content, but I have no development setup available at the moment.
and maybe, if you want, a `min-width` on the boxes themselves
It’s sad that this had been up for so long with no real solutions. A genuine failure of the CSSWG.
In this case, I'd probably switch to an automatic grid layout with equal size boxes regardless of content size. Then it could neatly wrap into multiple rows while keeping the boxes at a constrained size.
You could expand this game with much more advanced operations and tricks that people devised but I guess those would involve algorithms too. Floating point would be a good expansion and much better interactively than a textbook.
Algo:
For a proper binary search you should right nextdigit+first digit/2, if you're going backwards.