In my personal opinion High Sierra should be avoided on Macs with SSDs at all costs for a very simple yet astonishingly braindead reason: while Apple is forcibly converting all SSD-enabled Macs from HFS+ to APFS without notifying the user beforehand they have until today failed to provide proper APFS documentation for developers and professionals. In other words: should something go wrong with your APFS-enabled drive you're pretty much screwed as there are no data rescue/file recovery tools that know how to handle APFS. Personally, that is a red line for me.
That said my personal experience with High Sierra is something of a mixed bag. I first updated my 2016 13" MacBook Pro from Sierra (10.12.6) to High Sierra in December 2017 (not aware of the lack of APFS documentation) and then subsequently carried that installation over onto a 2015 15" MacBook Pro via Time Machine. Ever since updating I've had massive trouble on both MacBook Pros with Bluetooth devices - headset and mouse would annoy the living c**p out of each other to the point where the headset was showing signs of loss of connectivity when I was moving the mouse or the mouse was stuttering after I powered on the headset; my VPN connections required a several minute long wait before I was able to successfully reconnect after putting my Mac to sleep; the login screen was completely frozen for around 10 seconds almost every time I woke the MBP from sleep; my audio output devices suddenly and randomly changed without any sort of interaction on my part - e.g. while playing music and working in, say Excel, the OS would all of a sudden decide all by itself to switch from my external USB speakers to my Bluetooth headset for default audio output; several third-party applications kept crashing and had to be force quit regularly, among others 3CX soft phone, Outlook 2016, or Remote Desktop. In addition, 3CX soft phone crash and froze almost every time I woke the Mac from sleep. Long story short I went back to 10.12.6 after suffering and hoping for things to improve in early March when I accidentally stumbled upon the APFS documentation issue. The MacBook Pro was my one and only computer and as a self-employed Linux/UNIX operations consultant & developer my livelihood depended on it. Long story short the switch back to Sierra solved every single one of my issues.
Fast forward to Mid April and I got rid of the 2015 MBP because its fans were starting to drive me nuts. Since I don't travel for my job as often as I used to anymore I've decided to go with a stationary desktop computer for the first time since 2009, and have thus replaced the single 15" MBP with a 2017 5K iMac for my office and a 2017 MacBook for the road, both of which came with 10.13.4 preloaded out of the box. Given that my main computer would now be the iMac I was not concerned about the lack of APFS documentation anymore - it sports a Fusion Drive and thus remained on HFS+. The MacBook, on the other hand, came with APFS and I thus do not trust it to hold any important files or data - I really only use it when I'm out and about and make sure to either store everything in some sort of cloud storage right away or move everything off the APFS and onto the HFS+ drive as soon as I get back home. And truth be told with 10.13.4 and now 10.13.5 all my previous issues have all but disappeared, except for the 10 second freeze upon wake: for some reason the MacBook does the same thing as both MacBook Pros before. And this time, I have NOT restored it from backup at all since it's considered untrustworthy and more like an iPad to me that is not allowed to hold any data (hence there was no need to restore anything from backup anyway). Makes me think it could be somehow related to APFS since the iMac with High Sierra and HFS+ doesn't show this behavior at all. It's not a big deal but more of an annoyance.
That isn't to say that High Sierra is now completely bug free, quite the contrary. Earlier this week (on Tuesday morning) I dared to finally enable FileVault on my iMac. Boy was that a mistake... First, the reboot required for enabling FileVault ended with the infamous crossed-out circle and the Mac didn't even boot to single user mode anymore. I had to manually unlock my drive using the Terminal while booted from Recovery to fix it; then, somewhen on Tuesday afternoon, the iMac froze completely on me and I had to hard reset it. On Tuesday night it crashed again while in standby (sleep/wake failure), which meant I had to boot it up from scratch on Wednesday morning. Ever since everything was hunky dory again.
At the end of the day I would probably still advise anyone to avoid High Sierra due to its many inconsistencies, annoyances, bugs, and most prominently the lack of APFS documentation. For me personally my laziness got the best of me and I've decided to ride it out for now and put all my eggs in the 10.14 basket.