Comment Re:Right. (Score 0) 222
Please, do something if you can.
Please, do something if you can.
If only they could restore the type-ahead functionality they removed in 3.6, I would be satisfied. https://bugs.launchpad.net/ubu...
Awesome post, thanks. What about digital emulations of the analog effects? I implemented some filters for my guitar when I studied signal processing, and it was so much fun, I wish I had more time to kid around with it.
We tried neural nets back then. Didn't work.
It seems it is you that are stuck in 1960, because connectionist techniques nowadays are nothing like that. And deep-learning has been breaking record after record, even achieving superhuman performance in some tasks. And deep-learning is just a smart math trick over the regular backprop algorithm, allowing more layers without degrading the error gradients. When the models that actually incorporate neuroscientific knowledge (current research) mature, expect even better performances.
And wtf, this "I tried once, I failed, I'll never try again" is surely a loser-talk.
Ah, that explains it... I haven't realized that was the origin of his statements, but I guess you're right. The irony in his "Oh so you know how the brain works?" is that I've actually been studying it for a long time, so yeah, I have a good idea about the generals.
But after the "Wow, when did you receive your Nobel?", it's easy to see how his brain works - it doesn't!
You don't think at all, you're just a bunch of neural circuits.
Since 2011, most of my reading is done in a Galaxy S. I read before I sleep, so I use amber text over a black background, with the dimmest light intensity available. I haven't found any better alternative to an AMOLED display, it is just excellent. I have a newer Acer smartphone, but its display sucks in comparison, at least in low light settings.
And for software, I can't recommend enough the Moon+ Reader app for Android, it has everything you need and the UI is perfect, imo. If any dev reads this, congrats, great job!
Itâ(TM)s
bling bling bling!
You only realize their benefit when later on you change something you thought completely unrelated, and the "useless" tests start failing. I had my ass saved a couple of times in situations like that.
Franceâ(TM)s
And the walk of shame continues... bling bling bling! (https://slashdot.org/comments.pl?sid=9511599&cid=52681371)
I hate Perl, but even I know that you could solve (palliatively) this disgrace with a simple:
$post =~ s/â\(TM\)/'/g;
Or just use SoylentNewsâ(TM) [yeah, it was on purpose] version of Rehash, as they fixed this ages ago.
It's 2016, yet...
[...] Jet.comâ(TM)s [...] Samâ(TM)s Club. [...] companyâ(TM)s website[...]
...still happens.
- shame... shame... shame... bling bling bling
Very well said. I have no mod points, so here's my virtual +1.
But on the other hand, neither form is something that a beginner would know without being told, really you're going to need to be handed an example to learn it, so the actual practical difference between the two isn't that huge.
A beginner wouldn't know that a "read" method exists in a "file" object. But when confronted with a "file.read()" invocation, the meaning seems pretty straightforward to intuit.
Now, "local $/;" gives you absolutely nothing to reason over it. Only after your explanation I have a grasp on what's happening (which in Python could be represented with "".join(file)) , though I still don't understand how the $/ syntax means $INPUT_RECORD_SEPARATOR = undef.
It's mostly because Perl is line-by-line by default. Most of the time you don't want to read a whole file into memory, do you?
[...]
You could also do my @data = <$file>; which slurps the whole file, line-by-line, into an array, if that's what you need.
I can't say "most of the time", my guess is I use equally reading the whole file, reading chunks of binary files, and reading lines.
local $/; switches to slurp mode (temporarily).
Ahhh, of course!!! That's obvious! </sarcasm>
Not only the syntax is cryptic, the terminology is terrible! "Slurp" is a funny way to describe the process, but introduces one more step (two more for non-native speakers) to understanding it. Compare that to Python's `file.read()` and `file.readlines()` and you'll understand why Python is better for beginners and for people that want maintainable code.
Shakespeare's style might be great for poetry, but if you use it to write guides, don't be surprised if people get lost.
"If it ain't broke, don't fix it." - Bert Lantz
