Re: This API is a nightmare

[revarasi Sofa]

Service korsi sopa bandung

Pada tanggal Rab, 29 Mei 2019 22.02, SeriousJ  menulis:

> I agree completely. It's slow and constantly returns "Internal errors" and
> "deadline exceeded exceptions." No other company in the world would have
> dared to release such a flawed API.
>
> But they have no incentive to make it better so it probably won't improve
> much.
>
>
>
> On Wednesday, May 29, 2019 at 9:11:51 AM UTC+2, Sergei Kim wrote:
>>
>> +1 about slowness. We don't use libs provided by Google, just plain JSON
>> API and this is a nightmare:
>> https://groups.google.com/forum/#!topic/adwords-api/h9-N-Ypkcmw. Some
>> requests take minutes not seconds!!!
>>
>>
>>
>> On Thursday, May 23, 2019 at 1:40:48 PM UTC+3, SeriousJ wrote:
>>>
>>> This API is worse than the previous one, and that is no small feat.
>>>
>>> *1)* You need to comply to absurd requirements.
>>>
>>> For instance in PHP, you need to upgrade to a version above 7.1, which
>>> is used by less than 30% of servers
>>> . You also need to install GRPC,
>>> a Google-made Frankenstein of a library trying to replace REST, while REST
>>> is the gold standard used everywhere else. Unlike REST, GRPC has many
>>> issues and is not supported for Windows.
>>>
>>> *2)* This new API and the corresponding new SDKs are much more opaque
>>> and verbose than previously.
>>>
>>> Just a simple example to get a Keyword Match Type in PHP:
>>>
>>> Old API: $adGroupCriterion->getCriterion()->getMatchType()
>>> New
>>> API: 
>>> KeywordMatchType::name($googleAdsRow->getAdGroupCriterion()->getKeyword()->getMatchType())
>>>
>>>
>>> *3)* The new API is inconsistent and sometimes illogical to the point
>>> that even trained Google Ads API team members can't make it work
>>> 
>>> .
>>>
>>> *4)* The new API is tremendously slower
>>> 
>>> .
>>>
>>> Running a simple GetCampaign example, we get the following average
>>> response times:
>>>
>>> Old API: 0.49 s
>>> New API: 4.27 s
>>>
>>>
>>> The new API is 8.7 times slower than the old. Performing queries on
>>> large volumes of data with the new API frequently - but randomly - returns
>>> the dreaded deadline_exceeded error.
>>>
>>> *5)* Google Adwords deprecate their API versions every nine months to
>>> one year, making you jumping through the hoops all over again.
>>>
>>>
>>> Most non-Google APIs are not even remotely as bad to use. For example,
>>> Paypal still supports their versions for Checkout from ten years ago.
>>> Anyone who's used Stripe knows how an API can be set up in a matter of
>>> minutes. Most REST APIs can be called with simple Curl commands.
>>>
>>> So why is Google Ads (or Adwords) API so terrible?
>>>
>>> When you ask their team members they first give you some generic answers
>>> about how they're "addressing the issue" and are "aware of the
>>> difficulties". Then they'll end up saying that this is an extremely complex
>>> process. I personally don't believe that. How can adding a keyword be more
>>> difficult than setting up an asynchronous 3DS2 payment system? And yet
>>> Stripe allows you to do it in a few lines of code and with a great
>>> documentation.
>>>
>>> I think that Google APIs are bad to use because of three reasons:
>>>
>>>1. Google is a monopoly and thus doesn't care if you suffer or not.
>>>No other API can ask their clients for a PHP version more than 5.6 
>>> because
>>>they wouldn't get many clients. Yet Google knows we don't have a choice.
>>>2. Google has become a bloated inefficient administration caring
>>>more about its internal working than about users. It can afford it 
>>> because
>>>of point 1.
>>>3. As a consequence of point 2, Google likely doesn't attract many
>>>smart engineers anymore. If you're any good you start your own company or
>>>you go make fortunes working for a hot company or you save the world. You
>>>don't work for Google Ads API team.
>>>
>>>
>>>
>>>
>>>
>>> --
> --
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
> Also find us on our blog:
> https://googleadsdeveloper.blogspot.com/
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>
> You received this message because you are subscribed to the Google
> Groups "AdWords API and Google Ads API Forum" group.
> To post to this group, send email to adwords-api@googlegroups.com
> To unsubscribe from this group, send email to
> adwords-api+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/adwords-api?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "AdWords API and Google Ads API Forum" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to adwords-api+unsubscr...@googlegroups.com.
> Visit this group at 

