Technically it feels the same to me. Content-wise netflix is kind of a dumpster buffet, with a tons of meh stuff and a couple of really nice things. Disney has less content, but almost no low quality fluff.
It's easy to do things slowly, by the book, taking all the time in the world, while the world is waiting. It's part of the skill and mastery to know which corners to cut and which things are essential and which can be fixed later, and judge the effort to result ratio accurately.
LN situation is not perfect, but improved greatly last year.
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.
> Not sure what to you mean by 'fork&clone&submit&pr including 3rd party submodules'.
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.
Seconded. Especially for Go, because it's mostly a lowest common denominator of language features it's not hard to write the code itself. The problem is that the module system is different and had plenty of changes along the years, What I would really like is an up to date "learn how to handle Go project in 30 minutes" tutorial (initialize new project with all best practices, add modules, publish, fork&clone&submit&pr including 3rd party submodules, test, CI, profile, debug).
I'm a paid user, and I like the emphasis on the lightweight sites, but it's been years and it still misses some basic features like ... and index page.
> Then when you gut the HTML for UI overhaul, if the functionality hasn’t changed,
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.
Around 2 thousands people die every day from heart diseases in the US, every day (635k annually). Not in extreme temporary conditions. That's a standard baseline, year after year like that.
I wonder how many lives would been saved if we had mandatory 30 minutes jogging sessions, fastfood lockdowns and vegetable subsidies.
This even model is sooo confusing, clumsy and error-prone that writing any non-trivial test is a challenge. Whole product uses async/await or Promises and suddenly you have to switch to this baroque model just to write a test. Reusing logic between production code and tests is pretty much impossible.
Dynamic pages etc. often confuse cypress. I'm actually not a frontend developer, so I don't have a lot of insight while exactly that is, but I just know that it has been a huge drag.
Other than that, it would be OKish. Being able to test the UI is great, but I would advice everyone not to base the whole testing strategy on it. It's just too heavy, slow and unreliable. It doesn't not scale even moderately with the product growing.
e2e testing is better done on API level, IMO. You'll want redesigns, changes of UX, and suddenly your changes will require updating tests, which otherwise (if done on the API level) would require no modifications.
The OP is a long posts explaining how other people don't deserve their right to free speech and how that made them stop working on IPFS, and somehow you twist my frustration phrased as "just spare us" as saying I am trying to censor OP.
Agreed. Any recommendations of the tools to use? NixOS/Guix come to mind, k8s (thought I have a mixed feelings about it). Anything else worth keeping in mind?
I keep calling LinkedId "the saddest social network".
Create an account to list yourself in a CV catalog. Add connection with people you worked with to build credibility. Otherwise only ever open it when you're looking for a job. Otherwise you're risking getting cancer from looking at all that shameless self-promotion and posturing.