Read time: 1 minute

Trump Pretends To 'End' NAFTA; Ali Velshi Asks For 'English To English' Translation

NO Trump did not "end" NAFTA today. Did that stupid "ceremonial speakerphone call" about a Mexican Trade "Deal" fool the Trump Train? Canada wasn't part of whatever "deal" this was, and Mexico said so.
Views:

Whatever that stupid conference call with Mexico's president was supposed to accomplish, mark it hashtag Fail.

  1. It didn't distract from all the guilty pleas, convictions, indictments, and immunity deals in which Trump is now buried.
  2. It didn't distract from his WATB response to the death of John McCain.
  3. And above all, it didn't create a trade deal with Mexico or 'end' NAFTA.

And CNBC reporter Ron Insana just calmly pointed that out as a matter of fact to his audience of business news addicts:

ALI VELSHI: [The phone call with Mexico provided] simultaneous translation from the Spanish to English for the Mexican president. Unfortunately, we didn't have a simultaneous translation for the English to the English because the president made not a whole lot of sense. That was a little hard to interpret.

RON INSANA: It's a point of understanding it the way president Nieto described it. That sounds like a framework agreement where details still have to be put in place.

VELSHI: It's not a replacement for NAFTA?

INSANA: No, Congress would have to sign that and Canada would have to sign it. The president can repeal and replace NAFTA, but it would take congressional approval. NAFTA is still in effect.

VELSHI: And the Mexican president referred to Canada about five times. This wasn't a deal with Canada. Trump wants to tax Canadian cars. There are no Canadian car companies.

INSANA: That's right. [US car makers] reimport their cars to the United States.


Comments

We welcome relevant, respectful comments. Any comments that are sexist or in any other way deemed hateful by our staff will be deleted and constitute grounds for a ban from posting on the site. Please refer to our Terms of Service (revised 3/17/2016) for information on our posting policy.