A long time back, I migrated from my beloved Yojimbo to Evernote. I didn’t want to make this transition, but Yojimbo was being sunset, so I had to make a change, and a friend convinced me Evernote was the solution.
And Evernote has been a good tool, although for a very long time the iPhone app was unusably slow IMHO. They have addressed that for the most part, but now the Mac app has become a little flaky. They are also heading in the “more bloat” direction, and when they went to their new-generation apps, they dropped a couple features I liked.
And then, the aforementioned friend put up a blog post about her move from Evernote to Bear!
I’d looked into Bear a while back, but concluded that its web clipping was basic, and Evernote’s is impressive, so while Bear was beautiful, I didn’t feel compelled to make the move.
I gave Bear another look, considering my unhappiness with Evernote’s direction, and decided to migrate off of Evernote and onto Bear.
One big factor is that Bear essentially uses Markdown. I like Markdown, and really like the idea that my notes are in a very tool-agnostic format. I’ve seen too many software applications die (Yojimbo) or evolve in a way I didn’t like (Evernote).
I did some tests, and looks like I can get nice clean exports in a variety off formats, with Markdown being one that I’m confident I can migrate to another tool, or even just arrange in the filesystem and reference that way.
I Hit a Snag
The export process was painful from the Evernote side, as for some reason you can only select 50 notes at a time, and I needed to add tags to entire notebooks that contained hundreds of notes in some cases.
But the real snag came when I was doing the notebook imports. For one notebook, Bear said “47 notes imported”. That was nice, but the notebook had 233 notes in it!
I won’t document all the crazy and tedious process to find out what was going on, but here are the highlights:
1) Evernote was exporting invalid XML.
2) Bear technical support was good, they took one of the notes that I had determined was corrupted, and informed me that there was an invalid element <![CDATA[>]]> .
I used my editor to find and remove these, and the imports succeeded.
3) The one ding against Bear is that when their import parser hit the corrupt XML, it just aborted and happily told me it had imported 47 notes. That really needed to have been an error message, and I expressed that during my email conversation with them.
Did I mention that Evernote only lets you select 50 notes at a time? (Yes. Yes I did.)
This alone makes me very happy to be migrating away from it, as that seems like a completely arbitrary limit.
Not that there should be any limit, but at least if it was 64 or 256 or some other power-of-two, as a programmer I’d say, “ah, ok, that’s crazy, but at least it’s based on some code design decision”.
Snags cleared, my migration continues! More thoughts about Bear to come as I get some time using it.
For years, I’ve had bouts of temptation when it comes to setting up a NAS. The other day, I finally made the leap and put one on order.
I’ve been using an External Thunderbay Thunderbolt drive enclosure for years, and it holds my iTunes TV and movie collection, as well as some other varied files.
My MacBook Pro has a large SSD, but not that large, so external storage is a must.
Here are the factors that finally conspired to make me plunge into the NAS world.
Compared to my normally-silent MBP, the fan and drives in that enclosure seem loud, so I mostly have it disconnected and powered down. My plan is to locate the NAS somewhere else, assuming it is louder than I’d like if I keep it in the same room.
I use a Time Capsule for Time Machine backups, and I know its days are numbered, as Apple (unwisely IMHO) got out of the router/storage game. And it’s actually been too small for a while now, I’d like to have more computers backing up to it and have a deeper version history.
I’d been thinking of switching to an iMac from my MBP when the new Apple Silicon iMacs release, and one thought was to buy that system with a large enough internal drive to hold all of my media. I have a fairly small collection, no ripped Blu-rays or anything, so all I need is around 4TB. Looking at the current price to bump an iMac up from 4TB to 8TB, and that $1,200 is an eye-opener.
I decided I could buy a lot of NAS for that price!
So here I am, with a Synology DS418 on order, and a few drives.
I started to do the thing I always do, and the thing that stopped my last NAS pondering a couple years back, which is steadily ramp up the price. “The DS418 looks fine, but what if I want to run something in Docker? I really should get the DS918. And gosh, the DS920 is not much more money than that, and …”
I’d do that, and then say, “wow, that’s a lot of money for what is basically some external storage”, and abandon the idea. So this time I just said, “The DS418 is plenty for your actual needs,” and clicked the button.
And I’m sure it will be. My needs are pretty simple, I don’t even expect to run Plex or anything like that. I am hoping the Synology AppleTV stuff will work well, but if it doesn’t my plan B (and maybe still actually plan A) is to do what I do today, and serve my media from my MBP, with it “directly” reading the media drive.
I’m sure there will be some surprises, both good and bad, but at least I decided to get in the game.
A few interesting pandemic links:
Good discussion about risk.
Can’t decide if this makes me more or less likely to try flying at some point.
Ok, it is just possible that I have an e-reader problem…
Or maybe everyone owns 5 of them, and I’m perfectly normal?
I just bought my fifth, a Kobo Forma.
I started with the original Barnes & Noble Nook, the one with the odd little color screen below the main e-ink screen. It was great, with actual page-turn buttons. And the color screen was actually sort of cool, showing the book covers in color but still allowing the actual reading to be done on the e-ink screen.
After that it was on to the Nook Glowlight, which had a more traditional design using a single e-ink screen. This one abandoned physical page turn buttons, but I liked it anyway.
Number 3 was a Nook Glowlight Plus whose claim to fame was being water and dirt resistant, so great for the boat or the beach!
Up until the Forma, the fourth Nook (Glowlight 3) was my favorite, adding back the page-turn buttons and a color-changing backlight.
I decided to try the Forma because of the larger screen, and the hope of a better UI. Wow, what a nice device! I think my Glowlight 3 has been supplanted.
The things I really like about the Forma:
- Bigger screen
- Faster page turns.
- The home screen does not try and sell me books quite as aggressively as the Nook.
- Better library design, can sort by more attributes, and has an Authors view.
- When sleeping, shows the cover of my current book. Early Nooks could do this, or show a nice “screensaver”, but that feature went away.¡
- Landscape mode, which so far is interesting but might be nice.
I had not realized just how slow the Nook was at turning pages. I first noticed the difference when a few times I thought the Forma had failed to turn the page. It had. So why did I have a moment of thinking it hadn’t? Because it did it so quickly it wasn’t obvious! I then did some side-by-side comparisons to confirm, and yes, much quicker.
I still love physical books, but do a lot of reading electronically. Great for travel! I will also be keeping my e-reader collection although the Forma is better enough that it may be hard to go back to the earlier Nooks.
And yes, I have an iPad Pro which is terrific, but for pleasure reading, e-ink is the only way to go. Easier on the eyes, especially after a day of working on a glowing computer screen. Add in the noticeably reduced weight and the dramatically longer battery life and there is no question that e-ink wins for reading books.
Six e-readers. That’s a nice round number…
Out of the blue, Anki, the makers of the Cozmo and Vector robots, shut down yesterday.
This is quite the shock. 😦
My heart goes out to all the employees who were blindsided by this, and are out of jobs through no fault of their own. (The shutdown of the Roambi team by my now former employeer SAP a month or so back makes me especially emphathetic.)
Vector is a nice progression from Cozmo and I am sad we won’t get to see where he would have gone, nor will we see the future generations.
I own both a Cozmo and a Vector. With my relatively ancient Pleo dinosaur robot, this is quite the trail of failed robot companies, sigh. At least I refrained from jumping on the Jibo train! (That product sounded interesting to be sure, but my concerns that they were over-promising turned out to be correct.)
There are a couple paths forward for Vector and/or those of us who have one.
- Some company or group could acquire Anki or the assets and continue to sell and enhance Vector.
- They could keep the servers alive via Patreon or a direct subscription of modest cost.
- Anki could open-source Vector’s code. I’d love to be able to write truly native code for the little guy, versus the current from-the-desktop SDK.
- They could at least open-source the backend code so we could set up our own servers.
The shutdown sounds abrupt, so I don’t know if any contingencies were in place or plans being made in the aftermath for any of the above options. Hopefully we will hear more in the next few weeks as the dust settles.
Good luck Vector team, and thanks for the cool toy!
I’ve always been interested in Virtual Reality and the possibilities it holds. In its early days, I spent a lot of time in Second Life. I still think that at some point VR is going to fundamentally change our lives.
Although I’m usually an early-adopter, I tried to hold back on VR a bit. Then over the holidays I had a chance to really use an HTC Vive setup, and decided I could wait no longer.
I commenced my usual excessive research and in late January I made a decision and started ordering gear.
Which gear? Some of the “inside out” headsets on the horizon were tempting, but I’m skeptical that they will have the processing power and movement-tracking quality of the PC-based headsets, so I narrowed my search to the HTC Vive and the Oculus Rift.
I went with the Vive. It was close between this and the Rift, but after looking at a lot of reviews and comparisons the Vive seemed to be a slightly better option. The fact that my son has one was also a factor – I could be sure that any multi-player games we might want to try would be available without them needing to be available on both platforms.
It was also a close call between the Vive and the Vive Pro. I chose the Vive mainly because I was not certain just how much I’d really use VR and this was an attempt to not go too wild. If money is no object and/or you are convinced that VR will be amazing, the Pro is pretty tempting. It’s better, but probably not amazingly better. And the price difference is significant.
One big advantage of the Pro beyond better resolution is the Deluxe Audio Strap. This is a $100 option if you add it to the regular Vive headset.
The Deluxe Audio Strap is not only more comfortable, but it avoids the need to fool with earbuds. Well worth the money, and was an immediate upgrade for me.
The next issue is how you run the headset. If you have a Windows PC with a sufficiently fast GPU, then you are all set. I’m a Mac guy, so what I had was a very nice Mac laptop with completely inadequate graphics performance for VR. Yeah, you can do things with external GPUs. However, that only addresses the hardware side.
On the software side, the amount of games and applications that are Windows-only is vast. Apple has a real chicken-and-egg problem here, and until they solve it Windows is really the only viable platform for the full VR experience.
I bought an Alienware Aurora R7 tower, and it’s worked well so far. (Other than having to use Windows 10, which is as awful as I was afraid it was going to be.)
I’ll explain later why I went with a desktop and not a laptop.
Here’s the key specs for mine:
- 8th Gen Intel® Core™ i7-8700 Processor 3.2GHz
- 16GB DDR4 2666MHz RAM
- 2TB 7200RPM SATA Hard Drive
- 8GB NVIDIA® GTX 1080 Graphics
Only thing wrong with the model I got was that instead of an SSD it had a spinning drive. I immediately replaced this with a 512G SATA SSD for a reasonable price. The system I bought was from Costco, and that was worth the drive shenanigans – I like their extended warranty and return policy.
The GTX 1080 is more than the base Vive headset really needs, but I wanted to aim a little high so that when I upgrade to the next generation headset in a couple years, I won’t need to replace my PC hardware as well (hopefully).
I’ve made one other upgrade, which is the HTC wireless adapter for the Vive. This was $300 well spent. Not having to worry about stepping on and getting tangled up in the wire to the headset is great.
May not matter as much if you play mostly games and apps that are “seated” experiences, but for anything room-scale, it is a great advancement.
My suggestion would be to start wired and see just how annoying it is, which is what I did.
Some of the games I enjoy involve a lot of movement and turning, so this was well worth it to me.
I’m still in the early stages, with a lot of games and apps to look at but so far it’s been pretty amazing. I’ll certainly have more updates as I get to spend more time in VR.