Completion Insight changes since v1.5.5

Question

The completion insight is dramatically less useful in versions since 1.5.5. In that version the pop up completions were very fast, and the focus was always on the "best match" for the table in question. Also, common keywords such as FROM, WHERE, etc. popped up quickly. There current version is so slow that it isn't really useful, and it seems to stop working (3.2.20.09. but also 3.1.07) often.
When pounding out a lot of code, the completion insight for 1.5.5 is really a productivity tool. Is there any chance that a future version will get back to that level of excellence?

Answer 1

Previously, when I turned on my computer, a Safari browser window would automatically open on my screen. I didn't have to touch anything and I liked this. Now, however, the Safari application "starts" (as evidenced by the little blue dot under the dock icon) but no window opens...
Others have reported this. It seems to be a bug. The workaround is to remove Safari from your login items and replace it with a webloc file pointing to the site you want opened at login. To create the file, load the site and drag the URL from the address bar to the Desktop. Rename the file if you wish, then put it anywhere in your home folder. Add it to your login items.
I seem to have lost some auto-fill or predictive text functionality.
Also reported, also apparently a bug, or perhaps an intentional change. I don't know of a workaround.
...in Safari's preferences I have checked the box which reads "Open 'safe' files after downloading."  Previously, whenever I would download a document from my email, it would open automatically. I liked this. Now, however, the files download and are saved in my downloads folder but do not open.
I've never used this feature myself, because I think it's dangerous, so I don't know how it's changed. In the past it has caused security problems. It has always been true that Safari would only open downloaded files that were considered "safe," according to their type. Some file types that were formerly considered safe may no longer be -- at least, I hope that's the case.