Live data from Hacker News

Poll: What are your liked and disliked programming languages?

news.ycombinator.com

261–270 of 479 posts

Re: Poll: What are your liked and disliked programming languages?

#261

I like Prolog Also, I have a love/hate relationship with a lot of these langs, so votes go in both categories, I suppose.

Same here. I like many languages, the only two I dislike (although not in the hate category) are PHP and Java

Re: Poll: What are your liked and disliked programming languages?

#262

Saddened to see a high number of ColdFusion dislike votes. As a CFML developer who routinely bears the brunt of gleeful derision, allow me to point out what you're missing out on. Yes, ColdFusion was a bit awful in its early days, but to be fair, it was pretty much the first of its breed, predating PHP, JSP, and ASP. Modern CFML is a JVM-native language and framework that runs in a Java servlet engine. There are thre…

I liked ColdFusion as a whole but really disliked using it in a professional context - most other developers just seemed to have a bad understanding of how ColdFusion specific variable scoping worked.

Re: Poll: What are your liked and disliked programming languages?

#263

Polls like these are amusing but they're not particularly helpful. They broadcast subjective feelings about the "coolness" of languages at the expense of objective evaluation of languages. How many of you upvoted "Go" even though you've never really tried Go, just because you feel like it has got zeitgeist and pizzazz and you're attracted to trying Go? Did you downvote Visual Basic? Have you ever used it? If not, you…

Since this is a thread about biases, I'll phrase it like this: Yes, I have used Go, and yes, it does deserve the laurels.

Re: Poll: What are your liked and disliked programming languages?

#264

Earlier quoted context omitted.

I didn't down vote those or other languages I haven't really used. But you honestly can't think of any feature of those languages that might turn people off? ((((((((((((((((((((((((((((((((((((? any)))))))))))))))))))))))))))))))

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.

It was easy to dismiss Clojure for Scala and Haskell when I was first exploring functional programming.

Clojure was alien. When extrapolating what it might be like to work with Clojure, prefix notation (+ 1 2) was an obvious downgrade to infix notation 1 + 2 in a REPL. Arrow-keying your way around s-expressions on http://tryclj.com/ just seemed to confirm it.

But it's sort of like Vim: if you could see your Clojure workflow in a month, you'd be sold now. But since you can't, and since you don't know about Paredit, and since you don't realize that you probably will never even use a REPL since you'll be evaluating code in your actual source files, it's hard to be convinced and that's just how it is.

And there's still the risk of a month going by, just like in Vim, where you never even arrive at that killer could-be workflow because you never happened to stumble upon it and you don't even know it exists.

Re: Poll: What are your liked and disliked programming languages?

#265
post #63

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…

> The multiple ways to manage memory seem completely messy to me, the various ways to box values and what not and what the implications are. It's not pretty, it's not elegant, but then sometimes things aren't. I'm complaining about prettiness over usefulness somewhere else in this thread. But the box memory model thing left me feeling like it was a convoluted solution that could end up in confusion.

Rust is also the only industry language I'm aware of that gives you memory safety without garbage collection. We have some changes in the works to reduce the cognitive burden of the pointer types before 1.0 (most notably putting GC in the library).

If you firmly believe either (a) memory safety is not worth it or (b) garbage collection is superior to manual memory management in all circumstances, then Rust is not for you. That's fine! I don't want Rust to be the end-all-be-all language for all projects, and I love language diversity. But it's precisely this feature—low-level, runtimeless programming without segfaults or memory-related security vulnerabilities—that makes a lot of people interested in Rust.

> No SSL stuff. Not much encryption stuff. And worse of all in their mozilla IRC channel those guys said writing such things should be left to experts, that people should always use the C libraries with rust.

The opinion of the security community, including tptacek on Twitter, has been unanimously in favor of this decision. We consulted with our security team before deciding this. There is literally no reason to write security code in Rust, except for memory safety; the FFI in Rust is extremely well-integrated and you can call C code like it's Rust code (in fact, there's even work being done to optimize across C and Rust!)

> Being able to make HTTPS requests would be a pretty important feature for a browser like Servo I'd think.

Servo will be able to do HTTPS requests, of course. The plan is to do it via NSS.

> The pace of development. Given the state of the network io library, the many packages required to get to a useful state, it seems like it's going to be about a decade or so before Rust is even usable.

The fact that it requires several packages to get useful things working is a deliberate design decision. Rust's philosophy is small, composable modules—it's like Node in this regard.

We don't have SSL yet, and the I/O needs work, but the new scheduler, which involved a complete rewrite of the entire I/O subsystem, is literally 3 months old. I don't see how you can extrapolate from that to the idea that it'll take 10 years to make an SSL connection.

Re: Poll: What are your liked and disliked programming languages?

#268
post #80

Earlier quoted context omitted.

If C# wasn't made by Microsoft, but had a similar toolset and feature set, i would offer the opinion that it would be the top managed language.

I don't understand that attitude. First, you can use C# really well without depending on any Microsoft tech. Second, Microsoft standardized the language and made a community promise not to enforce their C#-related patents (like e.g. Oracle did against Google for Java). So, it free, it has full FOSS tooling. What's the problem?

The standard only covers up to C# 3.0, if I am not mistaken.

Re: Poll: What are your liked and disliked programming languages?

#269
post #199
post #144

Earlier quoted context omitted.

If that is your point, than you really failed to support it. Obviously you can do stuff in PHP. You could have done all that stuff in any scripting language. The closest thing to a benefit you listed was "we already had PHP installed on a server". If that is your best sales pitch, you should stop trying to sell it and let others take on that role.

My point was speed of development deployement,but you're not smart enough to get it whatever language you use.

Why not JS?

Re: Poll: What are your liked and disliked programming languages?

#270
post #80

Earlier quoted context omitted.

If C# wasn't made by Microsoft, but had a similar toolset and feature set, i would offer the opinion that it would be the top managed language.

I don't understand that attitude. First, you can use C# really well without depending on any Microsoft tech. Second, Microsoft standardized the language and made a community promise not to enforce their C#-related patents (like e.g. Oracle did against Google for Java). So, it free, it has full FOSS tooling. What's the problem?

> First, you can use C# really well without depending on any Microsoft tech.

As someone who is coming from a very FOSS world and trying to learn C#, I have to counter that no, C# does not have a really good open source ecosystem. Mono works, MonoStudio is pretty decent, but it lacks all of Windows, and there isn't much to target that is not Windows if you are doing anything that is not a webapp.

Objective-C also has a pretty decent open source toolkit in GCC, but a toolkit that lacks Cocoa is like trying to eat dinner but forgetting the food. Mono is a great toolkit, but it's missing 80% of the libraries that makes C# an easy language to use. You've got your forks and spoons, but you've got nothing to eat.

Note that I'm not complaining against C#. I'm really liking the language and everything I can do when I'm in a Windows or Windows Phone environment. I'm arguing that C# is not as portable, in practice, as everyone continually claims.

Post reply on HN