For a client that has a system that mostly meets their needs it is hard to convince them to move forward. The costs for your time, and new equipment will just seem unnecessary. It is like that 10 year old car that feels new, runs great. The difference is when that old car dies they can just buy a new one. At this point in computes, that is not the case.
Apple, and Microsoft have been warning of this impending crush for several years now. It takes years to get the whole industry to move forward from 32 bit to 64bit. That time is coming now though. In a year (and in some cases less) they are not supporting 32 bit OS. Customers will not be able to buy a 32 bit OS. As well, new hardware will not support running 32bit OS. That of course does not mean their current equipment or system will suddenly stop working. What will happen though is that a workstation will break down and they will need to buy a new one. It will not support 32 bit applications, but that is what their system is written in. Therefore without upgrading in a planned way, they will either need to move then, or do with less workstations. When the server dies, that is a whole lot different story. Suddenly they need to move yesterday, and to do it right it take times. It is for these reasons that all clients needs to move forward. My recommendation is that they move to 17.1 though. That way they have more 64 bit features, yet they can still get 32 bit remote applications. This is the cross over version with 4D. They can have their old hardware, but they can move to the new hardware when needed. Jody > On May 22, 2019, at 11:35 PM, Tom Benedict via 4D_Tech <[email protected]> > wrote: > > I’m trying make a recommendation to a client as to whether they should move > to 64-bit 4D Remote in v16.5 However, I’m not finding any compelling reasons. > But I know it’s a very big thing for 4D, so I’m wondering whether I’m missing > something? The documentation > (https://doc.4d.com/4Dv17/4D/17.1/Changing-from-32-bit-versions-to-64-bit-versions.300-4201298.en.html) > mentions: > > - The 64-bit architecture pushes back database cache limits. Improve your > database's performances simply by using a larger cache. <- this is only on > Server, right? And that’s been around since v12 on Windows and since v15.1 on > MacOS. > - Adopt powerful 64-bit features such as preemptive processes, animated form > objects, or new printing features. <- this is probably good, but I don’t > think this particular app can take advantage of these features > - Build your applications with 4D (Runtime) Volume Desktop 64-bit. <- not > applicable with this particular app > - Use final 64-bit versions of 4D Server on Windows and macOS. <- I don’t > understand this. What is a “final 64-bit version”? > - New Quick report editor, compatible with reports created using previous > versions. <- not applicable with this particular app > - New Label editor, compatible with label files created using previous > versions. <- not applicable with this particular app > - Create graphs using an Object type parameter with the GRAPH > <https://doc.4d.com/4Dv17/4D/17.1/GRAPH.301-4179545.en.html> command. <- not > applicable with this particular app > > According to the blog.4d.com <http://blog.4d.com/>, 4D v17R5 is 64bit only, > so that means v18 will be 64bit only. That will ultimately be the compelling > reason to move to 64-bit, but in the meantime I can’t see any reason to make > the move, especially since it would require moving to 4DWritePro, which > appears to be a massive undertaking. Am I missing anything else if we stick > to 32-bit 4D Remote? > > Thanks, > > Tom Benedict > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
