To stop asking “why” when debugging…
You think you master Javascript because your daily work is Javascript. But one day, the apprentice of your company comes to you and asks you why the result of his statement is not the expected one. And you start sweating... That’s why you need this article as much as I needed those explanations.
We will go through common javascript wtf and explain the logic behind them. At the end of this article, you’ll perhaps not better like the language, but at least you’ll know why 😉
Let’s start with :
1. Strings
A string is not a String
Let your end-users configure their own application layout with drag-n-drops….
Imagine a dashboard application where you have several widget that act as indicator for the daily business of the user. But there’s different users. The one, that mostly check the Widget1, the one that would love to have Widget2 in the aside region of the app, the one that don’t care about Widget1 and Widget2 and wan’t to have Widget3 take the whole space, etc. …
Make your legacy app great again…
Introduction
Why would you do that ?
A developer’s job is rarely only working on edge technologies and starting every 2 months a new project from scratch (it’s what you do ? then keep that job, it’s the dream job of everyone 😊). A lot of a developer’s job is maintaining legacy application because they still bring money home, but perhaps not enough to be rewritten every 5 years. Sometimes it’s the technology that’s old, lot of time it’s the whole code base that is creepy (I already hear you yelling at code authors about that shitty implementation even if you was the author 😁). So when…
…at least, if you’re new to the webpack world.
These are certainly not hidden features as you would find them somewhere in the documentation. But if you are like me and only read the documentation when you want information about something you know that exists, then you will like this article for the potential things you don’t know that exists 😊.
Browse Webpack-dev-server in memory files
Webpack-dev-server is awesome. You can watch file, live-reload,… But most of the time, when I start a new configuration, I set wrong path to ressources and nothing is working. And as the dev server keep generated bundles in memory, you will have to run a build to see…
Les composants web ne sont rien de plus que l’habituel combo HTML/CSS/JS. Pourtant, lorsque vous voudrez commencer à y ajouter du style, vous aller rapidement vous prendre un mur : la barrière du scope Shadow DOM.
Je ne vais pas ré-expliquer ce qu’est le Shadow DOM, ceci ayant déjà été fait dans un précédent article. Mais pour fixer le contexte, je vais juste vous rappeler que le shadow DOM permet d’isoler le HTML afin qu’il ne subisse pas les effets définis dans la page qui l’intègre. …
Breaking the monolith
Introduction
Les infrastructures Microservices sont le fruit d’un constat simple : les applications monolithes sont difficiles à gérer, maintenir ou moderniser. Il fallait donc trouver un moyen de réduire la codebase en petit sîlots qui seraient plus simples à faire évoluer.
Cette solution trouvée pour la structure “back”, il nous reste toujours la problématique du web front où nous avons une SPA qui est en fait un monolithe en soit. La gestion de modules, le lazy-loading, etc. nous permettent d’améliorer la structure, mais la codebase reste commune. Il nous faut donc maintenant splitter cela et ainsi créer des micro-frontends.
TL; DR;
Les architecture…
The list of available Web API is growing every month and so the browser’s support. The goal of the Web-Consortium is certainly to provide as much device API than what’s available to you when using native apps on your smartphone.
What is the feature you use the most on your mobile ? Probably your Camera. Today everyone as a photo camera in his pocket and can even use it to make video-calls, to scan bar-codes or document, or to play with Virtual-Reality (VR) and Augmented-Reality (AR).
Today we’ll see how we can use the camera from a webpage with the…
Suite logique de l’article précédent concernant la v1 de Custom Elements, on va s’attaquer aujourd’hui à ce qui à changé entre la v0 et la v1 de la spec Shadow DOM. Dans tout les cas, sachez que la spec n’est toujours pas au stade de “final” et donc que ça peut encore changer…
Retour en arrière
Pour ceux qui n’ont pas connu la spec v0, sachez que le Shadow DOM est une nouvelle spécification mise en place par le Working group du W3C afin de pouvoir isoler une partie du DOM du reste de l’application. Cette spec fait tout son sens dans le…
I wanted to use my Raspberry Pi 3 to host a .Netcore WebApi as now Microsoft turned their framework open-source. But my journey to a .netcore Pi was not as straightforward as what I first thought… So here is a small “how to” that you can use if you want to achieve the same in less time.
Install Raspbian
This step is pretty easy and that’s why I will lead you directly to the official documentation which contains everything you would need to install you PI https://www.raspberrypi.org/downloads/raspbian/
Install .netcore
A quick “how to” article
What is HATEOAS
If you’ve never heard of it, the HATEOAS acronym stands for “Hypermedia As The Engine of Application State”. It’s a model developed by Leonard Richardson that bring the REST model to a new level. You can find a complete description level by level from lvl0 to HATEOAS on Martin Fowler’s blog.
A simplistic explanation is that when you request the API, the response will returns you the object you are looking for, but also some described links to inform you how you can alter that given resource. You can also complete these link list with information about how to fetch…
