Encyclopedia Me 

Read My Stories

THE MOTH

First and Last Things by H. G. Wells, is part of the HackerNoon Books Series. You can jump to any chapter in this book here . FREE WILL AND PREDESTINATION FREE WILL AND PREDESTINATION. And now let me return to a point raised in the first Book in Chapter 1.9. Is the whole of this scheme of things settled and done? The whole trend of Science is to that belief. On the scientific plane one is a fatalist, the universe a system of inevitable consequences. But as I show in that section referred to, it is quite possible to accept as true in their several planes both predestination and free will. (I use free will in the sense of self-determinisn and not as it is defined by Professor William James, and predestination as equivalent to the conception of a universe rigid in time and space.) If you ask me, I think I should say I incline to believe in predestination and do quite completely believe in free will. The important belief is free will. But does the whole universe of fact, the external world about me, the mysterious internal world from which my motives rise, form one rigid and fated system as determinists teach? Do I believe that, had one a mind ideally clear and powerful, the whole universe would seem orderly and absolutely predestined? I incline to that belief. I do not harshly believe it, but I admit its large plausibility—that is all. I see no value whatever in jumping to a decision. One or two Pragmatists, so far as I can understand them, do not hold this view of predestination at all; but as a provisional assumption it underlies most scientific work. I glance at this question rather to express a detachment than a view. For me as a person this theory of predestination has no practical value. At the utmost it is an interesting theory like the theory that there is a fourth dimension. There may be a fourth dimension of space, but one gets along quite well by assuming there are just three. It may be knowable the next time I come to cross roads which I shall take. Possibly that knowledge actually exists somewhere. There are those who will tell you that they can get intimations in the matter from packs of cards or the palms of my hands, or see by peering into crystals. Of such beliefs I am entirely free. The fact is I believe that neither I know nor anybody else who is practically concerned knows which I shall take. I hesitate, I choose just as though the thing was unknowable. For me and my conduct there is that much wide practical margin of freedom. I am free and freely and responsibly making the future—so far as I am concerned. You others are equally free. On that theory I find my life will work, and on a theory of mechanical predestination nothing works. I take the former theory therefore for my everyday purposes, and as a matter of fact so does everybody else. I regard myself as a free responsible person among free responsible persons. About HackerNoon Book Series: We bring you the most important technical, scientific, and insightful public domain books. This book is part of the public domain. H. G. Wells (2009). First and Last Things: A Confession of Faith and Rule of Life. Urbana, Illinois: Project Gutenberg. Retrieved October 2022, https://www.gutenberg.org/files/4225/4225-h/4225-h.htm This eBook is for the use of anyone anywhere 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 , located at https://www.gutenberg.org/policy/license.html .

FREE WILL AND PREDESTINATION

THE LATER POSTGLACIAL PALÆOLITHIC MEN, THE FIRST TRUE MEN

