I've touched only a few programming languages, not enough to say I've gained proper competency. However, after looking at my options, I've chosen to dedicate myself to learning Ruby and eventually Ruby on Rails, to eventually specialise as a front-end developer.
Is there any resources or tips that you more knowledgeable, wiser people who have already tread the path would impart to myself and others who wish to become the best coder they possibly can for the sake of their future.
In the beautiful and cutting edge world of ES6, Webpack, React and Vue and ExpressJS and NodeJS etcetc you're going for Ruby and RoR? Are you sure you know what you're doing? Have you seen the StackOverflow survey where JavaScript as an ecosystem is light-years ahead of Ruby?
No I hadn't heard of that survey, and resources like that is why I'm asking for extra info.
There's many, many things I have to take into account, weigh up, and it's a highly opinionated subject among people already in the field, so it's hard to get a diverse collection of information without being in the field already.
Anything you or anyone else brings to the table, sans baseless prejudice or nonsense, is absolutely great.
Ruby is one of my favorite programming languages. It is a fantastic object-oriented language like Smalltalk, has some of the raw functional power of Lisp, and has a terse syntax like Perl (but more readable). The creator and community are great, too.
Rails is a great introduction to web development.
Here's some good Rails tutorials.
guides.rubyonrails.org
railstutorial.org
I didn't use any books to learn Ruby but I know Lainchan has some.
Rails, Node.js, Phoenix, etc. are designed for different things. Rails is designed for quickly building smaller CRUD websites, and its loss in market share is because it isn't suited to making Twitter-scale websites. Node.js is better at this but is frankly much less fun to work with than Rails.
Do you think he's making a self-congratulatory thread informing Sup Forums of his decision? This isn't a macfaggot thread where he wants praise for his purchase. He's clearly asking for more information
>In the beautiful and cutting edge world of ES6, Webpack, React and Vue and ExpressJS and NodeJS etcetc
>Have you seen the StackOverflow survey where JavaScript as an ecosystem is light-years ahead of Ruby?
Hilarious.
you're seriously retarded if you think js' ecosystem is anywhere being lightyears ahead
i wish only people who have actual jobs or have actually contributed to oss could post in these threads
a diamond, i will install pretty diamond
diamond pretty, I collect pretty
I'm on the fence about ruby/rails for dev work as well. I've considered front end, I basically have front basics down. But the more I look at the state of the industry the more appealing backend looks to me.
This or PHP & laravel Sup Forumsentlemen?
>PHP & laravel
PHP is BIG here in Europe unfortunately.
PHP has a lot of legacy applications that are 10+ years old still running out there. Ruby has far fewer, but a lot written in the last half decade.
With Ruby, you get a nicer, more concise syntax. However, it still underperforms when compared to PHP
That said, they're both similar enough to the point where if you know PHP and Laravel, Ruby on Rails would not take you very long to get into at all, and vice versa. If you really are on the fence, I would suggest seeing what employment opportunities are out there right now for both and see if either of the two are in higher demand. You should also consider contributing to projects on GitHub in either, just so you can demonstrate some competency to a potential employer
PHP is big everywhere my dude. It's on like 82% of the all websites according to various sources. People memeing against it aren't employed.
Cool thank you very much for the response and advice. I'm pretty sure that ruby/rails here in the states is only big in a few spots. SF, NYC, and other godless places.
I think I'll go into laravel because the amount of sites that use it and I can piggyback off my friends laracast account.
Sorry for hijacking OP
Anywhere where there's a tech sector doing web stuff will have some groups using Ruby. That said, too, a lot of companies will make use of a variety of tech if they're big enough. The company I started at last week is big on PHP, but they have a few repos in Ruby as well. This is in Minnesota
Well node.js, Rails and Django jobs barely exist here in Denmark.
PHP, .net and Java seems very dominant.
I'm not against php or anything I'm just trying to maximize my employability because why not?
I really want to learn ruby/rails too. I just happen to have access to laracasts so why not go with that language since I have access to more resources for it?
I know this is a noob question but where would I find projects that need help? That sounds like a good idea and I'd like to go down that avenue.
If php has a lot of legacy stuff does that mean starting with 7 is a poor choice or is it generally easier to work backwards?
The big thing I see EVERYWHERE in the states is C# I don't know what the deal is but that is almost unavoidable it seems.
>I know this is a noob question but where would I find projects that need help? That sounds like a good idea and I'd like to go down that avenue.
You can go to GitHub and search for projects based off of issues, or just on whatever applications are interesting to you. Another thing to do would be to go to Packagist.org and look up libraries based on whatever you'd like to check out, then see the linked GitHub page for that library and see if there are any open issues.
>If php has a lot of legacy stuff does that mean starting with 7 is a poor choice or is it generally easier to work backwards?
At this point, I would start with 7. If you encounter any older code, you'll be able to work through most of it in the same ways. If you're given a platform that's on a specific version, though, just make absolutely sure that you are running the same version as you work.
Dude you are the man. Thank you very much for letting me pick your brain a bit. It's a really big help to people trying to get into the industry. It's very easy to get overwhelmed and lost on this topic.
Thanks for lighting the way for me. I hope OP can get something out of the conversation we had as well.
This is Sup Forums after all. Good luck, user
OP, the first book you should read to learn Ruby is "The Well Grounded Rubyist". This book will teach you Ruby at a very deep level to where you will be able to use the language like an expert from the beginning.
As for Rails, generally speaking I think its bad to start out learning any kind of framework. The purpose of any framework is to automate boilerplate work. Also every framework has its own opinion on how a web app should be constructed so you are forced into their way of thinking. I would suggest learning to make simple web apps in vanilla PHP after you learn Ruby. Do NOT learn PHP with a framework for the reason I mention above, the whole purpose of learning PHP is that it does not hide details and is very simple. This makes it much easier to find errors compared to the kinds of errors you get using a framework. This is the reason so many companies still use PHP, it is much simpler than any framework so is easier to fix and maintain. PHP itself is a bad language. Its not a horrible language but you will be glad you learned Ruby first because PHP will give you bad habits and obsolete ways of thinking about code.
Beethoven 9 bump
>Is there any resources
"Are there any..."
You should try "English Grammar for Dummies" before you take on Ruby.
OP here, definitely helpful info, cheers for adding to the questions.
Thanks for answering without being a dick about anything. Somehow that's apparently an accomplishment these days. But seriously it awesome to get your input as I wouldn't have thought to contribute to github projects specifically, just assumed I'd have to do some odd free projects of my own until I got competent and had a portfolio big enough to have something to show during interviews.
Have an awesome day mate.
You fucked up. Learn Java + spring or node + express
any details behind your reasoning?
Ruby is a shit language and usage is decreasing. Spring is enterprise and node is cutting edge.
I'm a former Ruby programmer with several gems published.
Ask me anything.
>Is there any resources or tips
Yes.
Read books such as Eloquent Ruby and Well-Grounded Rubyist.
Master every single standard library class. Especially Enumerable and Enumerator.
Learn the Ruby object model and how to metaprogram Ruby.
Study the Ruby implementations. How the virtual machine works. This is where the deepest knowledge lies.
>The big thing I see EVERYWHERE in the states is C#
C# is big because it is one of the best programming languages available at the moment. It blows the fuck out of Java and its ilk. Microsoft stopped being incompetent; it's spending a lot of money on programming languages research and it's open sourcing everything as well.
The real enterprise technology isn't Java, it's the JVM. There are a shit ton of programming languages that target it, among them JRuby. All of those languages have binary compatibility with existing Java software.
But yeah learn Java as well. It's not like it's hard.
Ruby is being replaced with Elixir in the minds of the masses. Elixir is easier, faster, and cleaner.
Try it out.
It does look a lot like Ruby. Built on top of Erlang, huh? I assume the message-passing IPC maps directly to Erlang semantics.
I suppose it's as good a time as any to discuss this:
>Due to their lightweight nature, it is not uncommon to have hundreds of thousands of processes running concurrently in the same machine.
Okay just how big is the stack?
Linux uses 8 MB stacks by default but the minimum stack size is about 16 KB. If configured this way, 4GB of RAM lets you run 250,000 concurrent processes.
man7.org
>pthread_attr_setstacksize() can fail with the following error:
>EINVAL The stack size is less than PTHREAD_STACK_MIN (16384) bytes.
Just how lightweight are Erlang stacks?
I don't see your point? 16KB stacks are small enough, and I've never noticed any issues with it.
Are you saying they're falsely describing it as "lightweight?"
I'm just trying to figure out the source of their claims. Languages that implement "lightweight" concurrency often claim to be able to keep track of millions of them. For example, Go's stacks apparently take up about 4.5 KB, allowing the implementation to keep track of about 888 thousand goroutines using 4 GB of memory, maximum.
Where is OP
>It's on like 82% of the all websites according to various sources.
Because turdpress and some of the big forum packages are php
Isn't RoR a back end framework anyway?
get a load of this retard
I dont understand, you're asking about a language and a framework used for backend development and then say you want to become a front end developer?