hvasilev

First you pointed out your extensive experience as a basis for your argument and now when you realize you're completely out of your depths, you call us "locked in their ways" and call yourself "I am a hack programmer at best and I can admit that".

Fun fact: I'm actually not really seeing this "locked in your ways" as people get older, I see people asking about the cost-benefit of using a technology before using it a lot more. Just because I got curious, I took another look at the repo, there was a few libraries that I've never seen, but generally I'm up to date with what is going on (might have not used anything in production, but at least out of curiosity - I'm familiar). As I pointed out elsewhere, there are just literally 16 different languages used in this project and over 270k LoC.

I'm way past the stage of my life in which I feel a need to have a dick measurement contest online with random people about my experience, where I work and how many devices do we sell per year.

I think you might need emotional support in your life, take care.

I'm asking you what do you think about it, not what the devs think about it. Let me phrase it differently, there are a total of 16 languages and 276969 lines of code in the repo for a "soldering iron firmware"

what do you think is the proportion between boilerplate and tooling to actually useful functionality?

Given this ratio what do you think about the scope of this project?

I'm not sure why or when, but it seems to me that at some point this industry stopped trying to solve real issues.

i honestly didn't read half of this post. i have no interest in engaging into this sort of conversation. have a nice day.

> This is a project which builds firmware for multiple devices and processor architectures, supporting developers running various operating systems locally, and includes support for documentation generation and firmware localization.

exactly the source of the issue. The scope of the project is just preposterous for what it is. I'm not sure what the proportion between boilerplate and actual useful functionality would is, but from the little that I saw it is outrageous.

> Besides, you can always treat a built Docker image as a stable toolchain archive if that's a concern; there's little reason to assume that it won't work 12 years into the future as

I heavily disagree with this assumption and the rest of the assumptions related to the stability of the dependencies.

I don't think it is a "me" issue. On the contrary, I think this project has a lot of issues similar to what contemporary modern web development has. Generally firmware engineers know not to do this kind of stuff, since we have a highly derivative work that spans across decades.

I'll give you an example - because of chip shortages I had to redo a couple of devices and their firmware for the past few years. I had to dig into code that hasn't been touched for 12 years on more than one occasions and I had no issue compiling it more than a decade later. The reason why is because people weren't trying to be fancy and they kept the dependencies to a minimum.

Imagine if you stop pumping oxygen into this project for a month...

Well, it is unmaintainable, because maintaining this set of dependencies is absurd for what this firmware is and it is unreadable, because I tried to read it and lost interest in a few minutes later, because of all the bullsh*t.

because it is unreadable and unmaintainable with all of these dependencies. Even in the description it says that it spiraled out of control at some point

"Originally conceived as an alternative firmware for the TS100, this firmware has evolved into a complex soldering iron control firmware."

Oh wow, that is really bad. Like 10 different technologies and at least 2 programming languages for a soldering iron firmware.

You open source guys need to figure out a way to charge people for the value that you provide. You ran the experiment for a very long time and it looks like this "beggar" model really doesn't seem to be working for the vast majority of your projects.

Take money, don't wait for people to give you money for the free value that you provide.

Yea, me too. I don't really understand people that say that clean code is easier to understand.

The way that mammals learn is by play. Seems like the more the abstract something is, the harder it is to play with it, since it is by definition non-concrete. In order to play with these concepts, you have to do that in your head, which is non-intuitive (or maybe even impossible) for a large part of the population.

How did you know it was in Webkit or Blink? What was your thought process that lead you to this conclusion? Was it prior knowledge?