if anything kills python or ruby it'll be golang or erlang/elixir ..my money is on Phoenix Framework / Elixir eclipsing a lot of the ruby on rails environment -- a lot of core rails devs have already begun building all new apps in Phoenix. I haven't really grokked elixir yet, but it's on my todo list someday when my day job eases up a bit.
Has Python killed Ruby?
31–40 of 64 posts
Re: Has Python killed Ruby?
#32Python 3 killed Python. Ruby died by itself.
Re: Has Python killed Ruby?
#33Between those two Ruby. But always Perl first if using dynamic programming languages. Never Python.
Re: Has Python killed Ruby?
#34Who flagged this?
Re: Has Python killed Ruby?
#35I use both fairly regularly, and they are very similar. Where they are different in terms of syntax or capability or philosophy, I nearly always prefer ruby. I find bundler/Gemfile/rvm to be less headachy for project dependency management than pip/requirements.txt/venv. For me, ruby code is easier and more pleasant to read. When I need to write a quick bit of temporary code or do some simple data parsing/file managem…
Do you have experience with NPM and Yarn (javascript/node) and if so, how do the package managers and ecosystem compare?
I'm asking because I'm primarily a js dev with a bit of Ruby and Ruby on Rails experience, and I'm wondering if Python/Ruby are worth investing in at this point and if perhaps instead it makes more sense to stick with js (Yarn in particular for package management) and explore more fundamental (C/C#/C++/Swift/Objective-C) or exotic (Haskell, Clojure) communities/languages/environments at this point.
Re: Has Python killed Ruby?
#36Ruby is a much simpler and more aesthetically pleasant language. Python has all sorts of sharp corners. You really should learn both but I think Ruby is a much easier starting point. Also, a lot of research on dynamic languages is being done with Ruby, e.g. TruffleRuby, JRuby, RubyOMR, and probably a few more I'm forgetting. Each of those projects is an impressive body of work in and of itself that points to Ruby bei…
> Python has all sorts of sharp corners
Could you elaborate on that? I've used more Ruby than Python, and I'm aware of the fact that it's often more 'pleasant', but I'm very curious what you can tell me about Python's sharp corners, because even without using it I've been very attracted to the 'explicit over implicit' mantra after being bitten quite a few times by Ruby's ease (quote unquote, perhaps?).
(As in, so far Ruby feels like a good choice in general, but especially to someone new to programming, but I've grown to love explicit over implicit, not to mention functional over non-functional, and so but even without using Python I'm positive I might prefer it. I'd really love to hear what the gotcha's are in that particular ecosystem)
Re: Has Python killed Ruby?
#37Ruby is a much simpler and more aesthetically pleasant language. Python has all sorts of sharp corners. You really should learn both but I think Ruby is a much easier starting point. Also, a lot of research on dynamic languages is being done with Ruby, e.g. TruffleRuby, JRuby, RubyOMR, and probably a few more I'm forgetting. Each of those projects is an impressive body of work in and of itself that points to Ruby bei…
> Ruby is a much simpler and more aesthetically pleasant language That is open to disagreement. I will say the same, but of python. HOWEVER, among the languages that put "aesthetically pleasant" as part of the charm, I think is safe to say that python/ruby are from the top 5. Any of both will be a good choice using that criteria (and even considering the troubles with BOTH), so in my mind is hard to go "wrong" with a…
Without any strong feelings for or against a particular language, I suspect Ruby is hurt more by this than Python, at least in the future, on account of being more web-focused. Can people in both communities confirm or deny this (and as I said I'll happily use Ruby in many of my use cases)?
As for JS; what with TypeScript and ES6 (despite the worry of clutter) I can't help but wonder if it's the best non-choice we could have hoped for.
Re: Has Python killed Ruby?
#38Earlier quoted context omitted.
Not just visually. It is also conceptually much more aesthetically pleasant. I still don't know how metaclasses, descriptors, __magic__ methods, multiple inheritance, all the different string formatting schemes, generators/co-routines, etc. work in Python. The amount of stuff you have to learn in Python is a lot more than in Ruby.
> The amount of stuff you have to learn in Python is a lot more than in Ruby. I couldn't disagree more with this. Python is pretty thin when you get down to it. Magic methods alone are 80% of the way to knowing how everything in Python works. Multiple inheritance in Python is way simpler than the two-pronged inheritance scheme of Ruby, where you have both a parent class and modules (which can be loaded either before…
It's odd... I have relatively little Ruby or Python experience, but I have a kind of undefined affection for Ruby but if I'd have to choice at gunpoint I'd go for Python.
I think the reason is that while Ruby does feel more 'pleasant' to me, especially the me that is new to programming, Python feels less vague, and I've grown to hate vagueness in my code.
I'd probably recommend Python to new coders at this point, but for web development I would probably still opt for Ruby on account of Rails and the Rails Tutorial. If there was an equivalent to the latter, I'd go for Python though (suggestions?).
Re: Has Python killed Ruby?
#39No. I wrote a small Rails project a while back and along with it small non-Rails utility that made used a couple of generic modules (mail, config). Both the Rails project and the utility bit-rotted faster than anything anything that I ever written. Ruby, the language, is pleasant, and you can write beautiful, terse, expressive code. Functional constructs are nice, etc. Soured me on Ruby, I am afraid. I liked Perl too…
While I'm nowhere near a 'fan' of JavaScript, I do feel like defending it by pointing out that there's a difference between the language and the browser issues. The latter are maddening and the former is less bad when you separate the two.
That said, while I personally fell JS is decent with the ES6/ES2015 additions, I do share your worry that it erred on the side of complexity by adding a shit-ton of stuff that maybe should have been more carefully considered. It appears modern JS is and will become the kitchen-sink language, which I suppose is fitting.
But once again, that's still pretty cool. I love how I can introduce someone to programming using JS nowadays and actually be able to teach a whole bunch of different syntactical concepts. I also love how what you can do with JS directly impact the one thing most of us are constantly staring at (web pages). All in all I think things turned out better than I expected as far as the web ecosystem goes. Programming wise. Don't get me started on my worries about the increasingly walled-garden world we appear to live in...
Re: Has Python killed Ruby?
#40Earlier quoted context omitted.
> Ruby is a much simpler and more aesthetically pleasant language That is open to disagreement. I will say the same, but of python. HOWEVER, among the languages that put "aesthetically pleasant" as part of the charm, I think is safe to say that python/ruby are from the top 5. Any of both will be a good choice using that criteria (and even considering the troubles with BOTH), so in my mind is hard to go "wrong" with a…
Without any strong feelings for or against a particular language, I suspect Ruby is hurt more by this than Python, at least in the future, on account of being more web-focused. Can people in both communities confirm or deny this (and as I said I'll happily use Ruby in many of my use cases)? As for JS; what with TypeScript and ES6 (despite the worry of clutter) I can't help but wonder if it's the best non-choice we co…
I think that is a side-effect that ruby in rails was ruby in the mind of many, and python was weak at first in web (before django).
In the meantime, python get a lot of love for scientific computing and other stuff, but ruby (and others, I think no even java or .net) not and then get behind in this area.
So now, when the web side have more viable options and ruby is just one of many, the effect of web on ruby is felt more, but python have a good fallback on the rest.
Python have a more diverse portfolio of options ;)