241–250 of 479 posts
What's Shell? If you mean Unix/Linux shells, you should have picked a couple, or just used Bash, because many people would upvote one shell and downvote another. Csh, Bash, Zsh are completely different when it comes down to what you like or dislike.
Regarding the language itself, what's there to dislike about C#?
* References are nullable by default (IIRC Hejlsberg himself would do this different if he could)
* Its C-derived brace-heavy syntax can make C# code a bit messy-looking and stretch out a bit vertically, especially with the community's preferred brace style
In my very uninformed, and novice opinion, which you should entirely disregard, it is my probably incorrect estimation that the Rust developers are in maybe over their heads. I don't like saying negative things about an interesting idea, good engineers who mean well, so I don't like this so please someone convince me why I'm wrong. A few things: The multiple ways to manage memory seem completely messy to me, the vari…
When writing Rust, you simply tag those variables that the current thread of execution is responsible for free()ing when they go out of scope. The compiler enforces correctness and can tell when you've tried to use a variable that's no longer available. There's no such thing as an invalid memory reference and so long as you avoid using a GC library, there's no overhead whatsoever. When the compiler's happy, you can rest assured that your program is free from entire classes of subtle bugs that can lie in wait for years before you get your first segfault.
The Rust team has admittedly put very little time into optimizations at this stage. However, Rust's manual memory management combined with LLVM's existing optimizations have put its performance on par with C in several (simple) benchmarks. In others, it can be found somewhere between C and Go. That's quite a feat for so young a language.
Forgive my gushing. I'm very excited to finally have C speed and high level language features without segfaults.
Earlier quoted context omitted.
To be really honest, a Lisp programmer doesn't really see that many parens in his code. And clojure doesn't even have those many parens. Maybe its just me, but I have only seen those who haven't used Lisp complain about too many parenthesis.
As I mentioned, but you still downvoted me, I didn't downvote lisp. I have used lisp - required to use it in a course. And I do recall seeing that many parentheses in lisp programs. I recall seeing that many parentheses (and curly braces) in C, C#, Java, Javascript, Perl, Scala, groovy, PHP, and other programs, too. Let's not pretend they don't exist though.
What I meant was, Lisp programmers usually learn to ignore the parens. When I look at a Lisp code, I just see indentation and code. Your eyes train themselves to do that. Also I have never found excessive parens to be an issue at all. But like I said, maybe thats just me.
Personally I like and dislike Javascript.
Funny, I'd say I like functional programming... and yet I disliked all the functional and/or lisp-like languages that are the bees knees these days... Scala, Scheme, Clojure, Haskell, F#, ... All of them have neat sides, but I'm not really productive in any of them. There are things like too-clever type systems that get into your way, instead of catching errors. Constness can be silly in C++ if you are not careful, b…
Sure it has warts like all other languages -- memory hog, weird design patterns, bulky code -- but a lot of those can be easily avoided or worked with.
Sorry for the rant. I've just never had someone give me a straight answer as to why Java is so disliked. It usually has something to do with design patterns (FactorySingltonParentFactory.helper.blahblahblah) but that's just preference and is hardly the common case with Java code.
What is it about CoffeeScript that people don't like?
Most of the time, it's easy to ignore programming languages that you aren't familiar with. In day to day programming life, you're not going to be running into many examples of Eiffel, or Dylan, or D or E, in the wild. So you're not going to feel very strongly about them, either pro or con. For better or for worse (I think for the better), CoffeeScript is fully interoperable with JavaScript. The runtime characteristic…