When can we stop making 32-bit plugins?

[aciddose]

In addition it's interesting to note that MacOS will be dropping 32-bit support partially within the next year, even running 32-bit code from the 64-bit versions.

Many Linux distributions have never and will never support running 32-bit applications on a 64-bit system due to complexities associated with dynamic linkage and libraries.

Windows is the only platform where they felt it was important enough to include a robust compatibility layer (SXS).

So if Microsoft drops 32-bit compatibility from Win10 soon (<5 years?) this problem will have solved itself.

[elassi]

...consumer surveillance...

While I'm aware that all these things are just a matter of coding (read: amount of time) the devs like to invest, it is still and always frightening...

But thank you for the insights. Or, let's say: transparency.

[SJ_Digriz]

So if Microsoft drops 32-bit compatibility from Win10 soon (<5 years?) this problem will have solved itself.

I still support BASIC and RGP code I wrote for data transformations in the 80s. supporting 32 bits goes FAR beyond the piddly universe of DAWs and VSTs.

But the answer to the question is ... you should quit when you don't sell enough 32 bit plugins to justify the time.

[aciddose]

Nothing stops people from supporting old, obsolete software running on old, obsolete systems.

The difference will be that there will be absolutely no reason to create new software for any platform other than 64-bit.

People still create software to run on the C64 or Amiga 500. You probably won't find any new commercial software being ported there.

[SJ_Digriz]

Nothing stops people from supporting old, obsolete software running on old, obsolete systems.

The difference will be that there will be absolutely no reason to create new software for any platform other than 64-bit.

Yeah, I added to my post .. forgot to put that part.

[aciddose]

...consumer surveillance...

While I'm aware that all these things are just a matter of coding (read: amount of time) the devs like to invest, it is still and always frightening...

But thank you for the insights. Or, let's say: transparency.

If anyone was unaware that records of who downloaded what or which pages were accessed are kept by 100% of online services, well, that's a shame for them.

Do you think running a system that relies on a black-list is a good idea? That's purely due to ignorance about exactly how much data is transmitted non-stop by nearly every program you run. The only way to put a stop to bad behavior is to prevent the possibility of it ever taking place. Merely being upset about it while bending over and preparing to take it from every Tom, Dick and Harry with such an inclination is a bit of a contradiction.

You posted your comment from your "smart" mobile phone, right? Or maybe it was a tablet? That's like painting a giant target on your head.

[elassi]

...consumer surveillance...

While I'm aware that all these things are just a matter of coding (read: amount of time) the devs like to invest, it is still and always frightening...

But thank you for the insights. Or, let's say: transparency.

If anyone was unaware that records of who downloaded what or which pages were accessed are kept by 100% of online services, well, that's a shame for them.

Do you think running a system that relies on a black-list is a good idea? That's purely due to ignorance about exactly how much data is transmitted non-stop by nearly every program you run. The only way to put a stop to bad behavior is to prevent the possibility of it ever taking place. Merely being upset about it while bending over and preparing to take it from every Tom, Dick and Harry with such an inclination is a bit of a contradiction.

I wasn't negative on the process (which is helpful, e.g. to fulfill the customer's demands), but the detail. Checking how many seconds have passed until someone clicks this or that link... well. There are several reasons for that. But I don't want to start this discussion right now.

[aciddose]

That information is simply recorded by default. It isn't hard to see "xxxxx_64bit" is downloaded at 14:51:40 followed by "xxxxx_32bit" at 14:51:44 when the two entries exist almost directly next to each other.

The number of in-between log entries depends upon exactly how busy the server is and while it's super common to be serving 10+ requests at once, for the most part small-time free plug-ins like Xhip aren't being downloaded 1000 times per second. More like 1 per minute at the highest.

[Teksonik]

You can stop making 32 bit plugins today. I don't use them for the same reason I don't use Atari 1040 ST software any longer. You move on or you get left behind.

I don't know how much time it takes to create and maintain 32 and 64 bit versions of a plugin but any time spent with 32 bit is time not spent moving forward.

Besides you want 32 bit only plugins ? There are a million Synth Edit gems to keep you busy....

[highkoo]

Oh, right;
64bit is better somehow, and nothing good was ever done in 32bit...

Its just a hassle that will eventually be forced upon me.
I will get nothing out of it, but trouble.

[elassi]

That information is simply recorded by default.

Yes, for sure it is.

But it wasn't simply recorded by "default" in former days.

As I said, the topic does not fit to this thread, though I'd love to discuss it with you (guess you're a good guy).

____
If I have to to add a dystopia to explain my thoughts: One can't enter a shop without being monitored by all means: electromagnetic spectrum-scanning, eye-ball tracking, smell-detection (What did you eat today? What's the perfume of your wife/girl-friend/lover), database queries of FB-friends, purchases of the whole family, bank accounts, where did you drive with your car today/last week/month, ... and so on.

[Teksonik]

Oh, right;
64bit is better somehow, and nothing good was ever done in 32bit...

Its just a hassle that will eventually be forced upon me.
I will get nothing out of it, but trouble.

No hassle here. I've been 32 bit clean for years now.

Of course 64 bit is no better unless you use large sample packs but to be honest there is not one 32 bit only plugin I really want or need. I'd rather any time spent developing a 32 bit version of a plugin be spent on developing new features and functions in the 64 bit version.

We're starting to see 64 bit only plugins pop up. Like I said move on or be left behind. Or you could buy an Atari 1040 ST.

[jancivil]

Up thru 2015 I took advantage of the fact VE Pro will run 32 and 64 at the same time behind my distaste for IKMM Custom Shop installations, and I had a couple of old things I don't have anymore and that wouldn't install today anyway. It's actually more hassle now to deal with the older AT2-era installations.

[aciddose]

That information is simply recorded by default.

Yes, for sure it is.

But it wasn't simply recorded by "default" in former days.

As I said, the topic does not fit to this thread, though I'd love to discuss it with you (guess you're a good guy).

____
If I have to to add a dystopia to explain my thoughts: One can't enter a shop without being monitored by all means: electromagnetic spectrum-scanning, eye-ball tracking, smell-detection (What did you eat today? What's the perfume of your wife/girl-friend/lover), database queries of FB-friends, purchases of the whole family, bank accounts, where did you drive with your car today/last week/month, ... and so on.

It has always been the default though. The shopkeep sits at the front of the shop to keep an eye on customers (or others, non-customers especially!) and watch what they get up to. If a customer is spending a lot of time in one section, then wanders off to the near-by section to grab one item before coming to the register: it makes sense to place impulse-buy items in between and maybe stretch out the sections a bit to have the customer wander around the store.

This is why for example blogs tend to place an article spread across 12 pages when it would easily have fit on one!

It has always been that way, since 1200 BC to 1852 to 1990 to 2007 to five minutes ago and forward and so on.

I agree it's a bit off-topic but it is partially on-topic too. Improving the way the web page are laid out and spreading different platforms into different downloads is one part of improving non-invasive tracking of customer/user behavior. Adding "server pings" to download resources inside installers or even applications and plug-ins are another slightly more invasive option that provides far more useful and highly accurate information.

[fisherKing]

"When can we stop making 32-bit plugins?"

tuesday, 630pm, precisely.

the real question should be, "when will we be using 128-bit plugins?" that's what keeps me up at night...