The Google Engineer Accused of Risking It All with an Insider Polymarket Bet

   # plain text
   # article only contains one URL

   links -dump https://assets.msn.com/content/view/v2/Detail/en-in/AA24oJaI \
   |sed '1,/\"body\":/d;/readTimeMin/,$d' > 1.txt
   #vi -R 1.txt
   less 1.txt


   # html, no CSS, no Javascript
    x=https://assets.msn.com/content/view/v2/Detail/en-in/AA24oJaI 
   (echo url=$x
    echo header=user-agent:
    echo header=accept:
    #echo insecure
   )|curl -K/dev/stdin \
    |grep -o "<p>.*</p>" \
    |tr -d '\134' \
    |sed '1s/^/<meta charset=utf-8>/'  > 1.htm
   firefox ./1.htm
   #links 1.htm

Developers like it, it's everywhere, so we have to deal with it

Javascript is one way to make JSON "readable"

But it's not the only way

I don't use Javascript. I have own methods for making JSON easier to read