Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
Not open for further replies.
#1: Waytools has been untruthful in the units being production ready.

Because it implies, especially combined with the "deceitful" comments, that they lied. Certainly possible - or maybe they were simply wrong.

Don't you wonder why some critics who became testers suddenly talked about how they understood the problems in getting this right? Oh, I know the excuse on the reddit board - charges of stockholm syndrome, claims that we are afraid we'll lose our TB, etc. IOW, just any excuse against perfectly good people.

When the reality is that we can see the difficulties and how you can think it is about ready, only to have another problem come up.
 
Because it implies, especially combined with the "deceitful" comments, that they lied. Certainly possible - or maybe they were simply wrong.

Or maybe aliens, unicorns, or fairies. You see with out any evidence my three reasons are just a valid as yours.

Evidence for WT knowing that the product wasn't production ready during March 2015:

on March 28th 2015:

Waytools said:
This month, WayTools made changes to its manufacturing lines to further improve quality and performance.These changes required several weeks of additional work to complete, and we made updates to the server as we settled them. These manufacturing changes are near completion now, and the overall effect on ship dates has become well defined.
ref:https://waytools.com/threads/blog/robotic-butterfly-mold

Several weeks of additional work. But can we get a time frame for that. On March 11th 2015:

Waytools said:
At the Hands-On event for customers, WayTools demonstrated both the prior production butterfly, and an engineering sample of the new technique, and let customers compare the two.
ref:https://waytools.com/threads/blog/robotic-butterfly-mold

So at the hands on event the Macrumors covered March 6th 2015:

Macrumours said:
TextBlade is in production and many of the components are ready to go. The company has made some last minute changes to tweak the butterflies underneath each key to provide an even better, more precise key feel,
ref: https://www.macrumors.com/2015/03/06/hands-on-with-the-textblade-keyboard/

We can say that the butterfly changes were known about weeks prior to March 11th 2015 (the date of the Hands on) as evidenced by the presence of the new butterflies, already prototyped. In fact they state that the change to the production line was initiated some time in February. They state that the robotic production line would take 2 further weeks to complete. That they knew it would take longer to set up than the other lines, and that it the tool will come online mid April. That means that the delay announcement in late March of a delay until the end of April could reasonably have been foreseen in February when the process to update was actually initiated. The set up time for the line would have been a knowable or a possible estimate thing as they had already done it once, and knew that the process would be longer. We know from the Keycaps revision that a Month is a reasonable estimate for a moulding change, so 'More than a month' would be a good starting point. A month from the last possible (most generous) point the Line changes stated comes a delay estimate of a further 2 weeks for the new line to be ready and EOM April as their new earliest possible shipdate. That would have been known in February when you started.

Approximately one month after the launch of a product with 6-8 week lead time, you initiate a change which a reasonable person would have known was a 2 month delay but not announce it until well after the end of the original quoted ship period, at least one month into the process.

Any unit sold as "production ready" from the date the change was initiated in February until the announcement late March was sold knowing that the means of production was yet to be built.


Don't you wonder why some critics who became testers suddenly talked about how they understood the problems in getting this right?

No, I 'm sure the have their reasons. I wouldn't be so crass as to put words in their mouths.

Oh, I know the excuse on the reddit board - charges of stockholm syndrome, claims that we are afraid we'll lose our TB, etc. IOW, just any excuse against perfectly good people.

No evidence provided to counter the claims that Trickflow didn't make in the statement you quote. How people feel about the product before or after become a tester is not relevant to the statement
#1: Waytools has been untruthful in the units being production ready.

When the reality is that we can see the difficulties and how you can think it is about ready, only to have another problem come up.

This is possible, but if this is true then the quality of estimates is so bad as to make them meaningless.So for a new order placed today they estimated shipping is initially quoted as JAN (no year) but on the basket it's stated Q1. Things things are not the same as Q1 contains two months after January.

R
 
Where does it say they started this in February? Exact quote needed.

It does say that at the Hands-On, that they had an ENGINEERING SAMPLE, which is not necessarily close to working out a whole system and it sounded like they based part of their decision to make the actual change on the comments of people at the event - which wasn't until March 11. If they made this change in the PRODUCTION line FOR THIS in February, why would they only have engineering samples in mid March?

