Thanks to you I found something really useful. With this I can finally have the convenient replacement for the good old private window which gets overused for logging in to multiple accounts simultaneously.
An incredible project considering the average longevity of other vim key browsers and their limited communities. This one is loads better with a good renderer unlike most light weight browsers. (Qtwebengine which is just qt for blink because webkit is old now). It even has adblock.
Or OpenMW which does the same thing for Morrowind (The Elder Scrolls 3). The main difference here being it runs on Linux natively and fixes tons of engine bugs that never were. They even have their own map editor for Morrowind which is just awesome.
Engines are easier compared to the assets. You only need programmers writing code (hard but easier than finding teams to work on assets)
I think upx is more useful for static binaries like that of Haskell applications which is kinda huge. (GHC produces huge binaries - eg. pandoc or ghc-mod). A 100 something mb binary is not what you usually have. UPX can work its magic stuff like that. More manageable not necessarily essential but when you need it you need it badly.
When I first found upx I did this a couple of times only to fail pretty badly and then I stopped doing it. This was like 7-8 years ago when I first tried the portable version. Never found the cause till today.
Does proper version control mean using github or just a git repo or something of that sort? I guess the developer wants to keep it a single dev project (old fashioned but the small project size means it doesn't make a big difference).[1]
This may be because there is so much low quality stuff everywhere while only the good and high quality ones survived from the past (Survival of the fittest I guess). So the past looks like it was all good but the present is mostly rubbish.
Nearly as fast as Numpy but never faster for jitted code while for the first run it takes longer as the jit need to generate llvm code the first time. If your calculation does not use unsupported features like classes (last time I checked they were not supported 1 year ago) and needs to be written as a loop rather than vectorized code, numba can be used to speed it up.
I believe Scipyconf 2016 had a talk on numba where he goes into it in great detail. Just search it up on Youtube.
Anything that is not convenient to be written as numpy arrays can be written using numba. Also it works with pure python code so your prototype can be used at scale with nothing but a decorator.
It is quite for common things but searching uncommon ones always throws it off. Searching for research publications in a specific domain or just haskell or some thing like just returns 1good result with 10 bad ones. So I use !g for those.
Also the autocorrect really throws my search terms off while Google does is right most of the time.
WOW! The website looks so shiny just for hosting a single font. Almost thought it was some website advertising Hack the language related stuff. Great web devs behind the site. Kudos to you.