Re: Visual Cafe nixes Jworks?

Eric McDermid wrote: > > While the various language flavors of INFORMIX-Data Director do share a > common architecture, they will not necessarily share common > implementation. We would rather take on a little extra work and > provide a solution which takes advantage of the strengths of each > language/environment than provide a "lowest common denominator" > solution. (For example, while Java programs could probably make > use of the COM components in INFORMIX-Data Director for Visual > Basic, this probably wouldn't satisfy customers who need a > "pure" Java solution). > This is good to hear. It would be good to see Informix come out with a Java tool that is as much a success as 4GL. Stay away from the crap, and stick to building products that are professional, complete, and AHEAD of the pack. Observe other companies and follow the successful ones. > Within a language space, we expect that INFORMIX-Data Director > will be useable by any development language. However, some > environments may have tighter integration with INFORMIX-Data > Director than others -- Symantec's Visual Cafe is one > example of an environment that will have a higher level of > integration. > Wow, Informix actually decided to join the Java party. I've been in shock ever since they announced it. > FYI, the "Data Director" product line does not spell the end of > INFORMIX-NewEra. INFORMIX-NewEra will include the equivalent > features, but since we own the language we don't need to package > a separate add-in. > Why bother with NewEra. It's a dog. A pooch. Bow wow. arf arf. And if you announce a Java Toolkit, you might actually want to <deliver> it sometime soon after you announce it, unless Informix is now the Vaporware company. Take some common sense advice: DUMP NEW ERA. TOSS IT IN THE BAG, TWIST THE TOP CLOSED, AND HEAVE IT OUT WITH THE REST OF THE TRASH. SEND A REFUND TO ALL THE COMPANIES WHO PAID FOR IT. Take the developers being wasted on NewEra, and reassign them to working on a front-end management interface for OnLine Dynamic Server. Have them modify the config and the engine so it can be tuned DYNAMICALLY instead of having to bounce the engine every time you make a change to the ONCONFIG. Have them fix OnPerf so it can take more metrics or be more flexible. Have them fix all the other things that should be fixed with the engine instead of playing with New Era. Have them work on new onstat commands so that the onstat command doesn't have 20,000 options. Have them set up the rootdbs as a secure dbspace, writable only by the informix id, and have them improve the install. ( You probably thank god that I'm not at Informix development--I'd clean house. ) Have them fix sysmasters so that if it is indeed visible to end-users it won't crash the engine if a query is made to it. Or don't make sysmasters available to end-users if end-users can crash the engine doing queries against it. > Our aim is to ensure that developers can seamlessly access > INFORMIX-Universal Server in whatever language and whatever tools > they prefer to use. > Provided they actually get their hands on the product. > ObDisclaimer: I work for Informix, but I'm not an official > spokesperson (I'm in R&D, not marketing). While I'm relatively > sure that I've accurately described Informix's position, my > statements should be construed as only my opinion, and do > not necessarily reflect the views of Informix Software Inc. or > any of it's subsidiaries, relatives, dogs, pet rocks, etc. > > -- Eric McDermid Doubtful you'll post again... :-) -- Tim Schaefer \\\\|// tschaefe@mindspring.com (6 6) ------------------------oOOo---( )---o00o---------