Need clarification since the last time I followed one of you summaries, it was way off the mark - trying to imply a rapid response from WT (15 minutes) to a post of mine somehow was revealing. But it ignored the obvious facts. In the very same thread, I posted similar questions not just 15 minutes before a response came, but also 10 hours, 49 hours, 79 hours - as well as 7, 9, 10, and 12 days before their response. Which meant the out of context "timing" comment actually revealed nothing. But the full picture would have made it hard to imply anything negative.

So I need much more precise information from you.
 
Where does it say they started this in February? Exact quote needed.

Date of article March 28th 2015
Waytools said:
In order to use this material, an entirely new steel mold cavity had to be built, which WayTools initiated last month.
The quote was in :https://waytools.com/threads/blog/robotic-butterfly-mold

Month at time of writing was March
The month before March is February
February is the month the new cavities where initiated

Waytools said:
When we began the Butterfly mold upgrade described in our status log report, we also launched the second molding line at the very same time. And for this second line, we specified a more sophisticated molding system, with certain technical advantages.
The quote was in :https://waytools.com/threads/blog/robotic-butterfly-mold

The upgrade to the line started when the work on the moulds started.
work on the moulds started February
The upgrade to the line started February

QED

It does say that at the Hands-On, that they had an ENGINEERING SAMPLE, which is not necessarily close to working out a whole system and it sounded like they based part of their decision to make the actual change on the comments of people at the event - which wasn't until March 11. If they made this change in the PRODUCTION line FOR THIS in February, why would they only have engineering samples in mid March?

The decision to switch had already been made by the hands on(s) as they had made the decision to build the second robotic line when the made the mould required to product the samples used at he Hands on. As they state in their blog.

They state line would not be finish until "mid april" in :https://waytools.com/threads/blog/robotic-butterfly-mold
So the Engineering samples predate the completion of the robotic second line, this is undisputed in my post. What they can't predate is the Moulds for the part. They stated they need a new moulds for the new material.

Waytools said:
In order to use this material, an entirely new steel mold cavity had to be built, which WayTools initiated last month..
The quote was in :https://waytools.com/threads/blog/robotic-butterfly-mold

Lastly and I will be kind here, It took one month for them to straighten out some new injection moulds for the newest keycap iteration. This task at hand here was that, with the addition of all new automation, testing, QA, and so forth. Their QA of the part hadn't completed by the beginning of May, That is before subsequent issues derailed things further (retooling line to reduce keycap failure on assembly).

Need clarification since the last time I followed one of you summaries, it was way off the mark - trying to imply a rapid response from WT (15 minutes) to a post of mine somehow was revealing. But it ignored the obvious facts. In the very same thread, I posted similar questions not just 15 minutes before a response came, but also 10 hours, 49 hours, 79 hours - as well as 7, 9, 10, and 12 days before their response. Which meant the out of context "timing" comment actually revealed nothing. But the full picture would have made it hard to imply anything negative.

I said it was a fact, not an argument. Any other meaning is brought to the comment by the observer, and as such is not my problem. It is no surprise to me that you felt the need to spin it.

As a side note: Do you ever get tired of asking for something for 12 days and not getting a response?

So I need much more precise information from you.
It's not my information, it's Waytools.
 
Last edited:
So their blog says, in various ways, that shipping wouldn't begin until the end of April or so (of last year).

I don't see a problem there so I guess it has to do with your claim that this was "foreseeable" the prior February and, what, they were therefore lying in February?

Lots of things are "foreseeable" in hindsight. And some people might "foresee" it at the time - there being lots of people, each with their own predictions so someone is likely to be right even if they are just guessing.

> I said it was a fact, not an argument.

An argument - especially good ones - are based on facts. An argument is a reason for believing what you believe. This is commonly used ("legal arguments", "scientific arguments", etc).

>As a side note: Do you ever get tired of asking for something for 12 days and not getting a response?

