Normal Doc - Template: Fill & Download for Free

I think it depends what kind of work you do, if it’s primarily single page apps with a Go API, or a more traditional web app. You may have slightly more verbose code setting up types etc, but you gain a ton productivity-wise from things like:incredibly rich and robust stdlibreally, it even has hex dumping!!a lot of things literally everyone needs are standard (good http client etc)better third-party package quality on averagestatic typing (obviously)less time reading package docs and due to toolingsimple package system (no need for manifests)simple & obvious public/private interfaces via lowercase and uppercasenormalized code, all Go code effectively looks the same regardless of authorless time wasted waiting for installing / deploying 250mb of node_modulesbuilt-in test framework (no need for something like Mocha etc)built-in benchmarkingbuilt-in templatingbetter error handling, explicit and forces you to consider fail pointsbetter stream implementation with io.Reader / io.Writer and friendscross-compiling makes for easy binary deploysless indirection for publishing code (no extra registry step)verbose but easy to read, no guessing, it’s very explicitless fragmentation (callbacks, promises, async/await, …)I personally find it much more productive, it may take a bit of getting used to – so I wouldn’t judge the productivity right off the bat, give it an honest try for a few projects.Go has fewer third party packages, but they’re generally much higher quality, and very normalized thanks to gofmt and testing being standard. You don’t have to deal with 150 test frameworks or a wide variety of coding styles (typically pretty unreadable in JS IMO).What you won’t find is something like Rails (at least that I’m aware of) for more traditional apps, but for single-page apps (what I typically work on) it’s fantastic.For work that goes “beyond” web apps, like event processing pipelines and so on, I would strongly recommend not using Node. IMO It’s very hard to produce a production-ready robust program in Node, as someone who used it for ~5 years.The one notable strength (could be considered a con as well) is the lack of thread synchronization in Node since it’s an event loop. In practice it’s not too difficult to write thread-safe Go (or “concurrency safe” as most Go people would prefer to say), however that is an additional layer to worry about. With that said, it also makes it trivial to scale your program to any number of cores.