Re: This API is a nightmare

[SeriousJ]

I agree completely. It's slow and constantly returns "Internal errors" and 
"deadline exceeded exceptions." No other company in the world would have 
dared to release such a flawed API.

But they have no incentive to make it better so it probably won't improve 
much.



On Wednesday, May 29, 2019 at 9:11:51 AM UTC+2, Sergei Kim wrote:
>
> +1 about slowness. We don't use libs provided by Google, just plain JSON 
> API and this is a nightmare: 
> https://groups.google.com/forum/#!topic/adwords-api/h9-N-Ypkcmw. Some 
> requests take minutes not seconds!!!
>
>
>
> On Thursday, May 23, 2019 at 1:40:48 PM UTC+3, SeriousJ wrote:
>>
>> This API is worse than the previous one, and that is no small feat.
>>
>> *1)* You need to comply to absurd requirements.
>>
>> For instance in PHP, you need to upgrade to a version above 7.1, which is 
>> used by less than 30% of servers . 
>> You also need to install GRPC, a Google-made Frankenstein of a library 
>> trying to replace REST, while REST is the gold standard used everywhere 
>> else. Unlike REST, GRPC has many issues and is not supported for Windows.
>>
>> *2)* This new API and the corresponding new SDKs are much more opaque 
>> and verbose than previously.
>>
>> Just a simple example to get a Keyword Match Type in PHP:
>>
>> Old API: $adGroupCriterion->getCriterion()->getMatchType()
>> New 
>> API: 
>> KeywordMatchType::name($googleAdsRow->getAdGroupCriterion()->getKeyword()->getMatchType())
>>
>>
>> *3)* The new API is inconsistent and sometimes illogical to the point 
>> that even trained Google Ads API team members can't make it work 
>> 
>> .
>>
>> *4)* The new API is tremendously slower 
>> 
>> .
>>
>> Running a simple GetCampaign example, we get the following average 
>> response times:
>>
>> Old API: 0.49 s
>> New API: 4.27 s
>>
>>
>> The new API is 8.7 times slower than the old. Performing queries on large 
>> volumes of data with the new API frequently - but randomly - returns the 
>> dreaded deadline_exceeded error.
>>
>> *5)* Google Adwords deprecate their API versions every nine months to 
>> one year, making you jumping through the hoops all over again.
>>
>>
>> Most non-Google APIs are not even remotely as bad to use. For example, 
>> Paypal still supports their versions for Checkout from ten years ago. 
>> Anyone who's used Stripe knows how an API can be set up in a matter of 
>> minutes. Most REST APIs can be called with simple Curl commands.
>>
>> So why is Google Ads (or Adwords) API so terrible?
>>
>> When you ask their team members they first give you some generic answers 
>> about how they're "addressing the issue" and are "aware of the 
>> difficulties". Then they'll end up saying that this is an extremely complex 
>> process. I personally don't believe that. How can adding a keyword be more 
>> difficult than setting up an asynchronous 3DS2 payment system? And yet 
>> Stripe allows you to do it in a few lines of code and with a great 
>> documentation.
>>
>> I think that Google APIs are bad to use because of three reasons:
>>
>>1. Google is a monopoly and thus doesn't care if you suffer or not. 
>>No other API can ask their clients for a PHP version more than 5.6 
>> because 
>>they wouldn't get many clients. Yet Google knows we don't have a choice.
>>2. Google has become a bloated inefficient administration caring more 
>>about its internal working than about users. It can afford it because of 
>>point 1.
>>3. As a consequence of point 2, Google likely doesn't attract many 
>>smart engineers anymore. If you're any good you start your own company or 
>>you go make fortunes working for a hot company or you save the world. You 
>>don't work for Google Ads API team.
>>
>>
>>
>>
>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/dbd130d1-04f9-4a27-9778-35dea981da07%40googlegroups.com.
For more options, visit 

