|
Don't get me wrong - I'm very much in favor of everybody switching to RDi - the tools have to make money if we are to see progress. But enabling SEU and not WDSC in my opinion was a poor choice. To enable WDSC to use the RDi syntax checker/verifier should have been a trivial task the two tools are fundamentally the same. Updating it for SEU was almost certainly a lot more more work.Love the sentiment, don't much care for the delivery. Here's why: do you think your complaints here will get WDSC updated? If so, then please start a grass roots campaign to get that done. Put your name on it, and get 'er done. Otherwise, you're simply playing to the negative side of the audience. IMO, your position in the community gives you a certain responsibility to do something positive. Now, that doesn't mean toe the line. An honest movement to get a change in WDSC is good, and I'd support you 100%. However, complaining here about the awful IBM job has done isn't constructive.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.