Lazy developers exposed by Apple M1 transition (lack of native updates)

[CrystalWizard]

OP you seem to have no idea what you're posting about. Please change the seriously lame thread title.

No I’m not changing the thread title because it’s my honest opinion. You may disagree but that’s also just your opinion.

Are you suggesting 100% of all plugin developers are never lazy and all of the plugin developers are working very hard to deliver updates as fast as possible to users?

I've interacted with many developers (and engineers). My experience has been that it's a very rare. Usually quite the opposite, they will work until they drop. I attribute this partially to the interest most of them have in their work. Long hours ( i don't know a single dev that works a mere 40hrs/week and ok but generally not stellar pay. Now manglement and bean counters are another story. They seem to care about one thing and one thing only: money. So if you're wondering why the one or two person operation is keeping up with the changes and the bigger operations are dragging their feet it goes something like this: manager/ c suite creep- "Hurry up and get me that new shiny, shiny, it needs to be released next thursday and never mind if it works and never mind our older products and whether there are bugs, needs of upgrades, etc. We've got money to make." And the new shiny, shiny is where the money is, not updating, fixing bugs, listening to user requests. That's what i'm suggesting.

[cryophonik]

OP you seem to have no idea what you're posting about. Please change the seriously lame thread title.

No I’m not changing the thread title because it’s my honest opinion. You may disagree but that’s also just your opinion.

Are you suggesting 100% of all plugin developers are never lazy and all of the plugin developers are working very hard to deliver updates as fast as possible to users?

No, you’re just changing the goal posts instead. You’re the one who called out specific developers with nothing to substantiate your claim that they’re being “lazy”, and now you’re trying to turn the tables with that straw man logic? Nice try.

BTW, I am a scientist.

[SoftSynthLover99]

So 100% of all plugins developers are never lazy in your opinion?

This thread is called "Lazy developers exposed by Apple M1 transition". Which means that you call every developer lazy who didn't update his plugin to M1 native already.

Notice the difference to asking if I don't think that plugin developers can be lazy sometimes?

Apart from that, it's really not you who sets the standard in regard of what can be called lazy or not. So every plugin developer who didn't yet update his 20 year old plugin, which you love to use, to M1 yet is lazy for you? That really doesn't make any sense. Apropos sense. A bit more common sense, please.

I asked a very specific question to crystal wizard and you answered “yep”. Which indicates you don’t think developers can be lazy. Which is obviously foolish to believe.

And no I’m not talking about “20 year old plugins” that are irrelevant, I’m talking about current releases like t-Racks 5 MAX, Amplitube 5, Guitar Rig 6 Pro, iZotope Music Production Suite etc. Some of these plugins are fairly new and some of the T-Racks 5 plugins will instantly crash your DAW if you open it (like FAME studio reverb by IK Multimedia which is a NEW release).

And some of the plugins that are moving slowly are ironically SUBSCRIPTION based! Which means you will have to renew your subscription to use the M1 versions. The point of Subscriptions vs Perpetual was faster updates, more plugin releases and faster support. However this has not been the case for iZotope, Slate or Plugin Alliance. That can be considered taking advantage of users and trying to milk subscription time from them while you move slowly to update.

[SoftSynthLover99]

OP you seem to have no idea what you're posting about. Please change the seriously lame thread title.

No I’m not changing the thread title because it’s my honest opinion. You may disagree but that’s also just your opinion.

Are you suggesting 100% of all plugin developers are never lazy and all of the plugin developers are working very hard to deliver updates as fast as possible to users?

No, you’re just changing the goal posts instead. You’re the one who called out specific developers with nothing to substantiate your claim that they’re being “lazy”, and now you’re trying to turn the tables with that straw man logic? Nice try.

BTW, I am a scientist.

As a scientist you should know 1 of 2 things must be true then. Either A) No plugin developers are ever lazy and are always hard working. Or B) Some plugin developers are indeed lazy and moving slow with updates.

This is very simple logic and nothing to do with a straw man argument. You can’t have it both ways

I’m no scientist but I am science literate

[kidslow]

OP is being overly dramatic to stir up debate. Most developers are not lazy. Probably quite the opposite, where they take on more than they can handle and find themselves scattered asunder. Here is one place I am going to agree about the laziness of SOME developers: Release Notes. Why are they made so difficult to track down so often?

