Can you explain this more, or point me to a resource that explains the whole Space+Enter thing? I just did a Google search and didn't turn anything up. You're saying that pressing Space+Enter on a Chromebook is hard-wired to do bad things?
I don't have one — and am not likely ever to buy one — but my curiosity is now piqued.
Apparently, then, you have never used a Mac laptop.
Touchpads are for fat people.
Trackpoints are for dumb people. You can't even do the most basic operation (two-finger scrolling) using a trackpoint. The only thing you can do with a trackpoint is point. That's it. That's dumb. Enjoy the dumbness, though, if that's your preference.
I agree that teaching kids to code is not a good idea.
Gotta disagree with you there. If you mean forcing kids to learn to code (as in required curriculum) is not a good idea, well, then, ok, maybe. But to refuse to mentor a child who is eager to learn programming is stupid and shortsighted, IMHO.
I disagree with you. GP is spot-on. 30+ years professional programming experience here, and I agree with the GP on every single point. There's nothing arrogant or hauty about what GP is saying. The code he presented is garbage and his revision is much, much nicer. The fact that the original version was written by so-called professionals is extremely sad. Some people just can't write elegant code at all, unfortunately.
You prefer the semicolons because that's what you learned with and you've been doing for a while.
You would be wrong on that. I prefer semicolons because they make statements unambiguous.
If you had learned with line breaks, you would prefer it instead. Personally, it's just one less character I have to type virtually every line.
You would be wrong on that, too. I actually did learn coding originally in a language that used line breaks for the end of a statment. When I learned C, and switched to semicolons, it was a breath of fresh air for me.
It's not pronounced conch, it's pronounced zonsch.
Jesus, seriously? Zonsch? That's even dumber than being pronounced conch. At least if it were spelled Xonsh and pronounced "conch" they could claim that the X is a (chi) like TeX does.
You'll also notice how other languages need a semicolon after each line, whereas Python (and Julia, Fortran etc.) understands line breaks. I guess early programming environments had a good reason for cramming multiple statements on one line, but now that we can use line breaks for readability, it might as well be a part of the syntax.
I prefer languages which require statements to be terminated by a semicolon (C, C++, Java, Perl, etc.) — and not because I cram multiple statements onto a single line all the time. I just find it much easier for my mind to parse the syntax. I also prefer poetry that places a period at the end of a sentence rather than making me think about where the sentence ends.
I develop in python, java, and objective-c... you know what I hate more then python? Putting parenthesis around every single conditional statement. Once you work in python for awhile and go back, you start to notice how many brackets there are in the other languages.
Can you explain this more, or point me to a resource that explains the whole Space+Enter thing? I just did a Google search and didn't turn anything up. You're saying that pressing Space+Enter on a Chromebook is hard-wired to do bad things?
I don't have one — and am not likely ever to buy one — but my curiosity is now piqued.
I've never had a touchpad that doesn't suck
Apparently, then, you have never used a Mac laptop.
Touchpads are for fat people.
Trackpoints are for dumb people. You can't even do the most basic operation (two-finger scrolling) using a trackpoint. The only thing you can do with a trackpoint is point. That's it. That's dumb. Enjoy the dumbness, though, if that's your preference.
Give me a trackpoint and I will buy it. Touchpads suck, period.
Oh, Sweet Jesus Christ. I'd rather slice my throat wide open and bleed to death than use a trackpoint. The touchpads on Mac laptops are awesome.
if you re-encoded your lossy files enough they would eventually sound like garbage.
Not if you use a decent bit rate. For example, 192 kbps AAC can be re-encoded 10 times and still sounds great.
Thank you for pointing that out. I hadn't realized how dumb I was.
He presented no code,
That's odd. I thought the subthread I was replying to had the code in it. Here's the code:
https://ask.slashdot.org/comme...
Interesting. So a \ character in bash, for example, or in the C preprocessor, is sort of like an anti-line-break.
I agree that teaching kids to code is not a good idea.
Gotta disagree with you there. If you mean forcing kids to learn to code (as in required curriculum) is not a good idea, well, then, ok, maybe. But to refuse to mentor a child who is eager to learn programming is stupid and shortsighted, IMHO.
Excellent example; thanks for sharing! Wow, that is really shitty code. Your rewrite is much cleaner.
I disagree with you. GP is spot-on. 30+ years professional programming experience here, and I agree with the GP on every single point. There's nothing arrogant or hauty about what GP is saying. The code he presented is garbage and his revision is much, much nicer. The fact that the original version was written by so-called professionals is extremely sad. Some people just can't write elegant code at all, unfortunately.
And why would someone need to trademark and open-source shell?
You prefer the semicolons because that's what you learned with and you've been doing for a while.
You would be wrong on that. I prefer semicolons because they make statements unambiguous.
If you had learned with line breaks, you would prefer it instead. Personally, it's just one less character I have to type virtually every line.
You would be wrong on that, too. I actually did learn coding originally in a language that used line breaks for the end of a statment. When I learned C, and switched to semicolons, it was a breath of fresh air for me.
but if you always put a line break between statements then a period is redundant
Not true. It would still be ambiguous whenever a line wrapped to the next line.
It's not pronounced conch, it's pronounced zonsch.
Jesus, seriously? Zonsch? That's even dumber than being pronounced conch. At least if it were spelled Xonsh and pronounced "conch" they could claim that the X is a (chi) like TeX does.
You'll also notice how other languages need a semicolon after each line, whereas Python (and Julia, Fortran etc.) understands line breaks. I guess early programming environments had a good reason for cramming multiple statements on one line, but now that we can use line breaks for readability, it might as well be a part of the syntax.
I prefer languages which require statements to be terminated by a semicolon (C, C++, Java, Perl, etc.) — and not because I cram multiple statements onto a single line all the time. I just find it much easier for my mind to parse the syntax. I also prefer poetry that places a period at the end of a sentence rather than making me think about where the sentence ends.
I develop in python, java, and objective-c... you know what I hate more then python? Putting parenthesis around every single conditional statement. Once you work in python for awhile and go back, you start to notice how many brackets there are in the other languages.
Parentheses != brackets
Just saying.
Conch would have been a perfectly fine name for a shell. Does anyone know why they named it Xonsh (I mean...wut?) instead of Conch?
Uhmmmmmmmmm. Maybe they're playing digital files from their hard drive rather than streaming from Netflix or Amazon. Did you think about that?
Spectre is a brilliant film, the best Craig by far, and easily in the top five of all 007 movies.
FTFY. It's written 007 (double-zero), not OO7 (double-O).
Who wants a computer in their living room?
If only tiny computers like a Mac Mini existed! Man, I can't wait until that becomes a possibility.
For example if gravity failed to work on tuesdays at 10am for chocolate teapots
I believe that's called a royal fizzbin.
If a small, open source project (read: hobby project), for example, gets a DCMA due to copyright
How does a small, open-source project get a Digital Millennium Copyright Act?
That digital book's technology will be gone is 10 years and dead in 50.
Only if you're stupid and buy the digital book in a proprietary format.
.epub or .txt and you'll be able to read it forever. (For the uninitiated, .epub files are just HTML in a ZIP container.)
Get a book as
[...] but to use the force of law to help you make money is morally wrong.
He said use the force. Tee hee.
Of course it should be legal.