Part 1: Reasons and options to use the wolfram kernel Part 2 : Pros and cons of multiple options for a notebook interface.

Part 1 : Reasons and options to use the wolfram kernel. Options to code in the Wolfram kernel within a notebook interface or for package/script development. As far I know, there are no noteworthy limitations. To avoid misunderstandings, it's good to note that with the free Wolfram Engine you do get the full computational functionality. In the past there were other limitations too, which may have been addressed since then, such as the lack of interruption support (which is very important for any sort of interactive work), the lack of auto-completion, or the lack of built-in documentation with immediately runnable examples. Many convenience features will be lacking: Images won't be resizable, 3D graphics won't be rotatable, you won't be able to paste an image into an input cell, read off histogram bar heights from a tooltip, pick coordinates from a plot, etc.See here of how someone was unable to read the result of an integral. These are not only not copyable, but also not expandable or fully readable. In recent versions, non-trivial expressions are shown as 'summary boxes' with a button to expand them and reveal more information.Save outputs with the notebook in a structured and reusable format.You can switch to using OutputForm, like in command line mode, or even InputForm, but that reduces the readability of many outputs and makes it difficult to work with graphics. With Jupyter, most output shows up as a static image. Copy an output, or part of an output, and evaluate it or re-use it as part of another input.Just a few examples of things you wouldn't be able to do: But these two features are so deeply integrated into Mathematica that the usability of the system suffers greatly if they are not available. Similarly, you may think that you can live without creating Dynamic user interfaces. You may think that you would only want to type plain-text code, and you don't need 2D input. any kind of non-plaintext input such as mathematical notation or graphics. It's been a while ago since last time I tried Jupyter with Mathematica, and things may have improved since then, so I will only focus on limitations that I believe cannot be addressed. While using Jupyter is much better than using the 'naked' Mathematica kernel from the command line, and may be suitable for occasional use, it is not nearly comparable to using the full Mathematica notebook interface. The quality and usability of Jupyter with Mathematica is nowhere near that of the native notebook interface.

Wolfram mathematica notebook