It is interesting the strong correlation between developers who have either implemented native ARM or made public their plans for how their products will support it going forward and those who make it easy to see & find their release notes. My expectation is that Release Notes would be available in whatever mechanism is used for downloading a new release. I made a feature request to Izotope to make the RNs available in the Product Portal and who knows if they will. It seems easy enough for them to implement. Why are they not already available there? They're doing something wrong if I have to go to Google to search for their release notes or email support.

I'm OK taking them by email even to notify me you have an update, and here's what's been updated. More than acceptable. Not making the release notes for any update available at all or difficult to find for the end user is almost definitely laziness. What else would you call it ...

[chk071]

OP is being overly dramatic to stir up debate. Most developers are not lazy. Probably quite the opposite, where they take on more than they can handle and find themselves scattered asunder. Here is one place I am going to agree about the laziness of SOME developers: Release Notes. Why are they made so difficult to track down so often?

I'm pretty sure that, like the most of us, developers are very different in the way they work. Some comment every line of code, some don't, some document changes, some don't, and so on.

I agree though. Release notes are very important. At least for those who read them.

[donkey tugger]

OP you seem to have no idea what you're posting about. Please change the seriously lame thread title.

No I’m not changing the thread title because it’s my honest opinion. You may disagree but that’s also just your opinion.

Are you suggesting 100% of all plugin developers are never lazy and all of the plugin developers are working very hard to deliver updates as fast as possible to users?

No, you’re just changing the goal posts instead. You’re the one who called out specific developers with nothing to substantiate your claim that they’re being “lazy”, and now you’re trying to turn the tables with that straw man logic? Nice try.

BTW, I am a scientist.

As a scientist you should know 1 of 2 things must be true then. Either A) No plugin developers are ever lazy and are always hard working. Or B) Some plugin developers are indeed lazy and moving slow with updates.

This is very simple logic and nothing to do with a straw man argument. You can’t have it both ways

I’m no scientist but I am science literate

https://en.wikipedia.org/wiki/False_dilemma

No cigar. You've excluded the possibility that delays are due to other factors.

[cryophonik]

You completely missed the point, genius, and you have no scientific literacy. You identified developers by name, but have absolutely no evidence on which to make a case, so your argument has no merit. When others countered your claim, you changed your argument such that it relies on others claiming that no developers are lazy. That’s as simple as it gets and it’s not about science. Think you can figure out the rest from there? Yeah, I doubt it, too.

[SoftSynthLover99]

You completely missed the point, genius, and you have no scientific literacy. You identified developers by name, but have absolutely no evidence on which to make a case, so your argument has no merit. When others countered your claim, you changed your argument such that it relies on others claiming that no developers are lazy. That’s as simple as it gets and it’s not about science. Think you can figure out the rest from there? Yeah, I doubt it, too.

The “evidence” is that while many developers have updated to M1 recently (and some long ago) some developers haven’t. My “hypothesis” is that I believe some developers are being lazy. I have yet to hear a reasonable argument against this. “Your post is lame you should change the title” is not a counter argument, smart guy.

[cryophonik]

Congrats. You just earned your PhD in stupidity.

H1: something happened, therefore lazy

Apple fell on Newton’s noggin, must be because the tree was too lazy to keep holding it. F’ing lazy trees.

[FapFilter]

most of the “lazy“ programmers are actually updating their programs pretty frequently.
It's just that your requested feature is probably not as easy to achieve with some types / ages of code as you might like it

[chk071]

Many developers haven't released a VST3 version of their plugins yet. Lazy bastards.

[cryophonik]

Many developers haven't released a VST3 version of their plugins yet. Lazy bastards.

Yes, that can be the only reason. Quick, everybody Google the scientific method!

[SoftSynthLover99]

Congrats. You just earned your PhD in stupidity.

Exactly as I said, personal attacks are not counter arguments. What kind of Science degree do you have? Where I went to college you actually had to make an argument to disprove someones claim. Name calling is an ignorant persons last line of defense when they have nothing more to say.

[kidslow]

I agree though. Release notes are very important. At least for those who read them.

Maybe I'm old school. How else does one know whether there are fixes in the release that make an upgrade worthwhile?

Generally when I evaluate an app on any platform pre-purchase, free or paid, the first place I go will be the release history cadence and notes. Sometimes I am more forgiving of this than perhaps I should be. Lack of consistent recent release cadence and difficult/impossible to find release notes are a big red flag on the developer. Granted some products need less releases than others, and some are more complicated to update and will take longer (e.g. Uhbik)