sargas

If you replace "Go" with "JavaScript" the whole blog would also apply. Except there are way more JS lovers than Go lovers out there. And these two groups almost seem to never overlap.

I still don't think Windows will become the best dev platform for everyone even with Bash support, even though it is a great addition to the OS. But I think Microsoft is headed the right direction.

Windows really needed a better "native" CLI. This truly solves that issue.

Story of my life right there. The standard library will take you a long ways in web dev (specially in prototyping), but ultimately needs a lot of improvement that the community made in the form of 3rd party packages.

Here's one way to find you my friend: prototyping. Go is simple enough that could give you a good idea of what your life will be like using a package in a "short" amount of time.

I think people choose frameworks because they _prefer_ them instead of _needing_ them. If you think you _need_ a framework you need to reevaluate your programming skills.

Turtles all the way down indeed.

Agreed. Small correction: non-Gophers rather than non-Golangers. Now you know some more about the Go culture.

Shady.

JavaScript could benefit from a better standard language. But this isn't the biggest concern since the language is "friendly enough" to write most tasks in.

The other point this article points is that the JS committee is adding more features to the language. While most of them are great, if they keep adopting every feature form other languages that they think are "neat" the language will become like the chicken-pig-goaty thing the article describes.

It will become C++Script.

They can compete in the back-end space, but they are good at different things.

Node:

- Great for keeping one language in both back-end and front-end (if you're making a web app). - Has package managers that are battle proof, like npm (which is taking a lot of heat recently due to politics and implementation "issues" that broke peoples builds for 1-2 days). - Is asynchronous by default. Making it a good choice for certain use cases.

Go:

- Great concurrency model - Small language spec, easy to learn and become productive with (this is my opinion) - Single binary build - Great standard library

The fact that Go is getting lots of references in HN might be that it is simply picking up attention, which is normal for any good technology.

Node is also very popular (much more than Go).

Anyways, choosing one over the other seems to be more of a choice on which language you prefer to write in. Unless your use case rules out one of the two.

Edge cases like the ones mentioned on this article will keep happening more often with the increased access to the internet worldwide.

Either programs deal with these cases more intelligently or some family names will stop existing, virtually speaking.

I have lost count of how many different versions of my last name I have since I moved to the United States. My health insurance, car insurance, apartment contract, driver's license, passport (this one has the correct name) are all spelled differently because some systems here don't accept white spaces on last names, so they add dashes. They length constraint is a short number, so they concatenate my 3 last names into a humongous word. Etc.

I always find it funny, except when I need to, say, take an official certificate test and the name I put on the registration doesn't match to one on the IDs I bring, therefore I can't get admitted into the testing center.

Of course I learned how to work with the system by now.

Agreed. WebAssembly won't make the JS framework landspace stop from changing. But it maybe he meant to say that with WebAssembly, other languages will be able to be used in the browser, so maybe JS will see less rapid changes.

This blog post was 3x longer than it should have been. The SO survey results explain the situation clearly enough, which already makes it obvious that everybody's perception about JavaScript being used in almost every aspect of programming and by most of the devs, mostly because it was implemented first on browsers, which are now some sort of ultimate medium for applications.

But anyways. This seems to be just a repost of the SO survey to what appears to be a victory to JS lovers.

Moral of the story. Choose simple design, and test your code. Am I missing something?

Btw, this website is great! I really enjoy the writing approach.

I agree 100% with this.

I used to bring in dependencies with the "don't reinvent the wheel" mentality. Then I realized how much trust I'm giving to the authors of all dependencies I pull in. Now I tend to do my best to understand the dependencies I bring so I can improve them if I can.

The only problem I find with this decision is when I make an improvement/fix a bug on a dependency, and the project is either inactive or the authors don't give a crap about your work.

In addition, Visual Studio Code is another editor that is competing for space in the dev world.

> Granted I would expected it to be slower using an interpreted language

Javascript isn't interpreted, it is dynamically typed, but there is a compilation process before any JS code even executes.

The plugin system is great. But updating, searching, parsing, is very slow. Have you tried displaying the keybindings? It takes forever.

While I love Atom for small projects, its slowness is what drives me away for large projects.

One great thing that came out of it was Electron though, neat piece of software.

Note: I run it on the beefiest 17" mid 2015 Macbook Pro.

Agreed. This article isn't intelligent. It is just a rant that makes no sense to people that don't travel/commute a lot or can't afford to have a tablet + laptop (let alone overpriced Apple stuff).

I commute for 1.5 hours to and and back from work, my 17" laptop never bugged me, even though it might bug people sitting next to me.

This is a great idea to be exploring even though, as a developer, I think this just some fancy tech that has almost no use. Like already noted in a another comment, if you are on the go the phone can't replace a laptop.

However, it becomes more exciting to experiment different things with a versatile phone running Maru or something similar.

What would really like to see are tablets running non-Android linux, and iPads with OSX instead of iOS.

A great introduction for the go/* subpackages.

Decentralization is great, even when it breeds open source drama :)