Love and Mr. Lewisham by H. G. Wells, is part of the HackerNoon Books Series. You can jump to any chapter in this book here . A WITHDRAWAL CHAPTER XXX. — A WITHDRAWAL. On Tuesday Lewisham returned from Vigours’ at five—at half-past six he would go on to his science class at Walham Green—and discovered Mrs. Chaffery and Ethel in tears. He was fagged and rather anxious for some tea, but the news they had for him drove tea out of his head altogether. “He’s gone,” said Ethel. “Who’s gone? What! Not Chaffery?” Mrs. Chaffery, with a keen eye to Lewisham’s behaviour, nodded tearfully over an experienced handkerchief. Lewisham grasped the essentials of the situation forthwith, and trembled on the brink of an expletive. Ethel handed him a letter. For a moment Lewisham held this in his hand asking; questions. Mrs. Chaffery had come upon it in the case of her eight-day clock when the time to wind it came round. Chaffery, it seemed, had not been home since Saturday night. The letter was an open one addressed to Lewisham, a long rambling would-be clever letter, oddly inferior in style to Chaffery’s conversation. It had been written some hours before Chaffery’s last visit his talk then had been perhaps a sort of codicil. “The inordinate stupidity of that man Lagune is driving me out of the country,” Lewisham saw. “It has been at last a definite stumbling block—even a legal stumbling block. I fear. I am off. I skedaddle. I break ties. I shall miss our long refreshing chats—you had found me out and I could open my mind. I am sorry to part from Ethel also, but thank Heaven she has you to look to! And indeed they both have you to look to, though the ‘both’ may be a new light to you.” Lewisham growled, went from page 1 to page 3—conscious of their both looking to him now—even intensely—and discovered Chaffery in a practical vein. “There is but little light, and portable property in that house in Clapham that has escaped my lamentable improvidence, but there are one or two things—the iron-bound chest, the bureau with a broken hinge, and the large air pump—distinctly pawnable if only you can contrive to get them to a pawnshop. You have more Will power than I—I never could get the confounded things downstairs. That iron-bound box was originally mine, before I married your mother-in-law, so that I am not altogether regardless of your welfare and the necessity of giving some equivalent. Don’t judge me too harshly.” Lewisham turned over sharply without finishing that page. “My life at Clapham,” continued the letter, “has irked me for some time, and to tell you the truth, the spectacle of your vigorous young happiness—you are having a very good time, you know, fighting the world—reminded me of the passing years. To be frank in self-criticism, there is more than a touch of the New Woman about me, and I feel I have still to live my own life. What a beautiful phrase that is—to live one’s own life!—redolent of honest scorn for moral plagiarism. No Imitatio Christi in that ... I long to see more of men and cities.... I begin late, I know, to live my own life, bald as I am and grey-whiskered; but better late than never. Why should the educated girl have the monopoly of the game? And after all, the whiskers will dye.... “There are things—I touch upon them lightly—that will presently astonish Lagune.” Lewisham became more attentive. “I marvel at that man, grubbing hungry for marvels amidst the almost incredibly marvellous. What can be the nature of a man who gapes after Poltergeists with the miracle of his own silly existence (inconsequent, reasonless, unfathomably weird) nearer to him than breathing and closer than hands and feet. What is he for, that he should wonder at Poltergeists? I am astonished these by no means flimsy psychic phenomena do not turn upon their investigators, and that a Research Society of eminent illusions and hallucinations does not pursue Lagune with sceptical! inquiries. Take his house—expose the alleged man of Chelsea! A priori they might argue that a thing so vain, so unmeaning, so strongly beset by cackle, could only be the diseased imagining of some hysterical phantom. Do you believe that such a thing as Lagune exists? I must own to the gravest doubts. But happily his banker is of a more credulous type than I.... Of all that Lagune will tell you soon enough.” Lewisham read no more. “I suppose he thought himself clever when he wrote that rot,” said Lewisham bitterly, throwing the sheets forcibly athwart the table. “The simple fact is, he’s stolen, or forged, or something—and bolted.” There was a pause. “What will become of Mother?” said Ethel. Lewisham looked at Mother and thought for a moment. Then he glanced at Ethel. “We’re all in the same boat,” said Lewisham. “I don’t want to give any trouble to a single human being,” said Mrs. Chaffery. “I think you might get a man his tea, Ethel,” said Lewisham, sitting down suddenly; “anyhow.” He drummed on the table with his fingers. “I have to get to Walham Green by a quarter to seven.” “We’re all in the same boat,” he repeated after an interval, and continued drumming. He was chiefly occupied by the curious fact that they were all in the same boat. What an extraordinary faculty he had for acquiring responsibility! He looked up suddenly and caught Mrs. Chaffery’s tearful eye directed to Ethel and full of distressful interrogation, and his perplexity was suddenly changed to pity. “It’s all right, Mother,” he said. “I’m not going to be unreasonable. I’ll stand by you.” “Ah!” said Mrs. Chaffery. “As if I didn’t know!” and Ethel came and kissed him. He seemed in imminent danger of universal embraces. “I wish you’d let me have my tea,” he said. And while he had his tea he asked Mrs. Chaffery questions and tried to get the new situation into focus. But even at ten o’clock, when he was returning hot and jaded from Walham Green, he was still trying to get the situation into focus. There were vague ends and blank walls of interrogation in the matter, that perplexed him. He knew that his supper would be only the prelude to an interminable “talking over,” and indeed he did not get to bed until nearly two. By that time a course of action was already agreed upon. Mrs. Chaffery was tied to the house in Clapham by a long lease, and thither they must go. The ground floor and first floor were let unfurnished, and the rent of these practically paid the rent of the house. The Chafferys occupied basement and second floor. There was a bedroom on the second floor, formerly let to the first floor tenants, that he and Ethel could occupy, and in this an old toilet table could be put for such studies as were to be prosecuted at home. Ethel could have her typewriter in the subterranean breakfast-room. Mrs. Chaffery and Ethel must do the catering and the bulk of the housework, and as soon as possible, since letting lodgings would not square with Lewisham’s professional pride, they must get rid of the lease that bound them and take some smaller and more suburban residence. If they did that without leaving any address it might save their feelings from any return of the prodigal Chaffery. Mrs. Chaffery’s frequent and pathetic acknowledgments of Lewisham’s goodness only partly relieved his disposition to a philosophical bitterness. And the practical issues were complicated by excursions upon the subject of Chaffery, what he might have done, and where he might have gone, and whether by any chance he might not return. When at last Mrs. Chaffery, after a violent and tearful kissing and blessing of them both—they were “good dear children,” she said—had departed, Mr. and Mrs. Lewisham returned into their sitting-room. Mrs. Lewisham’s little face was enthusiastic. “You’re a Trump,” she said, extending the willing arms that were his reward. “I know,” she said, “I know, and all to-night I have been loving you. Dear! Dear! Dear....” The next day Lewisham was too full of engagements to communicate with Lagune, but the following morning he called and found the psychic investigator busy with the proofs of Hesperus. He welcomed the young man cordially nevertheless, conceiving him charged with the questions that had been promised long ago—it was evident he knew nothing of Lewisham’s marriage. Lewisham stated his case with some bluntness. “He was last here on Saturday,” said Lagune. “You have always been inclined to suspicion about him. Have you any grounds?” “You’d better read this,” said Lewisham, repressing a grim smile, and he handed Lagune Chaffery’s letter. He glanced at the little man ever and again to see if he had come to the personal portion, and for the rest of the time occupied himself with an envious inventory of the writing appointments about him. No doubt the boy with the big ears had had the same sort of thing ... When Lagune came to the question of his real identity he blew out his cheeks in the most astonishing way, but made no other sign. “Dear, dear!” he said at last. “My bankers!” He looked at Lewisham with the exaggerated mildness of his spectacled eye. “What do you think it means?” he asked. “Has he gone mad? We have been conducting some experiments involving—considerable mental strain. He and I and a lady. Hypnotic—” “I should look at my cheque-book if I were you.” Lagune produced some keys and got out his cheque book. He turned over the counterfoils. “There’s nothing wrong here,” he said, and handed the book to Lewisham. “Um,” said Lewisham. “I suppose this—I say, is this right?” He handed back the book to Lagune, open at the blank counterfoil of a cheque that had been removed. Lagune stared and passed his hand over his forehead in a confused way. “I can’t see this,” he said. Lewisham had never heard of post hypnotic suggestion and he stood incredulous. “You can’t see that?” he said. “What nonsense!” “I can’t see it,” repeated Lagune. For some seconds Lewisham could not get away from stupid repetitions of his inquiry. Then he hit upon a collateral proof. “But look here! Can you see this counterfoil?” “Plainly,” said Lagune. “Can you read the number?” “Five thousand two hundred and seventy-nine.” “Well, and this?” “Five thousand two hundred and eighty-one.” “Well—where’s five thousand two hundred and eighty?” Lagune began to look uncomfortable. “Surely,” he said, “he has not—Will you read it out—the cheque, the counterfoil I mean, that I am unable to see?” “It’s blank,” said Lewisham with an irresistible grin. “Surely,” said Lagune, and the discomfort of his expression deepened. “Do you mind if I call in a servant to confirm—?” Lewisham did not mind, and the same girl who had admitted him to the siance appeared. When she had given her evidence she went again. As she left the room by the door behind Lagune her eyes met Lewisham’s, and she lifted her eyebrows, depressed her mouth, and glanced at Lagune with a meaning expression. “I’m afraid,” said Lagune, “that I have been shabbily treated. Mr. Chaffery is a man of indisputable powers—indisputable powers; but I am afraid—I am very much afraid he has abused the conditions of the experiment. All this—and his insults—touch me rather nearly.” He paused. Lewisham rose. “Do you mind if you come again?” asked Lagune with gentle politeness. Lewisham was surprised to find himself sorry. “He was a man of extraordinary gifts,” said Lagune. “I had come to rely upon him.... My cash balance has been rather heavy lately. How he came to know of that I am unable to say. Without supposing, that is, that he had very remarkable gifts.” When Lewisham saw Lagune again he learnt the particulars of Chaffery’s misdeed and the additional fact that the “lady” had also disappeared. “That’s a good job,” he remarked selfishly. “There’s no chance of his coming back.” He spent a moment trying to imagine the “lady”; he realised more vividly than he had ever done before the narrow range of his experience, the bounds of his imagination. These people also—with grey hair and truncated honour—had their emotions I Even it may be glowing! He came back to facts. Chaffery had induced Lagune when hypnotised to sign a blank cheque as an “autograph.” “The strange thing is,” explained Lagune, “it’s doubtful if he’s legally accountable. The law is so peculiar about hypnotism and I certainly signed the cheque, you know.” The little man, in spite of his losses, was now almost cheerful again on account of a curious side issue. “You may say it is coincidence,” he said, “you may call it a fluke, but I prefer to look for some other interpretation! Consider this. The amount of my balance is a secret between me and my bankers. He never had it from me, for I did not know it—I hadn’t looked at my passbook for months. But he drew it all in one cheque, within seventeen and sixpence of the total. And the total was over five hundred pounds!” He seemed quite bright again as he culminated. “Within seventeen and sixpence,” he said. “Now how do you account for that, eh? Give me a materialistic explanation that will explain away all that. You can’t. Neither can I.” “I think I can,” said Lewisham. “Well—what is it?” Lewisham nodded towards a little drawer of the bureau. “Don’t you think—perhaps”—a little ripple of laughter passed across his mind—“he had a skeleton key?” Lagune’s face lingered amusingly in Lewisham’s mind as he returned to Clapham. But after a time that amusement passed away. He declined upon the extraordinary fact that Chaffery was his father-in-law, Mrs. Chaffery his mother-in-law, that these two and Ethel constituted his family, his clan, and that grimy graceless house up the Clapham hillside was to be his home. Home! His connexion with these things as a point of worldly departure was as inexorable now as though he had been born to it. And a year ago, except for a fading reminiscence of Ethel, none of these people had existed for him. The ways of Destiny! The happenings of the last few months, foreshortened in perspective, seemed to have almost a pantomimic rapidity. The thing took him suddenly as being laughable; and he laughed. His laugh marked an epoch. Never before had Lewisham laughed at any fix in which he had found himself! The enormous seriousness of adolescence was coming to an end; the days of his growing were numbered. It was a laugh of infinite admissions. About HackerNoon Book Series: We bring you the most important technical, scientific, and insightful public domain books. This book is part of the public domain. H. G. Wells (2006). Love and Mr. Lewisham. Urbana, Illinois: Project Gutenberg. Retrieved October 2022, from https://www.gutenberg.org/files/11640/11640-h/11640-h.htm This eBook is for the use of anyone anywhere 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, located at https://www.gutenberg.org/policy/license.html.

A WITHDRAWAL

