Re: Microsoft Introduces New Command-Line Text Editor

Paul <nospam@needed.invalid> wrote:

On Tue, 5/20/2025 3:54 AM, Lawrence D'Oliveiro wrote:

Kind of amusing to see the lengths that Microsoft keeps going to, to
try to bolster its sagging geek cred. Now it is introducing a new
command-line-based text editor for 64-bit Windows!
 
<https://www.theverge.com/news/669318/microsoft-edit-on-windows-command-line-text-editor>
 
Of all the excuses for reinventing the wheel, I’m not sure whether
this one is particularly creative, particularly lame, or both:
 
Microsoft also wanted to avoid the “how do I exit vim?” meme, so
it built its own text editor instead of relying on other available
options.
 
Really?? You wanted to spare your users the horrors of coping with
vim?!? They’re already suffering under Windows, for goshsakes!
 

 
This is so cool. <Slips on geek shades>
 
https://devblogs.microsoft.com/commandline/edit-is-now-open-source/
 
   "This is a godsend for computational biologists where we have to open
massive text files and..."

... anything microsoft was the last thing we'd use.

There's a reason why bioinformatics/compbio almost exclusively sits with
linux or macs: the flexibility of shell scripts for manipulating plain text
files of any size.

From a Wiki article:
 
   "Pharmacologists were able to use Microsoft Excel to compare chemical and
    genomic data related to the effectiveness of drugs. However, the industry
    has reached what is referred to as the Excel barricade. This arises from
    the limited number of cells accessible on a spreadsheet.            
    <=== OMG. The horror.

The real problem with excel is that it corrupts biological data.
https://blogs.nature.com/naturejobs/2017/02/27/escape-gene-name-mangling-with-escape-excel/

    This development led to the need for computational pharmacology."   
    <=== (Adds extra rows to Excel, runs away)
 
Now we know how the other half lives.
 
Sitting in an office, with the legend worn off your PgDn key.
 
   Paul