シャドーイング練習: How a CPU Works in 100 Seconds // Apple Silicon M1 vs Intel i9 - 動画で英語スピーキングを学ぶ

練習モードを選ぶ

各モードは全画面の練習ルームで開きます。

146 文

文が短すぎたり長すぎる場合は、Editをタップして調整してください。

The central processing unit, or CPU, is like the engine in your car, or the brain in your skull, and is like a really fancy calculator used to run the applications on your computer.

When you write software in a language like JavaScript or Python, you're actually writing a set of instructions that will be executed as machine code by a CPU,

which itself is a carefully crafted piece of metal and silicon that contains billions of tiny transistors, or on-off switches that represent ones and zeros.

To perform mathematical calculations, a CPU will combine multiple transistors together to form logic gates.

For example, AND will take two binary inputs and validate that both are true to produce a true output.

It only takes a few basic logic gates to solve highly complex computational problems.

Modern chips contain billions of transistors, and they can be flipped on and off billions of times per second.

The state of the CPU is synchronized by an oscillator known as the clock generator.

In general, the more times the clock can pulse per second, the faster the CPU can compute, and is normally measured in gigahertz.

Gamers will sometimes overclock their CPUs to gain more performance at the cost of higher temperatures and a lower life expectancy.

Now, in order to run applications, it interacts with the system memory or RAM in a series of four steps known as the machine or instruction cycle.

Step one is the fetch phase.

Think of a software program as a set of instructions stored in the RAM.

The CPU has registers to temporarily store the address and memory that it wants to interact with.

The program counter starts at zero and copies that address to the memory address register.

Then the control unit sends out a signal to copy the data from that address to the instruction register, at which point it needs to figure out how to use this instruction in the decode phase.

The control unit parses the actual bits in the instruction.

Most importantly, the opt code contains the instruction, like add or subtract, and the operand is the address and memory to perform that operation on.

The final execute stage takes the decoded information and passes it as electrical signals to the relevant parts of the CPU.

The Arithmetic Logic Unit, or ALU, can perform math on the data and then store the results in RAM to change the state of the program.

The cycle is repeated billions of times per second, and modern chips utilize multiple CPU cores to run multiple computations in parallel.

That's how a CPU works under the hood, but there's a lot more you should know about processor architectures if you're a developer.

And that's why I've invited Alex from the most underrated tech

channel on YouTube to break down some more advanced concepts like Apple Silicon

and how to run performance benchmarking on your own machine.

Hi everybody, my name is Alex

and I'm here to take you beyond 100 seconds in your quest to learn about how processor architectures differ

and also how those differences affect our productivity as developers.

I'll show you what the Apple Silicon chip and a refrigerator have in common, and then I'll share some of my own experiences with using developer tools

and build execution on the first generation Apple Silicon chip called the M1 chip, as compared to the Intel chip.

First and foremost, I just want to say

that my personal productivity as a developer depends less on processors inside my computer

and more on how much coffee I had and whether I'm I'm trying to work after a big meal.

But aside from human factors, let's dig deeper into why the new Apple Silicon machines have been really kicking up a storm and changing the industry, software development included.

And spoiler alert, the M1 machines have been beating the Intel machines in pretty much every build test I've thrown at it.

Except a couple.

But it's not all roses, so let's talk about some downsides later too.

So why is it so darn fast?

The first point I want to discuss is the physicality differences

of the new Apple Silicon way versus the old Intel and AMD way.

This is what Apple Silicon and your refrigerator at home have in common.

Alright, imagine for a minute that you want to make a turkey with cheese sandwich.

You go over to the refrigerator and in one place you have the turkey breast, the cheese, the mayonnaise, the mustard.

All those ingredients are right there in one place and you don't have to run around the house to gather them.

You don't have to drive to lots of stores to pick them up.

And this saves you lots of time and energy.

This kind of efficiency can be found in the new Apple Silicon chips because they aren't just a new processor.

Apple Silicon is a collection of many chips that are housed inside one silicon container.

