I use Textastic and BBEdit; Textastic “Open in Safari”: epic fail – Textastic Code Editor Review

I use Textastic, and my iPad, by habit for code writing. I have a copy on my iPhone to sync and test. It is somewhat handy to have an iOS code editor. One must be parient with its limitations. There is no “clear cache”. “Open in Safari” is worthless. If a local file links to an online CSS there is no telling which cached version of the CSS will be loaded. (Like, a *very* old one on my iPhone and an *even older* one on my iPad.) For an accurate view I must download and link CSS and its imbedded files (fonts and SVGs) locally, or upload the updated HTML and look at the online version in Safari by explicit URL. I found the MacOS version of Textastic primitive compared to BBEdit, so sometimes, when extreme needs arise, I go to the laptop. BBEdit is king. Textastic does most things quite well. (Read the features list.) By habit—tinfoil hat—I keep both local and iCloud copies of files—along with what gets FTPed. Textastic has no multi-file search. Text selection and pointer placement in long sections of “tidied” text can be…er…tedious. [Edit: the developer has responded as to his ability to reproduce “it” in various other apps. My main gripe is the inability to clear cache. Clearing cache has no relevance to the other apps to which the developer has referred, and indeed and obviously, is not true of syncing simple files in other apps. Web-interlaced/browser-involved files are a different matter.]
Review by fjpoblam on Textastic Code Editor.