If the coding dept. was as determined as the marketing dept. issues with initial releases wouldn't exist....although trying out beta ware at slightly discounted prices can be entertaining...
Rene Atchley: If the coding dept. was as determined as the marketing dept. issues with initial releases wouldn't exist....although trying out beta ware at slightly discounted prices can be entertaining...
I think you just described software in general.
WIN 11 i7 9750H, RTX 2060, 16GB RAM, 1TB SSD | iPad Air 3Verbum 9 Ultimate
Denise: abondservant:I started with L2... I loved L2. L3 confused and aggravated me. I didn't use it more than a handful of times between the release of 3 and the release of 4. Oh my ... Libby is super-wound-up. "How could ANYONE say such a thing?!" But I was surprised MJ found Libby to be a pain (I think). I liked Libby because she showed under-the-hood goings-on. Indeed, using L7, it's still quicker to ask Libby (about connections). Granted, Libby's search prowess is embarrassing. Well, maybe a new layout will calm Libby down. Ha.
abondservant:I started with L2... I loved L2. L3 confused and aggravated me. I didn't use it more than a handful of times between the release of 3 and the release of 4.
Oh my ... Libby is super-wound-up. "How could ANYONE say such a thing?!" But I was surprised MJ found Libby to be a pain (I think). I liked Libby because she showed under-the-hood goings-on. Indeed, using L7, it's still quicker to ask Libby (about connections). Granted, Libby's search prowess is embarrassing.
Well, maybe a new layout will calm Libby down. Ha.
L2 lvl4 (...) WORDsearch, L9
I get what you're saying and understand your sentiment, but I would like to suggest an alternate way of looking at this:
If [the powers that allocate resources (IE: human, financial, project management resources) and control release timing (IE: the decision makers who decide that it's time to capture some return on those resource investments) for] the coding dept. was as determined as the marketing dept. issues with initial releases wouldn't exist might be less existent.
The programmers who are the boots on the ground for the L9 project are likely among the most "determined" employees FL has. They can only do so much with a wish list that is a mile long and existing software limitations, coupled with staffing limitations, overtime policies, etc. Yet no matter how much they do or how many features or enhancements are deployed, the old adage "You just can't please everyone" still applies. FL could spend MILLION$ more on the L9 project, and those who have a bent towards complaining and griping will still....well, complain and gripe the moment it is released!
So there comes a time when the decision must be made and the release must be launched, or eventually there will be a point at which there are simply no financial resources left with which to fund any further developments (and then we have another WordSearch scenario on our hands!). Releases, no matter how imperfect they may be, raise needed working capital that allows these determined programmers and project managers to add more oil to the machine, thus making things run smoother and smoother as time goes on.
Myke Harbuck Lead Pastor, www.ByronCity.Church Adjunct Professor, Georgia Military College
DIsciple II: Wow resorting to children’s rhymes now, just when I thought I’d seen it all on these forums from FL fan boys.
Wow resorting to children’s rhymes now, just when I thought I’d seen it all on these forums from FL fan boys.
Myke Harbuck: If [the powers that allocate resources (IE: human, financial, project management resources) and control release timing (IE: the decision makers who decide that it's time to capture some return on those resource investments) for] the coding dept. was as determined as the marketing dept. issues with initial releases wouldn't exist might be less existent. (...) So there comes a time when the decision must be made and the release must be launched, or eventually there will be a point at which there are simply no financial resources left with which to fund any further developments
(...)
So there comes a time when the decision must be made and the release must be launched, or eventually there will be a point at which there are simply no financial resources left with which to fund any further developments
Myke Harbuck: Rene Atchley: If the coding dept. was as determined as the marketing dept. issues with initial releases wouldn't exist....although trying out beta ware at slightly discounted prices can be entertaining... I get what you're saying and understand your sentiment, but I would like to suggest an alternate way of looking at this: If [the powers that allocate resources (IE: human, financial, project management resources) and control release timing (IE: the decision makers who decide that it's time to capture some return on those resource investments) for] the coding dept. was as determined as the marketing dept. issues with initial releases wouldn't exist might be less existent. The programmers who are the boots on the ground for the L9 project are likely among the most "determined" employees FL has. They can only do so much with a wish list that is a mile long and existing software limitations, coupled with staffing limitations, overtime policies, etc. Yet no matter how much they do or how many features or enhancements are deployed, the old adage "You just can't please everyone" still applies. FL could spend MILLION$ more on the L9 project, and those who have a bent towards complaining and griping will still....well, complain and gripe the moment it is released! So there comes a time when the decision must be made and the release must be launched, or eventually there will be a point at which there are simply no financial resources left with which to fund any further developments (and then we have another WordSearch scenario on our hands!). Releases, no matter how imperfect they may be, raise needed working capital that allows these determined programmers and project managers to add more oil to the machine, thus making things run smoother and smoother as time goes on.
On one hand I recognize that, in essence, software is never quite finished particularly after using various shades of Microsoft software. However, I remember almost endless discussion on these forums on how I am suppose to take into consideration this or that factor that limits FL to produce a product that matches the marketing enthusiasm to sell me more and more product. FL limitations, or excuses, don't interest me as a consumer just the prices and quality of product the company wants me to spend my money on.
Not from USA or Canada. nor a Germanic country though I do have some German heritage going back three generations mixed with some English going back two generations, some Irish three generations and my Father was born in Scotland and well Scots are never ones to back down. But me with those mix of cultures that I am aware of and possibly more I don’t know going further back where else could I be from but the Great Southern Land of Australia.
All software has a level of usability but Logos 8.0 failed in its first impression. The very first thing you saw, the very first impression you got of the software was a broken home page. If there is one thing a software development team should make sure they get right it’s the first impression a user gets when then encounter the software, particularly when what you changed was not broken to start with. If there is one aspect of Logos 8 I could change it would be the home page. it is awful in appearance on a large wide screen format with huge white margins and then then filled with what looks like collector cards you used to buy with bubblegum as a kid with pictures of cricketers or rugby league players or for those in the USA baseball or gridion players, or the ones you used to find in your cereal box. Give me back the Logos 7 home page any day.
But the big thing is that FL marked Logos 8 knowing the home page was not functional, the code was incomplete and that notes was not complete yet kept their mouth shut on these things and waited till users complained about all the bugs before admitting they knew the software was not ready. And this failing lays at the feet of the company leadership because they should have a handle on this and they should above all desire to ensure when a customer purchases software from them they are fully informed of what is not yet ready for market, what could not meet completion in the time frame allotted and what the overall plan is to complete those things - specific dates don’t have to be given. I sincerely believe the developers worked above and beyond with the resources and time and with good intention. it’s those setting the agenda for Logos 9 that need to not repeat the same mistakes made with Logos 8.
abondservant:Any way, one of his ten rules for business lined up with what you say here - better to release a product when expected, than as expected. He said they were all based on his own personal failures in business. I responded to him, but wouldn't it be better still to release the product as expected AND when expected? His response was "unquestionably, but in life you often don't have that luxury".
Exactly right. If we were ever judged on how well we communicate the greatest of messages so imperfectly, we might never preach at all. We would all be like Moses and say send someone else.
The mind of man is the mill of God, not to grind chaff, but wheat. Thomas Manton | Study hard, for the well is deep, and our brains are shallow. Richard Baxter
There is a huge difference between mis-communicating a message and choosing to withhold what you know to be true because it does not support the narrative you want to present.
mab: abondservant:Any way, one of his ten rules for business lined up with what you say here - better to release a product when expected, than as expected. He said they were all based on his own personal failures in business. I responded to him, but wouldn't it be better still to release the product as expected AND when expected? His response was "unquestionably, but in life you often don't have that luxury". Exactly right. If we were ever judged on how well we communicate the greatest of messages so imperfectly, we might never preach at all. We would all be like Moses and say send someone else.
DIsciple II: If I had wanted to stay on Logos 7 and get updates for that then your suggestion would not helper because as soon as I ran an update the software would have upgraded me to 8 rather than pick up the update for 7 because I am a connect subscriber.
Suggestion came from experience on a MacBook Air (with my Faithlife Connect subscription). Setting Update Channel to Manual effectively turns off program updating. Manual channel does not exist on Faithlife servers so an installed Logos/Verbum cannot find a newer software release (while having Use Internet set to Yes so could download new resources). Caveat: Manual software update has a crash risk because some new resources need software changes so trying to index/use new resource(s) with outdated software can cause sudden software disappearance.
FYI: MacBook Air was a shared family resource that was used by one person at a time with their own macOS user account & Faithlife account. Changing Update Channel to Manual in all installations allowed application bundles to be installed once, which could be used by different users. Prior to manually updating Logos OR Verbum application, personally verified that no family member had their installation running.
Keep Smiling
Logos Wiki Logos 9 Beta Free Support
Keep Smiling 4 Jesus :): Caveat: Manual software update has a crash risk because some new resources need software changes so trying to index/use new resource(s) with outdated software can cause sudden software disappearance.
Funny that because FL employee said above all new resources are backwards compatiable while the prior version is still being supported so are you refering to after support was withrdawn or while it was still being supported ?
I <think> KS4J is saying that there is a crash risk because when the user does manual updates, he/she may not be keeping up with those updates appropriately. When that happens, a mismatch may occur.
macOS, iOS & iPadOS | Logs | Install
DIsciple II: Keep Smiling 4 Jesus :): Caveat: Manual software update has a crash risk because some new resources need software changes so trying to index/use new resource(s) with outdated software can cause sudden software disappearance. Funny that because FL employee said above all new resources are backwards compatiable while the prior version is still being supported so are you refering to after support was withrdawn or while it was still being supported ?
Logos 7.19 SR-1 (released on 23 May 2019) included addition of some new resource types, which were not in Logos 7.19 stable release on 25 Oct 2018 so Manual Update that had initial Logos 7.19 installed or older release has crash risk for new resource types that need Logos 7.19 SR-1 (or newer than Logos 8.4 SR-1 that was released on 2 May 2019).
JT (alabama24): I <think> KS4J is saying that there is a crash risk because when the user does manual updates, he/she may not be keeping up with those updates appropriately. When that happens, a mismatch may occur.
Concur mismatch of older software release and new resource has crash risk (remembering some threads where software update was needed)
DIsciple II:Funny that because FL employee said above all new resources are backwards compatiable while the prior version is still being supported
I think this is the quote you're thinking of:
Adam Borries (Faithlife):A "Maintenance" version of Logos falls under the category of "supported," and will continue to get updates to use newly published books.
It's not that the resources are backwards compatible, but the prior version gets updates to support newly published books.
Keeping your Logos 8 software updated should allow it to recognize and support any newly published book that Logos 9 supports.
Thanks to FL for including Carta and a Hebrew audio bible in Logos 9!
PetahChristian: DIsciple II:Funny that because FL employee said above all new resources are backwards compatiable while the prior version is still being supported I think this is the quote you're thinking of: Adam Borries (Faithlife):A "Maintenance" version of Logos falls under the category of "supported," and will continue to get updates to use newly published books. It's not that the resources are backwards compatible, but the prior version gets updates to support newly published books. As long as you keep your Logos 8 software updated, it should be able to recognize and support any newly published book that Logos 9 supports.
As long as you keep your Logos 8 software updated, it should be able to recognize and support any newly published book that Logos 9 supports.
Your saying the same thing i said just with different wording but yes this is what I was refering to but all that said it moot because my experince was that as connect subscriber I was pushe onto 8 without a choice, the upload downloaded automatically, my notes were forced onto the new system automatically and even if that were not the case and I stayed on 7 the mobile app was converted over to the new note system and so I would have been in a position of two separate note systems on different platforms that didn't play together as FL says they do.... And more my point all along has been FL not being upfront with there narrative about what they were actually releasing in the 8.0 product because despite them knowing they were releasing a broken product that was not intially as funcitonal in some areas as it was in version 7. That is the real issue here and the issue I want avoided with Logos 9. Be truthful as you release Logos 9 about what is not ready. Inform the cusotmer exacty what they are getting not on what you plan to give them in 3 months time or 6 months time, what you are gving them now. It's pretty simple and a pretty reasonable expectation to have of a company that says its serving the church and christian community.
DIsciple II:all that said it moot because my experince was that as connect subscriber I was pushe onto 8 without a choice
As previously mentioned, you can change your update channel from "stable" to (a non-existent channel such as) "manual" to prevent any software updates at all.
If you pre-emptively do this before Logos 9 comes out, you will never automatically be updated to Logos 9.
That does not fix the bigger picture issue of FL and the narrative they tell versus the reality of what they deliver. If FL talk matched their actions I would have a lot less to say. Users should not have to juggke update channels manually. FL should simply be open and honest upfront about what they are actually delivering.
PetahChristian: DIsciple II:all that said it moot because my experince was that as connect subscriber I was pushe onto 8 without a choice As previously mentioned, you can change your update channel from "stable" to (a non-existent channel such as) "manual" to prevent any software updates at all. If you pre-emptively do this before Logos 9 comes out, you will never automatically be updated to Logos 9. The full command you would type in the command box is set update channel to manual To return to automatically getting software updates, use set update channel to stable
Well judging from today's announcement looks like I made the right choice and logos 9 will be released Monday.
josh monda: Well judging from today's announcement looks like I made the right choice and logos 9 will be released Monday.
I hope this is not only an announcement with a demo but a proper release. Can't wait any longer for Logos 9!