The case for a headless default command line LTSpice for Linux

Question

I mean, You already have a Mac version... most of the work is done 
 I'm imagining internal resistance would centered around percieved effort/expense in supporting the GUI 
 The Linux community hass you on that one. 
 Not to be rude but It isn't as thought the it was ever LTSpices magical GUI that was ever the thing attracting users anyway as far as I know. 
 Looking at these forums AD is incurring expenses and effort supporting various windows compatibility layers. 
 Pretty Pretty Pretty Pretty please???

MStokowski · Accepted Answer

Hi KevinNewton , 
 KevinNewton said: I mean, You already have a Mac version... most of the work is done 
 All I can say at this time is&hellip;stay tuned. 
 KevinNewton said: Not to be rude but It isn't as thought the it was ever LTSpices magical GUI that was ever the thing attracting users anyway as far as I know. 
 True, for some, the magic only lies in the simulator. Though, 1000s of EE professors might disagree. The schematic editor / waveform viewer / GUI is an easy-to-use tool for those who choose to use LTspice as both a simulator and communication tool . 
 One must remember there is a tail that wags the LTspice dog (including head). This tail is more important than the incredibly helpful hobbyists, professors, students, youtubers who use LTspice regularly. That tail is ADI's internal users. How do we continue to provide LTspice for free all of these years? The answer is: LTspice is an incredibly powerful design tool and technical sales tool. Our field sales can use LTspice to show customers how our products fit their applications. At the same time, the customers can see a schematic of the proposed solution. It's fast, it's powerful, it's visual. 
 That said, you are in luck, as some at ADI also want the headless Linux solution&hellip; 
 KevinNewton said: Looking at these forums AD is incurring expenses and effort supporting various windows compatibility layers. 
 No lie. This illness of which you speak was spread throughout the desktop software industry in the late 80s, early 90s by a certain OS purveyor. Widnoze 11 is just a longterm symptom that we must treat locally, as will be Winesnooze 12. As you well know as a Linux user, there is only treatment for the symptoms; no cure. 
 mike)

Popular Forums

Product Forums

Application Forums

Design Center Forums

Highlighted Webinar

Places

Libraries

Upcoming Learning & Events

Challenge Yourself!

What's Brewing

Places

Resources

Visit ContentZone

The Latest Read

New Release

Recent Technical Insights

Products Mentioned

Thread Details

The case for a headless default command line LTSpice for Linux

Thread Summary