Reply to thread

Message

<blockquote data-quote="Oofta" data-source="post: 8365329" data-attributes="member: 6801845">The other aspect of this is simple cost benefit analysis.&nbsp; How many people are using the options?&nbsp; I have no clue, but I assume only a small percentage of their user base cares enough about UA to actually use the options.&nbsp; There comes a point of diminishing returns, especially for &quot;what-if&quot; development that inevitably will be thrown away.As far as &quot;they should have just made a perfect system&quot;, well obviously.&nbsp; Unfortunately it's software that was developed by humans who aren't perfect and software development is not simple.&nbsp; It's not &quot;just a database&quot; with a front end.&nbsp; You could describe some of the most complex systems out there that way, it's meaningless.All I know is that it works infinitely better than the first attempt that completely crashed and burned before it ever got out of beta stage.&nbsp; I'm not part of the dev team.&nbsp; I have no idea how well the back end is written.&nbsp; But I also don't know how many people took advantage of the UA material and, unless you actually work on the application neither do you.&nbsp; Nor does anyone know the amount of work that goes into maintaining or adding new features.It doesn't affect me because, like the majority of people, I don't care that much about UA stuff.&nbsp; For a one-off test I can just write something up with pencil and paper. Whether or not they &quot;should&quot; continue to support it, it's a business decision and we don't know all the factors that led to this decision.But I'm sure that won't stop the people that think software development is &quot;simple&quot;.&nbsp; <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f644.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":rolleyes:" title="Roll eyes&nbsp; &nbsp; :rolleyes:"&nbsp; data-smilie="11"data-shortname=":rolleyes:" /></blockquote>

[QUOTE="Oofta, post: 8365329, member: 6801845"] The other aspect of this is simple cost benefit analysis. How many people are using the options? I have no clue, but I assume only a small percentage of their user base cares enough about UA to actually use the options. There comes a point of diminishing returns, especially for "what-if" development that inevitably will be thrown away. As far as "they should have just made a perfect system", well obviously. Unfortunately it's software that was developed by humans who aren't perfect and software development is not simple. It's not "just a database" with a front end. You could describe some of the most complex systems out there that way, it's meaningless. All I know is that it works infinitely better than the first attempt that completely crashed and burned before it ever got out of beta stage. I'm not part of the dev team. I have no idea how well the back end is written. But I also don't know how many people took advantage of the UA material and, unless you actually work on the application neither do you. Nor does anyone know the amount of work that goes into maintaining or adding new features. It doesn't affect me because, like the majority of people, I don't care that much about UA stuff. For a one-off test I can just write something up with pencil and paper. Whether or not they "should" continue to support it, it's a business decision and we don't know all the factors that led to this decision. But I'm sure that won't stop the people that think software development is "simple". :rolleyes: [/QUOTE]

Verification