dpc_pw
Joined 11 years ago
Joined 11 years ago
With wallets like Breeze & Phoenix initial onboarding of new users to LN is quite painless because they offer in-flight inbound channel creation (for a tiny fee). So you can install and accept payment right away. Strike mobile app allows to easily fund your LN wallets with smallish amounts of money ($1-$1000) very quickly - just plug in your debit card.
I have been kicking tires paying for my coffee in LN-accepting Palo Alto coffee shop before the lockdown and it worked OK. But in other situations LN payments did have some problems (usually lack of receiving liquidity on the receiver end).
Another road to Bitcoin scaling for payments is using sidechains like Liquid. I haven't tried it myself yet.
But generally I agree that payments on Bitcoin are not critical right now, as it is becoming a trust-less collateral and saving device for bigger institutions for who $10 tx fees are irrelevant. It might however force smaller investors to try out sidechains/LN for casual payments.
Sometimes a 3rd party library needs a fix, and you want to fork it, add your changes, and run with it like that until your changes land in the upstream.
Last time I had to deal with it was a PITA, because libraries were fully qualified, and now I wanted to make an override. In Rust I would use https://doc.rust-lang.org/cargo/reference/overriding-depende...
For impatient, the game is now playable in the browser here: https://torustrooper.xyz/
Having said that, if you need to use it, it's awesome that now it has a modern and saner implementation.
Buy a Thinkpad, Zenbook, Dell XPS, System76 laptop or some model known to have good Linux support next time.
Can't remember any problems like this in the last decade, but I always, always research Linux compatibility before buying any hardware.
How often website redesigns are only about html? Usually everything changes. New flows, new dialogs, new toolbars, new frameworks.
Often the web UI gets and Android UI and iOS UI siblings. Gets replaced altogether by a completely different UI, developed by a different team.
APIs change much less often, and can be shared between many UIs. You can also version them. How are you going to version a web UI? Like reddit with "turn back on classic look"? How long can you keep the old UI around just because you have 1000s tests around that use it.
> but the idea that the tests are inherently brittle is wrong
I don't think so. Tests are great calcifyiers (check my blogpost about it if you want). If you test though your UI, you're calcifying your UI. The more you test though it, the more you calcifying it. No way around it.
I wonder how many lives would been saved if we had mandatory 30 minutes jogging sessions, fastfood lockdowns and vegetable subsidies.