I feel this is spot-on. From previous experience trying to get into it, trading gold or silver today feels like buying from car dealerships. If your platform delivers on its premise you may well have built the Tesla of precious metals.
2K seems like a fairly high price of entry. Are there plans for fractional trades? (I'm not even sure that's a thing).
French guy living in the US now. I miss "Eau de Cologne" deeply.
We've used it with fevers, headaches, indigestion... and my 95 y/o grandpa still uses it daily.
My understanding is the custom is probably more widespread than it being endemic to Turkey.
The immunology department of Marseille, France reported 3 days ago that taking hydroxy-chloroquine and azithromycin together led to 90% of pilot program patients testing negative after 6 days.
There are also several publications under review at the NIH. Glad to see the US Gov. stepping up to the plate so fast on the subject.
Contact Uber via Twitter directly, also contact their customer support.
As for the driver's accusation it should be verifiable since they have cameras running.
Congratulations on Raptor, I'll definitely give it a whirl.
Regarding static asset serving, I'm fairly certain serving them through the application server is often not the way to go anyway.
I personally just marvel at the implications of opening up an API for it.
Imagine playing Youtube workout playlists, or powering up other devices through it, it could certainly be the voice hub of the house.
It's one giant step towards the enablement of the "internet of things" for the household.
As I said, I've used Sails.js. Their ORM is subpar, doesn't even support associations yet.
By wrong I meant that where Node.js shines most is in its unified approach to client/server relationships. Since you're building an API (as in server-side logic with world-facing endpoints) you may want to stick to Rails, since it's great at that out-of-the-box, for tried-and-true.
It seems that Go is fast, so if you expect a very high volume and want to keep the server bill low (I don't know about the developer cost comparison) it might be the way to go.
I've used Sails.js (built on top of Express.js) and can't say it's anywhere near Rails yet.
Also, Node maybe be the "wrong" tool for building APIs. By wrong I mean it's not its particular strength.
Absolutely, screenshots & icon are the first hook to an app. In my opinion screenshots greatly influence my decision if I'm presented with two unknown apps of potentially same value/ratings.
I'll only make one point (out of the many) regarding my own experience from having worked at both large corp and startups:
- Big Tech Companies have way more money to fund new projects. If they do back a project up, they give it proper resources. Big companies are however more stringent about which projects they back, and the risk has to be as minimum as can be. Business sense most often trumps vision.
- Startups are very free-form. There might not be money floating around but organic (as in self-thought-out, grown, and nurtured) projects are encouraged and rewarded.