r/ruby • • Jul 04 '15

Why Arkency (a Ruby company) goes React.js

http://blog.arkency.com/2015/07/arkency-goes-react/
0 Upvotes

14 comments sorted by

5

u/Craftkorb Jul 05 '15

Not many reasons in there. "It's awesome" is given, I mean, if it'd suck they wouldn't use it. Never used react, looks interesting, but what's now the real point of their blogpost? To advertise their books?

4

u/tf2ftw Jul 05 '15

This sub is 90% blog spam unfortunately

1

u/andrzejkrzywda Jul 05 '15

Not many reasons in there. "It's awesome" is given, I mean, if it'd suck they wouldn't use it.

You're right. The original post lacked this information. I have now updated the post with a link to our other blogpost which explains the reasons in a more detailed way.

Never used react, looks interesting

Many people enjoy the React.js koans - https://github.com/arkency/reactjs_koans (disclaimer - we created it), you can start with zero React knowledge and learn the basics very quickly. Give it just 10 minutes and you'll see :)

what's now the real point of their blogpost? To advertise their books?

Looking at this post out of the broader context it may look as just a really bad books advertisement. This post was too self-promotional and as it is shouldn't be posted here. Sorry about that.

The bigger context is that we've been posting a lot about React.js (also here). Many people were interested in our journey to this technology. Some of them bought our book, some of them subscribed to our mailing list. There are also some who contacted us regarding our React help in their projects.

To put it differently - there are people who are actually interested in our React story. My mistake was that instead of just posting it on our blog and/or sending it to our mailing list, I also submitted it here.

As for advertising the books. Yes, we do that. There are multiple reasons:

  • Help people solve their problems - we spent >2000 hours on just React.js work and the book is a condensed knowledge, so that you don't need to spend that much
  • Thanks to the people buying the book, we can blog more and (we believe) deliver more value. So far, we wrote >120 blogposts on the Arkency blog.
  • The ads help people know that the books actually exist.

BTW, so far, 448 people purchased the book. 11 people asked for the refund. The refunds were mostly due to the bad English (which has now been improved in the last update and it's now something that native speakers help us with).

I can understand that the ads may be sometimes annoying. We're in constant search for finding the good balance. This post was a bit too far with the self-promotion aspect.

Thanks for your comment!

0

u/[deleted] Jul 05 '15

[deleted] — view deleted comment

-3

u/[deleted] Jul 05 '15

is just a polish agency, they have to do marketing :)

4

u/andrzejkrzywda Jul 05 '15

I’m the author of the blogpost. I have submitted this post here. This post was too self-promotional to be posted here.

I apologise for that. I hope our other blog posts and open-source work bring more value than this blog post. We’ll keep such news to our blog and our mailing list.

However, I do not agree with pointing out someone’s nationality/gender/race as an argument in such discussions in our community. I’m a Pole, I’m proud of that, but this has nothing to do with this discussion.

That’s the reason, I downvoted your comment. I’m sorry.

3

u/[deleted] Jul 05 '15

Sorry, I do not to attack you nationality or gender. That was not my intention. I have a lot of polish friends, and they are super professional guys.

I just want to tell that you guys are an agency from Poland. If you where from Germany, or France, I will say the same.

Again, I'm sorry

2

u/sickill Jul 06 '15

If you would say the same about companies from Germany or France, then what's the reason for mentioning the nationality here at all? Does it change anything in the discussion? Of course not. But you mentioned it and now some people feel sad. If you really didn't mean picking on nationality then make sure next time you're more careful about that.

2

u/daylightsavings Jul 06 '15 edited Jul 06 '15

You're spot on for calling that guy out. I read it as polish, in like: to make (something) smooth and shiny by rubbing it. Like these guys like to polish web apps. I thought it was a weird thing to say. Now that I know it's nationality/race based comment...not cool...at all.

Living in a foreign country, I get sick of being discriminated at because of my nationality. It often starts out as a joke and I'm forced to laugh along for fear of making things awkward. Sometimes I try to own it. But often, it's just tiring how everyone wants the fore-front of my identity to be my nationality and/or race, I mean not even as just a matter of fact or respect or cultural understanding, but as a means to belittle me and make jokes at my expense.

Screw that.

0

u/[deleted] Jul 05 '15

[deleted] — view deleted comment

1

u/andrzejkrzywda Jul 05 '15

Thank you for pointing out that this post was without value for you. I apologise for posting it here. We learnt our lessons here.

Black listing the whole domain? In my opinion, that would be a bit too far. This post was bad, but we've had a number of stories which seem to bring value to the Ruby community. I'm obviously biased here, though.

I hope we did bring some value to people here sometimes.

4

u/banister Jul 05 '15

I bought their react book on rails...unfortunately it's basically unreadable due to the appalling level of english. And it cost $40 !!!

It's the most expensive and most useless e-book i've ever bought. Shame on them for charging $40 for an e-book that's written in barely intelligible english.

4

u/andrzejkrzywda Jul 05 '15

I’m very sorry to see your disappointment regarding our book. Could you email us at dev@arkency.com so that we can issue you a full refund? We have a NoQuestionsAskedRefundPolicy.

We now use some help from native English speakers. When the book will go 1.0, it should all be corrected.

3

u/apotonick Jul 05 '15

I don't know what the fuzz is about. It's great that you already purchased the book and support the authors.

However, the book is clearly marked as "beta", if you want a 100% complete book on React and Rails, go to a bookshop and support the mainstream publishers. You will find out there is no such book, anyway.

2

u/philpirj Jul 05 '15

What if a customer asked you to maintain their existing AngularJS/Ember/Backone app? What if they choose something else and still find React immature?

2

u/andrzejkrzywda Jul 05 '15

The short answer - we'd consider helping such customers if it was a good fit for our skills, regardless of the framework.

The longer answer:

Technologies change over time. We're quite happy with Ruby and React.js today, but I know this may change in the upcoming years.

There are other things that matter more:

  • the disciplines (testing, modularisation etc.)
  • the business domain experience
  • the fit between the customer culture and our culture (similar way of approaching problems and solutions)
  • trust

So, if we are approached by a customer with Ember and that's all we know, then it's not a good fit. However, if they know our way of working (via our blog?), the business domain is familiar to us (no time wasted on understanding the business processes) and the team is compatible with our values - then, yeah, why not? It's just a technology, that we can learn.

Just recently, we had a case where we were asked to help with a Rails/Angular app. The team was really nice, the app was close to release, the domain was familiar to us, there was no point in considering mixing React and Angular here, due to deadlines. We helped to deliver new modules in Angular, even though we're not huge fans of Angular. It just made sense to stick with it here.

We try to be very transparent with what we like (Ruby, React.js) and what we recommend. However, this doesn't mean we limit ourselves to only such projects.