Oh, I don't like the level of communication. I also don't like it when someone takes events out of context to try to make it look like I am so connected to WT, that I can ask a question and they'll quickly respond. That is what YOU did. And now, rather than admit there was nothing special about the timing, you switch to essentially the opposite complaint - that they took too long! Weird.

>It's not my information, it's Waytools.

It is your information even if it originally comes from WT. Because you are using it for YOUR arguments. So it's like asking someone, "What information do you base your decision on?". They aren't asking for that person's original research normally, but what they got from others that they chose to use themselves.
 
So their blog says, in various ways, that shipping wouldn't begin until the end of April or so (of last year).

I don't see a problem there so I guess it has to do with your claim that this was "foreseeable" the prior February and, what, they were therefore lying in February?

Not arguing about "forseeability". They said on march 28th 2015 that they had initiated a change "last Month" (ie. February) to the means of production rendering production impossible while until it was completed. They continued to take orders under the aegis of the January statement saying they were production ready. They did not make an attempt to countermand their statement of readiness until March 28th 2015. At which point the admitted to at least a further month of unreadiness, two weeks of which production line was not "online".

It is not some augury of the future to which I am referring, but a fact in their own blog.

You claim that Trickflow's comment #1 was not valid, yet I have demonstrated a period on time where information regarding the production status was available to WT, and that they withheld it from a point in February 2015 until march 28th 2015. All the while continuing to take orders and leave the claim of readiness unchanged.

That's not "spun", the claims are all in their own literature, it is a statement of the facts surrounding the changes to the butterfly.

Note that they did not mention to @jclo on march the 6th that there was a production issue, only that there was a last minute change. They made no mention of it in the hands on literature a week later.

They had two opportunities in major press releases to mention the delay, any delay, any issue regarding the shipment of the first deliveries, but neglected to.

Lots of things are "foreseeable" in hindsight. And some people might "foresee" it at the time - there being lots of people, each with their own predictions so someone is likely to be right even if they are just guessing.

You don't need to foresee a past event.


> I said it was a fact, not an argument.

An argument - especially good ones - are based on facts. An argument is a reason for believing what you believe. This is commonly used ("legal arguments", "scientific arguments", etc).

No argument was made. See the original post. Your inferences are your burden not mine. NEXT!

>As a side note: Do you ever get tired of asking for something for 12 days and not getting a response?

Oh, I don't like the level of communication.

Aww shucks. you could have stopped there. An actual answer to a question. Hurrah!

I also don't like it when someone takes events out of context to try to make it look like I am so connected to WT, that I can ask a question and they'll quickly respond. That is what YOU did. And now, rather than admit there was nothing special about the timing, you switch to essentially the opposite complaint - that they took too long! Weird.

Still on that? Did I say there was a link? I have asked you questions in this thread to clarify the exact nature of your relationship with WT. You chose not to answer any of them, any answers found were sourced from WT, or from your posts to others. The only one keeping this issue alive is you.

Additionally I did not post that particular comment here, so you must have gone to the other place, looked inside a marked spoiler, then come back here to post here and at WT. For the record the comment is
ME said:
Well 10:33 to 10:48 (system time) is all it took for WT to respond to DBK.

No other context applied in my post. EVERTHING else is you spinning like there is no tomorrow, here, there, everywhere.

You were the one who originated the claim of "influence" however infinitesimal, not me. I asked questions about your relationship with WT and you were too busy fighting imaginary assailants to answer me.


>It's not my information, it's Waytools.

It is your information even if it originally comes from WT. Because you are using it for YOUR arguments. So it's like asking someone, "What information do you base your decision on?". They aren't asking for that person's original research normally, but what they got from others that they chose to use themselves.

Then ask: "What information did you base this on?" Equivocation is not your friend. Please note the sources were given with the original post. You just must not have read them.

I will be doing the usual thing, in the usual place as another week has elapsed. Be there or be an equilateral quadrangle with rotational symmetry order 4.

R

Edit 11:12: Formatting Tags, and spelling
 
Last edited:
  • Like
Reactions: Pushpaw
No other context applied in my post.

That's all the context needed: "Well, 10:33 to 10:48 (system time) is all it took for WT to respond to DBK". Three factors, all right there (WT, me, and the timing - YOU brought them up, not me.

