Thanks to Arnaud, Jeff, Jody and Kirk for their confirmation that, while it’s
important to plan for the 64-bit future, living in the 32-bit past continues to
make sense in specific cases.
This client has all Windows clients with a MacOS Server, which will be moving
to Windows soon, so we’re
Tom,
I think this is a germane and timely question. It correlates with the 'if
it isn't broke don't fix it' rule of thumb and is particularly relevant to
the 4D community because of the longevity of many of our projects. In your
case you have probably done all you can. There doesn't appear to be
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
There's really no compelling reason if you're still on v16. 32-bit works fine.
As Arnaud wrote things may be changing in the Fall with the next release of
macOS. My guess is that some kind of virtualization will be required to run
32-bit stuff at that point.
Also, the 64-bit version of 4D
> Le 23 mai 2019 à 07:35, Tom Benedict via 4D_Tech <4d_tech@lists.4d.com> a
> écrit :
>
> [...] Am I missing anything else if we stick to 32-bit 4D Remote?
If it's mac (?), your client will not be able to use a newly bought mac, next
os will not run 32b apps - Mojave was already supposed to…
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
6 matches
Mail list logo
