• Skip to primary navigation
  • Skip to main content
  • Skip to footer

Codemotion Magazine

We code the future. Together

  • Discover
    • Events
    • Community
    • Partners
    • Become a partner
    • Hackathons
  • Magazine
    • Backend
    • Frontend
    • AI/ML
    • DevOps
    • Dev Life
    • Soft Skills
    • Infographics
  • Talent
    • Discover Talent
    • Jobs
    • Manifesto
  • Companies
  • For Business
    • EN
    • IT
    • ES
  • Sign in
ads

CodemotionJune 5, 2019

The right and wrong with JavaScript: interview with Douglas Crockford

Web Developer
facebooktwitterlinkedinreddit

Paypal JavaScript architect Douglas Crockford is the man widely praised for discovering the much-loved JSON Data Interchange Format.

But when the American computer programmer and entrepreneur suggested there were good parts to JavaScript, the reaction was a tad more intense.

There’s a lot that’s wrong with JavaScript. But the interesting thing, the unexpected thing, was that there was a lot right with JavaScript.

“When I first announced that there were good parts to JavaScript, that news was met with scepticism and threats of violence – there’s no way that could be true! But it is true – JavaScript does have some brilliant ideas in it. Taking functions as first-class objects with lexical closure, which we got from scheme, combining that with simple objects is just absolutely brilliant.”

As the author of How JavaScript Works, also developing various JavaScript-related tools such as JSLint and JSMin, Douglas is an expert in his field. But he is reluctant to accept all the credit for the success of JSON and JavaScript.

“I don’t want to claim to do things that I haven’t done. With JSON, for example, JSON already existed as a subset of JavaScript. What I did was I observed it in nature and gave it a name and showed how it could be used. But I can’t take credit for it. Brendan Eich created JavaScript. He deserves all the credit for everything that’s good about it.”

These days, Douglas is concerned about the web and the concept of corporate capture. Unless governments become more serious about regulation, he sees the problem getting worse.

The web was originally intended to be a totally decentralised, totally distributed document sharing system.

“We assumed that this intermediation would be one of the benefits from it, that middle men or intermediary distributors we wouldn’t need them anymore, we could all form immediate, direct electronic relationships with anybody we needed to do business with.”

“It didn’t turn out that way… there’s a very small number of companies now that are taking over ownership of the internet – you know who they are – and that’s distressing. So, for a time we were worried about government capture, certainly in China that’s an issue. It was predicted that the Great Firewall wouldn’t work but, in fact, it seems to be working really well. But a bigger concern I think is corporate capture.”

Related Posts

Native CSS: A Whole New Story – Part 1

Daniele Carta
March 3, 2025
Flock. Fork flutter

Meet Flock: The Flutter Fork Aiming to Accelerate Development

Codemotion
November 4, 2024
Angular v18 fallback

Angular fallback content in ng-content

Davide Passafaro
May 13, 2024
setup project, web development, framework, typescript cypress

How to Set Up a Cypress TypeScript Project

Antonello Zanini
September 12, 2023
Share on:facebooktwitterlinkedinreddit
Codemotion
Codemotion
Articles wirtten by the Codemotion staff. Tech news, inspiration, latest treends in software development and more.
Machine learning and fairness, how to make it happen
Previous Post
XPay Mobile App: integrazione con Google Pay e Apple Pay
Next Post

Footer

Discover

  • Events
  • Community
  • Partners
  • Become a partner
  • Hackathons

Magazine

  • Tech articles

Talent

  • Discover talent
  • Jobs

Companies

  • Discover companies

For Business

  • Codemotion for companies

About

  • About us
  • Become a contributor
  • Work with us
  • Contact us

Follow Us

© Copyright Codemotion srl Via Marsala, 29/H, 00185 Roma P.IVA 12392791005 | Privacy policy | Terms and conditions