29 replies to this topic

[Monkeydog]

I'm sad no one is going to see Bean's posts here because I love them.

[Stars]

I don't remember any JS, but I have been reading the topic.

[dhm]

JS is more suited for front-end, whereas PHP is used as a back-end programming language. A mature PHP framework like CodeIgniter works well if you're interested in the industry-standard MVC pattern. 

 

Similarly, Ruby on Rails can get you a solid foundation for a data-driven website in 15-20 minutes. The learning curve thereafter is a bit difficult since you need some familiarity with both Ruby and Rails, and the language/framework is relatively new still compared to PHP or Java.

[Donkeymog]

Yeah, I've been using CodeIgniter for a couple of months and it works really well. The documentation is great too, which really helps me.

 

I'd been looking at Ruby on Rails, it sounds great from what I've read. I might check it out next.

[lazlo falconi]

I think you guys were reading that article wrong, because it's not "10 reasons to stop using javascript", it's "10 reasons NOT to use javascript". And each point is correct in certain aspects--even the one about server side, since if you notice, he goes on to talk about how most javascript is used for forms and stuff (Although I don't agree with the "most" statement).

The point of it wasn't saying, "Don't use javascript," it was, "Don't go straight to javascript."

[Donkeymog]

I think it's just finding the balance on what you should use Javascript for and what you should regulate to the server. Personally, I don't think the server should do much after the DOM is loaded, and everything after the fact should be relegated to Javascript. And I don't really think Javascript should be a replacement to PHP/Python/Perl/whatever. 

 

How do you feel about Node.js? I've been encouraged to look into it. The basic idea of it is batshit insane. Javascript on the server, bitches!

[Donkeymog]

I've been playing with Node.js. It's boss.

 

Anyone else played around with it?

[Monkeydog]

Not much, but I know if you like that you'd probably love Angular. 

[Donkeymog]

So I really like Node. I've been pissing around for months with MEAN, but having played around with Meteor I think I backed the wrong monkey.

[Hyperlisk]

Node seems cool except that everything seems to have to pull down all of NPM's packages. That's pretty annoying. I can see its use as a task runner (Grunt, Gulp, etc), but I just feel like other languages are better suited to being a backend. However I haven't tried Node as a backend so I can't really talk. Just since working at my current job I love Python as a backend. It is just the best.

Also, with a lot of the recent articles I've been seeing, Mongo is a terrible thing.

Meteor does look cool. I remember seeing it awhile back and wanting to experiment with it, but I haven't had the time.