101–110 of 197 posts
Earlier quoted context omitted.
Nit: "inflammable" means "can be set of fire". So does "flammable". Yes, I know. You want "not flammable", or if you want to be cute you could try "unflammable".
Looks like the post means 'either already burnt or will be burnt easily'? So what exactly is your nitpick here?
I suspect I will never ever ever use GCP for anything important.
Earlier quoted context omitted.
If a client hasn't learned by now, they're not gonna learn from this either. For niche apis Google has no trust left to burn, because all trust in its products is either already burnt or inflammable.
Nit: "inflammable" means "can be set of fire". So does "flammable". Yes, I know. You want "not flammable", or if you want to be cute you could try "unflammable".
Like with most loan words, it's best to just stick to the native word - which is not "flammable" as Merriam tried to invent 200 years ago, but rather "combustible"
Earlier quoted context omitted.
My company xmltravelgate.com offers a flight API (search & book) with many direct airlines (low cost and NDC) and 3 GDS already integrated, although you do need a contract with them... We're releasing a new aggregated flight API and flight cache API (only price & availability, no booking, no contracts) based on GraphQL scheduled for January. Feel free to contact me for more details.
This is me contacting you. Please share details, very interested.
And, "QPX Express was a lower-touch way to let companies start experimenting with QPX without needing full on biz-dev contract cycles", per someone I know with some inside knowledge.
Earlier quoted context omitted.
If that was their reasoning, they could do it whenever they were ready and willing after five years. So this explains why they had to do it for five years and might explain why they won't be doing it much longer than that. It might also indicate that cutting off the API was intended but not urgent.
Why would it be so close to the anniversary though? It seems to suggest something else might be going on at the 7-year mark.
I was part of a team developing a travel product which needed huge amounts of data from flights to car rental... My god the travel industry is a mess in terms of accessible data. It was the biggest pain point. API's would randomly change structure, endpoints would stop working with unknown errors, data would be significantly different across companies for the same data etc... It was a shambles. Never again will I dev…
I think this is probably the general state of data exchange systems in most industries/sectors where an IT company/startup hasn't come along to successfully disrupt it or none of the major players have become tech-oriented enough to see - much less sort out - these kinds problems well. That's been my experience anyways.
I don't think this necessarily signals the end of Matrix ITA. In fact, QPX Express and the Matrix are completely unrelated. And, "QPX Express was a lower-touch way to let companies start experimenting with QPX without needing full on biz-dev contract cycles", per someone I know with some inside knowledge.
I don't think this necessarily signals the end of Matrix ITA. In fact, QPX Express and the Matrix are completely unrelated. And, "QPX Express was a lower-touch way to let companies start experimenting with QPX without needing full on biz-dev contract cycles", per someone I know with some inside knowledge.
I used to use Matrix but stopped using it after finding that a lot of the time it doesn't actually catch certain deals available only on airline websites themselves. Now I'm back to individually searching every airline website.