I decided that for my first programming language, I want to learn Ruby on Rails. Yes, I'm aware that it's a framework and real coding is a lot more involved, but I would like to start designing web apps and all the advice I get is that Rails is the best option.
I'm making a concerted effort to learn, but I keep running into roadblocks; I'm a true beginner to this and a lot of the material I run into seems to assume I already know some things.
So what do I learn BEFORE getting into a specific language? Command prompt? MySQL? Power Shell? A text editor?
What's the most efficient order of operations a completely noobish person would have to learn in order to work their way up to actually programming?
i would suggest running linux on a VM and working in that rather than in Windows, getting Rails running efficiently can be a hassle. if you just want to learn Ruby then Rubyinstaller + some form of editor/IDE is fine.
Right now, Windows is my only option. If I get linux it would be an a separate harddrive to boot off of.
Still though, does it make sense to dive headfirst into Ruby without really knowing how to use the command prompt?
>If I get linux it would be an a separate harddrive to boot off of.
run in on a VM...
>Still though, does it make sense to dive headfirst into Ruby without really knowing how to use the command prompt?
of course. the only thing you'll be using command prompt for to start off with is changing the directory to where your ruby files are and running them.
i'm not OP but:
If I already know programming (at least on a conceptual level, i.e. I know what an object is, common design patterns, have made small text-only programs in Java and Python before etc but have no real whole-project experience), should I use the Pickaxe book (even though it's 15 years out of date) or pick a different guide?
I wanted to learn RoR to get some proper web development under my belt because their shit won't advance my career at all, and I figure building my own full website would be a good learning experience and portfolio-builder.
this is me, second paragraph was meant to say:
I wanted to learn RoR to get some proper web development under my belt because my job's current proprietary language shit won't advance my career at all...
i would use it. there's a more up to date version of the pickaxe book for sale at https://pragprog.com/book/ruby4/programming-ruby-1-9-2-0 if you're concerned that the book is too old.
P Y T H O N
While Rails does have incredible performance, Making shit on python is dead easy, after importing almost everything you need to do anything you want, it's just a matter of writing code to specify what import runs where and your done
None of these handles concurrency right, although Go is the least wrong one. Not OP's concern right now but something to have in mind. Erlang and Elixir and pretty much they only option for writing concurrent web application that scale painlessly to multiple server. (That said, it's way slower than Go.)
But it really depends on what you want to learn, if you want a better understanding about computers and coding in general start with something else. If you just want get a job, learn rails.
OP, get ahead of the curve. Rails is hot "now" as in, right now. By the time you become competent, the market will be so oversaturated with railsdevs that you won't hold a candle to any of them.
You want to get a job, as a junior, in a freshly appearing market... learn JS. Learn pure JS. And on top of that, learn node.
JS scares people, railsdevs (as in "I learnt rails and just rails") are hopeless with it. But it's the future, it's fucking fast. This is why you're seeing things like coffeescript and typescript appear. Because we ALL know that JS is a shit language, and these "sub-JS" languages that compile into JS are there to help make it readable. But at some point, you'll come undone with either Typescript or Coffeescript. It just wont work the way you intended it to, and at that point, only someone who knows raw-JS will be able to fix it.
In short, learn JS.
No, it's picked because it's a full programming language, running in unison between the front and back.
It's a full stack programmers toolbox, but for fucks sake, don't expect /gd/ to have any idea how to use JS on the back end. They're too busy arguing about which font is the new hotness.
THESE TECHNOLOGIES ARE HARMFUL. THE ONLY SOLUTION IS STATIC HTML (FUCK 4.01 VALIDATION FREE YOUR CODE) WRITTEN ON YOUR TOASTER WITH A SOLUTION LIKE VI AND POSSIBLY STITCHED TOGETHER WITH ASM.
STYLESHEETS ARE CANCER AND DON'T RESPECT USER'S FREEDOM.
You should really check out >>47764199
They have a course in both ruby and ruby on rails, and then a bunch of other beginner level courses. They are really easy too, but will still teach you a lot of what you need to get started.
Will it teach you to be good at anything? No, but it is great for getting past the "Oh, god I don't know how to do shit in this language, I'm going back to whatever language I'm comfortable with now." phase of learning a language.