I wouldn't say QNX is waning... It's used in trains, nuclear power stations, cars, embedded systems etc. If anything, QNX is a good counter-example to your argument because it's one of the few really successful microkernels out there.
I wonder if pg considered this: replacing up/down arrows with such a scale (0-name calling, 1-ad hominem, etc.) to force users to think about what up/down means every time they vote.
Salesforce.com has some ridiculous domain names: work.com, data.com, force.com, do.com, database.com, desk.com, social.com, etc.
I've never seen a corporation go after so many and so generic domain names... I'm assuming GP just meant that "clipboard.com" is yet another trophy domain name on their shelf.
Saying they're both turing complete isn't saying much. Firstly, even when comparing turing complete languages, it can be sometimes easy to pick out a superior one with respect to development (e.g. Brainfuck VS Haskell, also see http://en.wikipedia.org/wiki/Turing_tarpit). Secondly, it's not just about turing completeness, it is also about APIs. These languages -- vim script and emacs lisp -- don't live in total isolation, they live in an environment. Thus, it is not only the language we are comparing, but also the environment/API (what can you call? how is it called? how easy is it to do X? how many tools are available at-hand VS tools I have to build myself? etc.)
It'll be interesting to see it go head-to-head with Android. I think it has potential simply because of how popular Ubuntu is, whereas Google has yet to release a proper desktop operating system.
I'm having a hard time making conclusions based off of this data, except that Python/Ruby/JavaScript are slow, JVM is fast, and the rest are in between... It's odd how Haskell (Yesod) and C (Onion) are both slower than the JVM frameworks. Is it just a maturity issue? I know Yesod is very new relative to some of these JVM frameworks.
You are again pushing the "beheading" and "murder" argument, which is not what people disagree on. People agree already that these things are wrong (wow!). But you just hinted at what the problem actually is when you said "That may not be murder, but it is certainly something akin". So, again, the question is: what is it? When is it murder? Can I kill sperm? Can I let a woman have her period? Can I kill an egg that has just come into contact with a sperm? What about 1 second later? 1 minute after?
Keep in mind, I'm not even taking a position here. I'm just letting you know what the fuss is about.
Sure... and what caused the action? Was it not the belief? So should I have said "beliefs indirectly ruin lives"? Actually, does the action even directly ruin lives, or is it the way you react to an action that will ruin your life or not? Bah. It's just a nitpick, isn't it?
I'm not saying I have proved that I am right. I simply provided an argument for the position (which you have failed to do). I just said that homophobia ruins lives (and it does, ask a homosexual). Now, it is up to the other party to say "ah, but gay marriage is bad because the Bible says so." Then, when all arguments are done, it is up to the judge to say who is right and who is wrong.
You can't just say "umm but no one is evil and everyone disagrees and everyone ruins someone else's life some way or another so what the heck? Let's just do whatever?" That leads nowhere.
Serious issues like abortion must be approached with more care than you are offering it. Call things like they are, firstly, and avoid bending the English language for dramatic effect. Abortions deal with an "embryo" or "fetus", not a "baby" or a "generation", both of which are born beings (out of the womb). The argument is thus not "is it ok to murder people?", as you're trying to make it look like (we've solved that ethical problem already...), but rather, the question is "when does an embryo become a 'person'?".
I'm pretty sure some beliefs actually ruin lives (sexism, racism, homophobia, etc.). Do you just accept all of them as being "weird and wacky"? Shouldn't we draw the line somewhere? Even the great thinkers in ethics like Kant or John Stuart Mills draw the line somewhere, each in their own way... but both utlitarian and kantian ethics would agree that preventing sexuality equality is unethical.
How should we measure "power", though? I mean, Turing completeness is Turing completeness. You can do in one what you can do in another. So is power conciseness, then? Is it clarity? Is it maintainability? All/None of the above?
The original post is right: Lisp by itself is an incredibly powerful yet incredibly basic language. It's a functional Assembly for declarative DSLs. The most talked about Lisp nowadays is arguably Clojure, and this is probably so because Clojure provides much more built-ins and libraries out-of-the-box than other Lisps, where you'd have to build these things yourself. At the end of the day, we just want to call "solveMyProblems()", commit that 1 function call, and move on to our next project. The lower-level a language is, the further away from that goal it is, and the less reasons there are to use it.
You're conflating "success" with "popularity". Lisps weren't invented to become "popular", they were invented to get something done in a way that other languages couldn't easily do at the time. One only "fails" if one cannot accomplish its purpose. Different languages have different purposes, so "success" as a measure to compare them is inane... unless the purpose of all programming languages should be to be the most popular programming language?
Do you have a citation on that? That you cannot print metal? What about all the mentions of being able to print metals using various techniques on Wikipedia [1]?
A week ago, something broke in the toilet (the refill valve I think it's called... a long plastic tube that refills the tank after a flush). I could've just printed a new one.
I also needed a screwdriver recently, and since domestic 3D printers will eventually be able to print metal just as easily as they can print plastics, I will be able to just print one.
And these are just recent examples off the top of my head...
A workaround: the device you connect to has a bitcoin client running just to keep the block chain up to date. The USB key, upon connecting, syncs that block chain with the one stored on the key. When you connect to a new device, the block chain from the key is synced onto that new device. Depending on how often you switch device / how often you use the key, this might or might not be a useful workaround :P.
The problem with this argument is that the OS doesn't provide you with the mesh that integrates all these tools together under a consistent interface. That's what Emacs and Emacs Lisp provide. I can jump from code to documentation to org-mode (todos) to music player to git... and all the while I'm switching from tool to tool, the shortcuts are the same, the graphical interface is the same, and I never need to change windows. An Operating System doesn't give you that seamlessness... the seams are all too visible.
You're making the same mistake as GP. I love Git, and I know that asking "what branch was this commit on" makes no sense. My point is that some users have different requirements as to what a DVCS should provide. If Git can't fulfill some of these requirements, then just say "Git can't do this" rather than beating around the bush.
Although in implementation, a commit is not done on a branch, for the user, that is precisely what happens. You checkout a branch and you do a commit while on that branch. Thus, to the novice, it might be perfectly normal to expect Git to tell him what branches the commit was made on, even though that makes no sense from Git's point of view. I've never had that use case (knowing what branch a commit was made on), but if many people need it, surely explaining to them how Git works doesn't make Git any better for not being able to provide what the user needs.
From "git --help config": "To avoid confusion and troubles with script usage, aliases that hide existing git commands are ignored."
> “Use git checkout.”
This is just a jab at how "checkout" does too many different things.
> “I have a historical record of a merge commit with two parents. How can I find out which branch each parent was originally made on?”
Git doesn't let you do this.
> “Surely some of these could be made more consistent, so as to be easier to remember in the heat of coding?”
Git commands can be inconsistent.
> “git -h branch“.
This command tells you nothing about "branch" (throws error), whereas "git --help branch" launches the browser at git-branch's manpage. This goes against what people usually expect (that "-h" is just shorthand for "--help".
That's the first thing I noticed. What was used instead of Warp?
I also see that Snap got pulled in a couple days ago, so it will probably get tested in the next round. Should be interesting to see how it fares against Yesod.
depends. for small commits, a one-liner suffices. For large commits, merge commits, etc., or for repos that require you to sign-off on the commit or whatnot, a one-liner followed by a blank line and then a nice paragraph or bullet-point list is necessary. "launching a full editor" is hardly a problem with emacsclient or vi[m]
I wouldn't call Yesod "anti-haskell". By default, it relies on QuasiQuotes and TemplateHaskell a lot [1], which are extensions to the GHC. So by default, you'd have a hard time running Yesod applications on anything else but GHC (the Glasgow Haskell Compiler). These extensions allow you to write in an EDSL that generates Haskell for you. IMO, Yesod's use of these extensions are a benefit, as it allows the user to get stuff like type-safe URLs in HTML for free (e.g. you put href=@{Home} on your HTML element and Yesod will ensure that the value interpolates to a route that exists at compile time).
Haskell libraries often depend on language extensions, whether it is overloaded strings or type families or whatnot... so I think it's strange that Yesod gets picked on for doing the same: taking advantage of the tools provided by GHC to create a better environment for the developer.