Wa_english_title: "Intel® Fortran Compiler", Wa_subject: "emtsubject:itinformationtechnology/aiartificialintelligence,emtsubject:itinformationtechnology/clientcomputing,emtsubject:itinformationtechnology/cloudcomputing", Wa_emtsubject: "emtsubject:itinformationtechnology/aiartificialintelligence,emtsubject:itinformationtechnology/cloudcomputing,emtsubject:itinformationtechnology/clientcomputing", Wa_emtoperatingsystem: "emtoperatingsystem:linux,emtoperatingsystem:microsoftwindows", Wa_curated: "curated:donotuseinexternalfilters/producthomepage", Wa_emttechnology: "emttechnology:inteltechnologies/oneapi", Wa_rsoftware: "rsoftware:componentsproducts/intelfortrancompiler,rsoftware:developmenttools/compilers", Wa_emtcontenttype: "emtcontenttype:softwareordriver/softwarerepository/softwareoverviews", You can still buy IMSL that works with Intel Fortran, just not from Intel.Wa_emtprogramminglanguage: "emtprogramminglanguage:fortran", Maybe there was some legal issue that prompted this, but I didn't like it. What I didn't understand, though, was that things would immediately be made harder for customers who had previously purchased IMSL licenses from Intel, in that all of the downloads and KB articles disappeared. So when the contract came up for renewal, both sides agreed to call it quits. (I was doing most of that support!) I would repeatedly get asked if it was worth it for us to renew the contract, and as time went on it was harder for me to say yes. RW didn't like the different licensing terms (no run-time license checks and unlimited deployment) and the lower cost. The Intel business people weren't too thrilled with it either, as sales were low but support costs high. The change happened after I retired, but I know that when Rogue Wave purchased Visual Numerics, RW seemed less interested in this inherited bundling agreement which dates back to the Microsoft PowerStation days. This is not an accurate way to describe it.
0 kommentar(er)
