|
|
|
I believe I can pretty much guarantee that the next release of SQL Anywhere will not be called "SQL Anywhere 13". However, I am not aware of any decisions regarding naming at this time. You'll just have to be patient. What's the reason behind that - does "13" imply too much notion of "bad luck" in some cultures (as does "14" in others)? If so, well, to me a number is just a number... Besides that, we will be glad if the product name itself will remain the same:)
(24 Jun '11, 17:10)
Volker Barth
Replies hidden
1
Bad luck is why ASE went from version 12 to 15. Of course the name won't be SQL Anywhere 13 or 14. I'm betting on SQL Anywhere 15 because that's the
(25 Jun '11, 11:14)
Breck Carter
1
Are engineers less worried about the symbolic meaning of numbers? - I remember AutoCAD (not a niche product) having versions 13 and 14...
(26 Jun '11, 05:43)
Volker Barth
2
I bet nobody said of any buildings that fell down "oh no! We should have waited for AutoCAD 15! It's okay, engineer-who-designed-the-building, the project was doomed from the outset." On the other hand, if you run into somebody who is superstitious, it might make it harder to sell them something with a 13 (or 14, depending on the culture) in it. If a number is just a number, perhaps a UUID would be the best way to label the product. Maybe you want some uniform ordering, though.
(27 Jun '11, 10:23)
Phil Mitchell
So you say SQL Anywhere might be made responsible for damaged buildings...? As to the UUID: Please don't - then I prefer gaps in my default autoincrement:)
(27 Jun '11, 10:41)
Volker Barth
SQL Anywhere 0x4b67abbe3c9246f883db0ab2d2b78f8b
(27 Jun '11, 13:03)
Breck Carter
4
A famous person once pointed out that version numbers are a marketing decision. Marketing decisions involve politics. Don't try to apply reason and logic to politics. Such an endeavour rarely ends well. http://iablog.sybase.com/kleisath/index.php/2008/06/do-you-ski-our-code-names-do/
(29 Jun '11, 10:11)
Phil Mitchell
1
Oh...so now I'm a "famous person", when you reference my blog. :-) It remains true. The version number is a marketing decision. And you are absolutely right. There are many political considerations. My own personal bet (remember that I am in engineering) is that the number will be 16.
(29 Jun '11, 13:35)
Chris Kleisath
Better the hill, more fast and fun it is going down!
(29 Jun '11, 13:56)
PhilippeBert...
So you say even marketing is aware of hexadecimal notation:)
(30 Jun '11, 03:42)
Volker Barth
1
By "famous person" I was referring to the host of Family Feud. ;-)
(30 Jun '11, 09:52)
Phil Mitchell
If the sample code from that new 12.0.1 feature (related to .NET 4.5) is somewhat telling, than v16 seems reasonable:)
(I just came noticed this reading the fresh 12.0.1.3767 EBF readme...)
(20 Aug '12, 03:50)
Volker Barth
|
|
Maybe like Powerbuilder they are jumping from 12 to 15. 1
Jump they shall, but not to 15... that number has been used by ASE for the past several years... maybe 15 is good enough for PowerBuilder but not SQL Anywhere :) Volker has seen the Future!
(20 Aug '12, 12:12)
Breck Carter
|
