@velartrill I just woke up, so perhaps my brain isn't QUITE functional, but -
exactly WHAT does sending bytes around have to do with premature optimization?
Premature optimization is an _anti-pattern_ developers should avoid EXCEPT in rare cases.
@velartrill I ABSOLUTELY agree that compression of bytes saves energy. As does writing code that is efficient. Spending some time assuring that your code does not waste energy - or using the right tool for the job, rather than just the one you have - that also can save energy. Saving energy is a _good_ practice.
If your comment was intended to say that optimizing code can reduce energy, and therefore this is good: then I didn't find that before writing this 2nd statement.
@velartrill An example of wasted energy caused by code that should NEVER have been deployed to production:
SQL query run to match 2 lists; but first list had no integer identifier, and it's primary key was the email field.
WHICH WAS A FULLTEXT FIELD.
This simple query would take over 24 hours and, as it could not be fixed without affecting customers, required adding 8 processors and 24 gigs of memory to just get it to run in 24 hours.
Fixed query: 2 minutes. 128megs. 1 cpu.
@velartrill Had someone pointed out to this developer (and management) that this query was WOEFULLY inadequate, and the reason why, he'd have fixed it. And every time he writes a query now, or designs a database, he checks that he is using best practices.
That's not premature optimization.
That's doing your job well, and saving energy.
(This story can be modified for those who put money before energy by talking about the COST of energy wasted. Sometimes that change is needed.)
@Shamar @velartrill also if you happen to run into any nice, _working_ minimal browsers (that don't insist on using _ONLY_ vi keys, or can be easily altered to do basic things with other keys for navigation) then let me know.
surf is... not really working that well these days; netsurf has http2 issues; midori ... crashes...
and I don't have time to go fix them ):
I also like #NetSurf because it's written in plain #C and thus pretty portable. The codebase seems pretty readable and well organised too, so it could be another good choice if you want to learn about the internal of a browser and hack something like that.
The problem I see with Netsurf is that it aim to implement the standard, while the standard are designed to keep all #Chrome's competitors out (see #Edge end of life).
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!