Crossover: 2014

Chapter 269 The Absentees of the Developer Conference (continued)
This may lead to more severe antitrust charges.

But before the verdict is reached, Apple — Microsoft's greatest enemy, the work of Jobs' life — will be gone.

In short, no matter what perspective you look at, this behavior has elements of funding the enemy.

But this kind of financing of the enemy actually happened.

Probably because Microsoft feels that it is not easy to mix without an opponent.

Many times it is lonely without a business counterparty.

At the same time, it is very dangerous to have no commercial competitors.

If there is no business opponent, it will probably suffer from various invisible giants in law, economy, and culture.

Of course, this realm is still far away from Lin Hui.

However, Lin Hui is quite looking forward to reaching this level himself.

Although this is still a bit far away, it is not the kind that is out of reach.

As for what Huang Jing mentioned right now, Lin Hui didn't really take it too seriously.

Compared with these upcoming things introduced by Huang Jing.

Lin Hui actually cared more about what Huang Jing didn't mention.

It's the same as Elizabeth Nishi didn't mention the Swift language before.

Huang Jing also did not mention the swift language.

This could not help triggering Lin Hui's suspicions.

The previous SWIFT language was the real core of the 2014 Apple Worldwide Developers Conference.

It was even evaluated by the media as the biggest surprise of the entire 2014 Worldwide Developers Conference.

Past Life The Swift language is a powerful and intuitive programming language.

Such a programming language is available for iOS, iPadOS, macOS, Apple tvOS and watchOS.

Swift is syntactically concise, yet expressive, and packed with modern features developers love.

According to Apple's description, Swift code is safe by design and can develop software that runs as fast as lightning.

In the previous life, the Swift language was developed by Apple to replace objective-C.
Developers can continue to develop with Swift on the basis of Objective-C and C languages.

Compared with the previous Object-C, Swift is much more streamlined, and many cumbersome code symbols are removed, and the execution efficiency is much higher.

And the difficulty is also correspondingly reduced by a lot of development difficulty;
All Swift uses visual programming design, users can write code while viewing the actual running effect of the code.

Real-time preview can be performed, greatly improving the efficiency of programming.

In Apple's own words, programming has never been easier.

Why hasn't there been any news about this big killer at WWDC in the previous life?

Is it still under wraps and left to surprise? ?
Or is it that the SWIFT language will be absent from the Apple Developer Conference this time?

Lin Hui thinks it is most likely the latter.

After all, it has been warmed up for several rounds before.

It doesn't make sense to keep WWDC close to the official opening, right?

Know that preheating isn't just about hyping up the event.

In fact, it is also a test of the audience.

If a thing that is used as a tool is not taken out in advance to warm up, if there are many voices of opposition, wouldn't it be a slap in the face.

A company like Apple, which is well versed in marketing, probably wouldn't do this.

Lin Hui felt that such a voice hadn't come out until the end of June.

The SWIFT language should have directly contributed to the Apple Worldwide Developers Conference.

As for why such a powerful and important product as the Swift language has failed Apple's 2014WWDC, a global developer event?
Lin Hui thinks it may be because of the delay in the development progress of the space-time Swift language.

It seems normal for a major project to have some surprises.

Especially for such a major commercial project, it is very common for accidents to occur.

Not to mention the projects in the computer field, it is common to overthrow and start over because of a little shit.

What's more, since 2012, the development team of the Swift language in the previous life has repeatedly heard voices of disagreement.

Even Chris Lattner left the Swift language development team directly around 2017 in his previous life.

Chris Lattner has been the backbone of the Swift language development team.

Since July 2010 in his previous life, Chris Lattner has been designing the Swift programming language.

After completing the infrastructure, Chris led the development team to complete syntax design, compiler, runtime, framework, IDE, and documentation.

It is precisely because of the role played by Chris Lattner that it is more prominent.

Therefore, this person has always been dubbed the "father of the Swift language".

It is really amazing that a programming language development team can run away with the backbone of the team.

The reason why Lin Hui still has an impression of this matter is because Lin Hui remembers that his friends used it as a joke.

My friend analyzed this situation with great interest at the beginning. Either Chris Lattner, the so-called "father of the Swift language", is too lonely and out of gregarious.

Either that or Chris Lattner's co-workers were too fucked up.

But no matter what the reason is, it is hard to hide the fact that the entire development team of the Swift language is a bit weird.

In this case, even the Swift development team in this time and space exists as in the previous time and space.

A little accident seems to be a normal thing.

This is not Lin Hui's poisonous milk. In fact, Lin Hui's judgment that "the Swift language project in this time and space has been frustrated" is already very friendly.

At least according to Lin Hui's judgment, even though the Swift language project was frustrated, the project and project team at least existed.

This already belongs to the category of optimistic estimation.

Personal judgments are generally very subjective. Judgments with many subjective elements are not so much judgments based on all objective conditions, but rather a kind of expectation rooted in the heart. Believe the statement/explanation only.

Lin Hui's judgment on the Swift language above is also subjective.

Lin Hui hopes that the Swift language project team can exist.

The flapping of a tiny butterfly's wings can trigger a storm in America.

Although there are many minor differences between the two time and space, Lin Hui is already used to it.

But this does not mean that Lin Hui still turns a blind eye.

