Can you explain why you cannot provide the basic update before Feb 3rd, other than to play on customer's impatience to obtain more sales?
I'm not a Logos/Faithlife employee, just a user. However, my understanding is that they just want to pay the bills first, before giving away the milk for free. Logos5 will work just fine until then. There's been a lot of time and money spent so far on developing Logos6 and all the new data sets (they're really good, BTW). Seems fair that they would prioritize recouping those expenses first.
Consider it an opportunity to exercise your patience 'muscles.' Think about how much more patient you'll be by Feb. 3. You might even be patient enough to wait until Feb. 4, just to prove you can do it. [;)]
One of my most frequent (and unanswered) prayers is "God, please grant me patience . . . right now!" [li]
One of my most frequent (and unanswered) prayers is "God, please grant me patience . . . right now!"
I would also guess that support calls would increase greatly if they did not phase the releases. This costs money and time.
it's all in your perspective: most people did not expect it till November of next year, so getting it in February is like !!! 9 months early !!!
Can you explain why you cannot provide the basic update before Feb 3rd, other than to play on customer's impatience to obtain more sales? it's all in your perspective: most people did not expect it till November of next year, so getting it in February is like !!! 9 months early !!!
[Y]
Patience isn't learned by God taking everything that makes you impatient away.
In my opinion, this is poor practice. I have no desire to purchase an upgrade and will deal with Logos5 engine for the time being. Maybe its time to cut our losses and move to a platform whose software upgrades are value added and not heavily monetized.
Logos will give you the software free of charge starting February 3rd.
a platform whose software upgrades are value added and not heavily monetized
Alas, it takes money to keep writing new code and creating new features. I don't think we're unique in wanting to monetize upgrades -- I've paid for quite a few over the last 20 years for Windows, Adobe products, Microsoft Office, etc.
And in the case of Logos 6, a lot of what's new is a hybrid of code-and-content, and we had to pay to create (or purchase) that content.
Of course if that new content is not valuable to you -- and it won't be to everyone -- there's no need to buy it, and we'll support Logos 5 for some time. And, just for the record, we have delivered many improvements to Logos 5 at no cost. You can see the history here: https://wiki.logos.com/Logos_5_Release_Notes
Logos 6 -- like all our 'major' releases -- is essentially a lot of new 'products' wrapped up in a big library. We really do deliver updates for free -- and over the years, with the free engine updates which trail around three months behind the big new release -- we probably deliver more consistent free value than most purchased software packages. It's just the new 'products' (new content, new resources, etc.) that we charge far. Because we don't have another way to fund it!
Can't say that I am enamored with Logos' marketing strategy. Each version touts new cool features, which only are enabled by purchasing a $1,000 package. All features should work at all package levels. We should pay based on content desired, not a combination of content and features.
I understand Logos has a business to run, pay good developers good wages and make a little profit. I get that! I just don't appreciate the pricing structure.
If you have a base package, you might consider a small sidegrade.
I went from L5 Bronze/Ref Starter to L6 Reformed Starter for less than $40 (YMMV). For that I won't get but a small part of the new features, but I'll get the new interface before Feb. And unless you plan to apostasize and quit it altogether, nothing spent with these folks is wasted.
Is the Logos 6 core engine update free? When will the release date? 2/3/2015? Where did you find that information?
Thanks for your response.
Kelvin
Is the Logos 6 core engine update free?
Yes
When will the release date? 2/3/2015?
Where did you find that information?
See the first post in this thread: https://community.logos.com/forums/p/92878/644850.aspx
Calling some of the new features "datasets" is a good move, because that is precisely what they are: new content.
deal with Logos5 engine for the time being.
I still love Logos 5. Just because something new came out, doesn't make me feel like my Logos 5 is broken and not as good anymore. In fact, Logos 5 is better today than when I first got it because of minor updates that have arrived along the way.
You would be hard pressed to find another software package that can do even a portion of what Logos can do.
deal with Logos5 engine for the time being. I still love Logos 5. Just because something new came out, doesn't make me feel like my Logos 5 is broken and not as good anymore. In fact, Logos 5 is better today than when I first got it because of minor updates that have arrived along the way. You would be hard pressed to find another software package that can do even a portion of what Logos can do.
You're right, Logos 5 is a fine program. The additional features and improvements in L6 are a outstanding and I am glad to have them.
With L6 as with any other program one has to ask and answer some questions. What is new? Do I need it? Do I want it? Can I afford it? etc
I think we sometimes think we need to have the latest, greatest programs just because they exist.
If you'd like a free taste (although not the whole enchilada) of the L6 engine, you could test-drive Noet. Noet is based on 6, but lacks Bible-specific features (e.g. Bible search).
If interested, you can even try Noet without risking your current L4 or L5 installation. For example, I have Logos 4, Verbum 5, and Noet (based on 6), installed on the same machine. Here's a post from Bradley admitting that L5 + Noet is possible. He notes that it isn't an officially tested scenario; however, I haven't noticed any problems <except that this poor old machine was pretty slow when I tried running all three simultaneously : >
