L’ACM arrêtera ses publications papiers en 2024 : une page “papier” se tourne, une page “numérique” s’ouvre…

Ca me fait un petit choc de voir que l’ACM arrêtera en 2024 ses publications papiers pour des raisons environnementales.

Continuer à lire

Au delà du Mobile First et des problèmes de dispersion de l’information

D’après une étude du NN/g, l’approche Mobile-First peut avoir des impacts négatifs en termes d’efficacité de l’accès à l’information quand on est sur un desktop. En effet, il semble relativement évident que le contenu doit être adapté au média et qu’on ne présente pas l’information de la même manière sur un flyer ou sur un journal.

Continuer à lire

Le 8ème Principe “oublié” du “Local First”

Le mouvement du “Local First” a émergé des États-Unis avec une vision innovante pour le développement web, en particulier pour les Progressive Web Apps (PWA).

Cette approche consiste à développer les applications en utilisant d’abord les données localement et en les partageant aux autres utilisateurs via des mécanismes et protocoles de synchronisation. Elle repose sur 7 (sept) principes fondamentaux qui visent à transformer la manière dont nous concevons et utilisons les applications en ligne. Voici ces 7 principes, tels qu’énoncés par les chercheurs de Ink and Switch dans leur publication fondatrice (*).

Continuer à lire

Install your own (eco-designed) Sweet Home 3D Online server

In this post, I will explain the requirements to be able to install your own Sweet Home 3D Online server. I will also talk about performance, eco-design, white branding and commercial licensing issues.

Sweet Home 3D

Sweet Home 3D is an Open-Source plan editor for home design and floor planning. It comes with a real-time 3D viewer and allows the users to generate realistic 3D photographs (ray tracing) and virtual visit videos.

  • It has a strong community.
  • It gets more that 10.000 daily downloads.
  • It has 15 years of experience in home design, floor planning and other industries.
Continuer à lire

Intervention de Cinchéo à “Tech4Climate?” – L’éco-conception logicielle : quelques constats et conseils pour démarrer

Le 9 juin 2022, j’étais invité à intervenir dans l’atelier “Les acteurs du numérique au service de la transition” de l’événement “Tech4Climate?” organisé par le groupe Constellation.

Pour celles et ceux qui n’ont pas eu la chance d’y assister, voici quelques photos et le résumé des messages que j’ai fait passer.

Continuer à lire

Inside DLite: low-code components, model-driven tools, local-first and eco-design explained

DLite is an Open Source Low-Code platform that is designed to help building web front-ends. It is based on Web standards, such as the Vue.js reactive framework, and Bootstrap, the popular UI kit for responsive web design. In short, the core of DLite is a wrapper around BootstrapVue, including basic low-code components such as inputs, and more advanced components such as tables. Also, DLite comes with additional low-code components such as graphs (a chart.js wrapper), and many layout components such as containers, splitters (a split.js wrapper), tabs, and many others.

DLite’s comes with the following Open Source key elements:

  • Many low-code components to build UIs fast;
  • Model-driven tools, such as a model editor (which can create models inferred from a JSON structure), and builders, which can automatically create full forms and CRUD editors out of a model;
  • A local-first API and service (including an Open Source server for a sync service);
  • A builtin probe to measure consumed resources (in order to help with responsible software development and eco-design).

In this post, I will explain how these 4 key elements work. The source code for all these is available here.

Continuer à lire

Food for thought about Software Eco-Design

Things are not simple when it comes to Software Eco-Design.

Eco-Design is about maximizing a software Efficiency function of Usage, which can be defined as a ratio :

Efficiency(U) = Utility(U) / Resources(U) (U = Usage, a parameter)

  • Utility is related to the amount of useful work you can do in a unit of time (the word useful is important, because it depends on the context and what you need to achieve).
  • Resources, for software is the amount of computation, data, I/O you use, which in turn, corresponds to an amount of energy (electricity) and hardware resources (servers, routers, wires, satellites, laptops, smartphones, …). The more software resources your application use, the more energy you will need, and the more powerful hardware you will use.
  • Usage (U), corresponds of how your software is used. Usage is about how often your users will connect to the app, how many, from which county, etc. It is a parameter of Efficiency, Utility, and Resources because software impacts heavily depend on how the users will use it. The same software used differently may use up different amount of resources or have different utilities. Most importantly, Efficiency, Utility, and Resources might not be a linear function. Think of Amazon for instance: the utility might vary largely depending on the number of users, and the resources on where those users are located on the planet.
  • Energy and hardware resources end up to be direct impacts on the planet, contributing to climate change or environment destruction (side note: the IT sector is expected to reach 10% of GES within 5 years, that is to say the equivalent of all personal vehicles worldwide).
Continuer à lire

When Low Code meets Local-First Software

In this post, I explain the dLite low-code platform approach to build frontend applications. dLite relies on a new paradigm called the Local-First Software paradigm. With this paradigm, one can build applications using local data, which remains the ownership of the user. A generic synchronisation protocol is used to access the data cross-device, and a sharing protocol is used to share data among users and build collaborative applications. I explain that the Local-First paradigm is particularly well-fitted to low-code, since it removes the need of a specific backend and database for each application. Additionally, security and data privacy comes by design, so that all the complex access-right management usually required on the server-side for collaborative applications is not required anymore. As a consequence, it drastically reduces the complexity of the application as well as its maintenance and evolution costs. Last but not least, it is Green IT friendly since it opens the door to a better use of resources by reducing remote invocations, taking better advantage of the terminal (client) side computing power, and saving complex server-side CI/CD, application-server layers, and huge centralized databases.

Continuer à lire

MC2: a tool to remotely monitor computer resources

For more than a year now, EASYTEAM and Cinchéo have been working on a project that aims at creating new methods and tools to help IT departments to control the carbon footprint linked to digital services. It is a vast and complicated topic and a lot needs to be achieved. With MC2 (say M-C-square), we are contributing a small and modest part to the tooling ecosystem.

In this post, I will explain the principles of MC2 and how it works. The source code is fully available on Github: https://github.com/cincheo/mc2.

NOTE: MC2 it is still work in progress and is a small part of a wider R&D project involving EASYTEAM (Constellation group) and INRIA (Spirals team).

Continuer à lire

Back to the Future: let’s stop buying new Laptops and Smartphones ;)

When I was a teenager, I used to go to the center of Paris to buy specific parts to build my PC myself: sound cards, video cards, power blocks, hard drive, CPU, fans, memory, you name it. Not only it was fun and instructive, but it was also good for the planet.

Continuer à lire