Ramifications for Disabling Strong Migrations?

What are the ramification of disabling strong migrations?  Will it break the existing code?  Or is it just to prevent bad migrations?

I'm using acts-as-taggable-on and I can't figure out how to change the migrations to make them work with strong parameters,

Just wrap your migration in the safety_assured block to make them ignored by strong_migrations.

You can also remove it, but I wouldn't. The gem will save your butt later on in production.