ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: The forgotten developer who saved JavaScript...

It's 2009.

⏸ หยุดชั่วคราว

ความเร็ว:

120 ประโยค

หากประโยคสั้นหรือยาวเกินไป กดที่ Edit เพื่อปรับแก้

It's 2009.

You're at a Hannah Montana movie,

and your phone won't stop buzzing with notifications from a new dating app you just downloaded.

Your favorite artist is supposed to be releasing a new album next year.

Your favorite TV show is currently being made into a movie.

And you're still riding high from arguing how many days are in a week on the bodybuilding.com forums.

Life is good, at least on the weekends.

Because during the week, you have to spend all day using the worst programming language ever invented.

A language that was famously designed in 10 days,

but after using it, it had you wondering what Brendan did after day two.

A language that every browser interpreted differently,

had no standard library, modules,

or classes, and if your primary job was to write it,

I'm told you were a massive loser who didn't deserve to feel love.

At least that's how things were in 2009.

But over the next decade, that sentiment changed.

JavaScript went from being a language that you'd never touch directly without putting on a jQuery hazmat suit first,

to arguably the most popular programming language in the world,

while JavaScript developers, despite all the stupid stickers on their MacBooks,

went from being considered script kitties to real programmers with actual feelings and emotions.

So how exactly did this mass psychosis happen?

There's a bunch of different reasons,

but in my opinion,

I think the most underrated was all led by a single person who has since been forgotten to time, Jeremy Ashkenis.

In 2009, Jeremy was a developer at Document Cloud,

where he had the unfortunate task of working on a heavy client-side JavaScript application,

which was rare at that time.

Having a background in Ruby,

but being forced to write JavaScript,

I assume every morning he'd wake up and think to himself,

wow, today might be a good day to b***ing b*** myself off the b***ing Golden Gate Bridge.

But unlike everyone else who had JavaScript Stockholm Syndrome,

Jeremy had the audacity to think he could fix it,

and so he did.

His first act was dealing with the fact that JavaScript had no standard library.

Again, this was 2009.

Although Firefox had shipped support for some array helper methods like map,

reduce, and foreach, Internet Explorer hadn't yet,

which meant you couldn't use them unless you polyfilled them.

So to fix this, Jeremy released Underscore.js,

a utility belt library that contained about 60 helper functions that made it easier to work with the Rays and Objects.

Now, I know that doesn't sound exciting today,

but building for the web was so bad back then

that Underscore likely did save a few people from throwing themselves off the f***ing Golden Gate Bridge.

Underscore got so popular that many of its features were adopted into the JavaScript language itself,

which eventually made it obsolete.

But Underscore was only Jeremy's first act.

Next, he decided instead of augmenting fish head JavaScript with a new library,

he'd have more freedom if he just created an entirely new language with large cannons.

Again, I can't stress this enough,

the JavaScript in 2009 was very different than it is today.

There were no classes,

so inheritance was done through a pattern where you'd manually attach properties to a hidden object called prototype

that every function had access to.

The only way to declare a variable had bizarre scoping rules that hoisted declarations to the top of a function,

whether you were aware of it or not.

No one really understood or cared about the difference between the equality operator and the identity operator,

so you'd have a bunch of type coercion happening without even realizing it.

And to define even a simple function,

you had to literally type out the word function every single time,

which led to some pretty ugly code.

By building a new language that compiled a JavaScript,

Jeremy could fix it without having to wait for the standards committee or browser vendors to do it themselves.

And even better, he could leave JavaScript the bad parts in that musty room Brendan spent 10 days in.

And for a while, CoffeeScript was huge.

Father DHH adopted it almost overnight,

and in 2011, it shipped as the default JavaScript preprocessor in Rails 3.1,

meaning the front end for every new Rails app in the world was suddenly written in CoffeeScript.

GitHub, Dropbox, and a long list of early 2010 startups adopted it,

and for a few years,

it was the default choice for anyone who took JavaScript seriously.

Today, CoffeeScript is basically dead after its best features were absorbed into JavaScript itself,

but every time your agent writes a class,

arrow function, default parameters, a spread operator,

does string interpolation, or destructures a value, you can thank CoffeeScript.

But Jeremy still wasn't done yet.

