@ VentureStack Partners
Why are you spewing personal attacks? If you don''t like my arguments then just counter them. Why do you feel there is a need to attack the person? You suffering from the ad hominem fallacy? Can''t handle a little disagreement? Don''t know how to carry out a civil discussion on a public forum? What, belittling me made you feel superior? You get off of condescending people?
I''ll reply to this comment of yours with my points because it''s strike one, but if you can''t reply in a civil manner, then don''t bother replying at all.
1. Ah yes. Data privacy laws. If a country implements data privacy laws, we can migrate that country''s data to the cloud service providers. The aim is to have as much autonomy over the data as we can. Also, it isn''t like the infrastructure would go waste once the laws are enforced. Could always lease your cloud infra to the cloud service providers themselves in case your needs suddenly drop.
2. One of the reasons why Google was able to take over Yahoo was because of the file management systems. Yahoo used the traditional ones, while Google realized they could be designed in a better manner, so Google developed its own. They didn''t wait to reach a "certain scale" in order to redesign the fundamentals. This way, when the internet boom happened, Google was able to scale with the demand while Yahoo lagged. I tell this story to emphasize of the importance of building your own infrastructure in case you feel like that''s the best way forward.
3. Yes, the management of data on cloud isn''t that nimble IN THE CONTEXT IN WHICH I KEPT THE POINT. Ofc, it''s scalable. I was talking about operations. When you deploy on GCP as a business, you get a team of engineers who help you set you application and maintain it. Sure, you don''t need them when you run small applications at individual levels, but you will need them when you your data is as complex, huge, and constrained, as for an organization. You need to keep them in loop and request new features, which they deliver with the appropriate documentation. In contrast, native deployment will always give better autonomy. From an autonomy pov, native will always be better than third-party deployment.
4. No points really. IDK how you differentiate. Genuinely. Not a satire. How is it marketing when Happiest Mind''s did it, but deception when Rategain is doing similar things in similar circumstances?
5. You said and I quote, "this ''''ISN''''T A TRUE BLUE TRAVEL COMPANY'''' but a company that provides its services to travel companies." [CAPS are yours]
I looked up if "blue travel company" is a technical term, but nothing really came up. So for a second I thought you meant "blue chip", but you used a ''but'', so your second phrase is presented as a negation to the first one. The second phrase is that this is a B2B company. That implied that the first phrase would have meant "this is not a B2C company."
Maybe you meant something else [If I were like you, I would attack you here for your ineffective writing skills, because you''re using phrases that are cryptic as hell while trying to "explain" things to regular investors.]
6. My bad. I wanted to say "customer-related data providing SaaS" company, but missed those words while re-wording.
7. Wow, really? You feel companies pay for code? No. Companies pay for people who can understand and tweak the code. I''ll prove this with an example: open source. The entire codebase of the VLC Media Player, the biggest media player in the world right now, is open source. Still, they make money by providing custom features to enterprises (this is something a lot of open source org do). Why don''t those enterprises "hire anyone with half a decent knowledge of programming to write a few lines of code for them?" Because no one pays for code. People pay for the ability to understand, modify, and explain the code.
8. My point was never about the code. It was about algorithms. You do data analytics by using mathematical techniques and those cannot be patented. I know those tech giants have patents..... who design or build tangible things. Sure, Apple has patents. But what for? For the designs they make. Not the algorithms. For example, Apple''s RAM compression algorithm is state of the art (which is why iPhones with 2 GB RAM can sometimes run faster than Android phones with 4GB RAM), but they can''t patent it because you can only patent tangible things.
Even your summary has a personal attack. Hate the game, buddy, not the player. I''m not defending RateGain because I have no information about RateGain. Like I mentioned before, I''m arguing against your choice of metrics, not your conclusions.