The most important lesson that the success of JavaScript has taught us

Remo H. Jansen on January 27, 2018

The incredible rise in popularity that JavaScript has experienced over the last decade has been spectacular. According to the yearly developer su... [Read Full]

Is wishful programming the same as test driven development ?

For me they are different, is more like sketching for UX design. Sometimes I find myself with a piece of paper, not an IDE or a text editor, writing down how I would like an API to be like so it is as dev-friendly as possible, once I reach something I feel happy about I proceed to implement it. During the implementation phase, sometimes I use TDD but not always.

I do agree that they are different, but related, matters. And the description you provided illustrates it very well.

I would only add that I am pretty much a TDD practitioner, and not doing it is my utter-most exception. Thus I would say: always use both of them. Be wishful. Do TDD.

Unfortunately I'm not a JavaScript developer myself to quote/point to JS TDD practices (by that I mean that JS is not a language I'm proficient at, even though I'm not a stranger to Node and Angular) but I'm sure it's not hard to find the references if you ask around. :)

IMO, it is more basic.
Javascript boosted in popularity thanks to the web. If you want to build webapps, you have simply no other choice.
I think this langage is a pill of crap mostly because it lacks typing. Therefore all my projects are written in TypeScript.

Javascript boosted in popularity thanks to the web.

Exactly, it is accessible because JS is in web browsers.

Incorrect, javascript boasted after nodejs.
Javascript is destroying bigtime on backend and people who do use nodejs are one the most sophisticated programmers out there.

NodeJS is one the most popular choice when it comes to microservices, realtime-time services, services with high I/O , streaming, proxying and specially when you are working with NoSQL/Object store there is no better choice than nodejs

What is Javascript destroying in the backend? All I see in 2018 is people realizing that they don't care about Node's asynchronous nature in most web projects, thus minimizing Node's expansion: w3techs.com/technologies/details/w...

And in the cases where you care about non-blocking IO, the PHP community has a solution available: reactphp.org/

Meanwhile PHP is easier to set up, easier to learn and has a far more mature ecosystem than Node does. There's just no reason to go towards Node if you want a CMS for example, and Laravel is also one of the best frameworks in existence. These things actually matter more than a few performance benchmarks or made-up scalability concerns which can ultimately be solved (see Facebook), especially since PHP7 and ReactPHP exist.

If you don't want PHP, you have Python which is a joy to code in and is one of the most coherent modern languages. It's immensely helped by the likes of Django and Flask if you want to write web apps, those are some seriously good frameworks. Maybe it doesn't have such a rich assortment of CMSs but it's a seriously strong alternative.

Java is also a very strong contender when it comes to web services. I personally don't like it, but nobody can deny its strength.

Your opinion that Node is destroying everything in the back-end is, as a result, false. Node has immensely strong competition and has barely managed to dent the back-end marketshare.

"people who do use nodejs are one the most sophisticated programmers out there."

This is the most useless and biased piece of text in this whole comment section.
A little advice: the web space moves really fast, it's an ill act to fanboy over one technology like you're doing right now.

people who do use nodejs are one the most sophisticated programmers out there.

That is fanboy talk.
NodeJS is crushing nothing.
It is not used in most of the tech companies.

Please know that I saw your comment part questioning my programming capabilities before you erase it.

I doubt your credibility as a programmer as you use typescript when you have es6

I contributed to numerous open source projects among them Hibernate, Chrome, Spring and Maven.
PTAL github.com/pulls?utf8=%E2%9C%93&q=...
But maybe you googled me after posting your comment.
So I think I am entitled give an opinion on the subject.

Whatever the context, we should try to question the hype.

Last week, while every hipster was crying on the roof that Gradle >>> Maven, we discovered that Gradle was not so great.
Gradle support of Java 9 (started in 2016) is still experimental and buggy. By default, Gradle log output give zero information in case of failure. You cannot debug your Gradle script from IntelliJ.

Docker is another type. I think Docker is great, but not being able to start a container as the current user without scripting it is just lame.

I tried node as backend on little projects.
I think node is way behind JVM in the backend land because:

  • The ecosystem is not mature
  • Monitoring/profiling is not mature
  • The single threaded aspect is just an issue more than anything else
  • javascript (can be fixed with TS)
  • if you want to go all async, you can use Vert.x

But I enjoy building node CLI tools. With TS. I use it to build frontends. With TS.

At work, our main soft is a Java project made of 19 Millions lines of code. Can you imagine that with a weak typed langage like Python, Javascript or Ruby? You may answer microservices. But even a microservice have a few thousands lines of code.

IMO, weak typed langage are good for prototyping and other disposable projects.

I understood your position about accessibility of the JavaScript and hence the qualities of its community. I have a few side questions:

1) Judging by your surprise at the success of JavaScript, do you believe that JavaScript is not "a good programming language"?

2) Who, in your opinion, should carry the burden of proof, people who believe that JavaScript is "a good programming language" or people who believe that JavaScript is not "a good programming language"?

1) I consider JavaScript a very good programming language. However, I do acknowledge that in its early days (prior to ES5) some of its features created some issues (e.g. scope).

I personally use TypeScript because I enjoy working with types and I believe they make my life easier but that doesn't mean that JavaScript is a bad programming language.

I think accessibility has contributed to the success of JavaScript but it has also contributed to the misunderstanding of it. JavaScript is very easy to get started with but it is not so easy to master. So a lot of people got started with it without spending the time necessary to understand things like prototypes or closures.

2) I think no one needs to proof JS is a good or a bad language. If you like it, enjoy and if you don't like it, that's cool too, don't use it. Every language has pros and cons. For example, being single-threaded could be seen as a weakness but JavaScript (node.js) can be very good programming language to implement a proxy because being single-threaded (and non-blocking I/O) allows it to handle a lot of HTTP requests.

Great article! I was really surprised by the content, having expected something completely different based on the title. The accessibility angle is really interesting in the context of JavaScript, but also in programming in general, and even product development as a whole generalised topic.

Thanks for this food for thought!

At the end of the day I don't love programming in JS the way I LOVE programming in Ruby. I program in Javascript because I'm probably a lemming.

code of conduct - report abuse