By 2010, he had given JavaScript a standard library with underscore,

and a better syntax with CoffeeScript.

But there was still one massive problem left.

There was no good way to actually structure a JavaScript application.

If you wanted to build a large,

client-side-heavy app, you would still end up with thousands of lines of spaghetti where your data,

DOM manipulation, and event handlers were all tangled together.

So in 2010, Jeremy released Backbone.js,

a tiny library of less than 2,000 lines of code

that gave JavaScript developers their first real taste of MVC on the front end.

It introduced models for your data,

collections for groups of models,

views for rendering, and an event system that let everything stay in sync without the need to wire it up by hand.

But for the first time,

you could build a serious client-side app without it collapsing under its own weight.

And with Jeremy's track record,

it quickly caught on, powering the early versions of Trello,

Airbnb, Hulu, Pinterest, and basically every other startup that needed a real front end between 2011 and 2014.

If you were a JavaScript developer during that window,

you almost certainly wrote Backbone,

and you probably thought it was the future.

But as it turns out, it wasn't.

Angular, Ember, and eventually React would make Backbone obsolete by taking its core ideas and pushing them further.

100

But Backbone was the library that proved you could actually build client-side heavy applications.

101

It's easy to forget how bad JavaScript used to be,

102

and even easier to forget the people who fixed it.

103

But the modern web was built on top of ideas that Jeremy Ashkenis pioneered,

104

even if no one remembers him.

105

But speaking of things you no longer have to build yourself,

106

Auth is another one, thanks to Clerc,

107

the sponsor of today's video.

108

They just launched the Clerc CLI,

109

which comes with commands that are even more powerful than the ones I saw at that human dog show.

110

Just run clerk init in any directory,

111

and it'll set up end-to-end authentication for your entire project with custom middleware,

112

auth pages, and environment variables.

113

It even detects if you're migrating from next auth or auth zero and walks you through the entire process.

114

And since they know you're using agents to do all your dirty work,

115

they also created clerk skills,

116

which ships framework-specific patterns pinned to the CLI version so your coding agent knows exactly how to use it.

117

And the clerk API command lets your agent hit the entire clerk backend API from the terminal without copy and pasting credentials.

118

Try it out for free today at the link below,

119

or just run clerk init to get started.

120

Thanks for watching, and I will see you in the next one.

TRENDING

ยอดนิยม

เทคนิค Shadowing คืออะไร?

Shadowing เป็นเทคนิคการเรียนรู้ภาษาที่ได้รับการรับรองทางวิทยาศาสตร์ พัฒนาขึ้นสำหรับการฝึกนักแปลมืออาชีพ วิธีการนี้เรียบง่ายแต่ทรงพลัง: คุณฟังเสียงภาษาอังกฤษจากเจ้าของภาษาและพูดตามทันที — เหมือนเงาที่ตามผู้พูดด้วยช่วงเวลาห่าง 1-2 วินาที การวิจัยแสดงว่าเทคนิคนี้ปรับปรุงความแม่นยำในการออกเสียง ทำนองเสียง จังหวะ การเชื่อมเสียง การฟังเข้าใจ และความคล่องแคล่วในการพูดได้อย่างมีนัยสำคัญ

☕ เลี้ยงกาแฟเราสักแก้ว

ShadowingEnglish ยังคงเปิดให้ใช้งาน ฟรี 100% ได้ด้วยการสนับสนุนจากคุณ ค่าใช้จ่ายสำหรับเซิร์ฟเวอร์และ AI นั้นสูงมาก — กาแฟของคุณช่วยให้เราเดินหน้าต่อไปได้! 🙏

บริจาคผ่าน PayPal

ShadowingEnglish.com – ฝึกพูดภาษาอังกฤษแบบ Shadowing

ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: The forgotten developer who saved JavaScript...

ยอดนิยม

เกี่ยวกับบทเรียนนี้

คำศัพท์และวลีสำคัญ

เคล็ดลับในการฝึก

เทคนิค Shadowing คืออะไร?

ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: The forgotten developer who saved JavaScript...

ดาวน์โหลดแอป

เกี่ยวกับบทเรียนนี้

คำศัพท์และวลีสำคัญ

เคล็ดลับในการฝึก

เทคนิค Shadowing คืออะไร?