A Short History of the World,by  H. G. Wells, is part of the HackerNoon Books Series. You can jump to any chapter in this book here . THE NEANDERTHALER AND THE RHODESIAN MAN THE NEANDERTHALER AND THE RHODESIAN MAN About fifty or sixty thousand years ago, before the climax of the Fourth Glacial Age, there lived a creature on earth so like a man that until a few years ago its remains were considered to be altogether human. We have skulls and bones of it and a great accumulation of the large implements it made and used. It made fires. It sheltered in caves from the cold. It probably dressed skins roughly and wore them. It was right-handed as men are. Yet now the ethnologists tell us these creatures were not true men. They were of a different species of the same genus. They had heavy protruding jaws and great brow ridges above the eyes and very low foreheads. Their thumbs were not opposable to the fingers as men’s are; their necks were so poised that they could not turn back their heads and look up to the sky. They probably slouched along, head down and forward. Their chinless jaw-bones resemble the Heidelberg jaw-bone and are markedly unlike human jaw-bones. And there were great differences from the human pattern in their teeth. Their cheek teeth were more complicated in structure than ours, more complicated and not less so; they had not the long fangs of our cheek teeth; and also these quasi-men had not the marked canines (dog teeth) of an ordinary human being. The capacity of their skulls was quite human, but the brain was bigger behind and lower in front than the human brain. Their intellectual faculties were differently arranged. They were not ancestral to the human line. Mentally and physically they were upon a different line from the human line. Skulls and bones of this extinct species of man were found at Neanderthal among other places, and from that place these strange proto-men have been christened Neanderthal Men, or Neanderthalers. They must have endured in Europe for many hundreds or even thousands of years. THE NEANDERTHALER, ACCORDING TO PROF. RUTOT At that time the climate and geography of our world was very different from what they are at the present time. Europe for example was covered with ice reaching as far south as the Thames and into Central Germany and Russia; there was no Channel separating Britain from France; the Mediterranean and the Red Sea were great valleys, with perhaps a chain of lakes in their deeper portions, and a great inland sea spread from the present Black Sea across South Russia and far into Central Asia. Spain and all of Europe not actually under ice consisted of bleak uplands under a harder climate than that of Labrador, and it was only when North Africa was reached that one would have found a temperate climate. Across the cold steppes of Southern Europe with its sparse arctic vegetation, drifted such hardy creatures as the woolly mammoth, and woolly rhinoceros, great oxen and reindeer, no doubt following the vegetation northward in spring and southward in autumn. Such was the scene through which the Neanderthaler wandered, gathering such subsistence as he could from small game or fruits and berries and roots. Possibly he was mainly a vegetarian, chewing twigs and roots. His level elaborate teeth suggest a largely vegetarian dietary. But we also find the long marrow bones of great animals in his caves, cracked to extract the marrow. His weapons could not have been of much avail in open conflict with great beasts, but it is supposed that he attacked them with spears at difficult river crossings and even constructed pitfalls for them. Possibly he followed the herds and preyed upon any dead that were killed in fights, and perhaps he played the part of jackal to the sabre-toothed tiger which still survived in his day. Possibly in the bitter hardships of the Glacial Ages this creature had taken to attacking animals after long ages of vegetarian adaptation. We cannot guess what this Neanderthal man looked like. He may have been very hairy and very unhuman-looking indeed. It is even doubtful if he went erect. He may have used his knuckles as well as his feet to hold himself up. Probably he went about alone or in small family groups. It is inferred from the structure of his jaw that he was incapable of speech as we understand it. For thousands of years these Neanderthalers were the highest animals that the European area had ever seen; and then some thirty or thirty-five thousand years ago as the climate grew warmer a race of kindred beings, more intelligent, knowing more, talking and co-operating together, came drifting into the Neanderthaler’s world from the south. They ousted the Neanderthalers from their caves and squatting places; they hunted the same food; they probably made war upon their grisly predecessors and killed them off. These newcomers from the south or the east—for at present we do not know their region of origin—who at last drove the Neanderthalers out of existence altogether, were beings of our own blood and kin, the first True Men. Their brain-cases and thumbs and necks and teeth were anatomically the same as our own. In a cave at Cro-Magnon and in another at Grimaldi, a number of skeletons have been found, the earliest truly human remains that are so far known. So it is our race comes into the Record of the Rocks, and the story of mankind begins. COMPARISON OF (1) MODERN SKULL AND (2) RHODESIAN SKULL Nat. Hist. Mus. The world was growing liker our own in those days though the climate was still austere. The glaciers of the Ice Age were receding in Europe; the reindeer of France and Spain presently gave way to great herds of horses as grass increased upon the steppes, and the mammoth became more and more rare in southern Europe and finally receded northward altogether .... We do not know where the True Men first originated. But in the summer of 1921, an extremely interesting skull was found together with pieces of a skeleton at Broken Hill in South Africa, which seems to be a relic of a third sort of man, intermediate in its characteristics between the Neanderthaler and the human being. The brain-case indicates a brain bigger in front and smaller behind than the Neanderthaler’s, and the skull was poised erect upon the backbone in a quite human way. The teeth also and the bones are quite human. But the face must have been ape-like with enormous brow ridges and a ridge along the middle of the skull. The creature was indeed a true man, so to speak, with an ape- like, Neanderthaler face. This Rhodesian Man is evidently still closer to real men than the Neanderthal Man. This Rhodesian skull is probably only the second of what in the end may prove to be a long list of finds of sub-human species which lived on the earth in the vast interval of time between the beginnings of the Ice Age and the appearance of their common heir, and perhaps their common exterminator, the True Man. The Rhodesian skull itself may not be very ancient. Up to the time of publishing this book there has been no exact determination of its probable age. It may be that this sub-human creature survived in South Africa until quite recent times. About HackerNoon Book Series: We bring you the most important technical, scientific, and insightful public domain books. This book is part of the public domain. H. G. Wells (2011). A Short History of the World. Urbana, Illinois: Project Gutenberg. Retrieved October 2022, from https://www.gutenberg.org/files/11870/11870-h/11870-h.htm This eBook is for the use of anyone anywhere 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 , located at https://www.gutenberg.org/policy/license.html .

THE NEANDERTHALER AND THE RHODESIAN MAN

Though many programming languages have been in use for decades, there are a few that — comparatively — have only just arrived to the world of tech. Go is one of these languages, having been designed for general programming purposes with efficiency in mind. It still has a long way to go before it rivals the popularity of C++ or even PHP, but it’s proving to be a very useful tool for more professional programmers as time goes on. Anyone looking to hit “go” on learning this language should check out the 6 best Go programming books based on Amazon reviews! As usual, this list will rank books based on the amount of reviews they received alongside their 5-star average. It will also cover books with a major focus on Go, so don’t expect any “compilation” books on this list! List of The Best Go Programming Books Ranked by Amazon Reviews 6. Introducing Go by Caleb Doxsey is a book designed for newcomers to Go that have a basic understanding of programming fundamentals. Overall reviews are positive as a result, though some argue that it might be a bit too complicated for pure beginners — and yet, they also note that it’s not complex enough for veterans. Still, what’s there is very comprehensive, and it can easily fulfill its purpose as an introduction to the language. It’s also one of the cheapest options on this list, so there’s no harm in using it as a primer before diving into a more advanced resource later on. Introducing Go Out of 142 total reviews, 58% gave this book 5 stars Reviews: $24.99 Paperback, $21,99 Digital List Price: Buy now on (Digital) or (Paperback) Amazon AbeBooks 5. Head First Go by Jay McGavren is another beginner-friendly resource for learning the language. It doesn’t cover as many bases as some reviewers would like, but many of them argue that it’s still one of the best books they’ve found on Go. Head First Go is structured in a way that anyone can follow along as they please, and the way it’s formatted allows readers to easily take in new pieces of information at their own pace. Even if it isn’t the most comprehensive resource, it’s one of the best places to start your journey with Go. Head First Go Readers should be aware that this book is somewhat outdated. While a publication date of 2019 might not seem too long, the version of Go covered in this resource is no longer supported. This is unfortunately the case for most books on this list — if not all of them — so choose each item on this list with caution. Out of 145 total reviews, 82% gave this book 5 stars Reviews: $59.99 Paperback, $50.99 Digital List Price: Buy now on (Digital) or (Paperback) Amazon AbeBooks 4. Concurrency in Go by Katherine Cox-Buday For a resource that covers more than just Go, this offering by Katherine Cox-Buday how to master the language alongside concurrency techniques. While mostly covers how the language is used for these techniques, reviewers stated that it stands as another fantastic resource for any first-time programmers out there. Concurrency in Go Some readers seem to be conflicted on how they feel about the book’s writing style, but most are very pleased with the results. If you want to dig deeper into the world of programming even outside of which languages you learn or use, Concurrency in Go is one of the best resources you can find. Out of 166 total reviews, 72% gave this book 5 stars Reviews: $49.99 Paperback, $42.99 Digital List Price: Buy now on (Digital) or (Paperback) Amazon AbeBooks 3. Black Hat Go by Tom Steele, Chris Patten, and Dan Kottmann In another case of using Go for deeper purposes, explores how the language can be used in the hands of hackers. It covers a great deal of content and ideas while exploring interactions with other languages such as MySQL. Black Hat Go However, reviewers seem to be conflicted on how useful the book actually is in the long run. Some praise its lessons and presentations while others condemn its code structures and vague instructions. It might not be the best choice for everyone, but Black Hat Go is definitely a resource to consider — especially if you embrace the “Hacker” part of HackerNoon. Out of 183 total reviews, 78% gave this book 5 stars Reviews: $39.95 Paperback, $23.99 Digital List Price: Buy now on (Digital) or (Paperback) Amazon AbeBooks 2. Learning Go by Jon Bodner , despite its name, is a better resource for more moderately experienced programmers. It goes over some of the best practices a coder can follow with Go, and it still manages to cover the basics of the language fairly well. Reviewers almost universally agree, however, that this is certainly not a book for beginners. Learning Go Even those with prior experience found it to be somewhat difficult to get through. It’s one of the more recent items on this list, so it should prove more modern than its competitors, but any lack of prior knowledge on Go can make this book a difficult choice to recommend. Out of 305 total reviews, 76% gave this book 5 stars Reviews: $59.99 Paperback, $50.99 Digital List Price: Buy now on (Digital) or (Paperback) Amazon AbeBooks 1. The Go Programming Language by Alan Donovan and Brian Kernighan Rounding off this list about the Go programming language is the aptly-named resource by Alan Donovan and Brian Kernighan. is one of the most comprehensive resources you’ll find on Go, even with its publication date of 2015. Reviewers agree that the information within is fantastic. The Go Programming Language Where this book falls short is its presentation, with many readers arguing that either the presentation or the writing style was too much of a mess to follow along with. A few of these complaints are centered around the digital version of this book, so consider checking out a physical copy instead — if you can afford it. Out of 1,232 total reviews, 81% gave this book 5 stars Reviews: $39.99 Paperback, $31.99 Digital List Price: Buy now on (Digital) or (Paperback) Amazon AbeBooks What to Look For When Choosing The Best Go Programming Book For You Though Go is constantly updated, it’s still not as widespread of a language as others out there. Even outdated books can be useful resources as long as they cover a wide variety of content. Just be sure that you can comprehend what you find in the first place! If you want a closer look at a wider variety of languages, check out the best and based on reviews! SQL Books Java books

 Follow this account for the most updated lists. 