And this type of system is known as a system on chip or SOC.

And it's essentially an entire computer on one chip.

The main CPU, the GPU, the I.O controller, the ML engine, they're all co-located.

So when the task is to make an electronic sandwich, so to speak, or in other words, to do some work that involves all these different components,

a system on chip is going to be a lot more efficient in terms of energy usage, using only a tiny bit of power, and at the same time, it's going to be faster than,

say, a typical machine that has all the components separate.

Intel based machines have a CPU that's a single chip and memory is located somewhere else on the motherboard.

The I.O is somewhere else.

The individual components might be even more powerful than the ones available at the moment on the latest Apple silicon based machines.

But that comes at a cost since these powerful components are like supermarkets that carry different sandwich ingredients.

As a result, when you want a sandwich on an Intel machine, You'll have to drive all over town because one store will have the turkey another store will have the cheese

Yet another store will have the mayonnaise each store might be really good at their own process

and have the best ingredients

But each store also takes a lot of power to run losing out on the efficiency

And since all you really want is just to make a simple sandwich You're wasting a ton of time

and energy picking up the ingredients from all the different stores Of course, some might say the drawback with the system-on-chip design is that,

at least for now, with the current selection of Apple Macs, you won't be able to upgrade or change any of the components.

You get what's on the menu, and that's it.

But that's not news to most people that are familiar with the Apple ecosystem.

Once you accept that idea, you might even see the benefits of having a more efficient design where all the components are on one chip,

and they outweigh the cons and still provide better performance than the alternative.

All right, that's enough Let's talk about food.

So how does this all affect real world development workflows?

So I've been doing a bunch of developer focused tests on the latest Apple Silicon machines over on my channel,

as well as comparing them to other machines like the Intel Macs and PC machines too.

And in general, the new design has been showing really great promise for my own workflows as a developer, coffee and sandwiches excluded.

Now there are lots of technology stacks that developers use, of course, and I'm trying builds in a few of them.

But now let me share some of the results I've seen with Node and JavaScript tests.

And after that, I'll also discuss the tech stacks

that have the biggest gains on the new machines

and also the stacks that have the biggest losses right now at the moment.

I started off trying out some existing JavaScript tests that are in the browser and then in Node.

The browser test consisted of running Speedometer, which is a browser benchmark that measures the responsiveness of web applications.

It uses demo web apps to simulate their actions such as adding to-do items.

You visit the app in a browser of choice.

I tried Chrome and Safari for this.

And you execute the automated test

that runs through a collection of applications built with some of the more popular UI frameworks like Angular, React, Ember, even Vanilla.js and jQuery.

And a whole bunch more.

And then this test reports the results as a single number when it's done.

This number represents the runs per minute.

And the higher the better.

When it was finished, I found that it had significantly more iterations on the M1.

Safari had the best results, even going off the scale, and Chrome did pretty well too.

I also ran some JavaScript benchmarks in a node environment and found a pretty CPU-intensive algorithm called

Fancook Redux that's implemented in JavaScript and created for Benchmarks Game, a website that collects algorithms and tests in different languages.

And while my 16-inch MacBook Pro with the Intel Core i9 processor did beat the MacBook Air with the M1 chip, it really didn't do so by a lot.

And when you consider the price differences between the machines, and the fact that the M1 stayed cool throughout the test, and that the battery hardly even took a hit on the M1,

you might be thinking whether the extra few seconds saved

while running this benchmark on the Intel i9 is really worth the money.

So running benchmarks is often very telling, but it doesn't necessarily line up with real-world scenarios.

100

So that's why I also like to conduct my own tests, whether using my own projects or other open-source projects that are out there and that commenters send to me.

101

And here's what I found.

102

I ran a build of the official NativeScript plugins repository, which is a project based on NX workspaces.

103

If you're not familiar with NX workspaces, it allows you to scale large JavaScript and other tech stack projects, and you can see the NX quick start right here on this channel.

104

