48 karma · joined June 3, 2015
I agree that a lot of businesses now actively don't manage cash as they used to earlier... it's very difficult to get low-value notes as the central bank seems to be slowly reducing the supply by not printing as per demand.
Both are areas where costs are going up at a rate which is much higher than official inflation rates, and comp increases often don't even match inflation!
So the need for working till you're forced to give up still remains.
Unless you can optimise your CI runtime to be very balanced and fast, you're going to have a lot of jobs queued during working hours ... although it costs more per minute, the fact that CI jobs are bursty means it works out not too much costlier but with less queue time.
Sometimes the discussions on PRs are equally valuable to see how a commit was arrived at, and I'd be sad if that got lost in this change.
In contrast, Lago uses AGPL-3.0 and has an open-core model (not sure if the premium features are source available or not), which makes it more clearer on how they're going to make money.
Lago is better in that they have have support for custom payment integrations [3].
[2] https://paystack.com/stripe/south-africa
[3] https://getlago.com/docs/integrations/payments/custom-paymen...
OTOH if the code is something that I've haven't looked at in a while or don't understand that much, I'll read around a bit and see if there's a way the diff can be improved.
Did you manage to find a workaround for https://github.com/wkhtmltopdf/packaging/issues/2? If so, would appreciate a PR :-)
test1 test2 test3 test4 test5 test6 test7 test8 test9 test10 Average
cloudflare 3 ms 3 ms 2 ms 3 ms 3 ms 123 ms 3 ms 2 ms 3 ms 6 ms 15.10
cloudflare2nd 3 ms 3 ms 2 ms 3 ms 3 ms 2 ms 3 ms 2 ms 2 ms 3 ms 2.60
google 61 ms 61 ms 61 ms 61 ms 64 ms 273 ms 61 ms 64 ms 61 ms 62 ms 82.90
google2nd 1 ms 1 ms 1 ms 1 ms 66 ms 62 ms 2 ms 64 ms 1 ms 1 ms 20.00
quad9 124 ms 126 ms 124 ms 124 ms 124 ms 118 ms 127 ms 121 ms 125 ms 179 ms 129.20
opendns 2 ms 2 ms 2 ms 57 ms 5 ms 261 ms 2 ms 245 ms 2 ms 2 ms 58.00
norton 4 ms 4 ms 4 ms 5 ms 4 ms 4 ms 4 ms 4 ms 3 ms 4 ms 4.00
cleanbrowsing 225 ms 232 ms 235 ms 214 ms 232 ms 225 ms 219 ms 245 ms 233 ms 218 ms 227.80
yandex 136 ms 139 ms 142 ms 138 ms 140 ms 141 ms 136 ms 142 ms 142 ms 142 ms 139.80
adguard 205 ms 205 ms 196 ms 196 ms 217 ms 211 ms 212 ms 197 ms 205 ms 211 ms 205.50
neustar 233 ms 232 ms 236 ms 235 ms 233 ms 243 ms 246 ms 242 ms 232 ms 227 ms 235.90
comodo 132 ms 134 ms 133 ms 133 ms 133 ms 130 ms 130 ms 130 ms 131 ms 145 ms 133.10https://bugs.chromium.org/p/chromium/issues/detail?id=603559
Not sure if all the full functionality that wkhtmltopdf can be ported, it had patches to Qt/WebKit to enable that ... probably will need API enhancements in Chrome. Don't have the time right now, but I registered http://crhtmltopdf.org a while ago hoping that I'd get around to it.
Why am I walking, where am I running
What am I saying, what am I knowing
On this guitar I'm playing, on this banjo I'm frailin'
On this mandolin I'm strummin', in the song I'm singin'
In the tune I'm hummin', in the words I'm writin'
In the words that I'm thinkin'
In this ocean of hours I'm all the time drinkin'
Who am I helping, what am I breaking
What am I giving, what am I taking
But you try with your whole soul best
Never to think these thoughts and never to let
Them kind of thoughts gain ground
Or make yer heart pound
But then again you know why they're around
Just waiting for a chance to slip and drop down
-- Last Thoughts On Woody Guthrie
Switching to Blink is obvious, but which wrapper to use (CEF, Electron, etc) is hard to decide. Because they all use a multi process architecture, supporting the API around which the tools are built is not really possible. Time to work on it has also been in short supply in recent times.
So, good work by the authors. Wish we could get something better, but as long as browsers move at the pace they do, it's going to be tough.