I also think Perl 6 has some really cool and innovative ideas. Far from using it to smear Perl, I think it is more interesting than previous versions.
But you are in denial if you think that this chart isn't a reasonably representative cultural artifact of the Perl community and the Perl aesthetic. Perl 5 is not exactly poor in operators, and it is the same core community which produced both.
I don't think that Perl is bad. I am saying that Perl is very strongly what it is. And while some people won't like that aesthetic, I don't see why anyone should apologize for it.
This is an interesting idea, but if you need an extremely terse DSL which doesn't look anything like Python and has to be learned anew,
why not just use Perl directly? Maybe for environments where you can't install Perl?
Newbies writing code for things like (say) fiddling with directory trees should absolutely be writing unit tests, using VMs, etc. so that the worst outcome is that they waste time. Which isn't necessary if they devote some attention to properly learning the language.
I am not posting this to bag on Perl, but just to show its fingerprint. If you find that periodic table to be funny or cool then you are a lot more likely to be happy with Perl than if it makes you shudder.
Given the huge amount of disagreement in this thread and in the world, about what religion one should have, it is more than a little ridiculous to imply that people who don't swallow some dogma whole are 'reinventing the wheel.'
I don't accept your implication that it is bad to think for yourself. What kind of spiritual life are you living if you are only repeating what other people say rather than actively engaging with the subject?
If you are applying for a job in (say) mechanical engineering, your experience in track and field should not outweigh greater experience in mechanical engineering. This isn't a bias against track and field, it is simply an observation that track and field has no demonstrable link to being better at mechanical engineering.
If track and field is not relevant to what you are applying for, and is only something you do in your spare time, then what good reason is there to put it on your resume?
I didn't read this use of the word "McCarthyist" in that way.
It is really extravagant to use this to smear Canonical as being just as bad as Microsoft-in-the-90s. Really? What is Canonical doing to destroy GPL? Nothing. In the worst case they have used inflammatory language to ask GPL zealots to leave them alone, not to mount some massive assault on Open Source.
Breeds with really severe genetic problems that make them miserable and completely unviable outside human care should be allowed to go extinct. It's not ethical.
Many, many people who get degrees from CS programs won't step back to think about the problem, will solve the same problems over and over again, will not really understand the theoretical underpinnings of what they are doing, and so on.
I suspect that comment was more about the analogy of building detailed models out of pasta; in other words, that the subtext was that it looks like a painstaking technical feat achieved with strange materials for the purpose. And maybe in that respect all the more impressive.
PHP gets a bad rap because of problems with its design and implementation and some loosy-goosy culture (though most of these can be worked around or smoothed over by a framework and personal discipline, core language issues can be a form of technical debt). Really fixing this might require a breaking new version like Perl 6 or Python 3. But of course you can still build things with it. Like models of Neuschwannstein Castle ;)
These arguments are terribly heuristic. The full stack of software included in any significant JavaScript app is big and complicated. There are already runtime differences, and we aren't saying that those make JS unusable. There is not going to be a big 3->4 migration any time remotely soon. No 'version hell'. The current story for Python compatibility is certainly much worse!
I don't think that it's the right approach only ever to allow JavaScript (just because every time anything else is mentioned, we inevitably go off on this tangent).
There is no indication that browsers are going to standardize on a VM (let alone NaCl) any time soon.
If someone just stopped bikeshedding and did Python in the browser, there's no reason a machine-level bytecode or whatever couldn't be implemented later.
Alternatively, perhaps nothing changed, and the public propaganda about Linus is generated mostly by people who don't interact with him, and flaming about high-level things like driver support is only tangentially related to what it is like to interact with Linus.
How would you avoid this? If a change is made quickly due to because that other lone guy filed his bug report first, then the solution would have been to, well, ignore his report. However, a project which did that might well ignore your report too.
The question isn't whether there are easier ways of producing, but whether the thorium reactor doesn't provide better concealment for producing what would bring unwanted attention when done in the 'easier' way.
That has nothing to do with it. GP said that it's good for Python that Guido doesn't work on it full-time, and instead keeps his hands dirty with other projects. But this experience of Guido's doesn't really expose him to 'thousands of people' any more than looking at the Python issue tracker would.
My point is that Ubuntu's main job is and always has been as a package curator on top of Debian.
If you are a long-time Linux user then you should not have a problem using apt-get or synaptic, or installing xubuntu-desktop or whatever you want. You should also be familiar with the concept that some hardware does not come with good Linux drivers. Ho hum.
Any popular linux distro lets you choose your desktop and almost everything else, the main reason to choose one distro over another is your faith in their package curation
You mean taking care of driver issues, taking slightly better care of newbies, making it easier to install useful nonfree stuff and releasing reasonably fresh packages in a Debian-based distro?
It bears mentioning that Python can satisfy many of Go's use cases too. A fairer way to put it is that there is a lot of overlap across modern programming languages