MATLAB

Comentarios: I started with matlab from my undergrad days and still use it on daily basis for simulations and numerical analysis in my research work. Many industries (like the cellular network industry) heavily rely on Matlab for system level simulations. In my opinion, translating a pseudo code of any given algorithm to a working program is very easy in Matlab.

Puntos a favor: Matlab is an essential scientific computing environment. It is a must have for all students studying science and engineering. The pros are--
1. Easy manipulation of matrices. This is actually the main power of matlab.
2. Very intuitive way of writing program with no hassle of bookkeeping about data types, memory management, variable declarations etc which are essential for other programming languages.
3. Debugging tool is very easy to use.
4. One best feature is the GUI window for managing figures. A user can switch between the gui and the underlying code for generating any figures. This unique feature is absent in many of the advanced programming languages (like python or R, at least in the basic setup!)

Contras: The main problem is that it is not free. While the other open source languages have caught up Matlab in terms of ease of usage and availability of packages, Matlab is suffering due to its proprietary nature. A standard distribution of Matlab comes with a set of packages. For the other packages, one has to pay Mathworks for getting access. On the other hand, in Python or R, there are multiple packages available online and everything is free to use. After the recent boom in AI and machine learning, almost everyone has shifted to python to use the popular open source libraries released by several sources. Matlab being a proprietary software is failing to catch up to this fast evolving open source world!

Comentarios: I would state I've been utilizing MATLAB reliably for around 3 years, since my first year in doctoral level college. In undergrad, I may have utilized it a couple of times for a homework set. I say "I may have" in light of the fact that I don't exactly recollect that anything about it aside from that I had an establishment circle. My involvement in programming before MATLAB was some BASIC from youth and a smidgen of Pascal from a few courses in undergrad. My alumni counsel was an overwhelming MATLAB client, and my underlying knowledge with it included disentangling his MATLAB code for doing a few plots. In the meantime, I was taking a controls course which expected me to learn Simulink.

Puntos a favor: I esteem MATLAB. It is so smart and easy to make programming to do what you require. It has amazing exploring and profiling devices. It is cross stage, making code easy to share (expecting alternate people have forked out for the not by any stretch of the imagination unobtrusive allow). It has interfaces to other programming. In any case, there are a couple of things about it that chafe me. I'd get a kick out of the opportunity to get warning from different people what things aggravate them about MATLAB.

Contras: Supplanting subsref and subsasgn in a class is greatly awkward. The issue is this. Expect you override subsref with the true objective to change lead of obj(...). By then your subsref is moreover required the dialect structure obj.propname. With the objective for it to manage this viably (i.e. carry on the proportional as the intrinsic subsref) it needs to reimplement all of the checks for access confirmations that are normally done by the system. For precisely how precarious this is, see our rep's answer for my request here. Beside this genuine inconvenience, it's furthermore inefficient for each subsref to need to switch on the requesting type ('.', '()', or '{}') on each call, and for the system to need to collect a struct that joins the requesting type and furthermore the rundowns. To the degree I can see, it would be so much better if the various requesting accentuations called three unmistakable procedures.