> web. But I couldn’t face rewriting PerfectTablePlan from scratch for the web. Someone will develop for the web. But perhaps you don't want to make it easier

> web. But I couldn’t face rewriting PerfectTablePlan from scratch for the web. Someone will develop for the web. But perhaps you don't want to make it easier to clone. Building a business to sell for your retirement funds would need much more work and would get more money if SaaS for Planners? Unless you sell your engine to a wedding planner software specialist. The browser as a platform is daunting (touch support, small screen support, CSS, HTML, DOM, connections, browser versions, frameworks). > Javascript. Ugh. I personally never found JavaScript to be the problem - I think a single developer can good engineering workarounds. Avoid the bad parts. I developed for the browser using JavaScript: without using frameworks because my engineering was better than what was available. I personally would still avoid a frameworks unless I needed accessibility (which is crazy hard to support). > Also PerfectTablePlan is quite compute intensive, using a genetic algorithm to generate an automated seating plan and I felt it was better running this on the customer’s local computers than my server. And some of my customers consider their seating plans to be confidential Sounds like a price point: standalone should be more expensive. However likely difficult to hit that enterprise sale point (re patio11?)? Ideally you want to charge expensive wedding planners much more. Low end planners could still use your web version. I assume you've had competitors that have sunk because you are best value for money? Loved the writeup. I'm guessing I've written a bunch of ignorant stuff - I'm just practicing my thinking by writing... Most important, I presume you're looking forward to finishing up and not doing more work. I was.