hoeppnertill
Re:The future of loneliness
on Thursday April 02, 2015 @06:59AM (#9309853)
I'm mostly nitpicking here, but you're talking of a peaceful location, whilst the quoted text talks of a peaceful society.
Assuming a society must consist of humans, a peaceful society depends on the existence of a society and thus the existence of humans, so you can't just kill everyone.
Re:St – simple terminal
on Wednesday November 26, 2014 @02:58AM (#8661470)
tic -s st.info
or setting your TERM variable should help.The reason for not including an SD card slot is that this second-class storage is said to confuse users. It mounts after the system sends the BOOT_COMPLETED broadcast and may be removed at any time. Consequently, some operations are (or were) forbidden, like installing apps on the sdcard. Explaining this to users is fairly hard and, by removing the slot, unnecessary.
With 64GB inbuilt, I don't really see that as a problem, but for my 16GB N5 and N7, it's annoying at times. Also, file transfer on Linux is... improvable. I use adb to push my music onto the phone. :P
Re:Why your first Rust FizzBuzz implementation may not work
on Monday October 13, 2014 @06:12AM (#8448132)
To be fair, you can bind to any name. So, binding to `a` instead of `_` would work as well. You could then use that bound value in the corresponding expression.
However, I would have expected rustc to complain about unused variables in
fn main() {
for i in range(1i, 101) {
match (i % 3, i % 5) {
(0, 0) => println!("Fizzbuzz"),
(0, a) => println!("Fizz"),
(b, 0) => println!("Buzz"),
c => println!("{}", i),
}
}
}
but neither the playpen nor yesterdays snapshot complains. And if you want to suppress warnings about unused variables, you prefix the variable with an underscore, or just use only the underscore, which got common to mean "I don't care what value gets bound to this name.". fn main() { let a = 0u; }
compiles with warning: unused variable: `a`, but fn main() { let _a = 0u; }
compiles silently.