Live Stream 1980: Netizens Teach Me How to Make a Rocket by Hand

......

A few days later, at the joint press conference in San Francisco.

More than 500 tech journalists and Wall Street analysts packed the audience to capacity.

Flashes of light went off one after another.

The huge Intel logo on the stage was blindingly bright.

Andy Grove was the first to appear.

The Intel CEO looked smug, holding a small chip in his hand.

In order to stop the rampant expansion of the Red Star Fuxi chip in the North American compatible PC market, Intel pushed forward the epoch-making 80386 to April.

On the big screen, the benchmark data popped up one by one.

Integer performance.

Memory addressing.

Floating-point extension.

Each indicator caused a stir among the audience.

The applause of the audience was thunderous.

The analysts were frantically taking notes, and someone in the front row even shouted excitedly:

"This is the crown jewel of Silicon Valley!"

Grove left with a smile.

Intel played its hardware card brilliantly.

Next, it was William's turn to take the stage.

He was going to demonstrate the Windows 1.0 system that was paired with the new chip.

The focus of the entire audience shifted from the glittering chip to the large screen.

The scene changes, and a flat window appears.

The atmosphere in the audience immediately became strange.

The dozens of reporters in the front row even stopped taking notes.

No one booed, but the silence was more unbearable than any booing.

Over the past year, these practitioners have become quite accustomed to Taiji OS.

Smooth overlapping windows, responsive drag-and-drop feedback, and truly usable multitasking.

Looking at these rigid blocks in front of me, and the barely concealed sluggishness when the mouse moves, I realize that...

The gap is there, and it can't be hidden.

Then came the Q&A session.

A reporter wearing a Wired magazine badge stood up, picked up the microphone, and began to speak:

"Mr. William."

"Taiji OS had already achieved multi-tasking parallel processing in the graphical interface last year."

"Now that we have such a powerful Intel 386 processor, could you demonstrate for us how Windows 1.0 can perform true multitasking concurrent processing?"

The problem hits the nail on the head.

Flashbulbs started going off in quick succession as all the cameras were pointed at William.

William gripped the edge of the table, his hands taut.

He knew better than anyone how fragile the single-task foundation of DOS was.

But in this situation, he couldn't back down.

Taking a step back means publicly admitting that Microsoft has not caught up with Taiji OS.

"no problem."

William managed to squeeze out a sentence.

"We can open a text editor and perform table function calculations in the background simultaneously."

He gestured to the operator beside him.

The operator moved the mouse and double-clicked three program icons in succession.

Commands flooded in.

The old, single-threaded logic at the underlying level instantly lost its scheduling direction in the face of high concurrent load requests.

The hourglass icon on the big screen only spun halfway before the image froze completely.

For a full three seconds, the system did not respond.

Immediately afterwards, a low, muffled error message echoed throughout the venue through the speakers, and a line of cold, white text appeared on the large screen:

[Memory overflow error.]

The entire audience erupted in uproar.

A reporter in the back row couldn't help but burst out laughing.

The analysts in the front row were talking in hushed tones, their pens, which had been writing rapidly just moments before, now remained motionless on the paper for a long time.

Facts speak louder than words; everyone understands now.

Microsoft has never mastered the core scheduling logic of graphical multitasking.

This Windows 1.0 is essentially just an old system wrapped in a shell.

Before the shell could even be properly secured, it cracked open in front of the global media.

What's even more embarrassing is that Intel had just hailed the 80386 as a top-tier chip.

Microsoft then proved one thing.

Even the most powerful engine can't move a broken wheel.

The next morning, the San Francisco Chronicle and major technology magazines all published their headlines:

Microsoft, a company you can't even copy.

"Putting rusty wooden wheels on a Ferrari".

"The 80386 is powerful, but Windows is holding it back."

These headlines are like slaps to Microsoft's face.

It also slapped the entire Silicon Valley counterattack alliance in the face.

......

When the message was sent back to China via transoceanic telegram, Lin Xi was in the office of Red Star Software in the capital.

Liu Xiaodong placed a thick stack of English newspapers and reports on his desk.

"Mr. Lin, the press conference in the United States has been ruined."

Liu Xiaodong's tone was filled with barely suppressed excitement.

"Their counterattack failed."

Lin Xi glanced at the newspaper and then focused her attention on the latest reports.

With its early free licensing of underlying interfaces and fully open-source development kits, Taiji OS has seen a rapid increase in popularity in North America and Eurasia.

At this time, Red Star Ecosystem has gathered nearly 300 motherboard and microcomputer manufacturers of all sizes around the world, as well as thousands of software development teams.

Whether you are a parts assembly plant in South America or a long-established industrial control equipment supplier in Europe.

If you want to build a cheap, compatible machine that you can sell, Taiji OS is the only universal solution.

Because the developers are here, the driver interface is here, and the application software is here.

Developers follow the interface, software follows the developers, and hardware manufacturers ultimately have no choice but to follow the software.

Once this chain is connected, the ecosystem is complete.

Before anyone could react, Lin Xi had already used open source and compatibility as two trump cards to build an absolute barrier that would allow the winner to take all.

"Maintain strong support for the underlying software teams."

"The development kit will continue to be updated, the driver documentation will continue to be released, and compatibility testing cannot be stopped."

"Once developers get used to our ecosystem, hardware manufacturers won't be able to cause any trouble."

......