Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation on 06/15/19 in all areas

  1. I've been mostly living under a rock for a number of months... I just came out and installed my brand new copy of 10.3.1 and quickly went to lunch while it installed. I came back and noticed the familiar Java update pending notice and started quickly clicking to get it updated before jumping into some dev work. I then noticed the Updated License Terms screen and the "This version of the Java Runtime is licensed only for your personal (non commercial) desktop and laptop use." disclaimer. Has this topic been beat to death yet? : ) Links please! Seriously though - for commercial Delphi android development, does Embarcadero cover our commercial license with whatever bundled license they have, or do we need to go direct to Oracle?
  2. Stefan Glienke

    JSON string value

    If you have documentation you cannot just yolo refactor code every release and break something...
  3. New version 13.4.0 released! * TMiTeC_SMBIOS detection fixed * TMiTeC_OperatingSystem VMWare/VirtualPC/VirtualBox session identification fixed * TProcMonThread handles enumeration fixed + TProcMonThread file handle file position evaluated in handles detection * TMiTeC_TCPIP adapter detection fixed For more information about the library, download locations and documentation, see the MiTeC System Information Component Suite Home Page
  4. Darian Miller

    JSON string value

    CORRECT. The "time for docu work" was BEFORE THE FEATURE WAS RELEASED.
  5. David Heffernan

    JSON string value

    I don't buy that argument. People are using the software now. And software is never finished. There is always more to be done. So if you wait until it is done, then you never document it. My personal experience, and very strongly felt, is that writing documentation is a key part of finalising and debugging specification. So many times have I experienced this. Only when you write the documentation do you realise some of the issues that users will face. Deal with them before releasing and you don't have to spend as much time in back compat hell. My view is that writing documentation in a timely fashion actually saves time and resources in the long run.
  6. Just get rid of the stupid process altogether. If someone's going to steal the software, they probably weren't going to pay for it in the first place.
  7. Bill Meyer

    JSON string value

    To remember when things were documented is to be old.
×