Time Travel: 2014

Swift community members are also actively working to port the Swift programming language to more platforms.

With SourceKit-LSP, Swift community members are also working hard to integrate Swift programming support into various developer tools.

With this unremitting efforts, on the eve of Lin Hui's rebirth: Swift is a programming language that can not only develop many new applications for the Apple platform.

And also for a new range of modern server apps.

Beyond that, there are many broad applications.

And in all this, it is not difficult to find that the love of external contributors has greatly accelerated the growth of Swift as a programming language.

Without these external contributors, even the programming language Swift would have been born as planned.

I am afraid that the growth rate will also slow down significantly.

However, in this life, Lin Hui has found almost no information about open source communities like the Swift community or any other information that may be related to Apple's open source language projects through public and semi-public information channels.

In this case, judging objectively:

Lin Hui couldn't help but suspect that the SWIFT language was being developed behind closed doors.

Or maybe there is simply no so-called SWIFT language in this time and space!

It sounds weird, but it can happen.

Although judging from what happened in the past life, the programming language Swift will replace (a replacement in a mainstream scenario, not a complete replacement) Objective-C. This is an inevitable trend.

But when the Swift language first appeared in the previous life, people didn’t entirely see it this way.

Although it is not difficult to switch to the Swift programming language after mastering the Objective-C programming language.

But when the Swift language first appeared, it actually did not solve the problem of mixing with the C language and C++ language well.

When the interface and most of the logic are written in Swift language, the underlying core libraries of many projects use C language or C++ language.

At this time, it is inevitable to continue to use the programming language Objective-C as the glue layer.

In addition, when the Swift language first appeared, there were many libraries written in the Objective-C programming language. Using these libraries requires certain knowledge of the Objective-C programming language.

In other words, even if you learn the programming language Swift alone.

When doing some development, Objective-C is still inseparable from the programming language.

Any function written in the programming language Swift can also be done using the programming language Objective-C.

When the Swift programming language was first born, it did not particularly simplify the learning cost.

So why would you need to learn a new separate programming language?

Especially when a new standalone programming language seems a bit useless.

If measured by "tasteless".

It seems that even if Apple has not developed the programming language swift to replace the programming language Objective-C, there is a reason.

After all, developing a programming language from scratch is not an easy task.

Not only does it require a lot of money and time.

And it also requires a push from genius.

Apple has corresponding needs in developing the programming language Swift.

There is a corresponding reason for not developing it.

As for whether there is a programming language like Swift in this time and space.

For the time being, Lin Hui didn't want to draw too arbitrary a conclusion.

Everything will be said after there is further and more definite news.

And before that.

The forest ash needs to grow to a certain height quickly.

This height is not just a height of wealth.

It refers to a new level of ability.

If Lin Hui didn't have the corresponding strength.

Even if the programming language Swift has really undergone major changes compared to its previous life.

With Lin Hui's current strength, it was impossible to take chestnuts from the fire.

On the contrary, it is easy to get angry.

But Lin Hui is different now that he has great strength.

A tiny butterfly flapping its wings can cause a storm in the Americas.

But it seems that it is not difficult to avoid the coming storm.

Just kill the butterfly flapping its wings crazily at the beginning.

In the same way, when Lin Hui has enough strength.

Lin Hui can control variables.

If there are major changes in the Swift programming language, resulting in the missing of the puzzle pieces corresponding to the Swift programming language in the previous life.

With strong strength, Lin Hui can completely complete the puzzle.

As for Lin Hui, what is the benefit of completing this puzzle?

Maintaining the branches of the timeline is one consideration.

On the other hand, it has something to do with Lin Hui's previous ambitions.

When it comes to past life information, Lin Hui feels that the only product that has a high value (hundreds of billions of dollars in direct and indirect economic value) and is close to a finished product is Fuchsia OS.

If Lin Hui has strong strength in the future and has many resources (the resources here include but are not limited to money, human resources, etc.) to deploy.

Naturally, there is no need for too many twists and turns. When the time is right, just "carry" it and it's done.

But if Lin Hui is unable to handle the corresponding resource integration on his own.

(ps:...Although the so-called "powerlessness" is an extremely small probability event, even if it is possible, Lin Hui has to take measures to avoid risks in advance.)

If Lin Hui still wants to carry out the transportation when he is unable to do so.

I am afraid that we will have to rely on other aspects or higher-level forces to integrate resources to achieve transportation.

So when integrating resources, how should other aspects or higher levels believe that Lin Hui has the ability to handle the operating system?

Ideally, the most reliable way is that Lin Hui has previous experience in successfully developing operating systems.

If Lin Hui has had successful experience in developing operating systems before.

Then all parties involved in the resources integrated by Lin Hui will naturally believe that Lin Hui has the strength to handle a brand new operating system.

But this is basically unrealistic.

Due to various external reasons, it was impossible for Lin Hui to practice on individual operating systems before transporting one.

That can easily cause unnecessary trouble.

And even though Lin Hui may have a stronger ability to absorb knowledge in this life than in his previous life.

But the acquisition of knowledge is not something that can be accomplished overnight.

Judging from this perspective, even Lin Hui's future is limitless.

For now, Lin Hui doesn't have the ability to tinker with a brand new operating system.

Therefore, from the current point of view, it is difficult to develop another operating system in advance to practice before the official transfer.

In this case, how should Lin Hui win people's trust when integrating resources?

Lin Hui felt that even without successful experience in developing operating systems.

Having the experience of being responsible for a very large project will be a highlight in a developer's career.

Not only that, if such a large-scale development project can succeed, it will also be of great benefit to future resource integration.

Swift programming, a project that took several years in the previous life and involved nearly 10,000 people, can definitely be said to be a very large project development.

Lin Hui felt that if something went wrong with the space-time Swift programming project.

It would be a good choice to participate in the Swift programming project led by Apple.