In my test, the build that took about three minutes on each machine only differed in build time by tens of seconds,

105

with the M1 MacBook Air beating out the Intel MacBook Pro two out of three times.

106

So let's talk about what dev stacks benefit the most from the new Apple Silicon chips at this time.

107

For JavaScript developers, the benefits are already visible.

108

However, if you're building mobile apps for iOS or compiling C++ code, then this is where you'll see a 40 to 50% improvement in build times.

109

I ran a few Xcode builds and Swift builds, and I did some C++ algorithms and built OpenCV and WebKit.

110

In all those tests, the M1 came out on top.

111

So what DevStacks benefit the least?

112

So far in my own testing, any builds that have to do with running natively built software

113

and building using native tooling has absolutely destroyed Intel in speed and battery performance,

114

native being compiled for the Apple Silicon architecture.

115

Even when running some software via Apple's Rosetta,

116

that's the translation layer that allows you to run Intel and AMD-based x64 and x86 programs on the new Apple hardware,

117

even some of those software packages ran better than on Intel.

118

And that's just amazing.

119

But there are workflows that aren't ready yet, in my opinion.

120

If you are an Android developer, Android Studio and official Android emulators work on Apple Silicon,

121

but they're currently using Rosetta for translations.

122

And while Rosetta is generally pretty good at running x86 targeted code on ARM chips, it's not enough for the CPU-hungry Android workflows,

123

and I found the results to be not very usable at the moment.

124

The latest version of .NET, which is version 5 right now, isn't fully supported to run on ARM.

125

Simple console applications ran just fine for me, but testing any web workflows like ASP.NET Core doesn't work at all yet.

126

Now, it's expected that by the end of this year, .NET 6 will come out.

127

It's in alpha right now, and we'll have full support for ARM.

128

Until then, if you need to develop .NET apps, I suggest using a PC with Windows.

129

Oh, and if you think you can use a virtual Windows machine, I've tested this as well.

130

Parallels is the only vendor that currently supports the M1 chip to create a virtual Windows environment,

131

but the issue is that the Windows guest operating system for ARM is still quite immature and needs a lot of work.

132

Also, Visual Studio 2019, the latest Visual Studio offering from Microsoft, is unfortunately not compatible with ARM at all,

133

and in my test is not stable, even using the built-in Windows translation of x64 software to run on ARM hardware.

134

For game developers that use Unity, I'm pleased to say that it works surprisingly well on Apple Silicon via Rosetta.

135

However, it's not as performant as running natively on x86.

136

But by the time you watch this video, Unity might have a version natively compatible with M1, which I know they're working hard to get out as soon as possible.

137

Overall, Apple Silicon has really put a boost into many workflows for developers and other professions, and eventually even gaming.

138

And with the M1 tests, we're seeing the improvements with just their entry-level machines.

139

The upcoming second and third generation Apple Silicon machines will be even more performant and I can't wait to see that.

140

I think it's really going to help us as developers move to the next level

141

and I think it's just going to lift up the entire industry.

142

To follow the updates on the new Apple Silicon chips as they relate to us, developers, as well as seeing me conduct these tests that I've been discussing here,

143

consider subscribing to my channel as well.

144

The link is down below.

145

I'm going to wrap it up there.

146

Thanks to Fireship for hosting me to share this amazing new world that we're about to Enter as developers.

アプリをダウンロード

流暢に話すために必要なすべて

AI発音採点文ごとに採点

IPA練習すべての音をマスター

単語学習自分の単語帳を作る

単語ゲーム遊びながら覚える

QRをスキャン

Download on theApp Store Get it onGoogle Play

同じチャンネル

FOR YOU

このレッスンについて

このレッスンでは、「CPUの仕組み」について説明するビデオを使い、英語のスピーキング練習を行います。専門用語が多いため、リスニングと発音の精度を高めることができます。また、IELTS スピーキング対策にも役立つ、論理的な説明の仕方を学びます。

重要な語彙とフレーズ

