How to detect current culture in javascript

Detecting the current culture in javascript can be really useful in many cases, for example when you have a dropdown with the list of languages and you want the user’s preferred one already selected.

I am getting a little lazy these days, I would like to write more articles about software architecture, design patterns or fancy techs like MongoDb and so on…. but I am moving to another country and packing an entire house is taking away all my time and energies.

So this is just a quick post showing a couple of ways to detect the current culture in javascript. Probably just a reminder for my sloppy memory ūüôā

Based on the docs on the MDN website, the window.navigator object exposes a language property that represents  the preferred language of the user, usually the language of the browser UI. 

The compatibility is quite good except as usual for IE Mobile, however there are two valid alternatives, userLanguage and browserLanguage.

In case you want the list of all the preferred languages for the user, there’s an experimental property you can exploit, navigator.languages. That’s an “experimental technology”, so the compatibility list is still short (eg. Chrome and Firefox, as usual). It’s a string array containing the list of the user’s preferred languages, with the most preferred language first. 

Based on the docs, navigator.language should be the first element of the returned array but if I check the values in Chrome I get this:

navigator.languages -> [“it-IT”, “it”, “en-US”, “en”]
navigator.language -> “en-GB”

Weird, isn’t it?

My guess is that navigator.languages returns the list of the user system preferred languages, while navigator.language gives instead the current browser’s language. 

Searching on StackOverflow there’s a good answer to the question, I have extracted the code in this gist (link in the code):


Recording of Webinar Introduction to React & Typescript available

Last Saturday I had the chance to run my first webinar, thanks to my friend and ex-colleague Lalit Kale and the folks from Indiamentor.

We discussed about React, pros and cons, why should someone use it instead of AngularJS (for example eh, no puns intended) and how to setup the dev environment. Then I showed a small demo of a hello-world-like application made with Typescript using Visual Studio Code.

Later the same day, the Indiamentor team has also uploaded on Youtube the complete recording:

Unfortunately due to some obscure technical reasons, the streaming software decided to stop updating the screenshare after a couple of slides, so in the video you won’t see the second part of the presentation. However, I used Google Presentations to create my deck, so here’s the link ūüôā

I had a very good time preparing the slides and talking to the audience, even if I wasn’t actually seeing anyone. I am really starting to think that maybe I could prepare some coding or software architecture lessons and begin running¬†some (online) courses.

Data pagination with NodeJS and React


here’s the link to the GitHub repo.

Some time ago, in one of my articles I showed a way to paginate your data using WebAPI on the server and AngularJS on client-side. Funnily enough I wrote that post exactly two years ago, I just noticed it while writing this. Well, turns out a lot of people is still searching for it, so now, after two years, I have decided to write another couple of notes but with a different tech stack.

Yes, of course, I could have used the same backend from the old article, but where’s the fun in that?

Enter NodeJS and React!

So, let’s start with the server first. As you can see from the sources, I used Typescript this time. To be honest, I don’t feel “safe” while writing Javascript code, even with lots of unit tests. Having some form¬†of “strongly-typed” language is a little bit of relief, at least for the .NET coder in me.

The architecture is very simple: we have an express application with just one Route ( /api/products/ ) exposing a GET action which reads from a Repository the paged list of available products. Due to the nature of the example, I decided to keep things simple and not add any kind of IoC container, just to avoid to overcomplicate the code.

I have also added two middlewares, one to console.log() all the incoming requests and the other to allow CORS for a¬†specific¬†domain ( eg. our client application ). In case you need to refresh your memory, here’s a nice article about NodeJS middlewares.

The core concept that you can see from the Products API is to return an object that exposes the list of Products along with some infos like the total number of pages, the total Products count and the current page number.

Let’s talk about the client now.

I was definitely not disappointed discovering that the learning curve for React is actually very, very low. Coming from the Angular world, I was expecting more difficulties, but in a matter of hours I have been able to setup my dev env with Typescript ( wanna know how?  ) and start coding my components.

Oh yes, don’t miss my webinar this Saturday! I’ll do a quick introduction about Typescript and React.

Ideally, I could have served the client part directly from the NodeJS application, but I preferred to keep everything separated. Yeah, I had to activate CORS, but it’s not really a big deal. Also, it makes everything more “microservices-oriented“, which is becoming more and more an hype these days. In my mind, for that kind of architecture you should have two servers talking, but bear with me.

In our small demo, the client is using a service to read the products, displays them in a table and renders a pager at the bottom. As you can easily notice, I am using the fetch() polyfill to perform the AJAX request.

Also, to make things more interesting,¬†in this case I am using an IoC container, Inversify, to handle dependencies. However, since Components are instantiated directly by the React engine we cannot use constructor injection but have to revert to property injection….which in this case is handled by the @lazyInject decorator. I’ll write another post about the subject in the upcoming future.

For now, if you enjoy the example, don’t forget to write a comment!

Webinar: introduction to React & Typescript – again!

Due to the huge amount of registrations, me and the folks at Indiamentors have decided to postpone the Introduction to React & Typescript webinar to Saturday September 17th at 6:30 IST .

As I told you before, this webinar is going to be an introduction about React,  how to setup your dev environment and how to write your first piece of React code.
I’ll show you a small¬†demo and at the end we’re going to have a nice Q&A session.

Here’s the agenda:

  • Why React?
  • Let‚Äôs get started!
  • React Components
  • Properties and State
  • Webpack
  • Demo

Make sure to register and reserve your seat!

Webinar: Introduction to React and Typescript

Just a quick update: thanks to my good friend Lalit Kale who invited me, I will be running a webinar this Saturday about React and Typescript.

It’s going to be an introduction about how to setup your dev environment¬†and how to write your first piece of React code. ¬†Absolutely no rocket science involved, we’ll discuss¬†about pros and cons, there will be a quick demo and I’m sure it will be fun (at least for me).

It will be at 6:30pm IST . As you may have guessed,¬†most of the audience is in India, also because I’m doing this in partnership with Indiamentor.

Here’s the link for the registration.

Don’t miss it!

© 2017 Davide Guida

Theme by Anders NorenUp ↑