Re: This API is a nightmare

[revarasi Sofa]

Pada tanggal Rab, 29 Mei 2019 14.12, Sergei Kim  menulis:

> +1 about slowness. We don't use libs provided by Google, just plain JSON
> API and this is a nightmare:
> https://groups.google.com/forum/#!topic/adwords-api/h9-N-Ypkcmw. Some
> requests take minutes not seconds!!!
>
>
>
> On Thursday, May 23, 2019 at 1:40:48 PM UTC+3, SeriousJ wrote:
>>
>> This API is worse than the previous one, and that is no small feat.
>>
>> *1)* You need to comply to absurd requirements.
>>
>> For instance in PHP, you need to upgrade to a version above 7.1, which is
>> used by less than 30% of servers .
>> You also need to install GRPC, a Google-made Frankenstein of a library
>> trying to replace REST, while REST is the gold standard used everywhere
>> else. Unlike REST, GRPC has many issues and is not supported for Windows.
>>
>> *2)* This new API and the corresponding new SDKs are much more opaque
>> and verbose than previously.
>>
>> Just a simple example to get a Keyword Match Type in PHP:
>>
>> Old API: $adGroupCriterion->getCriterion()->getMatchType()
>> New
>> API: 
>> KeywordMatchType::name($googleAdsRow->getAdGroupCriterion()->getKeyword()->getMatchType())
>>
>>
>> *3)* The new API is inconsistent and sometimes illogical to the point
>> that even trained Google Ads API team members can't make it work
>> 
>> .
>>
>> *4)* The new API is tremendously slower
>> 
>> .
>>
>> Running a simple GetCampaign example, we get the following average
>> response times:
>>
>> Old API: 0.49 s
>> New API: 4.27 s
>>
>>
>> The new API is 8.7 times slower than the old. Performing queries on large
>> volumes of data with the new API frequently - but randomly - returns the
>> dreaded deadline_exceeded error.
>>
>> *5)* Google Adwords deprecate their API versions every nine months to
>> one year, making you jumping through the hoops all over again.
>>
>>
>> Most non-Google APIs are not even remotely as bad to use. For example,
>> Paypal still supports their versions for Checkout from ten years ago.
>> Anyone who's used Stripe knows how an API can be set up in a matter of
>> minutes. Most REST APIs can be called with simple Curl commands.
>>
>> So why is Google Ads (or Adwords) API so terrible?
>>
>> When you ask their team members they first give you some generic answers
>> about how they're "addressing the issue" and are "aware of the
>> difficulties". Then they'll end up saying that this is an extremely complex
>> process. I personally don't believe that. How can adding a keyword be more
>> difficult than setting up an asynchronous 3DS2 payment system? And yet
>> Stripe allows you to do it in a few lines of code and with a great
>> documentation.
>>
>> I think that Google APIs are bad to use because of three reasons:
>>
>>1. Google is a monopoly and thus doesn't care if you suffer or not.
>>No other API can ask their clients for a PHP version more than 5.6 because
>>they wouldn't get many clients. Yet Google knows we don't have a choice.
>>2. Google has become a bloated inefficient administration caring more
>>about its internal working than about users. It can afford it because of
>>point 1.
>>3. As a consequence of point 2, Google likely doesn't attract many
>>smart engineers anymore. If you're any good you start your own company or
>>you go make fortunes working for a hot company or you save the world. You
>>don't work for Google Ads API team.
>>
>>
>>
>>
>>
>> --
> --
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
> Also find us on our blog:
> https://googleadsdeveloper.blogspot.com/
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>
> You received this message because you are subscribed to the Google
> Groups "AdWords API and Google Ads API Forum" group.
> To post to this group, send email to adwords-api@googlegroups.com
> To unsubscribe from this group, send email to
> adwords-api+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/adwords-api?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "AdWords API and Google Ads API Forum" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to adwords-api+unsubscr...@googlegroups.com.
> Visit this group at https://groups.google.com/group/adwords-api.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/adwords-api/4427d77d-de87-48c7-8805-0fbda8e44ecc%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:

