Handshake domains are only accessible by a tiny percent of people, make stuff like HTTPS very difficult[1], and no matter how devices eventually use Handshake, you'll always need to have a domain on a normal TLD because there will always be devices (like TVs and old phones) that will not support it.
And what benefit do you get anyways? A custom TLD? There's already so many new TLDs but most domains are on gTLDs or ccTLDs because thats what people recognize. Even Google and Apple barely use theirs. Ownership? Not really. Handshake only manages TLDs. Buying a subdomain (like you can on Namecheap) doesn't happen on the blockchain, the owner of the TLD can take it away anytime. Say what you want to say about ICANN, but they do have rules (such as contingency plans) that new TLD owners have to follow. In what world is buying a handshake subdomain from an unknown person beholden to nobody better in any way?
I've been using Scylla for a project and have ended up reading quite a few of those blog posts. They are generally very well written and useful, but I've noticed the same sort of issues. There's the chat popup at the bottom, a banner for Scylla Summit, a cookie banner that doesn't seem to remember what I clicked, and a header with broken transparency.
For me, Cloudflare is the benchmark. Cloudflare.com is very clearly a marketing site, likely run by their marketing team, but their technical content such as their blog and docs are on completely different subdomains with a clean design with no popups or banners. I think this is the best way to run tech focused blog, making both developers and marketing happy.
They provide 3D asset downloads, most folks will only be downloading an asset a single time. Therefore, browser side caching doesn't really help, they need to cache the files on a CDN.
Yep was also going to mention this. Obviously, Argo still helps with latency and some other things probably, but if they're paying the additional $160 just for tiered caching, they should be able to switch off Argo.
I wonder how the pricing will end up. At the baseline, $1200 for a MacBook Air with 16 gigs of ram is great value for the machine you get, even compared to Windows alternatives. For the new MacBook Pros, there are multiple companies who felt that they were worth shelling out for top of the line configs outside of their normal refresh cycles. Maybe Apple will price their top of the line stuff for a reasonable price/performance ratio, or they might think that the people who actually need that config would be willing to pay sky high prices and charge accordingly.
You can't do quadruple esim, but arguably the experience with 4 esims on a single device is much better than carrying 4 sims.
"You can store more than one eSIM in your iPhone, but you can use only one at a time. To switch eSIMs, tap Settings, tap either Cellular or Mobile Data, and then tap the plan you want to use. Then tap Turn On This Line." [1]
On the iPhone 13, you can actually use two esims at the same time.
Currently the satellites don't have intersat links. There is a ground station in each geofenced region, which makes mobility difficult. I'd expect it to start working once the intersat links are functional.
I would expect that to be true. Not the best numbers, but Wikipedia puts coal power plants at 37% efficiency and combustion engines at 20-35%. This makes sense too, power plants have space, money, and an incentive to increase efficiency. And in reality, no power mix is 100% coal, increasing the overall efficiency to above 37%.
Build a native app and you get complaints about cross platform. Build an electron (or other cross platform toolkit) app and you get complaints about resource usage and non native ui.
Seems to me that they know their target market (large tech shops with lots of devs on macos) and preferred to optimize for resource usage and user experience by going native. For another company, this could very well be the wrong choice, but they should look at the numbers and decide what makes sense for them.
To only use Cloudflare for DNS, just add a record and make sure the orange cloud icon is off to disable proxying. However, your observation is mostly correct. Cloudflare offers at cost domain registration as an extra benefit (or lock in) for their customers, rather than as a general service and as such, you can't change your nameservers away from them.
The problem with Python type checking is that the general community still does not write libraries with types. On the other hand, the JS community is further along and most libraries written today include TS files. I think the same will happen with Python, but it obviously takes time.
I'd love to see that happen, but as I understand it, that's a decision for the crates.io registry. Cargo itself doesn't deal with those types of details and you could host a custom registry that does have namespaces.
I was under the impression that most of Next's server side capabilities, outside of the recently introduced middleware and react server components, required a node environment. I know Vercel does offer multiregion capabilities for enterprise and a bunch of smart things to make sites faster, but its still not the same as being able to do everything on edge the way remix advertises.
If you take a look at the CONTRIBUTING.md, Mold has taken an approach that is pretty novel to me. Instead of requiring a CLA to allow for relicensing, all patches are required to be released as dual-license AGPLv3 and MIT. I personally love this approach, but it could make it difficult to relicense to anything but MIT.
There's no fundamental reason you can't since there are X11 clients for windows, which is what this uses. However, FreeBSD jails and Linux containers have very little overhead on their native OS, whereas Docker on Windows runs a Linux VM, so the experience might not be that great. Only way to know though is to try it!
At the very least, you don't need to do the first two steps. Backblaze can ship you your backup on a hard drive, which you can then return for a full refund.
Sure the server hardware itself might cost only $5,000 a year, but it can't just be left there on its own forever, as seen with the ongoing log4j vuln. Either it costs that much and puts their entire network at risk, or it costs a lot more due to engineering costs for maintenance.
Unless you're running something that's mostly images, I'm a fan of pregenerating variants of images for static sites since storage has become so cheap. However, I think the best way of doing that is to actually generate the variants as part of the build step, the way that Next or Gatsby can. Hugo also seems to have some support for image processing [1] so it may be possible to put something together using only Hugo. It increases build time, but a build cache should fix that.
Yep there is so much overhead to making things decentralized. Take a look at filecoin sealing. Its a super cool system with a bunch of fun cryptography and math, but generating the proofs requires a lot of time and compute power and adds a whole bunch of restrictions to how you can upload data.
If you really, really, want to say your storage is decentralized, use it, but S3 is a 1000x simpler.
Micropayments are an interesting topic. I don't want to pay 5 cents per article I read, I'd much rather pay $10 a month for unlimited articles, even if I end up paying more than I would with the first scheme just because with the first one, I make a decision to spend money with every click. I know there are projects trying to streamline this, but it really should be as close to the UX of the latter as possible, pay a set amount and never think about how many things I can read.
- Customer UX: This really isn't as straightforward as you put it. The main issue for customers is that if they loose their wallet, they loose everything. This has to be accounted as part of UX, even making transactions is simple and straightforward.
- Settlement/Certainty time: Blockchains combine these into one. They depends heavily on the specific chain. For some networks, its basically instant. Eth seems to be around a minute or so. Bitcoin is around 60 minutes.
- Reversibility: Agreed, although whether this is good or bad depends on the user.
I like the way it was said in the article, these are all axes of comparison. Consumers choose products based on a set of criteria. For many, irreversibility or the risk of loosing everything due to a lost wallet is a dealbreaker, even if transfers may be much faster than other methods.
Its free for open source projects and integrated nicely into Github. Even if another CI service is better, the bar to get started with Actions is much lower.