SlideShare a Scribd company logo
Full download ebook at ebookmass.com
React and React Native - Fifth Edition
Mikhail Sakhniuk
https://ebookmass.com/product/react-and-react-
native-fifth-edition-mikhail-sakhniuk/
Download more ebook from https://ebookmass.com
More products digital (pdf, epub, mobi) instant
download maybe you interests ...
Test-Driven Development with React and TypeScript:
Building Maintainable React Applications 2nd Edition
Juntao Qiu
https://ebookmass.com/product/test-driven-development-with-react-
and-typescript-building-maintainable-react-applications-2nd-
edition-juntao-qiu/
Master React in 5 Days: Become a React Expert in Under
a Week Eric Sarrion
https://ebookmass.com/product/master-react-in-5-days-become-a-
react-expert-in-under-a-week-eric-sarrion/
Master React in 5 Days: Become a React Expert in Under
a Week Eric Sarrion
https://ebookmass.com/product/master-react-in-5-days-become-a-
react-expert-in-under-a-week-eric-sarrion-2/
React Hooks in Action MEAP 03 John Larsen [Larsen
https://ebookmass.com/product/react-hooks-in-action-meap-03-john-
larsen-larsen/
■■■■■■ ■■ TypeScript■React■Node.js■webpack ■ Docker
Frank Zammetti
https://ebookmass.com/product/%e7%8e%b0%e4%bb%a3%e5%85%a8%e6%a0%8
8%e5%bc%80%e5%8f%91-%e4%bd%bf%e7%94%a8-
typescript%e3%80%81react%e3%80%81node-
js%e3%80%81webpack-%e5%92%8c-docker-frank-zammetti/
Native Nations: Cultures and Histories of Native North
America
https://ebookmass.com/product/native-nations-cultures-and-
histories-of-native-north-america/
PharmCards Fifth Edition
https://ebookmass.com/product/pharmcards-fifth-edition/
Stuttering Fifth Edition
https://ebookmass.com/product/stuttering-fifth-edition/
Pan-Slavism and Slavophilia in Contemporary Central and
Eastern Europe. Origins, Manifestations and Functions
Mikhail Suslov
https://ebookmass.com/product/pan-slavism-and-slavophilia-in-
contemporary-central-and-eastern-europe-origins-manifestations-
and-functions-mikhail-suslov/
PDF React and React Native - Fifth Edition Mikhail Sakhniuk download
React and React Native
Copyright © 2024 Packt Publishing
All rights reserved. No part of this book may be reproduced, stored in a
retrieval system, or transmitted in any form or by any means, without the
prior written permission of the publisher, except in the case of brief
quotations embedded in critical articles or reviews.
Every effort has been made in the preparation of this book to ensure the
accuracy of the information presented. However, the information contained in
this book is sold without warranty, either express or implied. Neither the
author, nor Packt Publishing, and its dealers and distributors will be held
liable for any damages caused or alleged to be caused directly or indirectly
by this book.
Packt Publishing has endeavored to provide trademark information about all
of the companies and products mentioned in this book by the appropriate use
of capitals. However, Packt Publishing cannot guarantee the accuracy of this
information.
Early Access Publication: React and React Native
Early Access Production Reference: B19636
Published by Packt Publishing Ltd.
Livery Place
35 Livery Street
Birmingham
B3 2PB, UK
ISBN: 978-1-80512-730-7
www.packt.com
Table of Contents
1. React and React Native, Fifth Edition: Build cross-platform JavaScript
and TypeScript apps for the web, desktop, and mobile
2. 1 Why React?
I. Before you begin: Join our book community on Discord
II. What is React?
III. React is just the view layer
IV. Simplicity is good
V. Declarative UI structures
VI. Data changes over time
VII. Performance matters
VIII. The right level of abstraction
IX. What's new in React?
X. Setup a new React project
i. Using Web Bundlers
ii. Using Frameworks
iii. Online Code Editors
XI. Summary
3. 2 Rendering with JSX
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Your first JSX content
i. Hello JSX
ii. Declarative UI structures
IV. Rendering HTML
i. Built-in HTML tags
ii. HTML tag conventions
iii. Describing UI structures
V. Creating your own JSX elements
i. Encapsulating HTML
ii. Nested elements
iii. Namespaced components
VI. Using JavaScript expressions
i. Dynamic property values and text
ii. Handling events
iii. Mapping collections to elements
VII. Building fragments of JSX
i. Using wrapper elements
ii. Using fragments
VIII. Summary
4. 3 Understanding React Components and Hooks
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Introduction to React Components
IV. What are component properties?
i. Passing property values
ii. Default property values
V. What is component state?
VI. React Hooks
VII. Maintaining state using Hooks
i. Initial state values
ii. Updating state values
VIII. Performing initialization and cleanup actions
i. Fetching component data
ii. Canceling actions and resetting state
iii. Optimizing side-effect actions
IX. Sharing data using context Hooks
X. Memoization with Hooks
i. useMemo Hook
ii. useCallback Hook
iii. useRef Hook
XI. Summary
5. 4 Event Handling, the React Way
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Declaring event handlers
i. Declaring handler functions
ii. Multiple event handlers
IV. Declaring inline event handlers
V. Binding handlers to elements
VI. Using synthetic event objects
VII. Understanding event pooling
VIII. Summary
6. 5 Crafting Reusable Components
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Reusable HTML elements
IV. The difficulty with monolithic components
i. The JSX markup
ii. Initial state
iii. Event handler implementation
V. Refactoring component structures
i. Starting with the JSX
ii. Implementing an article list component
iii. Implementing an article item component
iv. Implementing an add article component
VI. Render props
VII. Rendering component trees
VIII. Feature components and utility components
IX. Summary
7. 6 Type Checking and Validation with TypeScript
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Knowing What to Expect
i. The Importance of Props Validation
ii. Potential Issues Without Proper Validation
iii. Options for Props Validation
IV. Introduction to TypeScript
i. Why Use TypeScript?
ii. Setting Up TypeScript in a Project
iii. Basic Types in TypeScript
iv. Interfaces and Type Aliases
V. Comparing PropTypes and TypeScript
VI. Using TypeScript in React
i. Type Checking Props in React Components
ii. Typing State
iii. Typing Event Handlers
iv. Typing Context
v. Typing Refs
VII. Summary
8. 7 Handling Navigation with Routes
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Declaring routes
i. Hello route
ii. Decoupling route declarations
IV. Handling route parameters
i. Resource IDs in routes
ii. Query parameters
V. Using link components
i. Basic linking
ii. URL and query parameters
VI. Summary
9. 8 Code Splitting Using Lazy Components and Suspense
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Using the lazy API
i. Dynamic imports and bundles
ii. Making components lazy
IV. Using the Suspense component
i. Top-level Suspense components
ii. Working with spinner fallbacks
V. Avoiding lazy components
VI. Exploring lazy pages and routes
VII. Summary
10. 9 User Interface Framework Components
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Layout and organization
i. Using containers
ii. Building responsive grid layouts
IV. Using navigation components
i. Navigating with drawers
ii. Navigating with tabs
V. Collecting user input
i. Checkboxes and radio buttons
ii. Text inputs and select inputs
iii. Working with buttons
VI. Working with styles and themes
i. Making styles
ii. Customizing themes
VII. Summary
11. 10 High-Performance State Updates
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Batching state updates
IV. Prioritizing state updates
V. Handling asynchronous state updates
VI. Summary
12. 15 Why React Native?
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. What is React Native?
IV. React and JSX are familiar
V. The mobile browser experiences
VI. Android and iOS – different yet the same
VII. The case for mobile web apps
VIII. Summary
13. 16 React Native under the Hood
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Exploring React Native architecture
i. The state of web and mobile apps in the past
ii. React Native current architecture
iii. React Native future architecture
IV. Explaining JS and Native modules
i. React Navigation
ii. UI component libraries
iii. Splash screen
iv. Icons
v. Handling errors
vi. Push notifications
vii. Over the air updates
viii. JS libraries
V. Exploring React Native components and APIs
VI. Summary
14. 17 Kick-Starting React Native Projects
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Exploring React Native CLI tools
IV. Installing and using the Expo command-line tool
V. Viewing your app on your phone
VI. Viewing your app on Expo Snack
VII. Summary
15. 18 Building Responsive Layouts with Flexbox
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Introducing Flexbox
IV. Introducing React Native styles
V. Using the Styled Components library
VI. Building Flexbox layouts
i. Simple three-column layout
ii. Improved three-column layout
iii. Flexible rows
iv. Flexible grids
v. Flexible rows and columns
VII. Summary
16. 19 Navigating Between Screens
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Navigation basics
IV. Route parameters
V. The navigation header
VI. Tab and drawer navigation
VII. File-based navigation
VIII. Summary
17. 20 Rendering Item Lists
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Rendering data collections
IV. Sorting and filtering lists
V. Fetching list data
VI. Lazy list loading
VII. Implementing pull to refresh
VIII. Summary
18. 21 Showing Progress
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Understanding progress and usability
IV. Indicating progress
V. Measuring progress
VI. Exploring navigation indicators
VII. Step progress
VIII. Summary
19. 22 Geolocation and Maps
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Using Location API
IV. Rendering the Map
V. Annotating points of interest
i. Plotting points
ii. Plotting overlays
VI. Summary
20. 23 Collecting User Input
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Collecting text input
IV. Selecting from a list of options
V. Toggling between on and off
VI. Collecting date/time input
VII. Summary
21. 24 Displaying Modal Screens
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Important information
IV. Getting user confirmation
i. Displaying a success confirmation
V. Error confirmation
VI. Passive notifications
VII. Activity modals
VIII. Summary
22. 25 Responding to User Gestures
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Scrolling with your fingers
IV. Giving touch feedback
V. Using Swipeable and cancellable components
VI. Summary
23. 26 Using Animations
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Using React Native Reanimated
i. Animated API
ii. React Native Reanimated
IV. Installing the React Native Reanimated library
V. Animating layout components
VI. Animating styling components
VII. Summary
24. 27 Controlling Image Display
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Loading images
IV. Resizing images
V. Lazy image loading
VI. Rendering icons
VII. Summary
25. 29 Selecting Native UI Components Using Tamagui
I. Before you begin: Join our book community on Discord
II. Technical requirements
III. Application containers
IV. Headers and footers
V. Using layout components
VI. Collecting input using form components
VII. Summary
VIII. Further reading
React and React Native, Fifth
Edition: Build cross-platform
JavaScript and TypeScript apps for
the web, desktop, and mobile
Welcome to Packt Early Access. We’re giving you an exclusive preview of
this book before it goes on sale. It can take many months to write a book, but
our authors have cutting-edge information to share with you today. Early
Access gives you an insight into the latest developments by making chapter
drafts available. The chapters may be a little rough around the edges right
now, but our authors will update them over time.You can dip in and out
of this bookor follow alongfrom start to finish; Early Access is designed to
be flexible. We hope you enjoy getting to know more about the process of
writing a Packt book.
1. Chapter 1: Why React?
2. Chapter 2: Rendering with JSX
3. Chapter 3: Understanding React Components and Hooks
4. Chapter 4: Event Handling, the React Way
5. Chapter 5: Crafting Reusable Components
6. Chapter 6: Type Checking and Validation with TypeScript
7. Chapter 7: Handling Navigation with Routes
8. Chapter 8: Code Splitting Using Lazy Components and Suspense
9. Chapter 9: User Interface Framework Components
10. Chapter 10: High-Performance State Updates
11. Chapter 11: User Interface Framework Components
12. Chapter 12: High-Performance State Updates
13. Chapter 13: Unit Testing in React
14. Chapter 14: Server Rendering and Static Site Generation with React
Frameworks
15. Chapter 15: Why React Native?
16. Chapter 16: React Native under the Hood
17. Chapter 17: Kick-Starting React Native Projects
18. Chapter 18: Building Responsive Layouts with Flexbox
19. Chapter19: Navigating Between Screens
20. Chapter20: Rendering Item Lists
21. Chapter 21: Showing Progress
22. Chapter 22: Geolocation and Maps
23. Chapter 23: Collecting User Input
24. Chapter 24: Displaying Modal Screens
25. Chapter 25: Responding to User Gestures
26. Chapter 26: Using Animations
27. Chapter 27: Controlling Image Display
28. Chapter 28: Going Offline
29. Chapter 29: Selecting Native UI Components Using Tamagui
1 Why React?
Another random document with
no related content on Scribd:
Broward sat down by Ingrid Nashdoi. She was a short dark and petite
woman of about thirty-three. Not very good-looking but, usually,
witty and vivacious. Now, she stared at the floor, her face frozen.
"I'm sorry about Jim," he said. "But we don't have time to grieve
now. Later, perhaps."
She did not look at him but replied in a low halting voice. "He may
have been dead before the war started. I never even got to say
goodbye to him. You know what that means. What it probably did
mean."
"I don't think they got anything out of him. Otherwise, you and I
would have been arrested, too."
He jerked his head towards Scone and said, "He doesn't know you're
one of us. I want him to think you're a candidate for the Nationalists.
After this struggle with the Russ is over, we may need someone who
can report on him. Think you can do it?"
She nodded her head, and Broward returned to Scone. "She hates
the Russians," he said. "You know they took her husband away. She
doesn't know why. But she hates Ivan's guts."
"Good. Ah, here we go."
After the destroyer had berthed at Clavius, and the three entered the
base, events went swiftly if not smoothly. Scone talked to the entire
personnel over the IP, told them what had happened. Then he went
to his office and issued orders to have the arsenal cleaned out of all
portable weapons. These were transferred to the four destroyers the
Russians had assigned to Clavius as a token force.
Broward then called in his four Athenians and Scone, his five
Nationalists. The situation was explained to them, and they were
informed of what was expected of them. Even Broward was startled,
but didn't protest.
After the weapons had been placed in the destroyers, Scone ordered
the military into his office one at a time. And, one at a time, they
were disarmed and escorted by another door to the arsenal and
locked in. Three of the soldiers asked to join Scone, and he accepted
two. Several protested furiously and denounced Scone as a traitor.
Then, Scone had the civilians assembled in the large auditorium.
(Technically, all personnel were in the military, but the scientists were
only used in that capacity during emergencies.) Here, he told them
what he had done, what he planned to do—except for one thing—
and asked them if they wished to enlist. Again, he got a violent
demonstration from some and sullen silence from others. These were
locked up in the arsenal.
The others were sworn in, except for one man, Whiteside. Broward
pointed him out as an agent and informer for both the Russians and
Chinese. Scone admitted that he had not known about the triple-
dealer, but he took Broward's word and had Whiteside locked up, too.
Then, the radios of the two scout ships were smashed, and the
prisoners marched out and jammed into them. Scone told them they
were free to fly to the Russian base. Within a few minutes, the scouts
hurtled away from Clavius towards the north.
"But, Colonel," said Broward, "they can't give the identifying code to
the Russians. They'll be shot down."
"They are traitors; they prefer the Russky to us. Better for us if they
are shot down. They'll not fight for Ivan."
Broward did not have much appetite when he sat down to eat and to
listen to Scone's detailing of his plan.
"The Zemlya," he said, "has everything we need to sustain us here.
And to clothe the Earth with vegetation and replace her animal life in
the distant future when the radiation is low enough for us to return.
Her deepfreeze tanks contain seeds and plants of thousands of
different species of vegetation. They also hold, in suspended
animation, the bodies of cattle, sheep, horses, rabbits, dogs, cats,
fowl, birds, useful insects and worms. The original intention was to
reanimate these and use them on any Terrestrial-type planet the
Zemlya might find.
"Now, our bases here are self-sustaining. But, when the time comes
to return to Earth, we must have vegetation and animals. Otherwise,
what's the use?
"So, whoever holds the Zemlya holds the key to the future. We must
be the ones who hold that key. With it, we can bargain; the Russians
and the Chinese will have to agree to independence if they want to
share in the seeds and livestock."
"What if the Zemlya's commander chooses destruction of his vessel
rather than surrender?" said Broward. "Then, all of humanity will be
robbed. We'll have no future."
"I have a plan to get us aboard the Zemlya without violence."
An hour later, the four USAF destroyers accelerated outwards towards
Earth. Their radar had picked up the Zemlya; it also had detected five
other Unidentified Space Objects. These were the size of their own
craft.
Abruptly, the Zemlya radioed that it was being attacked. Then,
silence. No answer to the requests from Eratosthenes for more
information.
Scone had no doubt about the attackers' identity. "The Axis leaders
wouldn't have stayed on Earth to die," he said. "They'll be on their
way to their big base on Mars. Or, more likely, they have the same
idea as us. Capture the Zemlya."
"And if they do?" said Broward.
"We take it from them."
The four vessels continued to accelerate in the great curve which
would take them out away from the Zemlya and then would bring
them around towards the Moon again. Their path was computed to
swing them around so they would come up behind the interstellar
ship and overtake it. Though the titanic globe was capable of
eventually achieving far greater speeds than the destroyers, it was
proceeding at a comparatively slow velocity. This speed was
determined by the orbit around the Moon into which the Zemlya
intended to slip.
In ten hours, the USAF complement had curved around and were
about 10,000 kilometers from the Zemlya. Their speed was
approximately 20,000 kilometers an hour at this point, but they were
decelerating. The Moon was bulking larger; ahead of them, visible by
the eye, were two steady gleams. The Zemlya and the only Axis
vessel which had not been blown to bits or sliced to fragments.
According to the Zemlya, which was again in contact with the Russian
base, the Axis ship had been cut in two by a tongue from Zemlya.
But the interstellar ship was now defenseless. It had launched every
missile and anti-missile in its arsenal. And the fuel for the tongue-
generators was exhausted.
"Furthermore," said Shaposhnikov, commander of the Zemlya, "new
USO has been picked up on the radar. Four coming in from Earth. If
these are also Axis, then the Zemlya has only two choices. Surrender.
Or destroy itself."
"There is nothing we can do," replied Eratosthenes. "But we do not
think those USO are Axis. We detected four destroyer-sized objects
leaving the vicinity of the USAF base, and we asked them for
identification. They did not answer, but we have reason to believe
they are North American."
"Perhaps they are coming to our rescue," suggested Shaposhnikov.
"They left before anyone knew you were being attacked. Besides,
they had no orders from us."
"What do I do?" said Shaposhnikov.
Scone, who had tapped into the tight laser beam, broke it up by
sending random pulses into it. The Zemlya discontinued its beam,
and Scone then sent them a message through a pulsed tongue which
the Russian base could tap into only through a wild chance.
After transmitting the proper code identification, Scone said, "Don't
renew contact with Eratosthenes. It is held by the Axis. They're trying
to lure you close enough to grab you. We escaped the destruction of
our base. Let me aboard where we can confer about our next step.
Perhaps, we may have to go to Alpha Centaurus with you."
For several minutes, the Zemlya did not answer. Shaposhnikov must
have been unnerved. Undoubtedly, he was in a quandary. In any
case, he could not prevent the strangers from approaching. If they
were Axis, they had him at their mercy.
Such must have been his reasoning. He replied, "Come ahead."
By then, the USAF dishes had matched their speeds to that of the
Zemlya's. From a distance of only a kilometer, the sphere looked like
a small Earth. It even had the continents painted on the surface,
though the effect was spoiled by the big Russian letters painted on
the Pacific Ocean.
Scone gave a lateral thrust to his vessel, and it nudged gently into
the enormous landing-port of the sphere. Within five minutes, his
crew of ten were in the control room.
Scone did not waste any time. He drew his gun; his men followed
suit; he told Shaposhnikov what he meant to do. The Russian, a tall
thin man of about fifty, seemed numbed. Perhaps, too many
catastrophes had happened in too short a time. The death of Earth,
the attack by the Axis ships, and, now, totally unexpected, this. The
world was coming to an end in too many shapes and too swiftly.
Scone cleared the control room of all Zemlya personnel except the
commander. The others were locked up with the forty-odd men and
women who were surprised at their posts by the Americans.
Scone ordered Shaposhnikov to set up orders to the navigational
computer for a new path. This one would send the Zemlya at the
maximum acceleration endurable by the personnel towards a point in
the south polar region near Clavius. When the Zemlya reached the
proper distance, it would begin a deceleration equally taxing which
would bring it to a halt approximately half a kilometer above the
surface at the indicated point.
Shaposhnikov, speaking disjointedly like a man coming up out of a
nightmare, protested that the Zemlya was not built to stand such a
strain. Moreover, if Scone succeeded in his plan to hide the great
globe at the bottom of a chasm under an overhang.... Well, he could
only predict that the lower half of the Zemlya would be crushed
under the weight—even with the Moon's weak gravity.
"That won't harm the animal tanks," said Scone. "They're in the
upper levels. Do as I say. If you don't, I'll shoot you and set up the
computer myself."
"You are mad," said Shaposhnikov. "But I will do my best to get us
down safely. If this were ordinary war, if we weren't man's—Earth's—
last hope, I would tell you to go ahead, shoot. But...."
Ingrid Nashdoi, standing beside Broward, whispered in a trembling
voice, "The Russian is right. He is mad. It's too great a gamble. If we
lose, then everybody loses."
"Exactly what Scone is betting on," murmured Broward. "He knows
the Russians and Chinese know it, too. Like you, I'm scared. If I
could have foreseen what he was going to do, I think I'd have put a
bullet in him back at Eratosthenes. But it's too late to back out now.
We go along with him no matter what."
The voyage from the Moon and the capture of the Zemlya had taken
twelve hours. Now, with the Zemlya's mighty drive applied—and the
four destroyers riding in the landing-port—the voyage back took three
hours. During this time, the Russian base sent messages. Scone
refused to answer. He intended to tell all the Moon his plans but not
until the Zemlya was close to the end of its path. When the globe
was a thousand kilometers from the surface, and decelerating with
the force of 3g's, he and his men returned to the destroyers. All
except three, who remained with Shaposhnikov.
The destroyers streaked ahead of the Zemlya towards an entrance to
a narrow canyon. This led downwards to a chasm where Scone
intended to place the Zemlya beneath a giant overhang.
But, as the four sped towards the opening two crags, their radar
picked up four objects coming over close to the mountains to the
north. A battlebird and three destroyers. Scone knew that the
Russians had another big craft and three more destroyers available.
But they probably did not want to send them out, too, and leave the
base comparatively defenseless.
He at once radioed the commander of the Lermontov and told him
what was going on.
"We declare independence, a return to Nationalism," he concluded.
"And we call on the other bases to do the same."
The commander roared, "Unless you surrender at once, we turn on
the bonephones! And you will writhe in pain until you die, you
American swine!"
"Do that little thing," said Scone, and he laughed.
He switched on the communication beams linking the four ships and
said, "Hang on for a minute or two, men. Then, it'll be all over. For us
and for them."
Two minutes later, the pain began. A stroke of heat like lightning that
seemed to sear the brains in their skulls. They screamed, all except
Scone, who grew pale and clutched the edge of the control panel.
But the dishes were, for the next two minutes, on automatic,
unaffected by their pilots' condition.
And then, just as suddenly as it had started, the pain died. They were
left shaking and sick, but they knew they would not feel that
unbearable agony again.
"Flutter your craft as if it's going out of control," said Scone. "Make it
seem we're crashing into the entrance to the canyon."
Scone himself put the lead destroyer through the simulation of a craft
with a pain-crazed pilot at the controls. The others followed his
maneuvers, and they slipped into the canyon.
From over the top of the cliff to their left rose a glare that would
have been intolerable if the plastic over the portholes had not
automatically polarized to dim the brightness.
Broward, looking through a screen which showed the view to the
rear, cried out. Not because of the light from the atomic bomb which
had exploded on the other side of the cliff. He yelled because the top
of the Zemlya had also lit up. And he knew in that second what had
happened. The light did not come from the warhead, for an
extremely high mountain was between the huge globe and the blast.
If the upper region of the Zemlya glowed, it was because a tongue
from a Russian ship had brushed against it.
It must have been an accident, for the Russians surely had no wish
to wreck the Zemlya. If they defeated the USAF, they could recapture
the globe with no trouble.
"My God, she's falling!" yelled Broward. "Out of control!"
Scone looked once and quickly. He turned away and said, "All craft
land immediately. All personnel transfer to my ship."
The maneuver took three minutes, for the men in the other dishes
had to connect air tanks to their suits and then run from their ships
to Scone's. Moreover, one man in each destroyer was later than his
fellows since he had to set up the controls on his craft.
Scone did not explain what he meant to do until all personnel had
made the transfer. In the meantime, they were at the mercy of the
Russians if the enemy had chosen to attack over the top of the cliff.
But Scone was gambling that the Russians would be too horrified at
what was happening to the Zemlya. His own men would have been
frozen if he had not compelled them to act. The Earth dying twice
within twenty-four hours was almost more than they could endure.
Only the American commander, the man of stone, seemed not to feel.
Scone took his ship up against the face of the cliff until she was just
below the top. Here the cliff was thin because of the slope on the
other side. And here, hidden from view of the Russians, he drove a
tongue two decimeters wide through the rock.
And, at the moment three Russian destroyers hurtled over the edge,
tongues of compressed light lashing out on every side in the classic
flailing movement, Scone's beam broke through the cliff.
The three empty USAF ships, on automatic, shot upwards at a speed
that would have squeezed their human occupants into jelly—if they
had had occupants. Their tongues shot out and flailed, caught the
Russian tongues, twisted, shot out and flailed, caught the Russian
tongues, twisted as the generators within the USAF vessels strove to
outbend the Russian tongues.
Then, the American vessels rammed into the Russians, drove them
upwards, flipped them over. And all six craft fell along the cliff's face,
Russian and American intermingled, crashing into each other,
bouncing off the sheer face, exploding, their fragments colliding, and
smashed into the bottom of the canyon.
Scone did not see this, for he had completed the tongue through the
tunnel, turned it off for a few seconds, and sent a video beam
through. He was just in time to see the big battlebird start to float off
the ground where it had been waiting. Perhaps, it had not
accompanied the destroyers because of Russian contempt for
American ability. Or, perhaps, because the commander was under
orders not to risk the big ship unless necessary. Even now, the
Lermontov rose slowly as if it might take two paths: over the cliff or
towards the Zemlya. But, as it rose, Scone applied full power.
Some one, or some detecting equipment, on the Lermontov must
have caught view of the tongue as it slid through space to intercept
the battlebird. A tongue shot out towards the American beam. But
Scone, in full and superb control, bent the axis of his beam, and the
Russian missed. Then Scone's was in contact with the hull, and a hole
appeared in the irradiated plastic.
Majestically, the Lermontov continued rising—and so cut itself almost
in half. And, majestically, it fell.
Not before the Russian commander touched off all the missiles
aboard his ship in a last frenzied defense, and the missiles flew out in
all directions. Two hit the slope, blew off the face of the mountain on
the Lermontov's side, and a jet of atomic energy flamed out through
the tunnel created by Scone.
But he had dropped his craft like an elevator, was halfway down the
cliff before the blasts made his side of the mountain tremble.
Half an hour later, the base of Eratosthenes sued for peace. For the
sake of human continuity, said Panchurin, all fighting must cease
forever on the moon.
The Chinese, who had been silent up to then despite their comrades'
pleas for help, also agreed to accept the policy of Nationalism.
Now, Broward expected Scone to break down, to give way to the
strain. He would only have been human if he had done so.
He did not. Not, at least, in anyone's presence.
Broward awoke early during a sleep-period. Unable to forget the
dream he had just had, he went to find Ingrid Nashdoi. She was not
in her lab; her assistant told him that she had gone to the dome with
Scone.
Jealous, Broward hurried there and found the two standing there and
looking up at the half-Earth. Ingrid was holding a puppy in her arms.
This was one of the few animals that had been taken unharmed from
the shattered tanks of the fallen Zemlya.
Broward, looking at them, thought of the problems that faced the
Moon people. There was that of government, though this seemed for
the moment to be settled. But he knew that there would be more
conflict between the bases and that his own promotion of the
Athenian ideology would cause grave trouble.
There was also the problem of women. One woman to every three
men. How would this be solved? Was there any answer other than
heartaches, frustration, hate, even murder?
"I had a dream," said Broward to them. "I dreamed that we on the
Moon were building a great tower which would reach up to the Earth
and that was our only way to get back to Earth. But everybody spoke
a different tongue, and we couldn't understand each other. Therefore,
we kept putting the bricks in the wrong places or getting into furious
but unintelligible argument about construction."
He stopped, saw they expected more, and said, "I'm sorry. That's all
there was. But the moral is obvious."
"Yes," said Ingrid, stroking the head of the wriggling puppy. She
looked up at Earth, close to the horizon. "The physicists say it'll be
two hundred years before we can go back. Do you realize that,
barring accident or war, all three of us might live to see that day?
That we might return with our great-great-great-great-great-great
grandchildren? And we can tell them of the Earth that was, so they
will know how to build the Earth that must be."
"Two hundred years?" said Broward. "We won't be the same persons
then."
But he doubted that even the centuries could change Scone. The
man was made of rock. He would not bend or flow. And then
Broward felt sorry for him. Scone would be a fossil, a true stone man,
a petrified hero. Stone had its time and its uses. But leather also had
its time.
"We'll never get back unless we do today's work every day," said
Scone. "I'll worry about Earth when it's time to worry. Let's go; we've
work to do."
THE END
*** END OF THE PROJECT GUTENBERG EBOOK TONGUES OF THE
MOON ***
Updated editions will replace the previous one—the old editions will
be renamed.
Creating the works from print editions not protected by U.S.
copyright law means that no one owns a United States copyright in
these works, so the Foundation (and you!) can copy and distribute it
in the United States without permission and without paying
copyright royalties. Special rules, set forth in the General Terms of
Use part of this license, apply to copying and distributing Project
Gutenberg™ electronic works to protect the PROJECT GUTENBERG™
concept and trademark. Project Gutenberg is a registered trademark,
and may not be used if you charge for an eBook, except by following
the terms of the trademark license, including paying royalties for use
of the Project Gutenberg trademark. If you do not charge anything
for copies of this eBook, complying with the trademark license is
very easy. You may use this eBook for nearly any purpose such as
creation of derivative works, reports, performances and research.
Project Gutenberg eBooks may be modified and printed and given
away—you may do practically ANYTHING in the United States with
eBooks not protected by U.S. copyright law. Redistribution is subject
to the trademark license, especially commercial redistribution.
START: FULL LICENSE
THE FULL PROJECT GUTENBERG LICENSE
PLEASE READ THIS BEFORE YOU DISTRIBUTE OR USE THIS WORK
To protect the Project Gutenberg™ mission of promoting the free
distribution of electronic works, by using or distributing this work (or
any other work associated in any way with the phrase “Project
Gutenberg”), you agree to comply with all the terms of the Full
Project Gutenberg™ License available with this file or online at
www.gutenberg.org/license.
Section 1. General Terms of Use and
Redistributing Project Gutenberg™
electronic works
1.A. By reading or using any part of this Project Gutenberg™
electronic work, you indicate that you have read, understand, agree
to and accept all the terms of this license and intellectual property
(trademark/copyright) agreement. If you do not agree to abide by all
the terms of this agreement, you must cease using and return or
destroy all copies of Project Gutenberg™ electronic works in your
possession. If you paid a fee for obtaining a copy of or access to a
Project Gutenberg™ electronic work and you do not agree to be
bound by the terms of this agreement, you may obtain a refund
from the person or entity to whom you paid the fee as set forth in
paragraph 1.E.8.
1.B. “Project Gutenberg” is a registered trademark. It may only be
used on or associated in any way with an electronic work by people
who agree to be bound by the terms of this agreement. There are a
few things that you can do with most Project Gutenberg™ electronic
works even without complying with the full terms of this agreement.
See paragraph 1.C below. There are a lot of things you can do with
Project Gutenberg™ electronic works if you follow the terms of this
agreement and help preserve free future access to Project
Gutenberg™ electronic works. See paragraph 1.E below.
1.C. The Project Gutenberg Literary Archive Foundation (“the
Foundation” or PGLAF), owns a compilation copyright in the
collection of Project Gutenberg™ electronic works. Nearly all the
individual works in the collection are in the public domain in the
United States. If an individual work is unprotected by copyright law
in the United States and you are located in the United States, we do
not claim a right to prevent you from copying, distributing,
performing, displaying or creating derivative works based on the
work as long as all references to Project Gutenberg are removed. Of
course, we hope that you will support the Project Gutenberg™
mission of promoting free access to electronic works by freely
sharing Project Gutenberg™ works in compliance with the terms of
this agreement for keeping the Project Gutenberg™ name associated
with the work. You can easily comply with the terms of this
agreement by keeping this work in the same format with its attached
full Project Gutenberg™ License when you share it without charge
with others.
1.D. The copyright laws of the place where you are located also
govern what you can do with this work. Copyright laws in most
countries are in a constant state of change. If you are outside the
United States, check the laws of your country in addition to the
terms of this agreement before downloading, copying, displaying,
performing, distributing or creating derivative works based on this
work or any other Project Gutenberg™ work. The Foundation makes
no representations concerning the copyright status of any work in
any country other than the United States.
1.E. Unless you have removed all references to Project Gutenberg:
1.E.1. The following sentence, with active links to, or other
immediate access to, the full Project Gutenberg™ License must
appear prominently whenever any copy of a Project Gutenberg™
work (any work on which the phrase “Project Gutenberg” appears,
or with which the phrase “Project Gutenberg” is associated) is
accessed, displayed, performed, viewed, copied or distributed:
This eBook is for the use of anyone anywhere in the United
States and most other parts of the world at no cost and with
almost no restrictions whatsoever. You may copy it, give it away
or re-use it under the terms of the Project Gutenberg License
included with this eBook or online at www.gutenberg.org. If you
are not located in the United States, you will have to check the
laws of the country where you are located before using this
eBook.
1.E.2. If an individual Project Gutenberg™ electronic work is derived
from texts not protected by U.S. copyright law (does not contain a
notice indicating that it is posted with permission of the copyright
holder), the work can be copied and distributed to anyone in the
United States without paying any fees or charges. If you are
redistributing or providing access to a work with the phrase “Project
Gutenberg” associated with or appearing on the work, you must
comply either with the requirements of paragraphs 1.E.1 through
1.E.7 or obtain permission for the use of the work and the Project
Gutenberg™ trademark as set forth in paragraphs 1.E.8 or 1.E.9.
1.E.3. If an individual Project Gutenberg™ electronic work is posted
with the permission of the copyright holder, your use and distribution
must comply with both paragraphs 1.E.1 through 1.E.7 and any
additional terms imposed by the copyright holder. Additional terms
will be linked to the Project Gutenberg™ License for all works posted
with the permission of the copyright holder found at the beginning
of this work.
1.E.4. Do not unlink or detach or remove the full Project
Gutenberg™ License terms from this work, or any files containing a
part of this work or any other work associated with Project
Gutenberg™.
1.E.5. Do not copy, display, perform, distribute or redistribute this
electronic work, or any part of this electronic work, without
prominently displaying the sentence set forth in paragraph 1.E.1
with active links or immediate access to the full terms of the Project
Gutenberg™ License.
1.E.6. You may convert to and distribute this work in any binary,
compressed, marked up, nonproprietary or proprietary form,
including any word processing or hypertext form. However, if you
provide access to or distribute copies of a Project Gutenberg™ work
in a format other than “Plain Vanilla ASCII” or other format used in
the official version posted on the official Project Gutenberg™ website
(www.gutenberg.org), you must, at no additional cost, fee or
expense to the user, provide a copy, a means of exporting a copy, or
a means of obtaining a copy upon request, of the work in its original
“Plain Vanilla ASCII” or other form. Any alternate format must
include the full Project Gutenberg™ License as specified in
paragraph 1.E.1.
1.E.7. Do not charge a fee for access to, viewing, displaying,
performing, copying or distributing any Project Gutenberg™ works
unless you comply with paragraph 1.E.8 or 1.E.9.
1.E.8. You may charge a reasonable fee for copies of or providing
access to or distributing Project Gutenberg™ electronic works
provided that:
• You pay a royalty fee of 20% of the gross profits you derive
from the use of Project Gutenberg™ works calculated using the
method you already use to calculate your applicable taxes. The
fee is owed to the owner of the Project Gutenberg™ trademark,
but he has agreed to donate royalties under this paragraph to
the Project Gutenberg Literary Archive Foundation. Royalty
payments must be paid within 60 days following each date on
which you prepare (or are legally required to prepare) your
periodic tax returns. Royalty payments should be clearly marked
as such and sent to the Project Gutenberg Literary Archive
Foundation at the address specified in Section 4, “Information
about donations to the Project Gutenberg Literary Archive
Foundation.”
• You provide a full refund of any money paid by a user who
notifies you in writing (or by e-mail) within 30 days of receipt
that s/he does not agree to the terms of the full Project
Gutenberg™ License. You must require such a user to return or
destroy all copies of the works possessed in a physical medium
and discontinue all use of and all access to other copies of
Project Gutenberg™ works.
• You provide, in accordance with paragraph 1.F.3, a full refund of
any money paid for a work or a replacement copy, if a defect in
the electronic work is discovered and reported to you within 90
days of receipt of the work.
• You comply with all other terms of this agreement for free
distribution of Project Gutenberg™ works.
1.E.9. If you wish to charge a fee or distribute a Project Gutenberg™
electronic work or group of works on different terms than are set
forth in this agreement, you must obtain permission in writing from
the Project Gutenberg Literary Archive Foundation, the manager of
the Project Gutenberg™ trademark. Contact the Foundation as set
forth in Section 3 below.
1.F.
1.F.1. Project Gutenberg volunteers and employees expend
considerable effort to identify, do copyright research on, transcribe
and proofread works not protected by U.S. copyright law in creating
the Project Gutenberg™ collection. Despite these efforts, Project
Gutenberg™ electronic works, and the medium on which they may
be stored, may contain “Defects,” such as, but not limited to,
incomplete, inaccurate or corrupt data, transcription errors, a
copyright or other intellectual property infringement, a defective or
damaged disk or other medium, a computer virus, or computer
codes that damage or cannot be read by your equipment.
1.F.2. LIMITED WARRANTY, DISCLAIMER OF DAMAGES - Except for
the “Right of Replacement or Refund” described in paragraph 1.F.3,
the Project Gutenberg Literary Archive Foundation, the owner of the
Project Gutenberg™ trademark, and any other party distributing a
Project Gutenberg™ electronic work under this agreement, disclaim
all liability to you for damages, costs and expenses, including legal
fees. YOU AGREE THAT YOU HAVE NO REMEDIES FOR
NEGLIGENCE, STRICT LIABILITY, BREACH OF WARRANTY OR
BREACH OF CONTRACT EXCEPT THOSE PROVIDED IN PARAGRAPH
1.F.3. YOU AGREE THAT THE FOUNDATION, THE TRADEMARK
OWNER, AND ANY DISTRIBUTOR UNDER THIS AGREEMENT WILL
NOT BE LIABLE TO YOU FOR ACTUAL, DIRECT, INDIRECT,
CONSEQUENTIAL, PUNITIVE OR INCIDENTAL DAMAGES EVEN IF
YOU GIVE NOTICE OF THE POSSIBILITY OF SUCH DAMAGE.
1.F.3. LIMITED RIGHT OF REPLACEMENT OR REFUND - If you
discover a defect in this electronic work within 90 days of receiving
it, you can receive a refund of the money (if any) you paid for it by
sending a written explanation to the person you received the work
from. If you received the work on a physical medium, you must
return the medium with your written explanation. The person or
entity that provided you with the defective work may elect to provide
a replacement copy in lieu of a refund. If you received the work
electronically, the person or entity providing it to you may choose to
give you a second opportunity to receive the work electronically in
lieu of a refund. If the second copy is also defective, you may
demand a refund in writing without further opportunities to fix the
problem.
1.F.4. Except for the limited right of replacement or refund set forth
in paragraph 1.F.3, this work is provided to you ‘AS-IS’, WITH NO
OTHER WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR ANY PURPOSE.
1.F.5. Some states do not allow disclaimers of certain implied
warranties or the exclusion or limitation of certain types of damages.
If any disclaimer or limitation set forth in this agreement violates the
law of the state applicable to this agreement, the agreement shall be
interpreted to make the maximum disclaimer or limitation permitted
by the applicable state law. The invalidity or unenforceability of any
provision of this agreement shall not void the remaining provisions.
1.F.6. INDEMNITY - You agree to indemnify and hold the Foundation,
the trademark owner, any agent or employee of the Foundation,
anyone providing copies of Project Gutenberg™ electronic works in
accordance with this agreement, and any volunteers associated with
the production, promotion and distribution of Project Gutenberg™
electronic works, harmless from all liability, costs and expenses,
including legal fees, that arise directly or indirectly from any of the
following which you do or cause to occur: (a) distribution of this or
any Project Gutenberg™ work, (b) alteration, modification, or
additions or deletions to any Project Gutenberg™ work, and (c) any
Defect you cause.
Section 2. Information about the Mission
of Project Gutenberg™
Project Gutenberg™ is synonymous with the free distribution of
electronic works in formats readable by the widest variety of
computers including obsolete, old, middle-aged and new computers.
It exists because of the efforts of hundreds of volunteers and
donations from people in all walks of life.
Volunteers and financial support to provide volunteers with the
assistance they need are critical to reaching Project Gutenberg™’s
goals and ensuring that the Project Gutenberg™ collection will
remain freely available for generations to come. In 2001, the Project
Gutenberg Literary Archive Foundation was created to provide a
secure and permanent future for Project Gutenberg™ and future
generations. To learn more about the Project Gutenberg Literary
Archive Foundation and how your efforts and donations can help,
see Sections 3 and 4 and the Foundation information page at
www.gutenberg.org.
Section 3. Information about the Project
Gutenberg Literary Archive Foundation
The Project Gutenberg Literary Archive Foundation is a non-profit
501(c)(3) educational corporation organized under the laws of the
state of Mississippi and granted tax exempt status by the Internal
Revenue Service. The Foundation’s EIN or federal tax identification
number is 64-6221541. Contributions to the Project Gutenberg
Literary Archive Foundation are tax deductible to the full extent
permitted by U.S. federal laws and your state’s laws.
The Foundation’s business office is located at 809 North 1500 West,
Salt Lake City, UT 84116, (801) 596-1887. Email contact links and up
to date contact information can be found at the Foundation’s website
and official page at www.gutenberg.org/contact
Section 4. Information about Donations to
the Project Gutenberg Literary Archive
Foundation
Project Gutenberg™ depends upon and cannot survive without
widespread public support and donations to carry out its mission of
increasing the number of public domain and licensed works that can
be freely distributed in machine-readable form accessible by the
widest array of equipment including outdated equipment. Many
small donations ($1 to $5,000) are particularly important to
maintaining tax exempt status with the IRS.
The Foundation is committed to complying with the laws regulating
charities and charitable donations in all 50 states of the United
States. Compliance requirements are not uniform and it takes a
considerable effort, much paperwork and many fees to meet and
keep up with these requirements. We do not solicit donations in
locations where we have not received written confirmation of
compliance. To SEND DONATIONS or determine the status of
compliance for any particular state visit www.gutenberg.org/donate.
While we cannot and do not solicit contributions from states where
we have not met the solicitation requirements, we know of no
prohibition against accepting unsolicited donations from donors in
such states who approach us with offers to donate.
International donations are gratefully accepted, but we cannot make
any statements concerning tax treatment of donations received from
outside the United States. U.S. laws alone swamp our small staff.
Please check the Project Gutenberg web pages for current donation
methods and addresses. Donations are accepted in a number of
other ways including checks, online payments and credit card
donations. To donate, please visit: www.gutenberg.org/donate.
Section 5. General Information About
Project Gutenberg™ electronic works
Professor Michael S. Hart was the originator of the Project
Gutenberg™ concept of a library of electronic works that could be
freely shared with anyone. For forty years, he produced and
distributed Project Gutenberg™ eBooks with only a loose network of
volunteer support.
Project Gutenberg™ eBooks are often created from several printed
editions, all of which are confirmed as not protected by copyright in
the U.S. unless a copyright notice is included. Thus, we do not
necessarily keep eBooks in compliance with any particular paper
edition.
Most people start at our website which has the main PG search
facility: www.gutenberg.org.
This website includes information about Project Gutenberg™,
including how to make donations to the Project Gutenberg Literary
Archive Foundation, how to help produce our new eBooks, and how
to subscribe to our email newsletter to hear about new eBooks.

More Related Content

PDF
React and React Native - Fifth Edition Mikhail Sakhniuk
PDF
React and React Native - Fifth Edition Mikhail Sakhniuk
PDF
React and React Native - Fifth Edition Mikhail Sakhniuk
PDF
[PDF Download] Architecting ASP.NET Core Applications Carl-Hugo Marcotte full...
PDF
Architecting ASP.NET Core Applications Carl-Hugo Marcotte
PDF
React 18 Design Patterns And Best Practices Fourth Edition Early Access 4 Con...
PDF
C# 12 and .NET 8 Modern Cross-Platform Development Fundamentals 8th Edition M...
PPTX
The top real-life React app examples
React and React Native - Fifth Edition Mikhail Sakhniuk
React and React Native - Fifth Edition Mikhail Sakhniuk
React and React Native - Fifth Edition Mikhail Sakhniuk
[PDF Download] Architecting ASP.NET Core Applications Carl-Hugo Marcotte full...
Architecting ASP.NET Core Applications Carl-Hugo Marcotte
React 18 Design Patterns And Best Practices Fourth Edition Early Access 4 Con...
C# 12 and .NET 8 Modern Cross-Platform Development Fundamentals 8th Edition M...
The top real-life React app examples

Similar to PDF React and React Native - Fifth Edition Mikhail Sakhniuk download (20)

PDF
Getting MEAN with Mongo Express Angular and Node 1st Edition Simon Holmes
PDF
Ionic in Action Hybrid Mobile Apps with Ionic and AngularJS 1st Edition Jerem...
PDF
Getting MEAN with Mongo Express Angular and Node 1st Edition Simon Holmes
PDF
Continuous Delivery in Java Essential Tools and Best Practices for Deploying ...
PDF
(Ebook) JavaScript Application Design: A Build First Approach by Nicolas Be...
PDF
Top React Native Interview Questions and Answers in 2023
PDF
Instant Access to Continuous Delivery in Java Essential Tools and Best Practi...
PPTX
React js basics
PDF
Large Scale Apps With Vue 3 And Typescript Damiano Fusco
PDF
[Ebooks PDF] download Continuous Delivery in Java Essential Tools and Best Pr...
PDF
ASP.NET Core Razor Pages in Action 1st Edition Mike Brind All Chapters Instan...
PPTX
10 Most Popular Websites Built Using ReactJS Library
PDF
Carlos Amador .Net Portfolio
PDF
Learning Java An Introduction to Real World Programming with Java Marc Loy
PDF
The Machine Learning Solutions Architect Handbook - 2nd Edition (Early Access...
PDF
Web Development with Node and Express Leveraging the JavaScript Stack 2nd Edi...
PDF
Web Development with Node and Express Leveraging the JavaScript Stack 2nd Edi...
PDF
Download full ebook of Become a ninja with Angular Ninja Squad instant downlo...
PPTX
GDG Workshop on React (By Aakanksha Rai)
PDF
(Ebook) Programming TypeScript: Making Your JavaScript Applications Scale by ...
Getting MEAN with Mongo Express Angular and Node 1st Edition Simon Holmes
Ionic in Action Hybrid Mobile Apps with Ionic and AngularJS 1st Edition Jerem...
Getting MEAN with Mongo Express Angular and Node 1st Edition Simon Holmes
Continuous Delivery in Java Essential Tools and Best Practices for Deploying ...
(Ebook) JavaScript Application Design: A Build First Approach by Nicolas Be...
Top React Native Interview Questions and Answers in 2023
Instant Access to Continuous Delivery in Java Essential Tools and Best Practi...
React js basics
Large Scale Apps With Vue 3 And Typescript Damiano Fusco
[Ebooks PDF] download Continuous Delivery in Java Essential Tools and Best Pr...
ASP.NET Core Razor Pages in Action 1st Edition Mike Brind All Chapters Instan...
10 Most Popular Websites Built Using ReactJS Library
Carlos Amador .Net Portfolio
Learning Java An Introduction to Real World Programming with Java Marc Loy
The Machine Learning Solutions Architect Handbook - 2nd Edition (Early Access...
Web Development with Node and Express Leveraging the JavaScript Stack 2nd Edi...
Web Development with Node and Express Leveraging the JavaScript Stack 2nd Edi...
Download full ebook of Become a ninja with Angular Ninja Squad instant downlo...
GDG Workshop on React (By Aakanksha Rai)
(Ebook) Programming TypeScript: Making Your JavaScript Applications Scale by ...
Ad

Recently uploaded (20)

PPTX
GDM (1) (1).pptx small presentation for students
PDF
O7-L3 Supply Chain Operations - ICLT Program
PDF
Sports Quiz easy sports quiz sports quiz
PPTX
Microbial diseases, their pathogenesis and prophylaxis
PDF
Complications of Minimal Access Surgery at WLH
PDF
Classroom Observation Tools for Teachers
PDF
TR - Agricultural Crops Production NC III.pdf
PDF
The Lost Whites of Pakistan by Jahanzaib Mughal.pdf
PDF
Anesthesia in Laparoscopic Surgery in India
PPTX
school management -TNTEU- B.Ed., Semester II Unit 1.pptx
PDF
FourierSeries-QuestionsWithAnswers(Part-A).pdf
PPTX
Final Presentation General Medicine 03-08-2024.pptx
PDF
01-Introduction-to-Information-Management.pdf
PDF
BÀI TẬP BỔ TRỢ 4 KỸ NĂNG TIẾNG ANH 9 GLOBAL SUCCESS - CẢ NĂM - BÁM SÁT FORM Đ...
PPTX
Pharma ospi slides which help in ospi learning
PDF
Module 4: Burden of Disease Tutorial Slides S2 2025
PPTX
Cell Structure & Organelles in detailed.
PPTX
PPH.pptx obstetrics and gynecology in nursing
PPTX
human mycosis Human fungal infections are called human mycosis..pptx
PDF
O5-L3 Freight Transport Ops (International) V1.pdf
GDM (1) (1).pptx small presentation for students
O7-L3 Supply Chain Operations - ICLT Program
Sports Quiz easy sports quiz sports quiz
Microbial diseases, their pathogenesis and prophylaxis
Complications of Minimal Access Surgery at WLH
Classroom Observation Tools for Teachers
TR - Agricultural Crops Production NC III.pdf
The Lost Whites of Pakistan by Jahanzaib Mughal.pdf
Anesthesia in Laparoscopic Surgery in India
school management -TNTEU- B.Ed., Semester II Unit 1.pptx
FourierSeries-QuestionsWithAnswers(Part-A).pdf
Final Presentation General Medicine 03-08-2024.pptx
01-Introduction-to-Information-Management.pdf
BÀI TẬP BỔ TRỢ 4 KỸ NĂNG TIẾNG ANH 9 GLOBAL SUCCESS - CẢ NĂM - BÁM SÁT FORM Đ...
Pharma ospi slides which help in ospi learning
Module 4: Burden of Disease Tutorial Slides S2 2025
Cell Structure & Organelles in detailed.
PPH.pptx obstetrics and gynecology in nursing
human mycosis Human fungal infections are called human mycosis..pptx
O5-L3 Freight Transport Ops (International) V1.pdf
Ad

PDF React and React Native - Fifth Edition Mikhail Sakhniuk download

  • 1. Full download ebook at ebookmass.com React and React Native - Fifth Edition Mikhail Sakhniuk https://ebookmass.com/product/react-and-react- native-fifth-edition-mikhail-sakhniuk/ Download more ebook from https://ebookmass.com
  • 2. More products digital (pdf, epub, mobi) instant download maybe you interests ... Test-Driven Development with React and TypeScript: Building Maintainable React Applications 2nd Edition Juntao Qiu https://ebookmass.com/product/test-driven-development-with-react- and-typescript-building-maintainable-react-applications-2nd- edition-juntao-qiu/ Master React in 5 Days: Become a React Expert in Under a Week Eric Sarrion https://ebookmass.com/product/master-react-in-5-days-become-a- react-expert-in-under-a-week-eric-sarrion/ Master React in 5 Days: Become a React Expert in Under a Week Eric Sarrion https://ebookmass.com/product/master-react-in-5-days-become-a- react-expert-in-under-a-week-eric-sarrion-2/ React Hooks in Action MEAP 03 John Larsen [Larsen https://ebookmass.com/product/react-hooks-in-action-meap-03-john- larsen-larsen/
  • 3. ■■■■■■ ■■ TypeScript■React■Node.js■webpack ■ Docker Frank Zammetti https://ebookmass.com/product/%e7%8e%b0%e4%bb%a3%e5%85%a8%e6%a0%8 8%e5%bc%80%e5%8f%91-%e4%bd%bf%e7%94%a8- typescript%e3%80%81react%e3%80%81node- js%e3%80%81webpack-%e5%92%8c-docker-frank-zammetti/ Native Nations: Cultures and Histories of Native North America https://ebookmass.com/product/native-nations-cultures-and- histories-of-native-north-america/ PharmCards Fifth Edition https://ebookmass.com/product/pharmcards-fifth-edition/ Stuttering Fifth Edition https://ebookmass.com/product/stuttering-fifth-edition/ Pan-Slavism and Slavophilia in Contemporary Central and Eastern Europe. Origins, Manifestations and Functions Mikhail Suslov https://ebookmass.com/product/pan-slavism-and-slavophilia-in- contemporary-central-and-eastern-europe-origins-manifestations- and-functions-mikhail-suslov/
  • 5. React and React Native Copyright © 2024 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. Early Access Publication: React and React Native Early Access Production Reference: B19636 Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK ISBN: 978-1-80512-730-7
  • 7. Table of Contents 1. React and React Native, Fifth Edition: Build cross-platform JavaScript and TypeScript apps for the web, desktop, and mobile 2. 1 Why React? I. Before you begin: Join our book community on Discord II. What is React? III. React is just the view layer IV. Simplicity is good V. Declarative UI structures VI. Data changes over time VII. Performance matters VIII. The right level of abstraction IX. What's new in React? X. Setup a new React project i. Using Web Bundlers ii. Using Frameworks iii. Online Code Editors XI. Summary 3. 2 Rendering with JSX I. Before you begin: Join our book community on Discord II. Technical requirements III. Your first JSX content i. Hello JSX ii. Declarative UI structures IV. Rendering HTML i. Built-in HTML tags ii. HTML tag conventions iii. Describing UI structures V. Creating your own JSX elements i. Encapsulating HTML ii. Nested elements iii. Namespaced components VI. Using JavaScript expressions i. Dynamic property values and text
  • 8. ii. Handling events iii. Mapping collections to elements VII. Building fragments of JSX i. Using wrapper elements ii. Using fragments VIII. Summary 4. 3 Understanding React Components and Hooks I. Before you begin: Join our book community on Discord II. Technical requirements III. Introduction to React Components IV. What are component properties? i. Passing property values ii. Default property values V. What is component state? VI. React Hooks VII. Maintaining state using Hooks i. Initial state values ii. Updating state values VIII. Performing initialization and cleanup actions i. Fetching component data ii. Canceling actions and resetting state iii. Optimizing side-effect actions IX. Sharing data using context Hooks X. Memoization with Hooks i. useMemo Hook ii. useCallback Hook iii. useRef Hook XI. Summary 5. 4 Event Handling, the React Way I. Before you begin: Join our book community on Discord II. Technical requirements III. Declaring event handlers i. Declaring handler functions ii. Multiple event handlers IV. Declaring inline event handlers V. Binding handlers to elements VI. Using synthetic event objects
  • 9. VII. Understanding event pooling VIII. Summary 6. 5 Crafting Reusable Components I. Before you begin: Join our book community on Discord II. Technical requirements III. Reusable HTML elements IV. The difficulty with monolithic components i. The JSX markup ii. Initial state iii. Event handler implementation V. Refactoring component structures i. Starting with the JSX ii. Implementing an article list component iii. Implementing an article item component iv. Implementing an add article component VI. Render props VII. Rendering component trees VIII. Feature components and utility components IX. Summary 7. 6 Type Checking and Validation with TypeScript I. Before you begin: Join our book community on Discord II. Technical requirements III. Knowing What to Expect i. The Importance of Props Validation ii. Potential Issues Without Proper Validation iii. Options for Props Validation IV. Introduction to TypeScript i. Why Use TypeScript? ii. Setting Up TypeScript in a Project iii. Basic Types in TypeScript iv. Interfaces and Type Aliases V. Comparing PropTypes and TypeScript VI. Using TypeScript in React i. Type Checking Props in React Components ii. Typing State iii. Typing Event Handlers iv. Typing Context
  • 10. v. Typing Refs VII. Summary 8. 7 Handling Navigation with Routes I. Before you begin: Join our book community on Discord II. Technical requirements III. Declaring routes i. Hello route ii. Decoupling route declarations IV. Handling route parameters i. Resource IDs in routes ii. Query parameters V. Using link components i. Basic linking ii. URL and query parameters VI. Summary 9. 8 Code Splitting Using Lazy Components and Suspense I. Before you begin: Join our book community on Discord II. Technical requirements III. Using the lazy API i. Dynamic imports and bundles ii. Making components lazy IV. Using the Suspense component i. Top-level Suspense components ii. Working with spinner fallbacks V. Avoiding lazy components VI. Exploring lazy pages and routes VII. Summary 10. 9 User Interface Framework Components I. Before you begin: Join our book community on Discord II. Technical requirements III. Layout and organization i. Using containers ii. Building responsive grid layouts IV. Using navigation components i. Navigating with drawers ii. Navigating with tabs V. Collecting user input
  • 11. i. Checkboxes and radio buttons ii. Text inputs and select inputs iii. Working with buttons VI. Working with styles and themes i. Making styles ii. Customizing themes VII. Summary 11. 10 High-Performance State Updates I. Before you begin: Join our book community on Discord II. Technical requirements III. Batching state updates IV. Prioritizing state updates V. Handling asynchronous state updates VI. Summary 12. 15 Why React Native? I. Before you begin: Join our book community on Discord II. Technical requirements III. What is React Native? IV. React and JSX are familiar V. The mobile browser experiences VI. Android and iOS – different yet the same VII. The case for mobile web apps VIII. Summary 13. 16 React Native under the Hood I. Before you begin: Join our book community on Discord II. Technical requirements III. Exploring React Native architecture i. The state of web and mobile apps in the past ii. React Native current architecture iii. React Native future architecture IV. Explaining JS and Native modules i. React Navigation ii. UI component libraries iii. Splash screen iv. Icons v. Handling errors vi. Push notifications
  • 12. vii. Over the air updates viii. JS libraries V. Exploring React Native components and APIs VI. Summary 14. 17 Kick-Starting React Native Projects I. Before you begin: Join our book community on Discord II. Technical requirements III. Exploring React Native CLI tools IV. Installing and using the Expo command-line tool V. Viewing your app on your phone VI. Viewing your app on Expo Snack VII. Summary 15. 18 Building Responsive Layouts with Flexbox I. Before you begin: Join our book community on Discord II. Technical requirements III. Introducing Flexbox IV. Introducing React Native styles V. Using the Styled Components library VI. Building Flexbox layouts i. Simple three-column layout ii. Improved three-column layout iii. Flexible rows iv. Flexible grids v. Flexible rows and columns VII. Summary 16. 19 Navigating Between Screens I. Before you begin: Join our book community on Discord II. Technical requirements III. Navigation basics IV. Route parameters V. The navigation header VI. Tab and drawer navigation VII. File-based navigation VIII. Summary 17. 20 Rendering Item Lists I. Before you begin: Join our book community on Discord II. Technical requirements
  • 13. III. Rendering data collections IV. Sorting and filtering lists V. Fetching list data VI. Lazy list loading VII. Implementing pull to refresh VIII. Summary 18. 21 Showing Progress I. Before you begin: Join our book community on Discord II. Technical requirements III. Understanding progress and usability IV. Indicating progress V. Measuring progress VI. Exploring navigation indicators VII. Step progress VIII. Summary 19. 22 Geolocation and Maps I. Before you begin: Join our book community on Discord II. Technical requirements III. Using Location API IV. Rendering the Map V. Annotating points of interest i. Plotting points ii. Plotting overlays VI. Summary 20. 23 Collecting User Input I. Before you begin: Join our book community on Discord II. Technical requirements III. Collecting text input IV. Selecting from a list of options V. Toggling between on and off VI. Collecting date/time input VII. Summary 21. 24 Displaying Modal Screens I. Before you begin: Join our book community on Discord II. Technical requirements III. Important information IV. Getting user confirmation
  • 14. i. Displaying a success confirmation V. Error confirmation VI. Passive notifications VII. Activity modals VIII. Summary 22. 25 Responding to User Gestures I. Before you begin: Join our book community on Discord II. Technical requirements III. Scrolling with your fingers IV. Giving touch feedback V. Using Swipeable and cancellable components VI. Summary 23. 26 Using Animations I. Before you begin: Join our book community on Discord II. Technical requirements III. Using React Native Reanimated i. Animated API ii. React Native Reanimated IV. Installing the React Native Reanimated library V. Animating layout components VI. Animating styling components VII. Summary 24. 27 Controlling Image Display I. Before you begin: Join our book community on Discord II. Technical requirements III. Loading images IV. Resizing images V. Lazy image loading VI. Rendering icons VII. Summary 25. 29 Selecting Native UI Components Using Tamagui I. Before you begin: Join our book community on Discord II. Technical requirements III. Application containers IV. Headers and footers V. Using layout components VI. Collecting input using form components
  • 16. React and React Native, Fifth Edition: Build cross-platform JavaScript and TypeScript apps for the web, desktop, and mobile Welcome to Packt Early Access. We’re giving you an exclusive preview of this book before it goes on sale. It can take many months to write a book, but our authors have cutting-edge information to share with you today. Early Access gives you an insight into the latest developments by making chapter drafts available. The chapters may be a little rough around the edges right now, but our authors will update them over time.You can dip in and out of this bookor follow alongfrom start to finish; Early Access is designed to be flexible. We hope you enjoy getting to know more about the process of writing a Packt book. 1. Chapter 1: Why React? 2. Chapter 2: Rendering with JSX 3. Chapter 3: Understanding React Components and Hooks 4. Chapter 4: Event Handling, the React Way 5. Chapter 5: Crafting Reusable Components 6. Chapter 6: Type Checking and Validation with TypeScript 7. Chapter 7: Handling Navigation with Routes 8. Chapter 8: Code Splitting Using Lazy Components and Suspense 9. Chapter 9: User Interface Framework Components 10. Chapter 10: High-Performance State Updates 11. Chapter 11: User Interface Framework Components 12. Chapter 12: High-Performance State Updates 13. Chapter 13: Unit Testing in React 14. Chapter 14: Server Rendering and Static Site Generation with React Frameworks 15. Chapter 15: Why React Native?
  • 17. 16. Chapter 16: React Native under the Hood 17. Chapter 17: Kick-Starting React Native Projects 18. Chapter 18: Building Responsive Layouts with Flexbox 19. Chapter19: Navigating Between Screens 20. Chapter20: Rendering Item Lists 21. Chapter 21: Showing Progress 22. Chapter 22: Geolocation and Maps 23. Chapter 23: Collecting User Input 24. Chapter 24: Displaying Modal Screens 25. Chapter 25: Responding to User Gestures 26. Chapter 26: Using Animations 27. Chapter 27: Controlling Image Display 28. Chapter 28: Going Offline 29. Chapter 29: Selecting Native UI Components Using Tamagui
  • 19. Another random document with no related content on Scribd:
  • 20. Broward sat down by Ingrid Nashdoi. She was a short dark and petite woman of about thirty-three. Not very good-looking but, usually, witty and vivacious. Now, she stared at the floor, her face frozen. "I'm sorry about Jim," he said. "But we don't have time to grieve now. Later, perhaps." She did not look at him but replied in a low halting voice. "He may have been dead before the war started. I never even got to say goodbye to him. You know what that means. What it probably did mean." "I don't think they got anything out of him. Otherwise, you and I would have been arrested, too." He jerked his head towards Scone and said, "He doesn't know you're one of us. I want him to think you're a candidate for the Nationalists. After this struggle with the Russ is over, we may need someone who can report on him. Think you can do it?" She nodded her head, and Broward returned to Scone. "She hates the Russians," he said. "You know they took her husband away. She doesn't know why. But she hates Ivan's guts." "Good. Ah, here we go." After the destroyer had berthed at Clavius, and the three entered the base, events went swiftly if not smoothly. Scone talked to the entire personnel over the IP, told them what had happened. Then he went to his office and issued orders to have the arsenal cleaned out of all portable weapons. These were transferred to the four destroyers the Russians had assigned to Clavius as a token force. Broward then called in his four Athenians and Scone, his five Nationalists. The situation was explained to them, and they were
  • 21. informed of what was expected of them. Even Broward was startled, but didn't protest. After the weapons had been placed in the destroyers, Scone ordered the military into his office one at a time. And, one at a time, they were disarmed and escorted by another door to the arsenal and locked in. Three of the soldiers asked to join Scone, and he accepted two. Several protested furiously and denounced Scone as a traitor. Then, Scone had the civilians assembled in the large auditorium. (Technically, all personnel were in the military, but the scientists were only used in that capacity during emergencies.) Here, he told them what he had done, what he planned to do—except for one thing— and asked them if they wished to enlist. Again, he got a violent demonstration from some and sullen silence from others. These were locked up in the arsenal. The others were sworn in, except for one man, Whiteside. Broward pointed him out as an agent and informer for both the Russians and Chinese. Scone admitted that he had not known about the triple- dealer, but he took Broward's word and had Whiteside locked up, too. Then, the radios of the two scout ships were smashed, and the prisoners marched out and jammed into them. Scone told them they were free to fly to the Russian base. Within a few minutes, the scouts hurtled away from Clavius towards the north. "But, Colonel," said Broward, "they can't give the identifying code to the Russians. They'll be shot down." "They are traitors; they prefer the Russky to us. Better for us if they are shot down. They'll not fight for Ivan." Broward did not have much appetite when he sat down to eat and to listen to Scone's detailing of his plan. "The Zemlya," he said, "has everything we need to sustain us here. And to clothe the Earth with vegetation and replace her animal life in the distant future when the radiation is low enough for us to return. Her deepfreeze tanks contain seeds and plants of thousands of
  • 22. different species of vegetation. They also hold, in suspended animation, the bodies of cattle, sheep, horses, rabbits, dogs, cats, fowl, birds, useful insects and worms. The original intention was to reanimate these and use them on any Terrestrial-type planet the Zemlya might find. "Now, our bases here are self-sustaining. But, when the time comes to return to Earth, we must have vegetation and animals. Otherwise, what's the use? "So, whoever holds the Zemlya holds the key to the future. We must be the ones who hold that key. With it, we can bargain; the Russians and the Chinese will have to agree to independence if they want to share in the seeds and livestock." "What if the Zemlya's commander chooses destruction of his vessel rather than surrender?" said Broward. "Then, all of humanity will be robbed. We'll have no future." "I have a plan to get us aboard the Zemlya without violence." An hour later, the four USAF destroyers accelerated outwards towards Earth. Their radar had picked up the Zemlya; it also had detected five other Unidentified Space Objects. These were the size of their own craft. Abruptly, the Zemlya radioed that it was being attacked. Then, silence. No answer to the requests from Eratosthenes for more information. Scone had no doubt about the attackers' identity. "The Axis leaders wouldn't have stayed on Earth to die," he said. "They'll be on their way to their big base on Mars. Or, more likely, they have the same idea as us. Capture the Zemlya." "And if they do?" said Broward. "We take it from them."
  • 23. The four vessels continued to accelerate in the great curve which would take them out away from the Zemlya and then would bring them around towards the Moon again. Their path was computed to swing them around so they would come up behind the interstellar ship and overtake it. Though the titanic globe was capable of eventually achieving far greater speeds than the destroyers, it was proceeding at a comparatively slow velocity. This speed was determined by the orbit around the Moon into which the Zemlya intended to slip. In ten hours, the USAF complement had curved around and were about 10,000 kilometers from the Zemlya. Their speed was approximately 20,000 kilometers an hour at this point, but they were decelerating. The Moon was bulking larger; ahead of them, visible by the eye, were two steady gleams. The Zemlya and the only Axis vessel which had not been blown to bits or sliced to fragments. According to the Zemlya, which was again in contact with the Russian base, the Axis ship had been cut in two by a tongue from Zemlya. But the interstellar ship was now defenseless. It had launched every missile and anti-missile in its arsenal. And the fuel for the tongue- generators was exhausted. "Furthermore," said Shaposhnikov, commander of the Zemlya, "new USO has been picked up on the radar. Four coming in from Earth. If these are also Axis, then the Zemlya has only two choices. Surrender. Or destroy itself." "There is nothing we can do," replied Eratosthenes. "But we do not think those USO are Axis. We detected four destroyer-sized objects leaving the vicinity of the USAF base, and we asked them for identification. They did not answer, but we have reason to believe they are North American." "Perhaps they are coming to our rescue," suggested Shaposhnikov. "They left before anyone knew you were being attacked. Besides, they had no orders from us." "What do I do?" said Shaposhnikov.
  • 24. Scone, who had tapped into the tight laser beam, broke it up by sending random pulses into it. The Zemlya discontinued its beam, and Scone then sent them a message through a pulsed tongue which the Russian base could tap into only through a wild chance. After transmitting the proper code identification, Scone said, "Don't renew contact with Eratosthenes. It is held by the Axis. They're trying to lure you close enough to grab you. We escaped the destruction of our base. Let me aboard where we can confer about our next step. Perhaps, we may have to go to Alpha Centaurus with you." For several minutes, the Zemlya did not answer. Shaposhnikov must have been unnerved. Undoubtedly, he was in a quandary. In any case, he could not prevent the strangers from approaching. If they were Axis, they had him at their mercy. Such must have been his reasoning. He replied, "Come ahead." By then, the USAF dishes had matched their speeds to that of the Zemlya's. From a distance of only a kilometer, the sphere looked like a small Earth. It even had the continents painted on the surface, though the effect was spoiled by the big Russian letters painted on the Pacific Ocean. Scone gave a lateral thrust to his vessel, and it nudged gently into the enormous landing-port of the sphere. Within five minutes, his crew of ten were in the control room. Scone did not waste any time. He drew his gun; his men followed suit; he told Shaposhnikov what he meant to do. The Russian, a tall thin man of about fifty, seemed numbed. Perhaps, too many catastrophes had happened in too short a time. The death of Earth, the attack by the Axis ships, and, now, totally unexpected, this. The world was coming to an end in too many shapes and too swiftly. Scone cleared the control room of all Zemlya personnel except the commander. The others were locked up with the forty-odd men and
  • 25. women who were surprised at their posts by the Americans. Scone ordered Shaposhnikov to set up orders to the navigational computer for a new path. This one would send the Zemlya at the maximum acceleration endurable by the personnel towards a point in the south polar region near Clavius. When the Zemlya reached the proper distance, it would begin a deceleration equally taxing which would bring it to a halt approximately half a kilometer above the surface at the indicated point. Shaposhnikov, speaking disjointedly like a man coming up out of a nightmare, protested that the Zemlya was not built to stand such a strain. Moreover, if Scone succeeded in his plan to hide the great globe at the bottom of a chasm under an overhang.... Well, he could only predict that the lower half of the Zemlya would be crushed under the weight—even with the Moon's weak gravity. "That won't harm the animal tanks," said Scone. "They're in the upper levels. Do as I say. If you don't, I'll shoot you and set up the computer myself." "You are mad," said Shaposhnikov. "But I will do my best to get us down safely. If this were ordinary war, if we weren't man's—Earth's— last hope, I would tell you to go ahead, shoot. But...." Ingrid Nashdoi, standing beside Broward, whispered in a trembling voice, "The Russian is right. He is mad. It's too great a gamble. If we lose, then everybody loses." "Exactly what Scone is betting on," murmured Broward. "He knows the Russians and Chinese know it, too. Like you, I'm scared. If I could have foreseen what he was going to do, I think I'd have put a bullet in him back at Eratosthenes. But it's too late to back out now. We go along with him no matter what." The voyage from the Moon and the capture of the Zemlya had taken twelve hours. Now, with the Zemlya's mighty drive applied—and the
  • 26. four destroyers riding in the landing-port—the voyage back took three hours. During this time, the Russian base sent messages. Scone refused to answer. He intended to tell all the Moon his plans but not until the Zemlya was close to the end of its path. When the globe was a thousand kilometers from the surface, and decelerating with the force of 3g's, he and his men returned to the destroyers. All except three, who remained with Shaposhnikov. The destroyers streaked ahead of the Zemlya towards an entrance to a narrow canyon. This led downwards to a chasm where Scone intended to place the Zemlya beneath a giant overhang. But, as the four sped towards the opening two crags, their radar picked up four objects coming over close to the mountains to the north. A battlebird and three destroyers. Scone knew that the Russians had another big craft and three more destroyers available. But they probably did not want to send them out, too, and leave the base comparatively defenseless. He at once radioed the commander of the Lermontov and told him what was going on. "We declare independence, a return to Nationalism," he concluded. "And we call on the other bases to do the same." The commander roared, "Unless you surrender at once, we turn on the bonephones! And you will writhe in pain until you die, you American swine!" "Do that little thing," said Scone, and he laughed. He switched on the communication beams linking the four ships and said, "Hang on for a minute or two, men. Then, it'll be all over. For us and for them." Two minutes later, the pain began. A stroke of heat like lightning that seemed to sear the brains in their skulls. They screamed, all except
  • 27. Scone, who grew pale and clutched the edge of the control panel. But the dishes were, for the next two minutes, on automatic, unaffected by their pilots' condition. And then, just as suddenly as it had started, the pain died. They were left shaking and sick, but they knew they would not feel that unbearable agony again. "Flutter your craft as if it's going out of control," said Scone. "Make it seem we're crashing into the entrance to the canyon." Scone himself put the lead destroyer through the simulation of a craft with a pain-crazed pilot at the controls. The others followed his maneuvers, and they slipped into the canyon. From over the top of the cliff to their left rose a glare that would have been intolerable if the plastic over the portholes had not automatically polarized to dim the brightness. Broward, looking through a screen which showed the view to the rear, cried out. Not because of the light from the atomic bomb which had exploded on the other side of the cliff. He yelled because the top of the Zemlya had also lit up. And he knew in that second what had happened. The light did not come from the warhead, for an extremely high mountain was between the huge globe and the blast. If the upper region of the Zemlya glowed, it was because a tongue from a Russian ship had brushed against it. It must have been an accident, for the Russians surely had no wish to wreck the Zemlya. If they defeated the USAF, they could recapture the globe with no trouble. "My God, she's falling!" yelled Broward. "Out of control!" Scone looked once and quickly. He turned away and said, "All craft land immediately. All personnel transfer to my ship."
  • 28. The maneuver took three minutes, for the men in the other dishes had to connect air tanks to their suits and then run from their ships to Scone's. Moreover, one man in each destroyer was later than his fellows since he had to set up the controls on his craft. Scone did not explain what he meant to do until all personnel had made the transfer. In the meantime, they were at the mercy of the Russians if the enemy had chosen to attack over the top of the cliff. But Scone was gambling that the Russians would be too horrified at what was happening to the Zemlya. His own men would have been frozen if he had not compelled them to act. The Earth dying twice within twenty-four hours was almost more than they could endure. Only the American commander, the man of stone, seemed not to feel. Scone took his ship up against the face of the cliff until she was just below the top. Here the cliff was thin because of the slope on the other side. And here, hidden from view of the Russians, he drove a tongue two decimeters wide through the rock. And, at the moment three Russian destroyers hurtled over the edge, tongues of compressed light lashing out on every side in the classic flailing movement, Scone's beam broke through the cliff. The three empty USAF ships, on automatic, shot upwards at a speed that would have squeezed their human occupants into jelly—if they had had occupants. Their tongues shot out and flailed, caught the Russian tongues, twisted, shot out and flailed, caught the Russian tongues, twisted as the generators within the USAF vessels strove to outbend the Russian tongues. Then, the American vessels rammed into the Russians, drove them upwards, flipped them over. And all six craft fell along the cliff's face, Russian and American intermingled, crashing into each other, bouncing off the sheer face, exploding, their fragments colliding, and smashed into the bottom of the canyon.
  • 29. Scone did not see this, for he had completed the tongue through the tunnel, turned it off for a few seconds, and sent a video beam through. He was just in time to see the big battlebird start to float off the ground where it had been waiting. Perhaps, it had not accompanied the destroyers because of Russian contempt for American ability. Or, perhaps, because the commander was under orders not to risk the big ship unless necessary. Even now, the Lermontov rose slowly as if it might take two paths: over the cliff or towards the Zemlya. But, as it rose, Scone applied full power. Some one, or some detecting equipment, on the Lermontov must have caught view of the tongue as it slid through space to intercept the battlebird. A tongue shot out towards the American beam. But Scone, in full and superb control, bent the axis of his beam, and the Russian missed. Then Scone's was in contact with the hull, and a hole appeared in the irradiated plastic. Majestically, the Lermontov continued rising—and so cut itself almost in half. And, majestically, it fell. Not before the Russian commander touched off all the missiles aboard his ship in a last frenzied defense, and the missiles flew out in all directions. Two hit the slope, blew off the face of the mountain on the Lermontov's side, and a jet of atomic energy flamed out through the tunnel created by Scone. But he had dropped his craft like an elevator, was halfway down the cliff before the blasts made his side of the mountain tremble. Half an hour later, the base of Eratosthenes sued for peace. For the sake of human continuity, said Panchurin, all fighting must cease forever on the moon. The Chinese, who had been silent up to then despite their comrades' pleas for help, also agreed to accept the policy of Nationalism. Now, Broward expected Scone to break down, to give way to the strain. He would only have been human if he had done so. He did not. Not, at least, in anyone's presence.
  • 30. Broward awoke early during a sleep-period. Unable to forget the dream he had just had, he went to find Ingrid Nashdoi. She was not in her lab; her assistant told him that she had gone to the dome with Scone. Jealous, Broward hurried there and found the two standing there and looking up at the half-Earth. Ingrid was holding a puppy in her arms. This was one of the few animals that had been taken unharmed from the shattered tanks of the fallen Zemlya. Broward, looking at them, thought of the problems that faced the Moon people. There was that of government, though this seemed for the moment to be settled. But he knew that there would be more conflict between the bases and that his own promotion of the Athenian ideology would cause grave trouble. There was also the problem of women. One woman to every three men. How would this be solved? Was there any answer other than heartaches, frustration, hate, even murder? "I had a dream," said Broward to them. "I dreamed that we on the Moon were building a great tower which would reach up to the Earth and that was our only way to get back to Earth. But everybody spoke a different tongue, and we couldn't understand each other. Therefore, we kept putting the bricks in the wrong places or getting into furious but unintelligible argument about construction." He stopped, saw they expected more, and said, "I'm sorry. That's all there was. But the moral is obvious." "Yes," said Ingrid, stroking the head of the wriggling puppy. She looked up at Earth, close to the horizon. "The physicists say it'll be two hundred years before we can go back. Do you realize that, barring accident or war, all three of us might live to see that day? That we might return with our great-great-great-great-great-great grandchildren? And we can tell them of the Earth that was, so they will know how to build the Earth that must be."
  • 31. "Two hundred years?" said Broward. "We won't be the same persons then." But he doubted that even the centuries could change Scone. The man was made of rock. He would not bend or flow. And then Broward felt sorry for him. Scone would be a fossil, a true stone man, a petrified hero. Stone had its time and its uses. But leather also had its time. "We'll never get back unless we do today's work every day," said Scone. "I'll worry about Earth when it's time to worry. Let's go; we've work to do." THE END
  • 32. *** END OF THE PROJECT GUTENBERG EBOOK TONGUES OF THE MOON *** Updated editions will replace the previous one—the old editions will be renamed. Creating the works from print editions not protected by U.S. copyright law means that no one owns a United States copyright in these works, so the Foundation (and you!) can copy and distribute it in the United States without permission and without paying copyright royalties. Special rules, set forth in the General Terms of Use part of this license, apply to copying and distributing Project Gutenberg™ electronic works to protect the PROJECT GUTENBERG™ concept and trademark. Project Gutenberg is a registered trademark, and may not be used if you charge for an eBook, except by following the terms of the trademark license, including paying royalties for use of the Project Gutenberg trademark. If you do not charge anything for copies of this eBook, complying with the trademark license is very easy. You may use this eBook for nearly any purpose such as creation of derivative works, reports, performances and research. Project Gutenberg eBooks may be modified and printed and given away—you may do practically ANYTHING in the United States with eBooks not protected by U.S. copyright law. Redistribution is subject to the trademark license, especially commercial redistribution. START: FULL LICENSE
  • 33. THE FULL PROJECT GUTENBERG LICENSE
  • 34. PLEASE READ THIS BEFORE YOU DISTRIBUTE OR USE THIS WORK To protect the Project Gutenberg™ mission of promoting the free distribution of electronic works, by using or distributing this work (or any other work associated in any way with the phrase “Project Gutenberg”), you agree to comply with all the terms of the Full Project Gutenberg™ License available with this file or online at www.gutenberg.org/license. Section 1. General Terms of Use and Redistributing Project Gutenberg™ electronic works 1.A. By reading or using any part of this Project Gutenberg™ electronic work, you indicate that you have read, understand, agree to and accept all the terms of this license and intellectual property (trademark/copyright) agreement. If you do not agree to abide by all the terms of this agreement, you must cease using and return or destroy all copies of Project Gutenberg™ electronic works in your possession. If you paid a fee for obtaining a copy of or access to a Project Gutenberg™ electronic work and you do not agree to be bound by the terms of this agreement, you may obtain a refund from the person or entity to whom you paid the fee as set forth in paragraph 1.E.8. 1.B. “Project Gutenberg” is a registered trademark. It may only be used on or associated in any way with an electronic work by people who agree to be bound by the terms of this agreement. There are a few things that you can do with most Project Gutenberg™ electronic works even without complying with the full terms of this agreement. See paragraph 1.C below. There are a lot of things you can do with Project Gutenberg™ electronic works if you follow the terms of this agreement and help preserve free future access to Project Gutenberg™ electronic works. See paragraph 1.E below.
  • 35. 1.C. The Project Gutenberg Literary Archive Foundation (“the Foundation” or PGLAF), owns a compilation copyright in the collection of Project Gutenberg™ electronic works. Nearly all the individual works in the collection are in the public domain in the United States. If an individual work is unprotected by copyright law in the United States and you are located in the United States, we do not claim a right to prevent you from copying, distributing, performing, displaying or creating derivative works based on the work as long as all references to Project Gutenberg are removed. Of course, we hope that you will support the Project Gutenberg™ mission of promoting free access to electronic works by freely sharing Project Gutenberg™ works in compliance with the terms of this agreement for keeping the Project Gutenberg™ name associated with the work. You can easily comply with the terms of this agreement by keeping this work in the same format with its attached full Project Gutenberg™ License when you share it without charge with others. 1.D. The copyright laws of the place where you are located also govern what you can do with this work. Copyright laws in most countries are in a constant state of change. If you are outside the United States, check the laws of your country in addition to the terms of this agreement before downloading, copying, displaying, performing, distributing or creating derivative works based on this work or any other Project Gutenberg™ work. The Foundation makes no representations concerning the copyright status of any work in any country other than the United States. 1.E. Unless you have removed all references to Project Gutenberg: 1.E.1. The following sentence, with active links to, or other immediate access to, the full Project Gutenberg™ License must appear prominently whenever any copy of a Project Gutenberg™ work (any work on which the phrase “Project Gutenberg” appears, or with which the phrase “Project Gutenberg” is associated) is accessed, displayed, performed, viewed, copied or distributed:
  • 36. This eBook is for the use of anyone anywhere in the United States and most other parts of the world at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at www.gutenberg.org. If you are not located in the United States, you will have to check the laws of the country where you are located before using this eBook. 1.E.2. If an individual Project Gutenberg™ electronic work is derived from texts not protected by U.S. copyright law (does not contain a notice indicating that it is posted with permission of the copyright holder), the work can be copied and distributed to anyone in the United States without paying any fees or charges. If you are redistributing or providing access to a work with the phrase “Project Gutenberg” associated with or appearing on the work, you must comply either with the requirements of paragraphs 1.E.1 through 1.E.7 or obtain permission for the use of the work and the Project Gutenberg™ trademark as set forth in paragraphs 1.E.8 or 1.E.9. 1.E.3. If an individual Project Gutenberg™ electronic work is posted with the permission of the copyright holder, your use and distribution must comply with both paragraphs 1.E.1 through 1.E.7 and any additional terms imposed by the copyright holder. Additional terms will be linked to the Project Gutenberg™ License for all works posted with the permission of the copyright holder found at the beginning of this work. 1.E.4. Do not unlink or detach or remove the full Project Gutenberg™ License terms from this work, or any files containing a part of this work or any other work associated with Project Gutenberg™. 1.E.5. Do not copy, display, perform, distribute or redistribute this electronic work, or any part of this electronic work, without prominently displaying the sentence set forth in paragraph 1.E.1
  • 37. with active links or immediate access to the full terms of the Project Gutenberg™ License. 1.E.6. You may convert to and distribute this work in any binary, compressed, marked up, nonproprietary or proprietary form, including any word processing or hypertext form. However, if you provide access to or distribute copies of a Project Gutenberg™ work in a format other than “Plain Vanilla ASCII” or other format used in the official version posted on the official Project Gutenberg™ website (www.gutenberg.org), you must, at no additional cost, fee or expense to the user, provide a copy, a means of exporting a copy, or a means of obtaining a copy upon request, of the work in its original “Plain Vanilla ASCII” or other form. Any alternate format must include the full Project Gutenberg™ License as specified in paragraph 1.E.1. 1.E.7. Do not charge a fee for access to, viewing, displaying, performing, copying or distributing any Project Gutenberg™ works unless you comply with paragraph 1.E.8 or 1.E.9. 1.E.8. You may charge a reasonable fee for copies of or providing access to or distributing Project Gutenberg™ electronic works provided that: • You pay a royalty fee of 20% of the gross profits you derive from the use of Project Gutenberg™ works calculated using the method you already use to calculate your applicable taxes. The fee is owed to the owner of the Project Gutenberg™ trademark, but he has agreed to donate royalties under this paragraph to the Project Gutenberg Literary Archive Foundation. Royalty payments must be paid within 60 days following each date on which you prepare (or are legally required to prepare) your periodic tax returns. Royalty payments should be clearly marked as such and sent to the Project Gutenberg Literary Archive Foundation at the address specified in Section 4, “Information
  • 38. about donations to the Project Gutenberg Literary Archive Foundation.” • You provide a full refund of any money paid by a user who notifies you in writing (or by e-mail) within 30 days of receipt that s/he does not agree to the terms of the full Project Gutenberg™ License. You must require such a user to return or destroy all copies of the works possessed in a physical medium and discontinue all use of and all access to other copies of Project Gutenberg™ works. • You provide, in accordance with paragraph 1.F.3, a full refund of any money paid for a work or a replacement copy, if a defect in the electronic work is discovered and reported to you within 90 days of receipt of the work. • You comply with all other terms of this agreement for free distribution of Project Gutenberg™ works. 1.E.9. If you wish to charge a fee or distribute a Project Gutenberg™ electronic work or group of works on different terms than are set forth in this agreement, you must obtain permission in writing from the Project Gutenberg Literary Archive Foundation, the manager of the Project Gutenberg™ trademark. Contact the Foundation as set forth in Section 3 below. 1.F. 1.F.1. Project Gutenberg volunteers and employees expend considerable effort to identify, do copyright research on, transcribe and proofread works not protected by U.S. copyright law in creating the Project Gutenberg™ collection. Despite these efforts, Project Gutenberg™ electronic works, and the medium on which they may be stored, may contain “Defects,” such as, but not limited to, incomplete, inaccurate or corrupt data, transcription errors, a copyright or other intellectual property infringement, a defective or
  • 39. damaged disk or other medium, a computer virus, or computer codes that damage or cannot be read by your equipment. 1.F.2. LIMITED WARRANTY, DISCLAIMER OF DAMAGES - Except for the “Right of Replacement or Refund” described in paragraph 1.F.3, the Project Gutenberg Literary Archive Foundation, the owner of the Project Gutenberg™ trademark, and any other party distributing a Project Gutenberg™ electronic work under this agreement, disclaim all liability to you for damages, costs and expenses, including legal fees. YOU AGREE THAT YOU HAVE NO REMEDIES FOR NEGLIGENCE, STRICT LIABILITY, BREACH OF WARRANTY OR BREACH OF CONTRACT EXCEPT THOSE PROVIDED IN PARAGRAPH 1.F.3. YOU AGREE THAT THE FOUNDATION, THE TRADEMARK OWNER, AND ANY DISTRIBUTOR UNDER THIS AGREEMENT WILL NOT BE LIABLE TO YOU FOR ACTUAL, DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE OR INCIDENTAL DAMAGES EVEN IF YOU GIVE NOTICE OF THE POSSIBILITY OF SUCH DAMAGE. 1.F.3. LIMITED RIGHT OF REPLACEMENT OR REFUND - If you discover a defect in this electronic work within 90 days of receiving it, you can receive a refund of the money (if any) you paid for it by sending a written explanation to the person you received the work from. If you received the work on a physical medium, you must return the medium with your written explanation. The person or entity that provided you with the defective work may elect to provide a replacement copy in lieu of a refund. If you received the work electronically, the person or entity providing it to you may choose to give you a second opportunity to receive the work electronically in lieu of a refund. If the second copy is also defective, you may demand a refund in writing without further opportunities to fix the problem. 1.F.4. Except for the limited right of replacement or refund set forth in paragraph 1.F.3, this work is provided to you ‘AS-IS’, WITH NO OTHER WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED,
  • 40. INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PURPOSE. 1.F.5. Some states do not allow disclaimers of certain implied warranties or the exclusion or limitation of certain types of damages. If any disclaimer or limitation set forth in this agreement violates the law of the state applicable to this agreement, the agreement shall be interpreted to make the maximum disclaimer or limitation permitted by the applicable state law. The invalidity or unenforceability of any provision of this agreement shall not void the remaining provisions. 1.F.6. INDEMNITY - You agree to indemnify and hold the Foundation, the trademark owner, any agent or employee of the Foundation, anyone providing copies of Project Gutenberg™ electronic works in accordance with this agreement, and any volunteers associated with the production, promotion and distribution of Project Gutenberg™ electronic works, harmless from all liability, costs and expenses, including legal fees, that arise directly or indirectly from any of the following which you do or cause to occur: (a) distribution of this or any Project Gutenberg™ work, (b) alteration, modification, or additions or deletions to any Project Gutenberg™ work, and (c) any Defect you cause. Section 2. Information about the Mission of Project Gutenberg™ Project Gutenberg™ is synonymous with the free distribution of electronic works in formats readable by the widest variety of computers including obsolete, old, middle-aged and new computers. It exists because of the efforts of hundreds of volunteers and donations from people in all walks of life. Volunteers and financial support to provide volunteers with the assistance they need are critical to reaching Project Gutenberg™’s goals and ensuring that the Project Gutenberg™ collection will
  • 41. remain freely available for generations to come. In 2001, the Project Gutenberg Literary Archive Foundation was created to provide a secure and permanent future for Project Gutenberg™ and future generations. To learn more about the Project Gutenberg Literary Archive Foundation and how your efforts and donations can help, see Sections 3 and 4 and the Foundation information page at www.gutenberg.org. Section 3. Information about the Project Gutenberg Literary Archive Foundation The Project Gutenberg Literary Archive Foundation is a non-profit 501(c)(3) educational corporation organized under the laws of the state of Mississippi and granted tax exempt status by the Internal Revenue Service. The Foundation’s EIN or federal tax identification number is 64-6221541. Contributions to the Project Gutenberg Literary Archive Foundation are tax deductible to the full extent permitted by U.S. federal laws and your state’s laws. The Foundation’s business office is located at 809 North 1500 West, Salt Lake City, UT 84116, (801) 596-1887. Email contact links and up to date contact information can be found at the Foundation’s website and official page at www.gutenberg.org/contact Section 4. Information about Donations to the Project Gutenberg Literary Archive Foundation Project Gutenberg™ depends upon and cannot survive without widespread public support and donations to carry out its mission of increasing the number of public domain and licensed works that can be freely distributed in machine-readable form accessible by the widest array of equipment including outdated equipment. Many
  • 42. small donations ($1 to $5,000) are particularly important to maintaining tax exempt status with the IRS. The Foundation is committed to complying with the laws regulating charities and charitable donations in all 50 states of the United States. Compliance requirements are not uniform and it takes a considerable effort, much paperwork and many fees to meet and keep up with these requirements. We do not solicit donations in locations where we have not received written confirmation of compliance. To SEND DONATIONS or determine the status of compliance for any particular state visit www.gutenberg.org/donate. While we cannot and do not solicit contributions from states where we have not met the solicitation requirements, we know of no prohibition against accepting unsolicited donations from donors in such states who approach us with offers to donate. International donations are gratefully accepted, but we cannot make any statements concerning tax treatment of donations received from outside the United States. U.S. laws alone swamp our small staff. Please check the Project Gutenberg web pages for current donation methods and addresses. Donations are accepted in a number of other ways including checks, online payments and credit card donations. To donate, please visit: www.gutenberg.org/donate. Section 5. General Information About Project Gutenberg™ electronic works Professor Michael S. Hart was the originator of the Project Gutenberg™ concept of a library of electronic works that could be freely shared with anyone. For forty years, he produced and distributed Project Gutenberg™ eBooks with only a loose network of volunteer support.
  • 43. Project Gutenberg™ eBooks are often created from several printed editions, all of which are confirmed as not protected by copyright in the U.S. unless a copyright notice is included. Thus, we do not necessarily keep eBooks in compliance with any particular paper edition. Most people start at our website which has the main PG search facility: www.gutenberg.org. This website includes information about Project Gutenberg™, including how to make donations to the Project Gutenberg Literary Archive Foundation, how to help produce our new eBooks, and how to subscribe to our email newsletter to hear about new eBooks.