And you couldn't follow the context, even though a good portion of it - more than enough to invalidate your comment - was in the prior two posts. Which showed I asked similar questions 10 and 49 hours before. So, gee, it wasn't "only" 15 minutes. But you needed to make it look like the timing mattered when it didn't.
 
That's all the context needed: "Well, 10:33 to 10:48 (system time) is all it took for WT to respond to DBK". Three factors, all right there (WT, me, and the timing - YOU brought them up, not me.

And you couldn't follow the context, even though a good portion of it - more than enough to invalidate your comment - was in the prior two posts. Which showed I asked similar questions 10 and 49 hours before. So, gee, it wasn't "only" 15 minutes. But you needed to make it look like the timing mattered when it didn't.

You spin Waytools more than the Mac Rumors fluff stories did. Honestly, you work for them or with them, right?
 
  • Like
Reactions: Pushpaw
You spin Waytools more than the Mac Rumors fluff stories did. Honestly, you work for them or with them, right?

What did I spin? And I've given all anyone needs to know about me and WT - I'm was a customer, just like all the others who complain. I was chosen as a tester, just as some other customers were. As a tester, I do my very best to find problems - even possible solutions - and inform WT and, as one of the few people who can give information outside of WT itself, I do my best to provide my experiences to others.

BTW, MR very clearly provided the information on delays both near the beginning and near the end of their last article - that is, the two places there it would carry the most weight. That's not what fluff pieces do.
[doublepost=1474325167][/doublepost]BTW, for all the talk about butterfly changes being made in February, I don't see anything really clear about then they actually decided the new ones were better and thus they were definitely going to make the change back then. Yes, they did produce some new ones, but producing something doesn't mean you decide to go with it. You evaluate the pros and cons and much of that can't be done until you have production samples.

For example, before WT decided to redo the PCB boards, they were testing the multiple sample lots (thousands in each lot) to see if any of the lots were unaffected by the problems some encountered. Obviously there were some changed made for each lot - because if there was no change, there would be no logic to separating them by lots to begin with! May have been different assembly approaches. May have been different groups of workers with some doing better than others.

Thing is, changes could have an effect and have to be checked. So this could be much the same. Old butterflies worked, they thought they found something better (which maybe they should have saved for version 2, but too late now), and so they created these - but still had to decide whether or not to actually make the change across the board.

And that may not have happened in February. Hard to tell because WT, even when they give a lot of information, often don't explain things clearly.

A good example of that, and an easier one to follow, is how they use "gating" when talking about things that determine whether something will ship. To me, and I suspect most people, a "gating issue" is ANYTHING that will block shipping until it is fixed. But WT description is different. Basically, if something will take 2 month (estimated) to fix, that's a gating issue. But if they also have other things they expect to have fixed in less than a month, they don't include them in any description of gating issues since they don't expect them to actually block release.

I don't think that is a good way of doing it, but it does show how you have to be careful in how you interpret what WT says.
 
BTW, for all the talk about butterfly changes being made in February, I don't see anything really clear about then they actually decided the new ones were better and thus they were definitely going to make the change back then.
Read post #604 again. I lay out the salient points in WT text which demonstrate that the production line was being changed in February when the moulds were being created. The decision must have been made by then, as you do not change an entire production line on a whim. It is an expensive and time consuming process.

To give a recent example WT dithered from at least 9th August 2016 https://forum.waytools.com/t/production-update-9-august/4042 before admitting on August 14th 2016 https://forum.waytools.com/t/production-update-9-august/4042/98 that "UV passivation" which seemed to be "testing well" on May 22nd 2016 https://forum.waytools.com/t/treg-validation-testing-update-21-may/1726 was not the fix to the intermittently issue reported; announcing on the 28th August 2016 that they were going to redo the flex PCB's.

From public confirmation of micro fractures in the flex PCBs https://forum.waytools.com/t/treg-testing-brief-update-14-may/1715 on May 14th 2016 to the tossing of the damaged (and potentially damaged) component stock on 28th August 2016 was 106 days. 106 days to accept a stated delay of a month, if indeed PCB's are turned out in September, all of which gets us back to the start of testing once more.

