Yes. In the case mentioned binaries written in Go (goaws). I can add all the goaws binaries into my git repo, and have a single cross platform entry point devs can call without figuring out which one is for their OS.
Using the equation listed in the article I couldn't generate a collision so far. Yet, I still check (in code) for id collision, and pick new id, just to be 100% sure.
Its battery lasts for several weeks. So I never realize it's battery hitting close to zero.
And unluckily its hit bottom several times at the beginning of a work day.
It wouldn't have hurt if they made the thing useable while plugged in.
planetscale (if I need rdbms) or firestore or dynamodb (if I need just document).
I checked latency of planetscale and dynamodb from frankfurt,paris,singapore from DO/linode/scaleway to db in same region; these are low latency (mostly single digit).
There is always places people can contribute. Look at some terrible softwares.. medical, insurance, 3pl logistics etc.. they don't need extraordinary brilliance to improve.. just UX, better systems, process and lots of area to cover.
If you can improve one industry a bit more than it is today, isn't that a sufficient place in the world?
The simplicity goes away when supporting SSR. You have to depend on multiple stores (one per request) being injected "from the top" (e.g via Context Provider).
- starting out, not knowing what carriers available in your target area and their real performance/SLA, until you try them out. This info is critical to do business.
- for merchants with lots of products the photo sessions + touch up takes a lot of time. Any way that can speed up the process would be helpful.
- large catalogs can't manage their SEO without some automation. Shopify doesn't give this out of the box. There are apps in this space though thankfully.
- merchendizers managing large catalogs can make many mistakes when adding product to website. There's got to be a customizable "checker" that could check if mandatory fields are filled, spell check etc.
- let's say you want to slash a collection's price by 10% for a sale. This can't be done easily without manually changing each product. (coupons not a solution, as price has to reflect on ad channels). Any way to do bulk actions like these faster?
- lots of customers enter in wrong email or phone number or don't respond.. is there a way to add optional OTP entry step after order placement?
- shopify (and most themes) don't give customers ability to request and manage returns. Their option is contacting customer support.
I guess you get where I am going with this.. look at the operational issues businesses face, there are opportunities there.
lol similar to the blog, I just got tricked into a prime membership. I'd swear that I didn't click the button in their full screen "upsell" page in the middle of the checkout process.. but yet money gone and only half refund. Their customer contact details is hidden so deep, that it took me 10 minutes to find out. Finally contacted them and got the remaining amount as store credit. Experiences like these puts me further of amazon. Now think about the definition of good UX.
0.7 and 1.0 gives nice writing experience. doesn't spread ink around or to underneath paper.
ink doesn't jam (once? in last 5 years..) doesn't get damaged on light/few falls (on heavier falls the retractable action could get damaged).
overall lasts long for the price tag (the one I am using now is close to 1 year old, still writing well)
The challenge is making it look pretty and at same time have a small svg output and at the same time not taking forever to generate (it's perf gets exponentialy slow). Took some time to tweak it to the settings I used.
It looks nicer than blurhash.. however blurhash is way smaller and might be more practical alternative
If there is enough incentive, OSS devs would create some libraries with common interface across stores.. but there is no incentive, as android's main store is google's.
And SVG icons should use svg `<use>` tag and shouldn't be counted in code size.