Looking at it and very excited. In unsupported features, charting is mentioned. Could there be any value in not directly implementing the drawing of charts, but tie in to other open source library? Just curious of your thinking.
Yes do the same for ICE - very constructive suggestion. Completely unnecessary to call the argument silly though..
There are marked differences in what's needed in an EV vs an ICE, most obvious of which is the giant battery with a very different supply chain.
So basically your source is: "trust me bro, I'll prove it to you?"
I think it is a relevant question. We cannot go around calling someone genius prompt engineers, and then skip the engineering part of noting down what actually works and how it can be replicated. Could we try to work backwards not from the perspective of the problems of the person asking the question, but perhaps work backwards from your claims (I.e. to where you have them from)
I like that you chime in on this and think better cooperation makes more sense here. I assume you also have no interest in enshittified, slower, more expensive, environmentally worse, lower quality Internet.
From your point of view, what are potential options/directions to approach to solve some of the issues arising from f.x. crawlers, bota, and other detection-avoiders?
I am genuinely curious here
My take from this comment is that maybe you do not understand it as well as you think you do.
Claiming that "other modern infrastructure" is easier to understand than CSS is wild to me. Infrastructure includes networking and several protocol, authentication and security in many ways, physical or virtual resources and their respective capabilities, etc etc etc.
In what world is all of that more easy than understanding CSS?