I think is more a observer bias, when you dwell in the HW circles as I do when my Arduino fingers get itchy (or I have some paid work on that realm :) ), you just see C or C++; some Python but more in the hobbie side. JS is not even in the radar most of the time. In general if you work with both, code and a soldering iron, you'll talk C/C++.
In the case of dev.to I've clearly notice a frontend bias, is somehow like the chicken and the egg problem (of course there is a clear answer the the chicken/egg problem, but I'm talking metaphorically), I wasn't there when dev.to was born but imagine they started with 3 post: 1 CS, 1 webdev, 1 embedded and then someone posted another a webdev article; now even if an heterogeneous group visit dev.to is more likely that a webdev will stay and post and then the bias towards webdev is even bigger and so on.
So if I have an idea for a post about some specific quirk of the ESP32 (a microcontroller), I would probably post it in another site if I want to be read. Naturally content starts to agglomerate. Sometimes some OS, backend or infrastructure slips but as you see they are also tangent to the frontend.
Sometimes is good to take a look outside, one can even realize that some "good practices", Agile and TDD are far from perfect and many times not even applicable :D
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think is more a observer bias, when you dwell in the HW circles as I do when my Arduino fingers get itchy (or I have some paid work on that realm :) ), you just see C or C++; some Python but more in the hobbie side. JS is not even in the radar most of the time. In general if you work with both, code and a soldering iron, you'll talk C/C++.
In the case of dev.to I've clearly notice a frontend bias, is somehow like the chicken and the egg problem (of course there is a clear answer the the chicken/egg problem, but I'm talking metaphorically), I wasn't there when dev.to was born but imagine they started with 3 post: 1 CS, 1 webdev, 1 embedded and then someone posted another a webdev article; now even if an heterogeneous group visit dev.to is more likely that a webdev will stay and post and then the bias towards webdev is even bigger and so on.
So if I have an idea for a post about some specific quirk of the ESP32 (a microcontroller), I would probably post it in another site if I want to be read. Naturally content starts to agglomerate. Sometimes some OS, backend or infrastructure slips but as you see they are also tangent to the frontend.
Sometimes is good to take a look outside, one can even realize that some "good practices", Agile and TDD are far from perfect and many times not even applicable :D