6 Best Go Programming Books Ranked by Reviews

The First Men In The Moon, by H. G. Wells, is part of the HackerNoon Books Series. You can jump to any chapter in this book here . The Landing on the Moon The Landing on the Moon I remember how one day Cavor suddenly opened six of our shutters and blinded me so that I cried aloud at him. The whole area was moon, a stupendous scimitar of white dawn with its edge hacked out by notches of darkness, the crescent shore of an ebbing tide of darkness, out of which peaks and pinnacles came glittering into the blaze of the sun. I take it the reader has seen pictures or photographs of the moon and that I need not describe the broader features of that landscape, those spacious ring-like ranges vaster than any terrestrial mountains, their summits shining in the day, their shadows harsh and deep, the grey disordered plains, the ridges, hills, and craterlets, all passing at last from a blazing illumination into a common mystery of black. Athwart this world we were flying scarcely a hundred miles above its crests and pinnacles. And now we could see, what no eye on earth will ever see, that under the blaze of the day the harsh outlines of the rocks and ravines of the plains and crater floor grew grey and indistinct under a thickening haze, that the white of their lit surfaces broke into lumps and patches, and broke again and shrank and vanished, and that here and there strange tints of brown and olive grew and spread. But little time we had for watching then. For now we had come to the real danger of our journey. We had to drop ever closer to the moon as we spun about it, to slacken our pace and watch our chance, until at last we could dare to drop upon its surface. For Cavor that was a time of intense exertion; for me it was an anxious inactivity. I seemed perpetually to be getting out of his way. He leapt about the sphere from point to point with an agility that would have been impossible on earth. He was perpetually opening and closing the Cavorite windows, making calculations, consulting his chronometer by means of the glow lamp during those last eventful hours. For a long time we had all our windows closed and hung silently in darkness hurling through space. Then he was feeling for the shutter studs, and suddenly four windows were open. I staggered and covered my eyes, drenched and scorched and blinded by the unaccustomed splendour of the sun beneath my feet. Then again the shutters snapped, leaving my brain spinning in a darkness that pressed against the eyes. And after that I floated in another vast, black silence. Then Cavor switched on the electric light, and told me he proposed to bind all our luggage together with the blankets about it, against the concussion of our descent. We did this with our windows closed, because in that way our goods arranged themselves naturally at the centre of the sphere. That too was a strange business; we two men floating loose in that spherical space, and packing and pulling ropes. Imagine it if you can! No up nor down, and every effort resulting in unexpected movements. Now I would be pressed against the glass with the full force of Cavor’s thrust, now I would be kicking helplessly in a void. Now the star of the electric light would be overhead, now under foot. Now Cavor’s feet would float up before my eyes, and now we would be crossways to each other. But at last our goods were safely bound together in a big soft bale, all except two blankets with head holes that we were to wrap about ourselves. Then for a flash Cavor opened a window moonward, and we saw that we were dropping towards a huge central crater with a number of minor craters grouped in a sort of cross about it. And then again Cavor flung our little sphere open to the scorching, blinding sun. I think he was using the sun’s attraction as a brake. “Cover yourself with a blanket,” he cried, thrusting himself from me, and for a moment I did not understand. Then I hauled the blanket from beneath my feet and got it about me and over my head and eyes. Abruptly he closed the shutters again, snapped one open again and closed it, then suddenly began snapping them all open, each safely into its steel roller. There came a jar, and then we were rolling over and over, bumping against the glass and against the big bale of our luggage, and clutching at each other, and outside some white substance splashed as if we were rolling down a slope of snow.... Over, clutch, bump, clutch, bump, over.... Came a thud, and I was half buried under the bale of our possessions, and for a space everything was still. Then I could hear Cavor puffing and grunting, and the snapping of a shutter in its sash. I made an effort, thrust back our blanket-wrapped luggage, and emerged from beneath it. Our open windows were just visible as a deeper black set with stars. We were still alive, and we were lying in the darkness of the shadow of the wall of the great crater into which we had fallen. We sat getting our breath again, and feeling the bruises on our limbs. I don’t think either of us had had a very clear expectation of such rough handling as we had received. I struggled painfully to my feet. “And now,” said I, “to look at the landscape of the moon! But—! It’s tremendously dark, Cavor!” The glass was dewy, and as I spoke I wiped at it with my blanket. “We’re half an hour or so beyond the day,” he said. “We must wait.” It was impossible to distinguish anything. We might have been in a sphere of steel for all that we could see. My rubbing with the blanket simply smeared the glass, and as fast as I wiped it, it became opaque again with freshly condensed moisture mixed with an increasing quantity of blanket hairs. Of course I ought not to have used the blanket. In my efforts to clear the glass I slipped upon the damp surface, and hurt my shin against one of the oxygen cylinders that protruded from our bale. The thing was exasperating—it was absurd. Here we were just arrived upon the moon, amidst we knew not what wonders, and all we could see was the grey and streaming wall of the bubble in which we had come. “Confound it!” I said, “but at this rate we might have stopped at home;” and I squatted on the bale and shivered, and drew my blanket closer about me. Abruptly the moisture turned to spangles and fronds of frost. “Can you reach the electric heater,” said Cavor. “Yes—that black knob. Or we shall freeze.” I did not wait to be told twice. “And now,” said I, “what are we to do?” “Wait,” he said. “Wait?” “Of course. We shall have to wait until our air gets warm again, and then this glass will clear. We can’t do anything till then. It’s night here yet; we must wait for the day to overtake us. Meanwhile, don’t you feel hungry?” For a space I did not answer him, but sat fretting. I turned reluctantly from the smeared puzzle of the glass and stared at his face. “Yes,” I said, “I am hungry. I feel somehow enormously disappointed. I had expected—I don’t know what I had expected, but not this.” I summoned my philosophy, and rearranging my blanket about me sat down on the bale again and began my first meal on the moon. I don’t think I finished it—I forget. Presently, first in patches, then running rapidly together into wider spaces, came the clearing of the glass, came the drawing of the misty veil that hid the moon world from our eyes. We peered out upon the landscape of the moon. About HackerNoon Book Series: We bring you the most important technical, scientific, and insightful public domain books. This book is part of the public domain. H. G. Wells (2010). The First Men In The Moon. Urbana, Illinois: Project Gutenberg. Retrieved October 2022, from https://www.gutenberg.org/files/1013/1013-h/1013-h.htm This eBook is for the use of anyone anywhere 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 , located at https://www.gutenberg.org/policy/license.html.