Altering a line is a big enough deal that burning 106 days of wages to try and avoid it was the route taken.

A TREG user might be able to provide more insight into the gap between TREG units going out at the end of March and admission of the fault in May. That would potentially scale the testing time required to demonstrate the lack of this fault in the new stock when it lands.

Yes, they did produce some new ones, but producing something doesn't mean you decide to go with it. You evaluate the pros and cons and much of that can't be done until you have production samples.

How much product design or industrial prototyping have you done? If it is none, then you might want to research tooling costs for complex multipart prototypes, and then consider the likelihood of the butterfly change being done without a clear will to change the product.

If it is even some, then think about the attendant risks in prototyping components with orders for finished product on the book.

In either case what happened regarding sheering of components was a foreseeable risk, trading up in stiffness of materials reduces flex, (solving the keyfeel) but increases stresses on other components. You don't need a degree in materials science to follow that.

Just have a look and a bit of a think.

R
 
  • Like
Reactions: Night Spring
It may very well have been made by then. Or not. And it has nothing to do with "whims", but trying new things and testing to see which is best.

So you are saying the decision to change the production line may of may not have been made when they said they changed the production line.

My point is and was that changing a production process was not done on a whim, and that a great deal of planning must be done prior to such a change. If the decision was made then on what basis was the planning and initiation of the production lin change done. Whim is as good a word to describe the 'blind idiot' process of product development you are potentially ascribing to WT with your casual or not.

No, they did not "dither". They were testing.

Simplest fix for component failure is redesign and replace component, this would have fixed the issue (if WT estimates for current flex PCB lead times) by mid June. (Based on the identified fault being public ally announced mid May).

Everything else was sub-optimal time usage and was always going to be.
 
Last edited by a moderator:
No, I'm not saying that.

Then are you saying when they said at the end of March they initiated the production line changes alongside the mould changes "last month" they lied? (I am assuming you are not, but for clarity please answer this one somewhere in your responses.)
 
Last edited by a moderator:
Let’s talk about WayTools’ sister company NextEngine, which also was founded and is run by WT's founder and CEO. Looks like NE burned through a bunch of money and then got embroiled in a legal battle:

“I. The Complaint and Cross-Complaint Bigfoot is a private venture capital company based in Hong Kong whose sole principal is Michael Gleissner. NextEngine is a private technology company based in Los Angeles whose founder and chief executive officer is Mark Knighton. In December 2009, Bigfoot filed this action against NextEngine, alleging causes of action for breach of a 2008 promissory note and breach of a 2008 mutual release agreement. In response, NextEngine filed a cross-complaint against Bigfoot, alleging causes of action for breach of a 2009 oral agreement, breach of the implied covenant of good faith and fair dealing, failure to preserve collateral in violation of the UCC, and improper disposition of collateral in violation of the UCC. The parties’ legal claims were tried to a jury in October 2011.”

There’s more detail about the debts NextEngine incurred and the resulting lawsuits here:
https://webcache.googleusercontent..../nonpub/B242559.PDF+&cd=2&hl=en&ct=clnk&gl=us
 
Not much new to report on, but I did get a firmware update after reporting a problem with caps lock right after I upgraded to the new MacOS. 20 minutes later they had updated firmware which solved it.

What we are really waiting for is another meaningful update. They said it will come after analyzing some treg testing, but it was way too vague to tell much about it. For example, it could refer to some specific group of testers who found something that others have not. Or it could refer to going back over many treg reports to deal with minor issues they put off while getting the bigger stuff done. Or something else. We just don't know at this point. Worse, we don't know how long it will be before they are done. This is the kind of stuff WT really needs to improve on.
 
Looks like a nice tidy on topic thread now.

This is the kind of stuff WT really needs to improve on.

Agree, and I think we always have.

