Webel vs Mathematica: The Very Good, The Bad, and The Ugly

Webel IT Australia promotes the amazing Mathematica tool and the powerful Wolfram Language and offers professional Mathematica services for computational computing and data analysis. Our Mathematica tips, issue tracking, and wishlist is offered here most constructively to help improve the tool and language and support the Mathematica user community.
DISCLAIMER: Wolfram Research does not officially endorse analysis by Webel IT Australia.
Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
FEATURE
TIP
TOOL
Policy level
INFORMATIVE
Keywords
TIP: Mathematica: The IntelliJ IDEA Plugin for Mathematica is HEAPS better than the Eclipse-based Wolfram Workbench (at least for the Wolfram Language as used by Webel projects)!

Obviously, Mathematica is simple extraordinary for maths! This significance of this is not always appreciated by some IT Project Managers. As Dr Darren says:

Webel: The single biggest disease in the world of IT is the idea that somehow mathematics is bad, or not useful, or not efficient, and that getting people who don't like maths to make stuff up (badly) in coding languages (rather than using maths) is ok.
However, when it comes to using Mathematica as a replacement for less powerful coding languages on large scale projects, there are some considerations.

Pro: The good (and where Mathematica is good, it's very very good):

Mathematica: TIP: Try //Dataset on just about anything and be amazed! Click on nearly anything to navigate through nearly anything in impressively interactive human-readable format.
Webel: Mathematica is functional programming on steroids (and has nearly everything else, except for decent in-built OO support, although you can make some progress with Abstract Data Types and even some inheritance).
Mathematica: The awesome Quantity system for values with units is everything the SysMLv1.x Quantity/Unit system should have been (and hopefully SysMLv2 will be). But it comes at a high performance cost!

Con: The bad and the ugly:

Mathematica: Some links on Object-Orientation (or the lack thereof)
Webel: Mathematica: WISHLIST: Support for decent vendor-supported, built-in, fully fledged, IDE-friendly, object-orientation (OO)! [With or without the use of state, which is a choice, not obligatory, and OO doesn't throw functional away]
Webel: Mathematica: WISHLIST: Support for the same intelligent (active) formatting in .wl Package files as is available in Notebooks
Webel: Mathematica: WISHLIST: Support for EXTRACTABLE structured documentation for individual arguments of functions RIGHT IN/NEAR THE CODE. Yes it is needed, really it is. (And ::usage support for "methods" would be nice too.)
Mathematica: Wolfram Workbench: Basic variable name refactoring is not supported. (Or just use the IntelliJ IDEA Plugin for Mathematica, which does variable and function renaming well.)
And some useful resources:
Mathematica: TIPS for living with the user-contributed MTools for Object-Orientation (until a vendor-supported OO solution is eventually provided)
TIP: Mathematica: Webel's ultimate guide to using Abstract Data Types to create "pseudo classes" (strong types) with inheritance for the Wolfram Language, all modelled in SysML!
Visit also the main list of tips and issues tracking for Mathematica.
Relates to
A word on classes and object orientation for Mathematica
Representing the SysMLv1 Block and SysMLv2 Part Def in Mathematica requires classes and object orientation (OO)
SysMLv1 vs SysMLv2
Related notes
[ISSUE, LIMITATION, MODELLING, TOOL] Mathematica: Some links on Object-Orientation (or the lack thereof)
[ASSERTION, TIP] Mathematica: The awesome Quantity system for values with units is everything the SysMLv1.x Quantity/Unit system should have been (and hopefully SysMLv2 will be). But it comes at a high performance cost!
[FEATURE, TIP, TOOL]{INFORMATIVE} Mathematica: TIP: Try //Dataset on just about anything and be amazed! Click on nearly anything to navigate through nearly anything in impressively interactive human-readable format.
[TIP]{INFORMATIVE} Mathematica: TIPS for living with the user-contributed MTools for Object-Orientation (until a vendor-supported OO solution is eventually provided)
[ASSERTION, TIP] Webel: Mathematica is functional programming on steroids (and has nearly everything else, except for decent in-built OO support, although you can make some progress with Abstract Data Types and even some inheritance).
[TOOL, WISHLIST] Webel: Mathematica: WISHLIST: Support for decent vendor-supported, built-in, fully fledged, IDE-friendly, object-orientation (OO)! [With or without the use of state, which is a choice, not obligatory, and OO doesn't throw functional away]
[LIMITATION, TOOL, WISHLIST] Webel: Mathematica: WISHLIST: Support for EXTRACTABLE structured documentation for individual arguments of functions RIGHT IN/NEAR THE CODE. Yes it is needed, really it is. (And ::usage support for "methods" would be nice too.)
[ANTI-PATTERN, ASSERTION] Webel: The single biggest disease in the world of IT is the idea that somehow mathematics is bad, or not useful, or not efficient, and that getting people who don't like maths to make stuff up (badly) in coding languages (rather than using maths) is ok.
Related notes (backlinks)
Related snippets (extracts)
Visit also
Mathematica and Wolfram Language zone
Visit also (backlinks)
External links
Dataset