tfranco

So, they do analytics looking only at the database data?

I wonder if they built the analytics system themselves or are using a COTS.

That domain needs a digital certificate.

Quarantine is killing me. I really need to stop eating beans...

They spelled aquihire wrong.

That will prob. only happen when something similar to the google glass can last more than 30 minutes on one battery charge.

Allow me to disagree. :)

I've worked on low budget one man shows. Nevertheless I did TDD all the way and, I still wrote my cap scripts to deploy and asked the client to validate the implementation was right.

You might not tick all the boxes on the list for one man projects, but you can definitely do them with a team of two.

That's exactly the opposite of what I say in the post :)

Shameless plug :)

Thanks. Same here. I truly respect the work that has been done on RubyMotion. Like I said in my post, brilliant people there.

Here: https://www.imaginarycloud.com/blog/node-js-admin-panels-str...

Amir, thanks for following up. Like I said in the article, I've used RubyMotion in production in the past. We were one of the early adopters and launched at least half a dozens apps in it. We payed for all our licenses. I love the product and this was money very well spent. It allowed us to use the same language (Ruby) in a larger portion of the projects. This was particularly important when some of our clients were small startups with an existing Rails app, and it was important for them to keep the same language for the mobile app.

I just think the support for Android should have happened a lot sooner. But of course this is easier said than done.

Moving forward to React Native is part of the same approach. It's important for us to use a technology that delivers fast in multiple channels and has a great chance of still being relevant in the next 10 to 20 years. And for me, these are the strongest points on Javascript.

And you're correct, React Native is not truly native, but it does the job pretty well without major impacts on usability. RubyMotion is truly native and very well designed IMHO.

Best of luck for the future.

I've been using Rails since 2008, and participated in more than 100 projects in these last 10 years. Either by coding or managing them. Most of these were Rails projects. Moving to node is part of planning the tech that we're going to propose to our clients during the next 10 to 20 years.

I didn't conduct a thorough analysis on the reasons why I've seen big corps rejecting Rails, so what I'm about to say is based on the the experience of being through all these projects.

But most Rails projects are connected to the innovation departments and once they passed through the PoC stage, their IT departments asked for a re-write on a tech already in their ecosystem. Supporting additional techs raises complexity and forces them to support another stack.

We were indeed able to push some Rails apps to production on enterprises, but these were usually apps that performed a specific goal for one of the departments, and once we went for the big projects within their core, tech stack was always an issue.

We're on the verge of baselining a reference architecture in JavaScript for all our projects. We did the research with parity of features that already exist in Rails (Rails Admin, Devise, Sidekiq, etc).

You might not need a year to, at least, get my thoughts on that.

Thanks for summing it up.

I avoided desktop because the last time I don't develop for desktop since 2008.

But I take a look at some options for Ruby near that time, and I don't think the ecosystem is much different now. There were a couple of options but very incomplete.

Regarding the JavaScript ecosystem, yes. Electron is a perfect killer.

I see the JavaScript ecosystem at the same level that Java was in 2006. If you pick it, you can virtually deliver to any channel.

And that as C++ developers before that.

You need to look under which title that is, and take the context into consideration. That is one of the reasons used to justify why the community is more active that the Rails one.

I avoided the tech part because, to be honest, I don't think it is relevant now. There is many information about that on the web. And from the technology standpoint both are fit for purpose if you're going to develop a web app.

The central point for me is exactly the adoption on the startup and enterprise world.

Sort of. How do you justify the fact that the corporate world is not coping with the technology very well?

It's not the point of being cool or not. If Java, Rails, etc works for you, please go ahead.

But we work on several projects by helping a lot of people at the same time. And need a solution that fits our and our client's purpose and context.

Rails did that to some extent, but I believe JavaScript will help us navigate a larger context.

Good point.

Is it?

There is Vapor. But unlike Rails, the timing for something like this is way gone.

The intentions of the authors is for Swift to take over the world. But the way it's going, it will probably become stuck on Apple's ecosystem like Objective C.

When you bitch about your competitor and everyone discover's your have feet of clay...

Good perspective. But some examples, like Coca Cola, didn't adapt that much. The logo pretty much stayed the same since early times.

Looks nice. I recognise at least one background from the library that comes with MacOS. Is that OK to use?

Just for the sake of completion, we covered ELM a few weeks ago: https://www.imaginarycloud.com/blog/elm-javascript-reinvente...

Interesting. We covered ELM a few weeks ago: https://www.imaginarycloud.com/blog/elm-javascript-reinvente...

Interesting... we covered ELM a few weeks ago: https://www.imaginarycloud.com/blog/elm-javascript-reinvente...

That was a milestone on the software industry.