Remaining on topic a round up of known issues waiting for fixes and/or announcements from WT

  • Keycap - Issue: Breaks when used on concave surface. Suggested solution: Redesign from the mold forwardSTATUS -.Not finished/No news this week. Last Known - Apparently Keycaps are in Santa Monica, however no news whether testing was completed.

  • Nano stand - Issue: Breaks in use. Suggested solution: Redesign from the mold forward. Status Not finished/No news this week. Last Known - Last heard of as test injections, however no news whether shipped to Santa Monica or tested.

  • Firmware - Issue: Unknown number of incremental issues. Suggested solution: None (no indication of position in any roadmap) Status- Not final/No news this week

  • Multimap for Android - Issue: Does not exist. Suggested solution: Create it (no indication of position in any roadmap) Status- Not Started/No news this week

  • IOS capability - Issue: Testing not complete on App settings for IOS/Mac. Suggested solution: test it. Status- Farmed out to TREG.

  • Factory Coating PCB - closed out on this list. It was a fix for the intermittant failure issue that was applied to the old componant inventory. Impossible to verify efficacy as old stock was faultier that initially thought. remains as a process in the new assembly line, unclear where, or what testing is expected when to new units hit Santa Monica.

  • Flex PCB - Issue: We threw them away as they were broken Solution: Make new ones. Status: New components ordered. Fabrication is indicated to take at least September 2016, testing duration unknown. Process continuing, apparently on track, which means nothing as the 'track' has not been specified. (no details given)
Some background

  • Things to Consider - At what point do the issue smaller in scale than Flex PCB get some reporting? If it is after Flex PCB "is deployed and all testing well..." message then that is obfuscation of the true project state. . If there is an issue that will slow GR then state it clearly and an estimate of investigation and/or solution time. Do not make people disappointed on September the 30th when you have the Flex PCB's in units in Samta Monica all on time and then say "There is an issue in the transom hoist relating to the Fnarlgle, more when we finish testing." If fabrication of Flex PCB's is going to slip, just say now, it's ten days out. 66% of the stated window of "concentration" as they put it has elapsed. If WT mentioned the ETA for the components at Satan Monica, and the allocated test time once there WT's customers would have a better idea of the minimum time to ship. I think I am not the only one who doesn't want holiday season to come and go and then get a Q1 2017 delay announcement out of the blue. After nearly 7 straight quarters of delays, transparency will not be harmful to your project, unless of course there are things that have not been announced yet material to delivery. In any case it's come clean time.

  • Final Thought - If you had put the full asking price down on a product, done however many hours road testing prototypes and issue reporting, you would probably expect better clarity on the project state. Although I imagine if you had put the full asking price down in Jan 2015 and still weren't getting quantitative assessments of when your product is going to arrive you might be wondering exactly why this as taken so much more time than you were originally told.
R
 
  • Like
Reactions: Trickflow
We received a new firmware update. Not a lot to report and what I have is based on just one test process so hardly definitive. Anyway, some of it had to do with the battery charging. I was pleased that, based on the LED lights, all were lit in 35 minutes starting from no charge. That's much faster than it used to be (49-55 minutes).

However, I found with my prior tests that having all the LEDs lit does not mean it is really up to the maximum charge. A couple times I started using it as soon as all were lit and it would drop to 9 LEDs sooner than normal, so I got in the habit of just charging longer - typically overnight or while going out for a little while so it probably typically would have at least 2 hours.

I have no idea if there is any change in that aspect, nor whether battery life is any different. I probably won't be testing for that simply because, unless the change is big, it is way too much of a hassle and any data is so subject to how much I'm actually typing on it that it isn't really worth the effort. But if I notice anything obvious, I'll report on it.
 
Another small tidbit, since firmware is being polished while we wait for the hardware to finish.

They have a "smart delete", which you can turn on or off. Normally, barring some customization changes a person may make, if you press Delete, you get a normal delete action. But if you press the space bar and delete, you get a forward delete instead. Very handy, usually, but the normal way you get the numbers is by holding the space bar and hitting keys on the top row (there are only 3 rows so no separate row for numbers). If you are doing a lot of numbers and want to delete something, chances are you are already holding the space bar, so you would get a forward delete - which usually won't be what you want.

So, without the smart delete turned on, you'd have to lift off the space bar, hit delete, then put it back down to continue typing numbers. But with it turned on, when you hit delete, even with the space bar down, you get a regular delete. If you do want a forward delete, you'd have to lift off the space bar and then put it back down - certainly awkward, but like I said, in most cases you wouldn't want a forward delete. In any case, it is just an option if it doesn't work for you.
 