Re: This API is a nightmare

[Sergei Kim]

+1 about slowness. We don't use libs provided by Google, just plain JSON 
API and this is a nightmare: 
https://groups.google.com/forum/#!topic/adwords-api/h9-N-Ypkcmw. Some 
requests take minutes not seconds!!!



On Thursday, May 23, 2019 at 1:40:48 PM UTC+3, SeriousJ wrote:
>
> This API is worse than the previous one, and that is no small feat.
>
> *1)* You need to comply to absurd requirements.
>
> For instance in PHP, you need to upgrade to a version above 7.1, which is 
> used by less than 30% of servers . 
> You also need to install GRPC, a Google-made Frankenstein of a library 
> trying to replace REST, while REST is the gold standard used everywhere 
> else. Unlike REST, GRPC has many issues and is not supported for Windows.
>
> *2)* This new API and the corresponding new SDKs are much more opaque and 
> verbose than previously.
>
> Just a simple example to get a Keyword Match Type in PHP:
>
> Old API: $adGroupCriterion->getCriterion()->getMatchType()
> New 
> API: 
> KeywordMatchType::name($googleAdsRow->getAdGroupCriterion()->getKeyword()->getMatchType())
>
>
> *3)* The new API is inconsistent and sometimes illogical to the point 
> that even trained Google Ads API team members can't make it work 
> 
> .
>
> *4)* The new API is tremendously slower 
> 
> .
>
> Running a simple GetCampaign example, we get the following average 
> response times:
>
> Old API: 0.49 s
> New API: 4.27 s
>
>
> The new API is 8.7 times slower than the old. Performing queries on large 
> volumes of data with the new API frequently - but randomly - returns the 
> dreaded deadline_exceeded error.
>
> *5)* Google Adwords deprecate their API versions every nine months to one 
> year, making you jumping through the hoops all over again.
>
>
> Most non-Google APIs are not even remotely as bad to use. For example, 
> Paypal still supports their versions for Checkout from ten years ago. 
> Anyone who's used Stripe knows how an API can be set up in a matter of 
> minutes. Most REST APIs can be called with simple Curl commands.
>
> So why is Google Ads (or Adwords) API so terrible?
>
> When you ask their team members they first give you some generic answers 
> about how they're "addressing the issue" and are "aware of the 
> difficulties". Then they'll end up saying that this is an extremely complex 
> process. I personally don't believe that. How can adding a keyword be more 
> difficult than setting up an asynchronous 3DS2 payment system? And yet 
> Stripe allows you to do it in a few lines of code and with a great 
> documentation.
>
> I think that Google APIs are bad to use because of three reasons:
>
>1. Google is a monopoly and thus doesn't care if you suffer or not. No 
>other API can ask their clients for a PHP version more than 5.6 because 
>they wouldn't get many clients. Yet Google knows we don't have a choice.
>2. Google has become a bloated inefficient administration caring more 
>about its internal working than about users. It can afford it because of 
>point 1.
>3. As a consequence of point 2, Google likely doesn't attract many 
>smart engineers anymore. If you're any good you start your own company or 
>you go make fortunes working for a hot company or you save the world. You 
>don't work for Google Ads API team.
>
>
>
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/4427d77d-de87-48c7-8805-0fbda8e44ecc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.