This is why there is so much concern about not getting a major update for nearly 17 months. We all can understand delays. Well, most of us. But I’m putting up this record so Waytools can maybe better realize how much this problem has grown.
The following dates sometimes ran into conflicts - the date listed on the Waytools “Activity” page may show one date, but clicking on the post would then show a different one. I remember there was a period when something messed up many dates on the posts so this is probably part of that. I opted to use the date on the Waytools activity page.
I read, or at least scanned, just about every post WayTools made going back to June 20 of last year. I may have missed some references to making an update, but I doubt it would be many and especially doubt it would matter to the basic issue.
HOWEVER, as I was reading through the many posts for many hours, I also found quite a number of things that could be considered “updates”. No, not the bigger one we have been waiting for, but certainly some good information.
I may go back yet again and create a similar list of those little updates to get a proper, complete, record of the past almost 17 months. But I’m sure not looking forward to that process. This one was hard enough, but scanning through them again, trying to find what was sometimes a single sentence of useful update info will likely be far more time-consuming.
Well, we’ll see. Meanwhile, the following are the statements about upcoming updates. If there is not a blank line between statements, it is from the same post. If there is a blank line, it is from the same date, but a different post.
I put an asterisk in front of the date of some to designate dates where the statements were particularly problematical to me, considering the update wasn’t made. But I probably didn’t do it every time I could have.
June 20, 2018
We’ve updated our servers to reflect our Fall release estimate, and we’ll post some technical details soon about a major upgrade to our infrastructure firmware to accommodate user requests and facilitate service in General Release.
confirm we are working on the update info now. We’ll be updating our server on Thursday to acknowledge summer time window, and we’ll follow up with info on current focus areas within the next week
June 21, 2018
We’ll post some tech details in our update, but it’s mostly the firmware subtleties. We fix those pretty quickly, but we need reports on them first, and good logs.
June 29, 2018
just a heads-up that we still have a few items to work through with the dev team before we post our evaluations of the current priorities. That’ll take a few days and we’ll likely will have the new post up around the time of the July 4th holiday.
*July 5, 2018
editing latest data, and a lot on the plate, so likely during quiet time on the weekend.
July 8, 2018
Working through update topics this Sunday, will advise soon.
July 9, 2018
Getting through our action items right now, will advise in advance of posting.
July 16, 2018
next up is posting some technical background, and that’s a function of some decisions currently being discussed by dev team.
Main thing we’re deciding now is how to manage transition to newest infrastructure code. Want to sort that out so we can give a coherent insight into the work we’re doing right now, and how it facilitates the overall release plan. Dev meetings this week are aimed at settling that.
July 24, 2018
Note - what we’re working on isn’t the volume of text, but rather the team decisions about how best to complete the migration so it’s most favorable for release. That is working through a lot of dependencies to minimize them. We’ll advise as soon as we’ve completed a coherent analysis and team agrees on most efficient path to help us advance quicker.
August 19, 2018
Got our hands very full this week, but will circle back soon to give example details of what we’re doing now.
August 27, 2018
We’ve got our hands full at the moment, but will aim to post a summary later next week.
Sept 9, 2018
we’re putting together descriptions to provide context for the infrastructure code we’re focused on right now. That code will accommodate the requests we’ve gotten from users, and will provide a good foundation to support the sort of needs that general release users will likely ask for. We’ll put in a few more days on those explanations, so you can all have good visibility on what remains for GR
recent asynchronous demands have been more intense than expected, so quiet time’s been a bit hard to come by. That’s what usually is needed to write-up detailed summaries based on latest dev results.
Sorry for not posting more details now, we definitely care a lot about you, and every customer who wants this new technology. We have quite a lot going on in this period, and we have to prioritize progress on GR shipping over PR content. We’ll give you some detail insights as soon as we can, but the focus on engineering action now is really what gets a great product to your door.
Sept 19, 2018
will update fairly soon, after working through decisions relating to transition for new code fork. Those decisions are operative to set overall plan.
Sept 26, 2018
There are complex interdependent choices which we are deciding now, and we’ll update our forecast soon.
December 15, 2018
We’ll reveal some interesting tech details after we’ve proven a few more steps in our dev labs. Not ready to comment publicly yet, but think you’ll really like the upsides for users. They’re significant.
February 5, 2019
we’ll unveil more tech details about the architecture advances soon.
March 7, 2019
we will provide some meaty tech details later this month.
we’ll be updating on tech details of the new fork later this month
March 30, 2019
Will publish a tech update soon, but not sooner than a week from now.
April 11, 2019
We’ll make some official announcements in a few weeks, but features and price will advance.
All existing preorders get to keep their original pricing, and will also gain all the added benefits.
The preorder deal is better than currently announced.
April 22, 2019
We’ll post a more in-depth TechTalk about the foundations for the new firmware and its significant advances in capability, after we complete a few more of the migration steps.
May 20, 2019
we’ll soon be publishing details of the new infrastructure firmware - around end of May.
*May 31, 2019
Just letting everyone know we expect to post our TechTalk update with a lot of exciting news about TextBlade’s powerful new firmware infrastructure, on Saturday evening after 9 pm pst
*June 1, 2019
Will be working on it for a while yet tonight, so please get your rest in the meantime.
*June 2, 2019
got some good content settled this evening, and want to cover a few more points of interest.
Will get some sleep now, and finish editing Sunday to post for you all.
Sundays are good quiet time for this kind of work.
Get some rest to see the Keynote. We’ll be busy on this for a while yet tonight.
*June 3, 2019
Quite a lot of ground to cover, but getting though it. Think you’ll like what you learn in this update
Gonna keep at it for a while to try to get this one off the plate.
Think cognitive productivity will improve to get it done faster after a few hours rest. Will come back at it fresh to finish up.
June 6, 2019
thanks for your patience while we finish the update. It contains many things you’ll like.
June 11, 2019
Although we’ve posted many points relating to our infrastructure work, there’s some important and exciting dimensions that we know folks are anxious to learn. We own that task, and we apologize for the time it takes to work through it. That onus is on us, and we feel it profoundly every day, until our update is online and it’s put behind us.
Reporting tidbits of data is not hard, we’ve been doing that, but to embrace what folks really want, and provide them enough context and depth of detail to understand it - that takes much more thought and care. Much of that involves not writing, but instead working through important decisions by our team about how we handle certain technical and business choices that defend our customers best interests. Some of those choices have more aspects than you first think, so you must work to settle any loose ends before you announce.
*June 12, 2019
We know what you need, and we’re making it. You’ll learn more about what we’ve done in our post.
Rather than declare a time that tries to please, we’ll just complete our post expeditiously and put it online.
don’t worry, this self-regulates. It’s simply too excruciating to stay in the soup of doing it
June 15, 2019
By the good questions raised above, you get a feel for why there is a lot to cover. The update goes into some good depth on these points, and we expect it will be helpful.
June 18, 2019
we’ll focus on finishing our main post which should give a bigger picture of what we’ve built.
June 19, 2019
we apologize for delaying our post. There were more points to decide than we had considered, and several asynchronous tasks added to our load. As we mentioned, we’ll post soon and hope it’s helpful to you.
July 11, 2019
As we said earlier, better to let our post give the full picture, and drive the date. We’ve been handling many time-intensive requirements which we believe will settle soon.
July 23, 2019
team has everyone focused on manufacturing facilities logistics tasks right now. Will post again after we get that done, which will be very helpful for shipping. Will make some comments next week
Sept 30, 2019
Will put bandwidth toward editing tech update next week, and post soon after.
Well, as to content, we don’t think folks are expecting a Hemingway, but the TechTalk should give everyone a good understanding of what we’ve been doing, and our timing.
We’ve provided small posts along the way, but nothing will quite satisfy like the big picture. So we’ll let the post itself do the talking.
Please nag us next Tuesday dbk if you want to follow up, right now we’re full-up laser focused on patent legal documents for Friday.
October 8, 2019
Patent stuff went excellent, so we’ll be putting bandwidth toward editing update for you during this week. Made considerable firmware progress in the meantime, and hope to post details for you soon.
October 16, 2019
Working to satiate that hunger soon.
Engineering milestone review went well today. Test data is quite encouraging.
We believe you’ll like what you learn when we announce details
October 30, 2019
will focus on that once the rest of the amazon servers that manage orders are likewise upgraded with new certs and security code.
November 7, 2019
Admin distractions often grab cycles for dull but necessary tasks. Definitely more fun to write about cool engineering advances the team has built. That work has marched forward in the meantime, and we’ll discuss a few in our update.