Months ago I reported a problem I had with my TB giving the wrong letter sometimes and it would occasionally be bad enough that I could make sure I was pressing the proper position on the keycap, but getting the wrong letter over and over.

At the time it was believed (and probably was correct) that some conductive contaminant had gotten inside. One supporting fact for that was that I would whack the edge on my leg and it would be good for a long time - so probably the contaminant got moved. Happened a few more times, far apart, and each time the whack approach solved it. They offered me a replacement but I figured it wasn't common enough to do so as everything else was fine. I could take it apart and clean it but didn't want to mess with it just in case I screwed something up in the process.

Anyway, more recently I started having a similar problem, more often though it never lasts as long (makes it harder to test for a TB error or a user error). Same keycap, but a different pair of characters (there are 6 main characters on this key). So I reported it and it looks like we'll go ahead and replace it this time.

On the bright side, the replacement will have a number of the improvements they have made since my last one in April. Including some stuff specifically for protecting the device from the effect of such contaminants. On the negative side, apparently it won't have the new keycap design or pcb board updates.

Still, looking forward to see if the new one works better in any obvious ways. I probably won't be able to compare how it handles contaminants since I certainly couldn't make that happen in exactly the same way, but there may be other things. For example, I've heard some time ago they made some changes to the magnet effect that gives a slightly different feel. I'm only sure about one person who has it and as I recall he liked it better.

UPDATE: New unit is supposed to arrive Tuesday.
 
Last edited:
It's cross-post, weekly Roundupdateathonarooney time.

So here we are late-September and actual news is: 9 words of update in 7 days.

Just to recap nothing has changed read last week's roundup on issues if you need that nostalgia vibe https://forums.macrumors.com/thread...users-next-week.1957232/page-25#post-23541853

Yup ^^ just up there, yeah left a bit, no your other left, yeah there. #618.

Some background
  • Things to Consider - Same as last week but replace "10 days out" with "3 days out" There is no new news.

  • Final Thought - WT is showing the lack of care given about it's non-intern/NDA customers by ignoring them. It is telling that the only communication it to thank someone for posting what is a essentially a bump for their TREG application. (Not a dig at the guy, love your enthusiasm by the way, he can't control what Captain Capricious Head of Webulation-Interossiters at WT facerolls into his magnetic coat-hanger of doom.)
R
 
WT is showing the lack of care given about it's non-intern/NDA customers by ignoring them. It is telling that the only communication it to thank someone for posting what is a essentially a bump for their TREG application. (Not a dig at the guy, love your enthusiasm by the way, he can't control what Captain Capricious Head of Webulation-Interossiters at WT facerolls into his magnetic coat-hanger of doom.)

I have no idea what you are referring to. Is this about something that happened on Waytools forum?
 
I have no idea what you are referring to. Is this about something that happened on Waytools forum?
Well, yes. That's where they post their updates. (that and the blog, but all quite there)

They posted 9 words in 7 days none relating to the product, and 93 words (that's circa 400 keystrokes) in the 7 days prior to that.

The content split of those 93 words was such that only 5 words related to news regarding the product. The of the rest 73 related to answering TREG users posts and 15 excusing themselves for not having done their test analysis.

If you add all the words posted by WT relating to their progress since the beginning of the month you get 66 whole words. A herculean effort, bravo all!

If you consider all the rest posted, another 547 words of almost random posting,

94 words of admin activity (Banning users, attacking banned users, closing threads)
35 words talking about Tesla (they like to talk about tesla)
73 words Tech support for TREG.
105 words of fluff with no actual content
15 words of excuse
225 words of blaming others for their lack progress. (time well spent I am sure)
380 words laughing at Samsung (time well spent I am sure)

September's update output percentage: 7.1%
Total words per day (to date):36.8
Total update words per day (to date):2.4
Total Words relating to a Day, date, time, in relation to completion of any process: 0

This from a company producing a Keyboard.

R
 
  • Like
Reactions: Pushpaw
Status
Not open for further replies.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.