If you have or ever want to have any kind of code behind your form, an .oft
file is not an option, because items created with .oft files use one-off
forms (form definitions embedded in the item) and, therefore, cannot run
code. Code runs only on published forms.

The same goes for forms with "send form definition with item" checked: They
create one-off form items, which can never run code.

Furthermore, you didn't say what kind of form it is -- message, contact,
etc. -- but if it's a message form, publishing in Public Folders is not
appropriate. Think about it: How would Outlook know to look in that folder
out of possibly thousands to find the form definition associated with a
message you received? A message form should be published either in the
Organizational Forms library or in the Personal Forms library of each user.

However, if you never plan to put code behind the form and don't care that
items created with the .oft are potentially much larger than normal items,
there's not harm in using an .oft file to create items.