Looks great. Interested in following this and wondering when you folks plan to move out of Beta to GA

We expect to have both free and paid products in GA around mid-2022.

AWS API Gateway : expensive NGINX plus : expensive Kong : Community is free but needs a small team owning it , if there is a DB KrakenD: relatively new but promising to me. ...

Agreed. I wonder why none of other competitors do that, especially in current context. There is Amazon fresh and Bringmeister but they arent as good.

All private banks up there? How has been your experience with public sector banks so far ?

Hi Abhishek,

Public sector banks will take a while, of course. But we will taking at least a couple of them onboard.

My two cents, Using OpenAPI enables in going API first. The stakeholders agreeing on an API is perhaps one of the most important things in lifecycle of the product and rest of the things really just snowballs from there. Also, an API that changes frequently is perhaps not a good sign, it will hurt the clients, new version of the API is different thing though.

My personal take is that for Jio the cellphone network is an opening to providing services that can be monetised in long run. Same strategy thats being followed by biggest tech companies across the world.

That will not work that well. Average Indian right now doesn't really have that much disposable income for such services to be very profitable. It will have to be the very long run. I doubt either google or Facebook earn a lot from India right now, and they are very well established, and their compute costs are as low as they can get. I don't see how Jio is going to be able to follow the strategy of the biggest tech companies.

I hope India does grow at a large enough rate for such services to be profitable.

I am also interested to course but 7k USD is still high to be paid as lumpsum upfront. Is someone aware if that would be a staggered payment schedule so that I can pay from my savings as I accrue them.

Thanks

It is not up-front, it is per-semester. I think there is a relatively small application fee ( $50? ). Once in, it is ~$500 per course plus ~$300 per semester. So if you take one course a semester it is ~$800 for the semester, if you take two courses per semester it is ~$1300. The program requires 10 courses to graduate. For some classes you will need to buy a book or two, but many do not have any required textbook, or use a book available online.

You pay at the beginning of each semester for the classes you'll take during that semester. It's not a lump sum.

So as a rough estimate if there would be 4 semesters , I would be spending roghly 1750 USD per semester . I know there would be some deviation. But is that a fair guess and financial planning ?

Here's the cost breakdown per course and semester: https://www.omscs.gatech.edu/program-info/cost-payment-sched...

But then if OO is a dud then why do we have some of its implementations C#, C++ and Java drive most of the enterprise. If they would not have existed would we have same amount to faith of enterprises to move to adopt software applications to run daily business.

OO was a fad for how many years? All these languages were strongly influenced by this, and this greatly colours the worldview programmers have who work with these languages.

If you work in Java, everything is contained within a class. You can't easily think outside the OO box because the language insists that everything you do is done in terms of OO, and this has great implications from the standard library, to primitive type boxing. It's very much constrained by the prevalent trends of the mid-90s. C++ is a more OO agnostic, it being something you can opt into as and when it makes sense.

I certainly don't think OO is a "dud", and it's provided a conceptual framework for programmers of wildly varying abilities to create and maintain vastly complicated codebases. But... it's only one way of many to structure and reason about program logic and data, and to constrain oneself to only using OO is greatly limiting. Now the hype has died down, I hope we can use OO where it fits, and avoid it where it does not, rather than as a blunt instrument for every problem?

The main problem I see in my day to day work (imaging related) is that OO is too costly. Arrays of object instances are too cache unfriendly. And code doesn't always need to be directly tied to data. I see Java code using collections of primitive arrays in place of objects because most OO languages don't provide a means of laying out objects in column stores, even though it wouldn't be technically difficult (just different offsets to members rather than packed structures). Treating objects as individual private collections of state leads to only being able to work with an object-centric rather than data-centric view, which can be quite detrimental. It's this view that leads to abominations like database object mappers, treating tabular data as object collections when they are not. While such things are possible and even popular, they often come with significant tradeoffs. I've encountered developers who are completely constrained within an OO worldview and can't take the blinkers off and see what's possible outside the box.