bonn1

Node: yes

Express: yes

Neo4J: why not

Angular: rather not

With 'more than 6.5 million monthly' they should do between 50K - 200K/m depending on the bizdev and sales skills.

50K is not enough to keep operations running, 100K would work with editors from low-wage countries.

But still a bit odd that they ran out of money.

Don't know if the concept of DevOps is bs but I know that it's unfortunate if a developer never did system administration: there are many of this "git push heroku" kind of devs who pee in their pants if they have to deal with bare metal and the production servers. It's not that they wouldn't be able too handle them, it's that they are afraid because they never did and besides, good system administration knowledge leads always to better application and system design.

Dogmatic thinking is never good. I've been on many conferences and many could been perceived as wasted time. And on one which was one of the worst I met tons of 'useless' people and by accident one guy who invested in me $4M.

So you never know who will be 'useless' and on conferences you meet so many people in a very short time, that it's ultra efficient. And you get appointments easier because meetings can be quicker.

However, most important with any conference is that you try to get at least 5-10 appointments for a conference which means you have to reach out to min 50

Hijacking the thread: Anyone made already experiences with HTTP2, Node, Express and Nginx together?

Where do you see 1sec latency difference?

EDIT: ok found it and it's striking, the difference is even more than 1 sec (total loading time)

Do they have a showcase where the same app is implemented on both iOS and Android?

"A friend of mine ..."

How to save context with any note/todo app/list:

Just append a "#context"

Many folks in this thread are expressing that it's the OP's fault and not Ruby's.

The OP made his post as objective as possible, politely written and nobody is loosing his face, neither Ruby as a language nor the Ruby community. But people are still resentful and fire back.

I believe it's not a discussion about Ruby anymore, its strengths, its weaknesses and wether Ruby still fits in 2015—no it's the fear of people that their core competence might be less worth in future. That all the time and energy they invested all the years into one language might be not a good investment anymore. The fear that better tech will replace their tech and that they have to start at zero again.

I know I am going to be heavily downvoted for this post. Before you downvote just think a second again why you'll downvote me.

> The persistence module is an optional extra

But a DB offers usually persistency and you called your product ForerunnerDB

I still think that the communication/positioning/branding of ForerunnerDB could be improved since it's misleading.

But at the end you have to store it somehow and thus you employ the underlying browser DBs for that (like IndexedDB or WebSQL) => wrapper

re 2.: sure? And did you try it with the new Google Mobile Freindly Test too?