Is there some other meaning you had in mind when asking this, or was this a pedantic question?

Also, I'll add that the "there is the door" comment is entirely wrong. There are countless stories of open source maintainers being harassed to make language changes to their code base, master/slave, whitelist/blacklist. The harassers never offered to do the work themselves just demanded it be done for them or they'll keep harassing. These were people matching into someone else's "safe space" to police their private language.

The government disappearing people and dismantling the country is very bad, and nothing good can be said about it. What I'm talking about are the individuals on both sides not formally in power, and their equal efforts to stifle what they see as "bad speech". It's that mentality, on both sides, that led us to where we are.

Not to say that I buy this EV hype, which is suspiciously timed with teslas weakening position.

Comments URL: https://news.ycombinator.com/item?id=43167453

Points: 1

# Comments: 0

It would be awkward to work with since you'd have to be aware of all of the eventual caller scopes rather than your current local scope when defining it.

I suppose it would be like macros instead of true functions.

It's not always 100%, but in general the fewer the dependencies the better the code.

Most battery packs have integrated power management chips, so you could focus on modifying the battery firmware.

You could have another component send a message to the power management controller to trigger it.

You could also use the power controller's internal current sensor and clock to watch for a device event (power draw from the screen at a certain time or the power profile for a specific set of CPU instructions), giving you means to trigger it without modifying any other part of the device.

That said, your topic doesn't sound like most people would consider on topic for HN. It shouldn't be flagged, but I'd expect it to be buried.