Years ago, I was working as a nurse in a cardiothoracic ICU taking care of post open heart surgical patients. I was in charge one day and one of my colleagues called me over. She was worried about her patient. He had been with us for three days and something was going on with him.Nancy* asked me for a second opinion. She suspected that the patient might be having a cardiac tamponade (a slow bleed into the pericardial sac surrounding the heart) which would be potentially fatal, but very rare three days after surgery, normally it occurred within a few hours of surgery. The patient, meanwhile, a 60-year-old man, was breathing on his own and loudly demanding something to drink.“Water! I need water! I´m dying of thirst!” He kept saying over and over.I looked at Nancy and she nodded knowingly. “See why I´m worried?”Both of us had many years of experience and we knew that when patients suddenly have an uncontrollable desire for water or a sudden need to poop when they hadn´t eaten in days, that usually meant they were going to die – and soon.His signs and symptoms of tamponade were very borderline, nothing clearly pointed to her diagnosis.“Water! Water!” He started screaming, becoming very agitated.“Like I told you,” Nancy said patiently. “I believe you may be going back to surgery soon, so you can´t have anything to drink if they are going to give you anesthesia. It is too dangerous.” She spooned two tiny ice chips into his mouth.He glared at her with hatred. “Those slivers of ice are not enough. Why are you being so mean to me? Do you really think a glass of water is going to kill me?”“It could.” She said firmly. She turned to me. “What do you think?”I knew she wasn´t asking me about the water. “I don´t know. You know three days out would be really unusual for him to have that. Have you talked to the surgeon?”“Yes. He doesn´t agree with me. But I did get him to order a chest x-ray. I´m waiting for them now.”“Please, please, I´m begging you.” The patient interrupted, alternating sobbing with yelling. “I am going to die if I don´t get something to drink right now.”He grabbed my hand. “Please, you look like a nice lady. Can you get me a glass of water?” He looked at Nancy. “She´s trying to let me die of thirst.”Nancy looked at him. “You are getting plenty of IV fluids, trust me, you are not going to die of thirst. Here, have a couple more ice chips.” She spooned some more ice into his mouth as he greedily tried to pry the full cup of ice from her hands.“No, no. Just a little at a time.” She chastised him, pulling the cup out of his grasp.“Give me a glass of water!” He screamed again at the top of his lungs.The x-ray tech came in then and shot a film of his chest. After they left, I assessed him again, listening to his heart. “You could be right, Nancy. His heart sounds are pretty muffled.”“I know, right?”“Water, water, water, water…” He began to chant a manic mantra, his voice getting louder with each repetition of the word.I walked up to the front of the ICU and began to refresh the X-ray screen, waiting for the image to come through. A few minutes later, it began to download.Normal heartCrazy big heart (and not in a good way)She was right. The pericardial sac was filled to the brim with blood and clots, making it about three times its normal size.I turned to the secretary. “Page the surgeon and ask him to come.” I called over my shoulder to Nancy. “Hey, you were right, he has a huge tampo….”“OH SHIT!” I hear her yell.Upon hearing the universal ICU code sign for I need help right now, I spun and sprinted down the unit to her bedside. Both of us stood on either side of the patient´s bed, staring at his chest. There was blood seeping out from under his bandage where his fresh incision was. Lots of blood.At that moment, his chest exploded.There is no better word to describe what happened. Nancy and I jumped back simultaneously, but it was too late. A fountain of blood and clots erupted from his chest like a volcano, hitting both of us square in the face, spraying almost to the ceiling, the walls, the floor.“HOLY SHIT!” We said together. For anyone who has seen the movie Alien with Sigourney Weaver, when the alien bursts out of Kane´s chest, this was a template for that scene.We both stood there, frozen in shock. With all of our years of experience, we had NEVER seen such a thing. Clearly, the patient had to be dead. No one could have survived that explosion. Anxiously we looked at him. He looked like he had been in a head-on collision with a semi-truck. Blood and clots covered his face, hair, chest and turned the crisp white sheets red. We stepped forward at the same time, prepared to start CPR to try to save him.He blinked and looked at us calmly from behind the mask of blood. We glanced at the monitor; all of his vital signs had returned to normal.In a dead flat voice, he said, “I guess I´m never getting that glass of water now, huh?”Nancy and I burst out laughing. We stood there, dripping blood, and laughing hysterically. Even the patient started to laugh. The surgeon ran in with the anesthesiologist by his side. The secretary had been on the phone with him when the patient´s chest had exploded, and she told him what was happening.They skidded to a stop, taking in the horror scene, and stared at the three of us laughing.“Hey doc,” Nancy said. “I was right. He was tamponading. He seems to have fixed that, but I think you need to go fix his ruptured pericardium.”The surgeon left to scrub in for surgery and the anesthesiologist was left to prepare the patient.He asked him a few questions, then he said. “Sir, have you had anything to drink in the last two hours?”The patient looked at us accusingly and all of us burst out laughing again.“Ask them.” He said between gales of laughter.The next day, after he had recovered nicely from his second surgery, Nancy made sure to bring him an ice-cold glass of water and let him drink all he wanted.

You need to know basic Java and it will be very helpful to know SQL; although Hibernate can create a database automatically, it can be hard to understand what’s going on exactly unless you know SQL. If you plan to create websites, you’ll need to know some HTML/CSS.You won’t really need to know about servlets, although it would only take you a short amount of time, like an hour or a few hours, to learn what they are. If you plan to create web projects, Spring will give you a pre-made servlet and you won’t need to deal with any others. But a Spring web project will have to run under a server (unless you use an embedded server), so you could gain a bit of experience of that in the process of creating a basic servlet.As for JSP, it depends. Usually a Spring MVC (web) project will use some kind of template engine. This is the thing that lets you write what looks like HTML pages but contains special tags that invoke Java code. JSP is the most popular template engine out there for Java (usually used with JSTL, the Java Standard Tag Library), but there are others like Freemarker and Thymeleaf that are newer but not yet as popular.I’ve been learning Spring Boot recently, and the Spring Boot docs actually mainly use Thymeleaf, if I remember well. This is because there is a minor issue (which you can work around if you want to) regarding using JSPs and embedded servers.You’ll probably need to pick one of these template engines, at least if you plan to create websites with Spring directly, rather than implementing a REST service and creating your front end using a Javascript library. But you could learn about your chosen template engine alongside learning about Spring; the Spring docs contain many examples you can work from.In case you haven’t come across it, an embedded server is a server that’s contained it the jars you use with your application. Then you can start your application like a normal Java program, and the server will start.Finally, you’ll likely want to use a build tool like Maven or Gradle. Maven is more popular, but Gradle has made big inroads. This is mainly because creating a Spring app involves using lots of different jars which you’d otherwise have to download from different sites in the exact right versions, and a build tool can do that automatically for you. You won’t have to understand either of these in any depth, and again you can learn about them alongside Spring.If you don’t want to make web apps, most of this doesn’t apply; you’ll only be using Java, SQL will be handy, and you’ll probably use a build tool like Maven.