Mr Cavor's Moon Landing

In this article, I will show you how to use React to replace useEffect in most cases. I've been watching , and it's 🤯 blows my mind in a 😀 good way. I agree that useEffect has been used so much that it makes our code dirty and hard to maintain. I've been using useEffect for a long time, and I'm guilty of misusing it. I'm sure React has features that will make my code cleaner and easier to maintain. "Goodbye, useEffect" by David Khoursid What is useEffect? useEffect is a hook that allows us to perform side effects in function components. It combines componentDidMount, componentDidUpdate, and componentWillUnmount in a single API. It's a compelling hook that will enable us to do many things. But it's also a very dangerous hook that can cause a lot of bugs. Why useEffect is dangerous? Let's take a look at the following example: import React, { useEffect } from 'react'

const Counter = () => {
  const [count, setCount] = useState(0)

  useEffect(() => {
    const interval = setInterval(() => {
      setCount((c) => c + 1)
    }, 1000)
    return () => clearInterval(interval)
  }, [])

  return <div>{count}</div>
} It's a simple counter that increases every second. It uses useEffect to set an interval. It also uses useEffect to clear the interval when the component unmounts. The code snippet above is a widespread use case for useEffect. It's a straightforward example, but it's also a terrible example. The problem with this example is that the interval is set every time the component re-renders. If the component re-renders for any reason, the interval will be set again. The interval will be called twice per second. It's not a problem with this simple example, but it can be a big problem when the interval is more complex. It can also cause memory leaks. How to fix it? There are many ways to fix this problem. One way is to use useRef to store the interval. import React, { useEffect, useRef } from 'react'

const Counter = () => {
  const [count, setCount] = useState(0)
  const intervalRef = useRef()

  useEffect(() => {
    intervalRef.current = setInterval(() => {
      setCount((c) => c + 1)
    }, 1000)
    return () => clearInterval(intervalRef.current)
  }, [])

  return <div>{count}</div>
} The above code is a lot better than the previous example. It doesn't set the interval every time the component re-renders. But it still needs improvement. It's still a bit complicated. And it still uses useEffect, which is a very dangerous hook. useEffect is not for effects As we know about useEffect, it combines componentDidMount, componentDidUpdate, and componentWillUnmount in a single API. Let's give some examples of it: useEffect(() => {
  // componentDidMount?
}, []) useEffect(() => {
  // componentDidUpdate?
}, [something, anotherThing]) useEffect(() => {
  return () => {
    // componentWillUnmount?
  }
}, []) It's effortless to understand. useEffect is used to perform side effects when the component mounts, updates, and unmounts. But it's not only used to perform side effects. It's also used to perform side effects when the component re-renders. It's not a good idea to perform side effects when the component re-renders. It can cause a lot of bugs. It's better to use other hooks to perform side effects when the component re-renders. useEffect is not a lifecycle hook. import React, { useState, useEffect } from 'react'

const Example = () => {
  const [value, setValue] = useState('')
  const [count, setCount] = useState(-1)

  useEffect(() => {
    setCount(count + 1)
  })

  const onChange = ({ target }) => setValue(target.value)

  return (
    <div>
      <input type="text" value={value} onChange={onChange} />
      <div>Number of changes: {count}</div>
    </div>
  )
} useEffect is not a state setter import React, { useState, useEffect } from 'react'

const Example = () => {
  const [count, setCount] = useState(0)

  // Similar to componentDidMount and componentDidUpdate:
  useEffect(() => {
    // Update the document title using the browser API
    document.title = `You clicked ${count} times`
  }) // <-- this is the problem, 😱 it's missing the dependency array

  return (
    <div>
      <p>You clicked {count} times</p>
      <button onClick={() => setCount(count + 1)}>Click me</button>
    </div>
  )
} I recommend reading this documentation: https://reactjs.org/docs/hooks-effect.html#tip-optimizing-performance-by-skipping-effects Imperative vs Declarative : When something happens, execute this effect. Imperative : When something happens, it will cause the state to change and depending (dependency array) on which parts of the state changed, this effect should be executed, but only if some condition is true. And React may execute it again for concurrent rendering. Declarative no reason Concept vs Implementation : Concept useEffect(() => {
  doSomething()

  return () => cleanup()
}, [whenThisChanges]) : Implementation useEffect(() => {
  if (foo && bar && (baz || quo)) {
    doSomething()
  } else {
    doSomethingElse()
  }

  // oops, I forgot the cleanup
}, [foo, bar, baz, quo]) : Real-world implementation useEffect(() => {
  if (isOpen && component && containerElRef.current) {
    if (React.isValidElement(component)) {
      ionContext.addOverlay(overlayId, component, containerElRef.current!);
    } else {
      const element = createElement(component as React.ComponentClass, componentProps);
      ionContext.addOverlay(overlayId, element, containerElRef.current!);
    }
  }
}, [component, containerElRef.current, isOpen, componentProps]); useEffect(() => {
  if (removingValue && !hasValue && cssDisplayFlex) {
    setCssDisplayFlex(false)
  }
  setRemovingValue(false)
}, [removingValue, hasValue, cssDisplayFlex]) It's scary to write this code. Furthermore, it will be normal in our codebase and messed up. 😱🤮 Where do effects go? React 18 runs effects twice on the mount (in strict mode). Mount/effect (╯°□°)╯︵ ┻━┻ -> Unmount (simulated)/cleanup ┬─┬ /( º _ º /) -> Remount/effect (╯°□°)╯︵ ┻━┻ Should it be placed outside of the component? The default useEffect? Uh... awkward. Hmm... 🤔 We couldn't put it in render since it should be no side-effects there because render is just like the right-hand of a math equation. It should be only the result of the calculation. What is useEffect for? Synchronization useEffect(() => {
  const sub = createThing(input).subscribe((value) => {
    // do something with value
  })

  return sub.unsubscribe
}, [input]) useEffect(() => {
  const handler = (event) => {
    setPointer({ x: event.clientX, y: event.clientY })
  }

  elRef.current.addEventListener('pointermove', handler)

  return () => {
    elRef.current.removeEventListener('pointermove', handler)
  }
}, []) Action effects vs Activity effects Fire-and-forget            Synchronized
 (Action effects)        (Activity effects)

        0              ----------------------       ----------------- - - -
        o              o   |     A   |      o       o     | A   |   A
        o              o   |     |   |      o       o     | |   |   |
        o              o   |     |   |      o       o     | |   |   |
        o              o   |     |   |      o       o     | |   |   |
        o              o   |     |   |      o       o     | |   |   |
        o              o   |     |   |      o       o     | |   |   |
        o              o   V     |   V      o       o     V |   V   |
o-------------------------------------------------------------------------------->
                                       Unmount      Remount Where do action effects go? Sorta. Event handlers. <form
  onSubmit={(event) => {
    // 💥 side-effect!
    submitData(event)
  }}
>
  {/* ... */}
</form> There is excellent information in Beta React.js. I recommend reading it. Especially the . "Can event handlers have side effects?" part Absolutely! <u>Event handlers are the best place for side effects.</u> Another great resource I want to mention is Where you can cause side effects In React, <u>side effects usually belong inside event handlers.</u> If you've exhausted all other options and can't find the right event handler for your side effect, you can still attach it to your returned JSX with a <u>useEffect</u> call in your component. This tells React to execute it later, after rendering, when side effects are allowed. <u> </u> However, this approach should be your last resort. "Effects happen outside of rendering" - David Khoursid. (state) => UI
(state, event) => nextState // 🤔 Effects? UI is a function of the state. As all the current states are rendered, it will produce the current UI. Likewise, when an event happens, it will create a new state. And when the state changes, it will build a new UI. This paradigm is the core of React. When do effects happen? Middleware? 🕵️ Callbacks? 🤙 Sagas? 🧙‍♂️ Reactions? 🧪 Sinks? 🚰 Monads(?) 🧙‍♂️ Whenever? 🤷‍♂️ State transitions. Always. (state, event) => nextState
          |
          V
