You're right that we use square brackets on Hackaday to indicate usernames. However, in this case I think I left out a word in my submission and the/. editors added it using the square brackets to indicate the change.
It's not a judgement on your method of communication, but a recognition that a telephone from 80 years ago will still work on the same system. Remarkable.
We publish about 10 posts a day on Hackaday so it's certainly not every post.
But I've long been a Slashdot reader, so when we have a great piece of content that I think fits here I try to submit it.
Just submitted this comment, but not that I think about it. If you want these to be easier to type you should set up your IDE to auto-replace the mnemonics. Type GT(space) and it gets replaces with '>'.
I think he's right about the mnemonics being easier to type. They're generally on dominant fingers and you use letters constantly (not so much with pipe, ampersand, great and less than).
That being said, I do think the capitalization should be saved for constants, and scanning code with your eyes proves the symbology easier to pick out.
Symbols are better.
Problem not solved. Sure you can arrest and charge someone for breaking the rules but the vast majority of these cases are people not knowing any better. If these drones are interfering with full-sized aircraft, penalties don't prevent the danger presented by naive operators. This is an educational problem -- people need to know there are places you're not allowed to fly and that it's important to stay out of those with their hobby equipment.
The issue there is user input. In this case, the Atari joystick is half the fun. I've seen this same display used to play tetris with an IR remote control... it's not nearly as fun as with a joystick.
Slashdot Mirror
You're right that we use square brackets on Hackaday to indicate usernames. However, in this case I think I left out a word in my submission and the /. editors added it using the square brackets to indicate the change.
It's not a judgement on your method of communication, but a recognition that a telephone from 80 years ago will still work on the same system. Remarkable.
We publish about 10 posts a day on Hackaday so it's certainly not every post. But I've long been a Slashdot reader, so when we have a great piece of content that I think fits here I try to submit it.
I never got into Who. Is it too late? And if not, where in that mammoth string of series' would one start?
An excellent set of points. I had not considered the visual feedback loop you mentioned, but indeed this is simple to tell that it's working.
Just submitted this comment, but not that I think about it. If you want these to be easier to type you should set up your IDE to auto-replace the mnemonics. Type GT(space) and it gets replaces with '>'.
I think he's right about the mnemonics being easier to type. They're generally on dominant fingers and you use letters constantly (not so much with pipe, ampersand, great and less than). That being said, I do think the capitalization should be saved for constants, and scanning code with your eyes proves the symbology easier to pick out. Symbols are better.
In this particular situation many of the farmers have cellphones that allow texting but not smartphones or other Internet connections.
Problem not solved. Sure you can arrest and charge someone for breaking the rules but the vast majority of these cases are people not knowing any better. If these drones are interfering with full-sized aircraft, penalties don't prevent the danger presented by naive operators. This is an educational problem -- people need to know there are places you're not allowed to fly and that it's important to stay out of those with their hobby equipment.
The issue there is user input. In this case, the Atari joystick is half the fun. I've seen this same display used to play tetris with an IR remote control... it's not nearly as fun as with a joystick.
That's a good point, which is why the grand prize includes consideration for taxes (read the official rules)
Am I eligible to win your challenge?