New episode for the New Year and that title is almost entirely nonsensical because they are different subjects.
Fusion 360 is a CAD / CAM application with finite element analysis capabilities. I was going through the Autodesk forums and read a lot of chatter about their position on the Linux client. It appears that for several years, there have been requests but there is no plan to support it.
One user gave a fantastic well thought out, logical reason for building Fusion 360 to work in Linux and he gave the typical reasons for not doing so with answers:
- the management sees not enough customers here. It’s a question about cost/income ratio.
- I think if done right, there are not much costs (keyword continuous integration)
- Number of potential customers. Linux users need to raise there hand and write to Autodesk, so that they can see, there are potential customers. Linux leads already on the server market, and on embedded devices, smart phones and tablets (if you count Android as Linux).
- On the desktop, Windows is still the dominating system (88%), Mac (9%), Linux (2%). But this is for the average user, this doesn’t need to be true for engineers and makers using CAD software.
- I have no statistic here, but I personally have never seen engineers working on Mac.
But I have seen many engineers, software developers and scientists that work on Linux.
- Linux users are willing to Beta test and are able to generally figure things out for themselves.
There was a lot more that you can look at here:
There were a lot of hostile responses from Windows users that were just… hostile. I do think that is a large part of the untold story. There are those that point to Linux and talk of the technological elitism but I don’t think that is a behavior that exclusive to Linux users at all. I can refer to this post for evidence otherwise.
Even though Autodesk has stated that they have no plans to support Linux, it is always with the caveat that of “at this time.” I still have hope that Linux will be supported in the future. It’s inevitable as there are a larger percentage of Linux users in the engineering field, Autodesk does support Linux on the Maya application and since there are more and more professional tools on Linux, I truly believe it will follow.
It took me far too long to complete the write up and video but I must say that the tiling features in Plasma are pretty fantastic. I spent this past weekend doing a lot of administrative work for another job of mine and the tiling manipulation of windows and desktop navigation made the tasks far less painful than they have been historically. I have to emphasis once again that it is important to have key combinations that make sense that are easy to remember that can are quickly intuitive to you.
I made a little video about this with Kdenlive and put it on YouTube. I had a less than stellar comment about my production quality. For that, I can say, I’ll try better next time.
I did a post this last week on my use of Linux in the kitchen. I did appreciate a lot of the great feedback II received from this. I don’t want to understate, at all the value of technology in the kitchen. It is not at all a strange science experiment being shoe-horned into a role in which it doesn’t make sense. Linux and the array of tools make several kitchen tasks more efficiently completed.
For my case, the right hardware was an important part of the implementation as I have a very limited amount of counter space. There were already several software applications I had been using, I just happen to further expand how I had been using them.
How it recently made the Christmas season more efficient…
What would improve Linux in the Kitchen is going to take some real effort on my part. Most of these things will be aided by single board computers or IoT like devices. I need more metrics in order to improve my results when baking. Improved inventory management, improved meal planning. All but the last one will take some serious work and effort in order to implement.
BDLL Follow Up
Fedora 31 challenge. Lot of people were rough on it and in some ways I understand but in others I do not. I have used Fedora periodically and I have always found it to be an enjoyable experience. Fedora is a lot more like getting a Lego set with some instructions than it is a ready-made product. I look at Fedora as being a more industrial grade Linux system that you implement for a specific feature. While distributions from the Ubuntu flavors are more like products that are ready to be used that focus on the out-of-box experience. All the flavors of Linux have a place and a target audience. Everyone is entitled to their own opinions about a distribution experience but I think it is almost a bit unfair to evaluate Fedora in the same way you would evaluate an Ubuntu.
I have decided to use Fedora’s Plasma edition and I am going to give it a fair, but biased, review. My expectations are very focused. I don’t need the “last mile” type polish, nor do I expect that from a Fedora or an openSUSE for that matter. What I do expect is something very easy to work with and mold to my wishes.
openSUSE does a great Plasma. I don’t mean out-of-the-box perfect for my needs. No distribution should ever target me as the core user, that would be tremendously silly. I am an edge case and I am never satisfied, I am a moving target of requirements and expectations for what I want as my personal workspace. I would be a high maintenance target for a perfect out-of-box experience.
wiggle (1.1 -> 1.2) a program for applying patches that ‘patch’ cannot apply due to conflicting changes in the original. Wiggle will always apply all changes in the patch to the original. If it cannot find a way to cleanly apply a patch, it inserts it in the original in a manner similar to ‘merge’ and reports an unresolvable conflict.
bubblewrap (0.3.3 -> 0.4.0) The biggest feature in this release is the support for joining
existing user and pid namespaces. This doesn’t work in the setuid mode (at the moment). Other changes include Stores namespace info in status json, In setuid mode pid 1 is now marked dumpable also now build with musl libc.
gthumb (3.8.2 -> 3.8.3)
gnome-shell (3.34.2+0 -> 3.34.2+2): polkitAgent, Only set key focus to password entry after opening dialog. The keyboard now stops accessing deprecated actor property.
libnl3 (3.4 -> 3.5.0) * xfrmi: introduce XFRM interfaces support
xfrm: fix memory corruption (dangling pointer)
mypy (0.720 -> 0.750) More Precise Error Locations and the daemon is No Longer Experimental
python-Sphinx (2.2.2 -> 2.3.1)
python-Sphinx-test (2.2.2 -> 2.3.1)
python-jedi (0.15.1 -> 0.15.2)
python-parso (0.5.1 -> 0.5.2)
python-pybind11 (2.4.2 -> 2.4.3)
python-typeshed (0.0.1+git.1562136779.4af283e1 -> 0.0.1+git.20191227.21a9e696)
wireshark (3.0.7 -> 3.2.0) bug fixes and updated protocol support as listed
Firefox (70.0.1 > 71.0) Improvements to Lockwise, integrated password manager, More information about Enhanced Tracking Protection in action, Native MP3 decoding on Windows, Linux, and macOS, Configuration page (about:config) reimplemented in HTML, New kiosk mode functionality, which allows maximum screen space for customer-facing displays. Numerous CVEs were addressed relating to memory.
20191225 – Stable 99
20191227 – Stable 99
20191228 – Stable 99
20191229 – Stable 99
20191230 – Stable 99
The Computer Chronicles – Computer Music (1983)
I think we often take for granted the multimedia capabilities of computers today. It seems like someone is always harping about PulseAudio on Linux. I’d say they are likely not using the right distribution, by that I mean openSUSE, I don’t have these issues. The purpose of the section is not to tout the superiority of my favorite operating system when it comes to audio subsystem, rather, it is to talk and reflect about how great we have it today with all things audio on modern computers.
In 1983, the state of digital music was not as rich as it is today. We can enjoy a virtually endless supply of content never before available in human history. Let’s go back in time to an era when the Commodore 64 was the pinnacle in home computer audio. Where audio was entirely programmed, limited to 4 wave forms of sawtooth, triangle, pulse and noise. A multi-mode filter featuring low-pass, high-pass and band pass outputs and three volume controls of attack / decay / sustain / release (ASDR) for each audio oscillator and a few other things I barely understand. Regardless, the capabilities were limited and synthesizing voice was an incredible undertaking that took years of work long after the chip was in the wild. This was one of the first polyphonic sound chips on the consumer market that, to this day, is held in high regard and many still like the sounds this chip produces.
All this said, this was very interesting record of computer generated music that is certainly worth a listen. I find the experimentation and musical education tools used in this perod incredibly fascinating. Today, things are very different. Musical composers and artists use computers in music production and to do so otherwise would likely be considered insane. I now wonder if individuals in the 80s that pushed the art and science of computers in music were considered insane by their peers.