I'm getting an error when trying to run the builds for MacOS in the Files. Is this because I am running on a M2 Mac? Thanks.

Hi,

Thanks for picking up on this. The .dmg file uploaded here is meant for Intel hardware only I'm afraid. Sorry it didn't work for you, I'll make the files page more descriptive on this.

My current setup is a MacBook Pro using Intel i5 processor, that's all I have available to me to develop and test the product. It's not viable for me to go out and get M1/M2/M3 hardware that I would have to pay for and use infrequently (PSUD is all done for free so generates only cost - no income). This is going to be a growing dilemma as the Apple hardware base migrates to newer processors.

I'm having a think about what the options might be around this.

1. Open source PSUD 3 and later versions to allow a wide community to help with development and code testing
2. Phase out Mac versions of the product and support
3. Start some sort of charging model for the product to enable more hardware for development

Open to sensible suggestions...

Regards,
Duncan

开云体育

Sensible suggestions:

1. Depends on the team doing open source. A perfect example of things gone wrong is LibreOffice. It's been taken over by script kiddies that focus on glitter and break decades old functionality, rendering the product almost unusable by keyboarders. If you can manage the product development by assigning tasks to competent programmers, go for it.
2. Definitely a sensible option. I have friends who've used Mac's for 40 years and have a collection of old boxes to run applications obsoleted by non-support in later OS & platforms.
3. See Pareto. Nearly 80% of platforms are Windows. Given Apple's propensity to bust applications with OS releases, 80% of the work will be spent supporting 15% of the market. Speaking as a retired software developer and hardware engineer, I'd gladly contribute to $$ supporting PSUD.
   

- Ian

On 5/29/2024 3:04 AM, Duncan Munro via groups.io wrote:

I'm having a think about what the options might be around this.

You know that your TSC got re-written in JavaScript.



As such it runs in any 'good' web browser; just checked linuxMint.

An amazing effort. Of course a tone control is linear and an AC-DC power supply is at its core non-linear. Beyond that, I can't say how awful JavaScript is as a calculating language. And prime author jatalahd seems to be busy with other projects.

You know that your TSC got re-written in JavaScript.

Hi Paul,

Yes, I saw the Javascript version - it's really good. In fact it was so good and worked on any system with a browser, so it did not make sense for me to continue developing the Windows version of TSC.

Regards,
Duncan

I'm not a software guy, but if anyone knows where the resources are to work through this installation issue, I'd take a stab at it.? LOL, it'd be a real shot in the dark so to speak.

Hi Chris, I did write a reply to you on May 9th over Mac security constraints and the fix - did you get to see it?

/g/duncanampspsud/message/286

Regards,
Duncan

Thanks for the info Ian.

1. Depends on the team doing open source. A perfect example of things gone wrong is LibreOffice. It's been taken over by script kiddies that focus on glitter and break decades old functionality, rendering the product almost unusable by keyboarders. If you can manage the product development by assigning tasks to competent programmers, go for it.

Any open source as a group thing needs to be run from a development plan with agreed tasks and controlled updates. If people want a free for all, they can fork the software and do as they wish - it shouldn't be allowed to impact the core product.

Regards,
Duncan