(state, event) => (nextState, effect) // Here Where do action effects go? State transitions. Event handlers. Which happen to be executed at the same time as event handlers. We Might Not Need an Effects We could use useEffect because we don't know that there is already a built-in API from React that can solve this problem. Here is an excellent resource to read about this topic: You Might Not Need an Effect We don't need useEffect for transforming data. useEffect ➡️ useMemo (even though we don't need useMemo in most cases) const Cart = () => {
  const [items, setItems] = useState([])
  const [total, setTotal] = useState(0)

  useEffect(() => {
    setTotal(items.reduce((total, item) => total + item.price, 0))
  }, [items])

  // ...
} Read and think about it again carefully 🧐. const Cart = () => {
  const [items, setItems] = useState([])
  const total = useMemo(() => {
    return items.reduce((total, item) => total + item.price, 0)
  }, [items])

  // ...
} Instead of using to calculate the total, we can use to memoize the total. Even if the variable is not an expensive calculation, we don't need to use to memoize it because we're basically trading performance for memory. useEffect useMemo useMemo Whenever we see in , it's a warning sign that we can simplify it. setState useEffect Effects with external stores? useSyncExternalStore useEffect ➡️ useSyncExternalStore ❌ Wrong way: const Store = () => {
  const [isConnected, setIsConnected] = useState(true)

  useEffect(() => {
    const sub = storeApi.subscribe(({ status }) => {
      setIsConnected(status === 'connected')
    })

    return () => {
      sub.unsubscribe()
    }
  }, [])

  // ...
} ✅ Best way: const Store = () => {
  const isConnected = useSyncExternalStore(
    // 👇 subscribe
    storeApi.subscribe,
    // 👇 get snapshot
    () => storeApi.getStatus() === 'connected',
    // 👇 get server snapshot
    true
  )

  // ...
} We don't need useEffect for communicating with parents. useEffect ➡️ eventHandler ❌ Wrong way: const ChildProduct = ({ onOpen, onClose }) => {
  const [isOpen, setIsOpen] = useState(false)

  useEffect(() => {
    if (isOpen) {
      onOpen()
    } else {
      onClose()
    }
  }, [isOpen])

  return (
    <div>
      <button
        onClick={() => {
          setIsOpen(!isOpen)
        }}
      >
        Toggle quick view
      </button>
    </div>
  )
} 📈 Better way: const ChildProduct = ({ onOpen, onClose }) => {
  const [isOpen, setIsOpen] = useState(false)

const handleToggle = () => {
  const nextIsOpen = !isOpen;
  setIsOpen(nextIsOpen)

  if (nextIsOpen) {
    onOpen()
  } else {
    onClose()
  }
}

  return (
    <div>
      <button
        onClick={}
      >
        Toggle quick view
      </button>
    </div>
  )
} ✅ Best way is to create a custom hook: const useToggle({ onOpen, onClose }) => {
  const [isOpen, setIsOpen] = useState(false)

  const handleToggle = () => {
    const nextIsOpen = !isOpen
    setIsOpen(nextIsOpen)

    if (nextIsOpen) {
      onOpen()
    } else {
      onClose()
    }
  }

  return [isOpen, handleToggle]
}

const ChildProduct = ({ onOpen, onClose }) => {
  const [isOpen, handleToggle] = useToggle({ onOpen, onClose })

  return (
    <div>
      <button
        onClick={handleToggle}
      >
        Toggle quick view
      </button>
    </div>
  )
} We don't need useEft for initializing global singletons. useEffect ➡️ justCallIt ❌ Wrong way: const Store = () => {
  useEffect(() => {
    storeApi.authenticate() // 👈 This will run twice!
  }, [])

  // ...
} 🔨 Let's fix it: const Store = () => {
  const didAuthenticateRef = useRef()

  useEffect(() => {
    if (didAuthenticateRef.current) return

    storeApi.authenticate()

    didAuthenticateRef.current = true
  }, [])

  // ...
} ➿ Another way: let didAuthenticate = false

const Store = () => {
  useEffect(() => {
    if (didAuthenticate) return

    storeApi.authenticate()

    didAuthenticate = true
  }, [])

  // ...
} 🤔 How if: storeApi.authenticate()

const Store = () => {
  // ...
} 🍷 SSR, huh? if (typeof window !== 'undefined') {
  storeApi.authenticate()
}
const Store = () => {
  // ...
} 🧪 Testing? const renderApp = () => {
  if (typeof window !== 'undefined') {
    storeApi.authenticate()
  }

  appRoot.render(<Store />)
} We don't necessarily need to place everything inside a component. We don't need useEffect for fetching data. useEffect ➡️ renderAsYouFetch (SSR) or useSWR (CSR) ❌ Wrong way: const Store = () => {
  const [items, setItems] = useState([])

  useEffect(() => {
    let isCanceled = false

    getItems().then((data) => {
      if (isCanceled) return

      setItems(data)
    })

    return () => {
      isCanceled = true
    }
  })

  // ...
} 💽 Remix way: import { useLoaderData } from '@renix-run/react'
import { json } from '@remix-run/node'
import { getItems } from './storeApi'

export const loader = async () => {
  const items = await getItems()

  return json(items)
}

const Store = () => {
  const items = useLoaderData()

  // ...
}

export default Store ⏭️🧹 Next.js (appDir) with async/await in Server Component way: // app/page.tsx
async function getData() {
  const res = await fetch('https://api.example.com/...')
  // The return value is *not* serialized
  // You can return Date, Map, Set, etc.

  // Recommendation: handle errors
  if (!res.ok) {
    // This will activate the closest `error.js` Error Boundary
    throw new Error('Failed to fetch data')
  }

  return res.json()
}

export default async function Page() {
  const data = await getData()

  return <main></main>
} ⏭️💁 Next.js (appDir) with useSWR in Client Component way: // app/page.tsx
import useSWR from 'swr'

export default function Page() {
  const { data, error } = useSWR('/api/data', fetcher)

  if (error) return <div>failed to load</div>
  if (!data) return <div>loading...</div>

  return <div>hello {data}!</div>
} ⏭️🧹 Next.js (pagesDir) in SSR way: // pages/index.tsx
import { GetServerSideProps } from 'next'

export const getServerSideProps: GetServerSideProps = async () => {
  const res = await fetch('https://api.example.com/...')
  const data = await res.json()

  return {
    props: {
      data,
    },
  }
}

export default function Page({ data }) {
  return <div>hello {data}!</div>
} ⏭️💁 Next.js (pagesDir) in CSR way: // pages/index.tsx
import useSWR from 'swr'