CPU (Central Processing Unit)：中央演算処理装置。コンピュータの「脳」に相当する部分。
transistor：トランジスタ。オン/オフのスイッチとして働く微小な部品。
instruction cycle：命令サイクル。CPUが命令を実行するための4段階のプロセス。
system on chip (SoC)：システムオンチップ。1つのチップにコンピュータの主要部品を集積したもの。
overclock：オーバークロック。CPUのクロック速度を通常以上に上げて性能を引き出すこと。

練習のヒント

ビデオのスピードは速めですが、shadowing（シャドーイング）を使うことで効果的に練習できます。まず、ビデオを1文ずつ止めて、すぐにその文を繰り返しましょう。「transistors」や「architecture」などの長い単語は、発音のリズムを捉えることが重要です。

英語スピーキング練習には、「shadowspeak」と呼ばれる方法もおすすめです。ビデオを流しながら、1～2秒遅れで発声し、発音やイントネーションを真似ます。専門用語の部分は、正確に発音することで、IELTS スピーキング対策にも繋がります。

shadowing siteを利用して、自分の発声を録音し、ビデオの音声と比較することも効果的です。間違いや発音のずれを見つけて修正し、徐々にスピードを上げていきましょう。

この動画の文法

話し手がよく使っている文型を、動画の実際の表現とともに紹介します。

文型	動画での表現
現在完了進行形 have/has been + -ing — 以前に始まり今も続いている動作	have been beating · I've been doing · has been showing
受動態 be + 過去分詞 — 誰がするかより、何が起きるかに焦点を当てる	will be executed · can be flipped · is synchronized
現在完了形 have/has + 過去分詞 — 過去の出来事が今も関係している	I've invited · have been · I've thrown
関係詞節 who / which + 節 — 人や物について情報を加える	Speedometer, which is · repository, which is · NET, which is

シャドーイングとは？英語上達に効果的な理由

シャドーイング（Shadowing）は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的：ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影（shadow）」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。

シャドーイングのやり方: ステップ別の完全ガイドを読む →

シャドーイング練習: How a CPU Works in 100 Seconds // Apple Silicon M1 vs Intel i9 - 動画で英語スピーキングを学ぶ

練習モードを選ぶ

アプリをダウンロード

PostgreSQL in 100 Seconds

A $6.3 billion open-weight model just got embarrassed by the French...

Every app on Earth is now open source... whether it likes it or not

OpenAI’s lead engineer was secretly a spy...

OpenAI’s new browser feels familiar…

Intel chips can’t possibly be this bad… 100% crash rate?

Did Google just kickstart the intelligence explosion?

Godot in 100 Seconds

The most interesting "hack" in history...

Grok 4 pushes humanity closer to AGI… but there’s a problem

Array Map in 100 Seconds

Docker in 100 Seconds

The one OpenAI announcement that can actually make you money...

How to NOT Fail a Technical Interview

10 weird OSS projects you need right now...

Firefox and Tor hit with 9.8 critical level exploit

5 open source tools that replaced my $320/mo AI stack...

25 crazy software bugs explained

C++ in 100 Seconds

DHH has gone completely off the rails...

The Engineering that Runs the Digital World 🛠️⚙️💻 How do CPUs Work?

Rust in 100 Seconds

Nvidia CUDA in 100 Seconds

My Puzzle Robot is 200x Faster Than a Human

How Bitcoin Works in 5 Minutes (Technical)

Introduction to RTOS Part 1 - What is a Real-Time Operating System (RTOS)? | Digi-Key Electronics

JavaScript Visualized - Event Loop, Web APIs, (Micro)task Queue

Making RAM at Home

Power Plant | How it Works Power Plant Steam Cycle

Watch this before you boot up another device

Deep Dive: Investigating Thermal Cycling Failures Cracked MSOP Solder Joints

Steve Jobs & Bill Gates interview 2007

このレッスンについて

重要な語彙とフレーズ

練習のヒント

この動画の文法

シャドーイングとは？英語上達に効果的な理由