Oren Eini

CEO of RavenDB

a NoSQL Open Source Document Database

Get in touch with me:

oren@ravendb.net +972 52-548-6969

Posts: 7,546
|
Comments: 51,162
Privacy Policy · Terms
filter by tags archive
time to read 2 min | 372 words

Just got (after three weeks) a response to my issue with them:

The confirmation letter you received initially displayed this message : "This page is your proof of purchase. Please print and save it for future reference."
 
The responsibility of keeping track of your license details is yours.
 
Keeping track of user license  and hosting it in our data base, consumes a lot of storage space, and demands the attention of a large crew of people, dealing with both software and hardware, and as I wrote before, this task is not free of charge.

So, basically they are saying it is my fault (correct) and that I should deal with it (wrong). I am talking wrong in making me a happy customer. Every other company that I did business with was more than happy to resend me the license details, sometimes several years after the fact. The fact that Babylon is treating a customer like this is amazing.

Hiding behind "it cost a lot of money" is a sad excuse for someone who know how this stuff works. My response:

I am aware of that, but you know what, that is not a nice way of getting repeated business.
And don't try to tell me that keep the user data cost a lot of money that you wouldn't spend anyway.
Frankly, I expect response times that are greater than three weeks and a far more civil treatment as a paying customer.

 

 

time to read 2 min | 384 words

If you are not familiar with it, Babylon is an OCR / Dictionary program that can be a god send for trying to find the right word. I have bought the last two versions, but I don't think that I am going to give that compnay my money evey again.

The story is quite simple, I repaved my machine (when I installed Vista), and I wanted to install Babylon again. I couldn't find my key, so I pinged Babylon with a request that they will send it to me again. This is something that I have done before with a number of companies, and I never had any issue with them.

Babylon's response to my request was:

Over the years enormous amounts of Data accumulated in our systems.
This Data Base is constantly being maintained by a professional IT team, managing a vast hardware and software system.
Naturally, maintaining the Data Base systems does not come free of charge.
Therefore, restoring your license and setup file will cost a one-time fee of 7 USD.

As someone that deals with IT, I understand the enormous amounts of data that they have, but I find it hard to understand what is the big cost of running a SELECT on the system. And why something that should be built into the system should be so cumbersome. I can understand that this attidute means that they have low return calls, which may be nice for the support department, but very bad from the sales departments.

What is worse, when I (repeatedly) replied to the response above, I got no answer. So, for about two weeks, Babylon has been treating me in a way that is not appropriate if they intend to have me come back to them, and they decide to ignore repeated emails from me in this subject. I was a paying customer, but I do not believe that I would have any further dealings with them.

By the way, I have restored the license info from backup, to foretell those who would say that this is what I should have done in the first place. I am not arguing that, I am arguing that when I had a problem, Babylon treated me in a way that I find offensive, and then proceeded to ignore me.

FUTURE POSTS

  1. Partial writes, IO_Uring and safety - about one day from now
  2. Configuration values & Escape hatches - 4 days from now
  3. What happens when a sparse file allocation fails? - 6 days from now
  4. NTFS has an emergency stash of disk space - 8 days from now
  5. Challenge: Giving file system developer ulcer - 11 days from now

And 4 more posts are pending...

There are posts all the way to Feb 17, 2025

RECENT SERIES

  1. Challenge (77):
    20 Jan 2025 - What does this code do?
  2. Answer (13):
    22 Jan 2025 - What does this code do?
  3. Production post-mortem (2):
    17 Jan 2025 - Inspecting ourselves to death
  4. Performance discovery (2):
    10 Jan 2025 - IOPS vs. IOPS
View all series

Syndication

Main feed Feed Stats
Comments feed   Comments Feed Stats
}