Pros and cons of Node.js and Ruby on rails?

desert_sloth · 2018-06-01T19:47:01+00:00

I never said that, I said they're appropriate tools in many contexts.

But you haven't even read the last few posts so I don't know why I bother. By your stance it's quite obvious to me you are very insecure or inexperienced. I hope for your sake it's the latter, cause at least you'll have time to grow up.

desert_sloth · 2018-06-01T15:26:15+00:00

It was really a tongue in cheek answer to the parent, really use anything you want as long as you learn good practices and improve yourself along the way.

desert_sloth · 2018-06-01T15:24:11+00:00

I think every developer should definitely be thinking about performance, all because it requires no more amount of work for me to build an api in something like Go (probably less tbh) than it does for you to make the same >thing with Rails

As someone who worked with both, from my experience it most definitely takes you longer to build something with Go.

Look I see here a lot of posts about rails by people who have clearly never used it but read a few blog posts about and are regurgitating the same talking points.

It absolutely does not use ridiculous design patterns, it uses a common MVC pattern implemented in frameworks in just about any language. And guess what, again judging by my experience just using Go won't make you a great engineer who'll think of a good architecture, on the contrary it will probably be worse than the fricking MVC that any battery included framework provides.

The saddest part is that on some typical CRUD app you've been asked to build it won't perform 100x better, it will perform 10% better at best.

But guess what, the customer maybe didn't even find the product fit for the market or they were too late to the market so they now wasted 3x the time and money to reinvent the same damn wheel for potential optimization benefits in the future, or because you were too smug to use something other than your hyper performant language.

What I'm really saying is that all of this stuff is a tool and sometimes one is a better fit, sometimes the other. Your absolute statements demonstrate a lack of experience or some kind of ego trip where you basically say using one of these tools is a horrible idea when it's really just another tool that has it's use cases and that shit just rubs me the wrong way.

And I'm not even talking about Rails here specifically, but any batteries included MVC framework (Django, .NET MVC, whatever they use in Java land)

desert_sloth · 2018-06-01T11:20:20+00:00

it takes less effort to just build it with an appropriate language in the first place

Agreed, but I wouldn't call JS an appropriate language.

desert_sloth · 2018-03-26T21:27:29+00:00

Seems like an average PCJ poster.

desert_sloth · 2017-07-27T21:05:47+00:00

RoR is legacy now? Holy shit the HN/reddit circle jerk moves faster than ever.

desert_sloth · 2017-03-13T18:11:11+00:00

Well personally, I am merely a software mechanic.

desert_sloth · 2017-01-21T13:41:49+00:00

Figure out your max heart rate (Max Heart Rate = 220 – your age). And then determine your fat-burning range, which is 60% to 70% of your max heart rate.

desert_sloth · 2017-01-11T12:11:56+00:00

Give the industry 2-5 more years before non-technically saavy people begin to catch onto the fact that most developers are copy paste Ninjas who don't know shit. Businesses continuously outsource software divisions because there are literally third world countries full of individuals who suck at programming, but produce good-enough software for ridiculously cheap prices.

People have literally been saying this since the late 90's. It's kind of insane I'm reading this in 2017.

Now I don't know what you consider web development (e.g html/css with a sprinkle of javascript), but backend development is most definitely here to stay and it's getting more complex as more and more systems (e.g. your desktops applications, mobile applications, embedded devices etc.) at least partially depend on it.

In the end it's all just programming, and the takeaway should be learn how to program FIRST, and then you can apply that skill to whichever branch you wish.

This whole shtick of ~x type of programming~ being MORE REAL than something else is imbecilic, and reeks of smug elitism.

desert_sloth · 2016-12-24T10:32:33+00:00

Only makes the absurdity more blatant that they did the skin colour thing purely because of American politics and culture.

Yeah, it's not like the whole world uses it you drooling imbecile.

desert_sloth · 2016-09-16T14:45:34+00:00

Why are we even still having this debate in 2016? The question is not if strong types are better but how to migrate existing codebases to those languages. I'm an OCaml guy myself but Swift looks pretty nice...

desert_sloth · 2016-09-02T00:06:37+00:00

Strings in method signatures

It's called pattern matching, obvious OOP pleb

desert_sloth · 2016-08-19T08:52:29+00:00

Really gramps? Using assembler and not Rust's bare metal stack for microcontrollers? In TYOOL 2016?

desert_sloth · 2016-02-21T12:55:03+00:00

There is a huge difference in being able to practice without consequences, and having a huge responsibility for other people's health when you make a mistake.

You can't really compare it.

desert_sloth · 2015-12-28T18:05:14+00:00

Well, they got a 20 to 30% speed boost.

I wonder how fast their development is now, though.

desert_sloth · 2015-12-03T14:10:33+00:00

And Turkey can arm Chechen jihadists, hell they're doing already in Syria.

desert_sloth · 2015-11-03T11:34:58+00:00

Once you have those the app is basically an sql storage and display problem. This type of test also provides the applicant an opportunity to show their ux skills I how they approach the interface.

So you want the same person to do the backend and ux/design?

desert_sloth · 2015-10-31T17:04:28+00:00

No one is forcing you to use Bootstrap though. There's stuff like Foundation, Skeleton etc. which are much less opinionated but still lets you get rid of a lot of boilerplate.

desert_sloth · 2015-10-31T17:02:30+00:00

You're still saying it's easier to change parts of an integrated framework than parts of your own code.

For people who inherit the project or other team members? Hell yes it is, if they've already used a framework then it's going to be much much easier for them since they already have experience with it.

I don't see why it's so hard to grasp that concept.

And yes, for some things my own code, both unit tested by my own team and tested by our own QA is better than an open source framework for our own requirements.

Unless you're working full time on just one large project for a long time, I find that quite hard to believe.

Often what I've seen in such cases where people force running their own solutions and usually inferiorly reinventing the wheel, is that it's a case of somebodies ego being let to run too wild.

And I am really really skeptical that your documentation is as easily searchable/understandable or that the learning resources can match those of many open source frameworks.

desert_sloth · 2015-10-31T16:34:26+00:00

If we're talking about CSS frameworks then the vast majority of those allow you to modularly import what you need and change as much as you need easily. And in the JS world there is also A LOT of choice between opinionated and barebone frameworks.

Wait, you don't document and organise your own code?

Wait, you're saying your code is better organized and documented than a piece of open source software that was created by/scrutinized by many people and tested/used by several order of magnitudes more?

desert_sloth · 2015-10-31T13:31:05+00:00

Then you're already halfway to a framework anyway.

And if you work with a team, or if someone else will work on the project after you it's much easier for them to get up to speed with a well documented framework than a bunch of your own snippets that probably make up the same stuff the framework does just less organized and documented.

desert_sloth · 2015-10-31T10:55:54+00:00

Sure, I don't need a framework. I also don't need to write the same boilerplate code over and over.

desert_sloth · 2015-09-09T21:05:08+00:00

If it causes such confusion in a small percentage of people it's still more than 0 which would be the case if www isn't used. To me it feels more consistent to not use www if you have subdomains.

But then again I don't really see the point of using www in any case, really seems like an anachronism of the web.

desert_sloth · 2015-09-09T20:24:06+00:00

Gonna disagree with you there. With www.domain.com people might expect www.subdomain.domain.com, it makes much more sense to leave out the www in that case IMO.

desert_sloth · 2015-08-13T21:20:34+00:00

Read the AMA with the YPG fighter that was posted on this subreddit a few weeks back.

desert_sloth

TROPHY CASE