I highly recommend their whitepaper as it's also a great overview of the Blockchain ecosystem as a whole.
3,589 karma · joined December 8, 2009
I highly recommend their whitepaper as it's also a great overview of the Blockchain ecosystem as a whole.
If you build an app, you say you're building an app. If you're building a web site, you might say web app.
It'd be interesting to know if this was taken into account.
A human composing new creative Jazz is using a much wider set of sources for creativity, not just existing jazz songs.
You manage "upgrades" by changing pointers (aliases and DNS). We'll be exploring this in upcoming posts.
However, our process of starting from scratch is actually faster than running `npm install` on your own computer in many cases.
As an example, I've found myself getting into the habit of using `now` instead of `localhost`.
HTTP/2 significantly improves performance by introducing multiplexing and header compression. There's no need to introduce new concepts or APIs. REST away!
With the advent of microservices, code will become more succinct. Your backends will be aggregations of small functions with clear inputs and outputs.
The syntactic differences between languages will matter less. Our bet is that JS has the largest and most prolific community!
Every time you run `now` it's as if you had installed from scratch (including semver invalidations like ^ or ~). The focus is on reproducibility.
[1] ES6 features (arg defaults, destructuring, modules, template literals, String.prototype.repeat), babel configuration and runtime compilation, async / await
- Events / actions as main abstraction.
- Support for degradation for old devices, browsers, corporate networks.
- WebSocket is not very good at multiplexing. One discrete TCP connection per socket (opposite direction of what HTTP/2 is going)
- Binary support inside JSON (`Buffer` etc)
Imagine that you have 300GB available to store logs for requests to your webserver.
Let's say you're at 250GB and you can make calculations that, based on your website's growth and traffic projections, you'll hit your 300GB limit by the end of the year.
One way to scale is to buy new hard drives. Another way to scale is to keep only the most recent 300GB.
Another way to scale is to ask yourself: do you want every single entry in the log, with user agent, IP, headers and TLS handshake parameters? Perhaps you care only about malicious actors. Perhaps you care about some critical business events.
In that case, an alternative would be to aggregate and collapse log entries.
In the context of a system that is designed for decentralization, those scaling strategies seem to be a better fit.
This is not the case. See: https://bitcoin.org/en/bitcoin-core/capacity-increases-faq
What some of the core developers don't want to do is scale by increasing the block size and thusly increase the costs of being part of the decentralized network.
As an analogy, consider the EMFILE error in Unix. The kernel has a pre-set constant of how many file descriptors a user can open simultaneously.
Your computer might have it set to 256 and you might never have a problem because you use it for single-user workloads. When I deploy services to the cloud, however, it's annoying that sometimes the constant is too low: the system can handle a lot more TCP connections sometimes and the constant is inappropriate.
Now let's say you have a peer-to-peer network whose participants' computing capabilities (= EMFILE limit) are unknown. Let's say this network becomes super popular, and a lot of the nodes are close to hitting their file descriptor limit.
If you raise the constant from 256 to Infinity for everyone in the network, some nodes might be able to handle the load (for example powerful cloud computers), but some desktop computers will just struggle. No matter how high you set the constant, you're not introducing more capacity. You're throwing nodes out.
Luckily, there seem to be ways to scale the network without relaying (and persisting) every single transaction to every node.
Other than that, curl is always better.
[1] Aliasing `wget` to ~`curl -O` might be a good idea :)
These are some interesting reflections on the present state of the tech by Gregory Maxwell:
https://www.reddit.com/r/Bitcoin/comments/47rk85/first_succe...
I suspect there's a great opportunity here for startups. The theory is sound, and tooling (UX) needs to be built around it.
It's also oriented around single-purpose (single-function) microservices, but pure HTTP.
By Google being the best, it only becomes better, and introduces a huge barrier to entry to competitors. It used to be possible to know what people were searching for to end up in a given Wikipedia article, but the process is now only asynchronous (and limited) through Webmaster tools[1]
In my mind, the most interesting aspect of the announcement should not be how much money they have to spend, but how they plan on solving this paradox.