The first universities were founded to educate priests, lawyers, and physicians. This can be seen in the way that universities standardized on 4 faculties: theology, law, medicine, and arts. What you are thinking of is the Humboldtian model of higher education which is a set of ideas that emerged in the 19th century and made research a central part of university's mission.
I still agree with you though in that it is not necessarily the universities responsibility to cultivate founders.
They're not really targeted at artists but for writing and taking notes. In my opinion, they have a nice smooth feel and work well for this purpose. But they're on the expensive side, so if you don't care about the looks, there are many other—wallet-friendly—options out there!
The eraser is infamous for being terrible. But it looks cool.
> So it appears the primary reason BioJulia code is slower than Seq code in these three benchmarks is that BioSequences.jl is doing important work for you that Seq is not doing. As scientists, we hope you value tools that spend the time and effort to validate inputs given to it rather than fail silently.
This shows imo that BioJulia is better, precisely because it validates data and is a broader programming language invented for science, not a DSL that optimises for speed over all else. Besides the new version of BuiJulia seems to perform even better than seq.
Launch bc using the -l or --mathlib option to get 20 decimals of precision and load some basic math functions. I have this as an alias in my .bashrc, so I don't need to do this every time I launch the program.
To clarify: this is not Emacs. Instead, it is a text editor that features improvements over the built-in editor. It was partly written by Carsten Dominik (creator of Org mode), who is an Emacs user. Some features were inspired by Emacs, but the similarities end there.
TECO got easier to use with time, especially after the MIT people added ^R (Realtime) mode, which showed a whole screenful of text at a time as opposed to the earlier behavior where TECO would print on command but was otherwise like ed instead of vi. Makes sense, seeing as how TECO originally stood for Tape Editor and COrrector, as in paper tape.
TECO's main claim to fame was its command language, which became its programming language: People wrote programs (including the original EMACS) in TECO's command language, where most commands were non-printable characters in ASCII. There were conventions to print those characters readably (well, readable for human TECO users), such as printing Esc as $, but the fact remained you were programming with line noise. ;)
There's a TECO for modern systems, called Video TECO, here:
I still agree with you though in that it is not necessarily the universities responsibility to cultivate founders.