I’ve now tried the Hemingway Editor for a few days, and well, it’s not bad nor great. One of the biggest issues is that it checks only for style errors. It doesn’t check spelling or grammar. So you inevitably end up having to copy your content into another editor (like Word) to do that. Having to copy text back and forth is a bit of a drag. So for this issue alone I will try something else next, probably ProWritingAid.
But core functionality isn’t my only gripe with the Hemingway Editor. When you open the app, it shows an empty document that for some reason is automatically marked “unsaved.” Which means it asks you to save the empty & unchanged document if you try to close it, and if you open a file it’ll do so in a new window instead of the existing window. Opening existing files is also a bit of a drag: there isn’t a “Recent Files” menu option.
More indefensible is that .hemingway files aren’t associated with the application during installation, and if you try to associate them manually, it turns out the app has no support for that! Meaning, if associate the app with .hemingway files and try to open them, it’ll just open an empty document instead. Something else I found out while trying to create the file association for the app is that it installed itself into the “AppData” folder. I’m not an expert in Windows software development, but I doubt that’s the right location.
So in conclusion, would I recommend it and is it worth its money? No. But of course you can still use it for free online.
Edit: I ended up going for Grammarly after all (but using the standalone app and not as browser plugin). And ProWritingAid too. I’ll probably end up using all three tools together. What made me reconsider Grammarly was: in the original text of this review (I used it to test all three), I accidentally wrote “expect” instead of “expert.” That’s not an easy mistake to spot, yet Grammarly did it. ProWritingAid isn’t bad either though not as smart, and it sometimes makes suggestions that make little sense. There is no substitute for your brain as the best proofreader.
I’m currently trying to develop my own WordPress theme from scratch (called “Tengu” but be warned: at time of writing it’s nowhere near usable yet). And I encountered a rather odd bug: part of the
style.css file would get corrupted when viewing through the browser.
I am using PhpStorm on Windows and for live testing I use a virtual machine using Vagrant. On it I was using a plain, hardly modified installation of nginx to serve a WordPress test blog. As it turns out, by default nginx configuration turns the “sendfile” option on which usually makes sense, but sendfile apparently is extremely unreliable when used with remote file systems (in my case, VirtualBox extensions).
The quick solution: turn sendfile off during development (look for the appropriate line in
/etc/nginx/nginx.conf). Supposedly this also applies to Apache btw. The problem went away immediately when I did that.
Notice: see this follow-up post for better ways of keeping WordPress & phpMyAdmin up-to-date.
Keeping up-to-date with the latest versions of commonly used web software such as WordPress and phpMyAdmin can be a bit of a drag if you would have to manually download, unzip and upload new files through FTP each time a new version is released.
But keeping WordPress and phpMyAdmin up-to-date can be as simple as logging into your server with SSH and executing just a single command. The key to this is that these software are being developed using version control software like Subversion and Git. Not only developers can take advantage of this however; you as end-user can use them as well.
First you’ll need to install Subversion and/or Git of course. On Debian (and Ubuntu presumably) you can do this by simply running the following command (as root):
aptitude install subversion git-core
Once either or both have been installed, I can simply recommend the excellent Installing/Updating WordPress with Subversion article in the case of WordPress.
For phpMyAdmin you will need to following commands from the root directory where you would want to install phpMyAdmin in:
git clone https://github.com/phpmyadmin/phpmyadmin.git cd phpmyadmin/ git branch --track STABLE origin/STABLE git checkout STABLE git pull
In case of a new install don’t forget to copy “config.sample.inc.php” to “config.inc.php” and editing it where applicable (see the phpMyAdmin documentation for more info). To keep it up-to-date, then simply run the following command from the “phpmyadmin” folder whenever a new version is released:
This command should not overwrite custom files like the configuration file.
Update April 2012: it would appear phpMyAdmin has moved to GitHub, so the URL above has been updated.