I get that command line is cool and all, but sometimes opening it up in Paint is just easier. Especially if you'd have to look up the right commands to do it otherwise.
"The background should be white and the window/screen must be at least 400 pixels by 400 pixels. If your language doesn't support windows/screens that large then use the largest size it does support as long as that is not less than 200 by 200."
Write a complete program that takes a boolean or integer input. It must:
Output its own source code if the input value is falsy
Output its own source code in reverse if the input value is truthy
Your program cannot be palindromic, nor can it read its own source code by any means.
This is cod...
Does anyone here know of problems that are easy for a computer to verify correct solutions to, but hard for computers to solve, and that humans could solve faster?
> A 2010 paper in the science journal Nature credited Foldit's 57,000 players with providing useful results that matched or outperformed algorithmically computed solutions.
it's highly unlikely that there exist problems which are impossible to solve quickly by computer but easy to solve by human unless you mean driving a car :)
@Lembik Not instantly, but I want a team of thousands of people to have a good chance of one of them solving it in about 10 minutes (even if one person alone has much smaller chance).
So, about the cat challenge. Does anyone have suggestions for a better name? It's about as much cat as it is echo since it doesn't take any command-line arguments or read files or anything. I suppose as far as command-line scripts go it's the identity. But at the same time, at least when it comes to showcasing esolangs this is often called cat, so calling it that would be good for searchability...
@El'endiaStarman it's useful for multiplying polynomials.. so you start with the normal coefficient representation, convert to point-value representation, multiply quickly, convert back
How long should I leave a question in the sandbox?
In general you should leave a question at least 72 hours to ensure that the people who check it fairly regularly will have a chance to see it and comment.
@Lembik I know what you mean... my latest challenge was in the sandbox for over a year. But it ended up being much better than if I had just posted it at the time.
So how do I actually score Scratch? The meta post has no real conclusion, just a bunch of options. I'm pretty sure my heading is going to be #Scratch, ? bytes at this point.
@Lembik Harder questions are welcome. Easy questions hit HNQ and get more rep, so there's less incentive to make hard questions that attract few answers.
i type in dvorak. i have a raspberry pi that uses qwerty. i can ssh in and it's fine because the characters i type are sent to the pi, not the keys i pressed to send them. but for some reason in nano some of them don't work right. when i try to type "+" it shows up as a comma instead. this makes no sense to me
@MartinBüttner I have an idea of what to do in case you decide not to. I'll just make up a fake day and show what it looks like if you fall off the bottom of the world
You could just use a single number as the O position instead of ASCII art for output. Zero indexed, it looks like the sequence so far is 12, 16, 20, 17.
Write a complete program that takes a boolean or integer input. It must:
Output its own source code if the input value is falsy
Output its own source code in reverse if the input value is truthy
Your program cannot be palindromic, nor can it read its own source code by any means.
This is cod...
How long should I leave a question in the sandbox?
In general you should leave a question at least 72 hours to ensure that the people who check it fairly regularly will have a chance to see it and comment.