export default function Page() {
  const { data, error } = useSWR('/api/data', fetcher)

  if (error) return <div>failed to load</div>
  if (!data) return <div>loading...</div>

  return <div>hello {data}!</div>
} 🍃 React Query (SSR way: import { getItems } from './storeApi'
import { useQuery } from 'react-query'

const Store = () => {
  const queryClient = useQueryClient()

  return (
    <button
      onClick={() => {
        queryClient.prefetchQuery('items', getItems)
      }}
    >
      See items
    </button>
  )
}

const Items = () => {
  const { data, isLoading, isError } = useQuery('items', getItems)

  // ...
} ⁉️ Really ⁉️ What should we use? useQuery? useSWR? useEffect? or... just use() 🤔 use() is a new React function that accepts a promise conceptually similar to await. use() handles the promise returned by a function in a way that is compatible with components, hooks, and Suspense. Learn more about use() in the React RFC. function Note({ id }) {
  // This fetches a note asynchronously, but to the component author, it looks
  // like a synchronous operation.
  const note = use(fetchNote(id))
  return (
    <div>
      <h1>{note.title}</h1>
      <section>{note.body}</section>
    </div>
  )
} Fetching in useEffect problems 🏃‍♂️ Race conditions 🔙 No instant back button 🔍 No SSR or initial HTML content 🌊 Chasing waterfall Reddit, Dan Abramov Conclusion From fetching data to fighting with imperative APIs, side effects are one of the most significant sources of frustration in web app development. And let's be honest, putting everything in useEffect hooks only helps a little. Thankfully, there is a science (well, math) to side effects, formalized in state machines and statecharts, that can help us visually model and understand how to orchestrate effects, no matter how complex they get declaratively. Resources Remix Next.js React Query use SWR Goodbye, useEffect - David Khourshid React 18: The One with Suspense for Data Fetching

Get Advanced!

How to Use React to Replace useEffect

The crypto industry’s biggest secret -  the Shadow Banking System, where cryptocurrencies worth billions of dollars are borrowed & lent on an un-collateralized basis, between some of the industry’s biggest names, was exposed in recent months as the biggest driver of the spectacular bull market... . as well the collapse & contagion that is still ongoing While the crypto shadow banks are going through their most difficult moments, it was the Securities and Exchange Commission’s (SEC’s) decision to declare a lending program an unregistered security offering might have unintentionally saved Coinbase from the same deadly blow that struck BlockFi, Celsius, Voyager, Gemini, and many others. Crypto shadow banks are companies that engage in bank-like activities such as borrowing & lending but obviously are not licensed banks, hence fall outside the regulatory constraints of fully licensed banks, which are required to have capital reserves to cover losses from bad loans or available liquidity in case of a bank run. With the promise of “L ”, crypto shadow banks such as Celsius, BlockFi, Voyager & Gemini managed to attract billions of AUM from professional and retail investors, which got lent out further to the world’s biggest crypto whales, the likes of 3AC and Alameda Research. ess risk than a bank with better returns for customers. In the midst of the 2021 bull market, the crypto industry’s second biggest player had its own plans to launch a lending program, namely Coinbase Lend. While the details of Coinbase’s Lend program are no longer publicly available, I found out that the program would work by “matching lenders of the USDC stablecoin with qualified borrowers” and that “ ”. Coinbase would guarantee the principal creditors lend out It is unclear whether Coinbase would match borrowers to lenders directly or simply create a pool out of which they could undertake lending activities. While the semantics of Coinbase’s wording is of less importance for this story, the playbook was meant to be similar to that of the largest crypto shadow banks; borrow cryptos worth billions of dollars from clients already onboarded with Coinbase and lend out in the Shadow Debt Market to worlds largest proprietary trading firms, hedge funds, and market makers. The details of Coinbase’s Lend program caught the attention of the SEC, and the US regulator reacted fiercely & aggressively by threatening to sue Coinbase if the program was launched. Coinbase Lend program was immediately scrapped, with Coinbase noting SEC’s “ ” since many other crypto shadow banks were engaging in those same lucrative borrowing & lending activities. unfair treatment The rest is now history. SEC’s decision unintentionally saved Coinbase from the same catastrophic fate that struck BlockFi, Celsius, Voyager, Gemini, and many more - the collapse of Terra/LUNA, the blow-up of 3AC, the fiasco of FTX & Alameda Research, and the ongoing contagion. In retrospect, it’s easy for crypto critics & skeptics to point fingers at crypto companies or praise regulators around the globe, but very few people understand the plumbing & infrastructure of the crypto ecosystem, with crypto shadow banking as the biggest mystery of them all. My goal is to provide insider insights into the secretive workings and shed light to strengthen our industry which will be the backbone of infrastructure for the world's growth in the coming decades.

This story contains new, firsthand information uncovered by the writer.

Get insider cypto secrets 

SEC Saved Coinbase From The Fate That Befell Voyager, Celsius, BlockFi, and Gemini

The below updates are reflective up to November 30, 2022 It's been a busy couple of months for HackerNoon developers on all ends. From improving website performance and design to carrying out the constant task of page indexation (go, SEO!) to expanding the website's reach by breaking the language barrier, our devs did it all. And we're so excited to tell you all about it! Continue reading to discover all our new features. Pin Your Best Work 📌 Excellent news, Hackers! You can now pin your three favorite stories to the top of your story list, which means you can give whatever post on your profile the highlight whenever you choose to. This feature also helps you ensure your best work always shows first, representing you fairly on HackerNoon. Moreover, you can filter your stories by latest or popularity, making browsing your content painless and personalized! Fresh for Readers Hackernoon in 8 Different Languages Our readers spread far and fast, and we know how much reading your favorite articles in your mother tongue would make a difference. . It all started with our users: , the catalyst to start us off on our translation journey! For that reason, we've enabled Cloud Translation API to bring you HackerNoon's top stories in foreign languages they spoke and picked Spanish as the winner We have used machine learning to translate on our platform from English to , , , , , , and . We will keep translating new upcoming top stories. Top stories will now see all these languages on top of the feature image. all top stories Spanish Hindi Mandarin Vietnamese French Portuguese Japanese Also, if you navigate to the tag page of a specific language, you will notice that the entire page will be in that language. , for example, will only show stories in one language, in this case, Hindi. But it's the same for other languages. https://hackernoon.com/tagged/hackernoon-hi This helps both readers and writers. On the one hand, it allows readers to dive into HackerNoon stories in the language they’re most comfortable with. On the other hand, it helps writers have a translated version of their work, helping them reach bigger audiences - all powered by HackerNoon machines. new feature Click the flag button at the top of every article page to pick the language you’d like to read in or visit the homepage in your target language to enjoy the hundreds of stories already available! To visit our translated homepages, use these links: | | | | | | | English Vietnamese Portuguese Spanish Hindi French Chinese Japanese Wallet Assets are 4Show We knew we had to integrate a versatile web3 login system to accommodate future features. Building it in-house allowed us complete control of security and a wide range of tooling to help support users in their transition into web3 DAPPS, allowing them to seamlessly link into HackerNoon’s existing authorization infrastructure. So, what does that mean for you? You can now ! connect and log in with your Ethereum wallet on HackerNoon If you have an existing account with us, you can simply and connect your wallet! This will allow you to take full advantage of the future features that HackerNoon will offer, as well as being able to via your wallet! edit your profile log in directly to your account You can link your Metamask, Coinbase, or any other ERC-20 wallet that you use to store your crypto! If it can hold Ethereum, Polygon, Chainlink or USDC, it will work on HackerNoon! If you don’t have an account with us yet and would like to create one, you can do so directly on our by clicking “Login with Wallet”! signup page HackerNoon Web3 accounts collect no additional data on you, so you can remain completely anonymous online! And that’s it! You can now take full advantage of all the new upcoming features of the decentralized web! Please note that, unlike most Metamasks, you can only log in with Coinbase after account creation by linking the wallet to your account. You cannot create an account using the Coinbase wallet. On this day in Tech History… is done and ready to rock your world! With this new development, you can browse any day in HackerNoon history and find out what was happening at the time while reading stories published on your selected day! On this day feature What better way to keep tabs on current and past events than this?! New Pages to Browse Keeping in tune with the latest developments, our devs added a few pages to our listing. One of the pages making the big recent HackerNoon hits is the . We’ve all been on the edge of our seats waiting for the weekly ranking, and now it’s easier than ever to find them. Visit and enjoy current and previous company briefs! Tech Company Briefs hackernoon.com/tech-company-brief But that’s not all! Everyone’s favorite emails turned stories are also getting a page of their own. The , full of fresh tech content, will be waiting for you on . Worth the check! Noonification hackernoon.com/noonification And, remember ? Each poll now has its own page! So you can keep tabs on easily. And to make matters sweeter HackerNoon polls results are also currently available at the bottom of each poll - like . Awesome, right? polls past polls this one Why not cite/use these as headlines for your next top HackerNoon story? Merry Quizmas! Who doesn't love a good quiz?! You know we do! We've been working on quizzes for stories that track users' progress while reading them, meaning that now you can test your knowledge in real-time! At the moment, only editors hold de quiz maker stick, but everyone is open to answering. In time we hope to extend the creative power to our talented writers. Story Stats are now prominent more than ever! In every story, you can now access some key elements straight away. Is it a new story? Does it have more than ten reactions or 100 reads? Is it trending? You can find all about it on story cards! stats Homepage UI Revamped Our developers don’t cease to amaze us. This time they brought their UI expertise to improve the homepage, including updates to polls, trending, and story-card layout. Mobile also got a slice of their attention, receiving a lot of fixes, so the website looks nice and coherent on all screens. Story Pages: The Holy Grail of Information Surprise, surprise! We’ve made story pages prettier! In case you haven’t noticed the changes, let us point them out for you. It started with TL:DR: not only does it show up differently in your stories, but it also includes all coins, companies, and profiles mentioned in your text, making it easier to find what you’re looking for! Story tags have also been resized to fit the story width, guaranteeing a coherent layout. As for images, download is now possible for every story image, and smaller feature images on stories also get a new background to maintain the ideal proportion across the website. The author section shows a “learn more” button to answer CTA dimension limitation, and social sharing buttons no longer show on the sticky profile. Instead, you can find them under the linking option on the sticky profile along the text, with a new and improved design. Also on the sticky profile, you can now see the bookmark option, added for your convenience. Last but not least, got that redesign! 🔥 comments Sleeker than ever, the new design offers a cleaner version of the comment section, with the added option to copy a link that will take users directly to a comment! Just click the “share” button to watch the magic happen. These changes make it easier for our users to find all relevant information in one place. Enjoy! Fresh for Writers Stable Diffusion aka AI Generated Images in app.hackernoon.com Published writers can now generate images using directly in the HackerNoon editor! 🥳 We’ve added stats (storyCouny, totalTimeReading) to the green user context to determine which users can use Stable Diffusion. Stable Diffusion The new option at the bottom of the image upload modal allows users to create ten images an hour. If an error pops up saying it won't count toward this limit. Just edit the prompt and try not to be so gross next time. NSFW content was detected, Anywho, type in what you'd like to see in the image and press enter or the Submit button, then wait a bit while we talk to to generate your image. And the best part is that you won't even have to worry about image captions! We've added auto-add captions for Stable Diffusion on the main images! replicate.com Moreover, you can also opt for the instead. This tool produces distinct results from Stable Diffusion, creating images with richer colors and slightly more surrealist. Have fun! mid-journey diffusion option NFTs as story embeds Did you know you can embed NFTs ( ) into your ? No? Well, that isn't too surprising because we haven't told anyone about it. say what? Hacker Noon stories Here's what it looks like: Paste something along the lines of… 0x495f947276749Ce646f68AC8c248420045cb7b5e#80305803031457727000169367139464419088647062543998058403747637890778052689921 … into 2.0 stories and hit enter, you will embed an NFT viewer. The 0xwhatever part is the Contract Address, and the bit after # is the token ID. If all goes well, you will see the embedded NFT load in a matter of seconds! You can check the step-by-step guide . here Make sure that the token standard is ERC-721, or it won’t work. Profile Page Remodeled, Again! Taking care of our users' is our pleasure! Improving them is our passion! And that's just what we did! Profile pages are now limited to one CTA to prevent clutter, and a subscribe button is visible when viewing your own page instead of the email input form. profiles NFT on Profile Pages Let it be known that you can now . What’s more? It shows up bordered by the notorious identity hexagon. upload Eth- or Matic-based NFTs to your HackerNoon profile as your avatar Just like this: All you have to do is link your wallet to HackerNoon and update your avatar. Click to read the detailed instructions. here Fresh for Brands New Partnership with Arweave Have you seen the little “Permanent on Arweave” button under the “THIS ARTICLE WAS FEATURED IN…” section? Well, that’s because HackerNoon has struck a brand new partnership with Arweave, backing up 20k+ stories with them, making sure your precious content is never lost! Favicons Around Web We’re suckers for detail, and we had to zhuzh up company mentions around the web throughout the website. That’s why we included Favicons next to each company’s name, like so… Pretty neat, right? Go-odbye-Daddy It’s time we address the elephant in the room: . If you follow , you heard all about the hardship HackerNoon went through at the start of November on the account of a GoDaddy Domain. GoDaddy our socials To keep us all in the loop here's what happened. On November 1st, we received an automated email saying an article published on our site had to be taken down for violating GoDaddy ToS. The communication came via our CEO's personal email, without a phone call or any other alert given. We were given 24 hours of the message's reception to do so. Upon review, we realized the person did make a mistake. We promptly removed the article and had a call with them to understand the matter further. After many attempts to contact GoDaddy and speaking with various scapegoat call center workers who had no power in the matter whatsoever, we were told that this matter could only be solved by their "back office" and that the process could take from 24 to 72 hours. So much for the 24/7 hour customer support advertised on the site. We couldn’t stand still and watch as HackerNoon’s reputation was being tarnished and the livelihoods of every employee, writer and customer, who rely on our ad space and content publishing, were put at risk. For that reason, HackerNoon has decided to cease its contract with GoDaddy and follow a different direction with a different partner. Noonies Winners on Site Winner, winner, Techies dinner! The results for the 2022 edition are in - congratulations 2022 Award Winners! Noonies More than 300 awards have been awarded to our nominees across categories, and your votes made a difference. With over 140K votes and 4K nominees, we couldn’t possibly have done it without the help of our marvelous community. As for the , I hope you enjoy your special award and badge that you’ll be able to show off across your profile page. Don’t forget to let the world know what you’ve just achieved, and feel free to tag us while you’re at it 😉 winners A special thanks to our partners in crime, .TECH domains and BingX, who sponsor HackerNoon’s efforts to give back to the tech community. Thank you all for being a part of the HackerNoon community! Post written and compiled by Linh, Mónica, and David!

"Productivity Updates" Aug 10

Product Updates

About Our Softwares

The CMS That Powers HackerNoon.com

Slogging (Slack Blogging App)

Free Internet Plugin

#hackernoon

Our Content Management System, and Related Publishing Software

Paint us Red and Call us Santa! Our Devs Just Gifted You a Sleigh of New Features!

How are you, hacker?
🪐 has got you covered with fresh content from our top 5 stories of the day, every day at noon your local time! Set email preference . What's happening in tech this week: The Noonification by HackerNoon here Paint us Red and Call us Santa! Our Devs Just Gifted You a Sleigh of New Features! By [ 10 Min read ]
Hey there, Hackers. It’s time for our regular updates on the fun new features we’ve deployed in the past two months. As always: a big thank you to our devs team @product Read More. SEC Saved Coinbase From The Fate That Befell Voyager, Celsius, BlockFi, and Gemini By [ 3 Min read ]
SECs decision to declare Coinbases Lend program unregistered security offering unintentionally saved Coinbase from the same fate as BlockFi, Celsius, Genesis @antongolub Read More. How to Use React to Replace useEffect By [ 16 Min read ]
useEffect is a hook that allows us to perform side effects in function components. It combines componentDidMount, componentDidUpdate, and componentWillUnmount @imamdev Read More. 6 Best Go Programming Books Ranked by Reviews By [ 5 Min read ]
Learning Go and Black Hat Go are some of the best Go programming books based on their review scores. 🧑‍💻 What happened in your world this week?It's been said that , , . Feeling stuck? We got you covered ⬇️⬇️⬇️ We hope you enjoy this worth of free reading material. Feel free to forward this email to a nerdy friend who'll love you for it.See you on Planet Internet! With love,
The Hacker Noon Team ✌️ @hackernoonbooks Read More. writing can help consolidate technical knowledge establish credibility and contribute to emerging community standards ANSWER THESE GREATEST INTERVIEW QUESTIONS OF ALL TIME

HackerNoon Tech Stories Archive December 31st, 2022

THE MOTH

@hgwells
H.G. Wells

FREE WILL AND PREDESTINATION

@hgwells
H.G. Wells

THE LATER POSTGLACIAL PALÆOLITHIC MEN, THE FIRST TRUE MEN

@hgwells
H.G. Wells

A WITHDRAWAL

@hgwells
H.G. Wells

THE NEANDERTHALER AND THE RHODESIAN MAN

@hgwells
H.G. Wells

6 Best Go Programming Books Ranked by Reviews

@hackernoonbooks
Official Account for HackerNoon Books

Mr Cavor's Moon Landing

@hgwells
H.G. Wells

How to Use React to Replace useEffect

@imamdev
Imamuzzaki Abu Salam

SEC Saved Coinbase From The Fate That Befell Voyager, Celsius, BlockFi, and Gemini

@antongolub
Anton Golub

Paint us Red and Call us Santa! Our Devs Just Gifted You a Sleigh of New Features!

@product
HackerNoon Product Updates

The Noonification: How to Use React to Replace useEffect (12/31/2022)

@noonification
Noonification

HackerNoon Tech Stories Archive December 31st, 2022

@imamdevImamuzzaki Abu Salam

@antongolubAnton Golub

@productHackerNoon Product Updates

@imamdev
Imamuzzaki Abu Salam

@antongolub
Anton Golub

@product
HackerNoon Product Updates