i literally have no clue if this is a memory leak or its just . thats just how it is (remember that servo is still in early alpha releases , this is 0.0.1 , and memory optimization is probably definitely not a priority rn)
what this means is that i might start looking into the servo gtk wrapper library and begin to familiarize with the api
servile is gonna be gtk . im not gonna bother with qt because thats one of tge two things i despise about qutebrowser . but it wont look like a gtk ui , and i wanna keep the ui as minimal and close to qb as possible
also i cannot be bothered to not use a pre existing ui toolkit , or web render everything the way some other servo browsers already do . sorry to disappoint @coolbean lol
anyways yea . big project probably
@coolbean is embedding lua a good idea . for config and scripting . hm..
@coolbean interesting …… wait actually isnt there some lua runtime written in rust
@coolbean because the library i wanna use is a rust library and thats waaaay better handled from rust . embedding lua in rust is also fairly trivial . and rust is more fun in general