51–60 of 380 posts
Earlier quoted context omitted.
I'd like to know why people are downvoting this.
For Python there is no native support for threads because of GIL. You can get around this through multiprocessing etc but these are hacks
Thing that really gets me about perl is the syntax, it's horrendous. No other reason, that's all. Just the syntax.
why is everybody saying they are put off by Go? Did we pass the "trend" phase and now it's cool to say go sucks?
Thing that really gets me about perl is the syntax, it's horrendous. No other reason, that's all. Just the syntax.
I haven't looked at Perl 6 yet, don't know if that's better or worse. Too many other things to do, and I don't think I'll ever work with Perl professionally again, that ship has probably sailed.
Earlier quoted context omitted.
I'd like to know why people are downvoting this.
For Python there is no native support for threads because of GIL. You can get around this through multiprocessing etc but these are hacks
Earlier quoted context omitted.
For Python there is no native support for threads because of GIL. You can get around this through multiprocessing etc but these are hacks
Only relevant on CPython, other implementations don't have a GIL.
In #devops is turtle all way down but at bottom is perl script. - @devopsborat
> Why is this important? Concurrency is hard and if you want M:N thread multiplexing (i.e. WEB SCALE CODE, where application threads aren’t pinned to pthreads) your options today are precisely Erlang, Go, .NET, and Perl 6. I guess the author doesn't know about Haskell? The concurrency story for Haskell is great, and using the right library, you can literally just define types for the routes for your backend and then…
Earlier quoted context omitted.
Indeed, a GILless bytecode VM is worth a look.
GIL less yes, but not lockless. The previous perl6 VM, parrot, had lockless threads, scaling linearly per native core. MoarVM even needs to lock on hash or array accesses, which is certainly not state of the art.
> Concurrency is hard and if you want M:N thread multiplexing (i.e. WEB SCALE CODE, where application threads aren’t pinned to pthreads) your options today are precisely Erlang, Go, .NET, and Perl 6. Putting aside the "web scale" jokes ( http://www.mongodb-is-web-scale.com/ ), this statement is still absurd. Every major language, or at least the ones that matter for backend development, has support for thread multipl…
I'd like to know why people are downvoting this.
It's probably just my age, as I started out online when most discussion forums lacked explicit voting mechanisms. Before social media came along, and "gamified" human conversation. Maybe it helps police trolls, but at the cost of encouraging group-think and excessive meme-referencing, and just making a lot of people more neurotic and insecure in general. Overall, I think that online discussion is worse than it was 15 years ago, due to the psychological effects of all the imaginary Internet points.
But anyhoo, at the time I saw this (45 minutes after my original comment), my comment had 25 votes and was the top-most thing on this page. More often than not, if you wait an hour, the crowd straightens out the impact of any early outliers.