For example, the fact that the Swift language cannot be delivered as promised is only a small ripple in the two dimensions of time and space.

But given the importance of the Swift language to Apple's software.

If there is a big change in a language like Swift.

Lin Hui is not sure what kind of collateral impact it will cause.

Although as a pure passerby, even if Apple goes bankrupt, it may not lose anything.

But Lin Hui didn't really want to see this.

At least Lin Hui doesn't want to see this in the short term.

In a short period of time, Lin Hui still hopes to use the apples to harvest the wool.

If there are relatively large changes in Apple's major projects.

This kind of thing is what Lin Hui does not want to see.

Therefore, Lin Hui subjectively hopes that the Swift language project exists.

As for why such a language project has to dove WWDC, Lin Hui would rather believe that such a programming language is just a setback in research.

However, the world is objective, at least it is not transferred by personal subjective consciousness.

From a purely objective perspective, Lin Hui's previous subjective judgment may have been a little too optimistic.

The Swift language in the previous life is the latest research result of programming languages ​​in the computer field.

This programming language is almost a fusion of decades of experience from the previous Apple platform.

Although this language incorporates a lot of Apple's experience.

But such a language was developed as open source on Swift.org during the development process.

Its source code, bug tracker, forum, and regular development releases were open to all in previous lives.

During the birth of the SWIFT language in the previous life: internal Apple employees worked together with hundreds of external contributors.

In this way, the Swift language in the previous life can quickly support all Apple platforms and Linux.

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

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

With this kind of unremitting efforts, until the eve of Lin Hui's rebirth: the Swift language can not only develop many new applications for the Apple platform.

And also for a new set of modern server apps.

In addition, there are many wide-ranging applications.

And all of this, it is not difficult to find that the use of love power generation by external contributors has greatly accelerated the growth of the Swift language.

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

I am afraid that the growth rate will also be greatly slowed down.

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

In this case, objectively judged:

Lin Hui couldn't help but suspect that Apple's development of the SWIFT language was behind closed doors.

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

It sounds weird, but it could happen.

Although judging from what happened in the previous life, Swift will replace (it is a replacement in the mainstream scene, not completely replace) Objective-C, which is an inevitable trend.

But people didn't think so when the Swift language first appeared in the previous life.

Although it is not difficult to switch to Swift when you have already mastered Objective-C.

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

In the case that the interface and most of the logic are written in Swift language, but the bottom layer of many projects uses the core library of the bottom layer of many projects but uses C language or C++ language.

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

In addition, when the Swift language first appeared, there were still many libraries written in Objective-C, and the use of these libraries required certain Objective-C knowledge.

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

When doing some development, it is still inseparable from Objective-C.

Likewise with any functionality written in Swift, the same can be done with Objective-C though.

When the Swift language was first born, the cost of learning was not particularly simplified.

So why bother learning a new, separate programming language?
Especially since a new, separate programming language seems a bit tasteless.

If measured by "chicken ribs".

It seems that there is a reason why Apple has not developed the Swift language to replace Objective-C even in this life.

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 takes a genius push.

Apple has a corresponding demand for developing Swift.

There is a corresponding reason for not developing.

As for whether there is Swift in this space-time.

For the time being, Lin Hui doesn't want to draw conclusions too arbitrarily.

Everything will be discussed after further and more definite information is available.

And before that.

Forest ash has to grow quickly to a certain height.

This height is not just the height of wealth.

Rather, it refers to new heights in capability.

If Lin Hui does not have the corresponding strength.

Even if the Swift language really undergoes major changes compared to the previous life.

With Lin Hui's current strength, it is impossible to extract chestnuts from Zhonghuo.

On the contrary, it is easy to catch fire.

It is different when Lin Hui has strong strength.

The flapping of a tiny butterfly's wings can trigger a storm in America.

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

Just kill the crazy flapping butterfly at the very beginning.

The same reason, when Lin Hui has enough strength.

Lin Hui can control variables.

If there is a major change in the Swift language, the puzzle of the Swift language in the previous life is missing.

After possessing strong strength, Lin Hui can completely complete this puzzle.

As for Lin Hui, what are the benefits of completing this puzzle?

Maintaining the branches of the timeline is one aspect of 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 thinks that the product with relatively high value (direct and indirect economic value of hundreds of billions of dollars) and almost a finished product is probably only fuchsia OS.

If Lin Hui has strong strength in the future and has many resources (the resources here include but 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 "transport" and it's over.

But if Lin Hui is not strong enough to handle the corresponding resource integration alone.

(ps: ... Although the so-called "powerlessness" is an extremely low probability event, even if it is possible, Lin Hui has to prepare risk avoidance measures in advance.)
In such a situation where his strength is insufficient, if Lin Hui still wants to carry it.

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

Then when integrating resources, how should other aspects or higher levels believe that Lin Hui has the strength to handle the operating system?
Ideally speaking, the most reliable way is that Lin Hui has previous experience in successfully developing an operating system.

If Lin Hui had successful experience in developing an operating system before.

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

But that's basically unrealistic.

Due to various external reasons, it is impossible for Lin Hui to engage in individual operating systems to practice before carrying out an operating system.

It is easy to cause some unnecessary troubles.

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 a one-off thing after all.

From this point of view, even Lin Hui's future is limitless.

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

(End of this chapter)