HNHacker News
TopNewBestAskShowJobs

Rauchg

3,589 karma · joined December 8, 2009

Guillermo Rauch. https://twitter.com/rauchg https://vercel.com
submissionscomments
Rauchg··on Ethereum Contracts Are Going to Be Candy for Hackers
ICYMI: Bitcoin will gain Turing-completeness via a merge-mined sidechain called Rootstock (http://www.rootstock.io/), that also offers a transaction throughput boost (300TPS right off the bat).

I highly recommend their whitepaper as it's also a great overview of the Blockchain ecosystem as a whole.

Rauchg··on The Startup Zeitgeist
Also notable: app likely to match for web, but not vice-versa.

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.

Rauchg··on Ns: single-command static hosting
`micro-list` is more comparable to that, which we just open-sourced: https://github.com/zeit/micro-list
Rauchg··on Ns: single-command static hosting
We're introducing `now alias` to handle any alternative domains to the links you receive :)
Rauchg··on Deepjazz: AI-generated 'jazz'
Even then, true jazz music composition would not involve only jazz training data. Even if it's thousands or hundreds of thousands of songs. Wouldn't you just be diversifying the source for your statistical reproduction?

A human composing new creative Jazz is using a much wider set of sources for creativity, not just existing jazz songs.

Rauchg··on Now: realtime Node.js deployments
We'll add the keyword "hosting" in some of the explanations which should help. Thanks for the feedback!
Rauchg··on Now: realtime Node.js deployments
Fixed! Sorry about that. We exceeded all quotas. All emails should be going out smoothly :)
Rauchg··on Now: realtime Node.js deployments
Yes. There's no downtime whatsoever because you don't overwrite or take down anything. Your architecture is immutable.

You manage "upgrades" by changing pointers (aliases and DNS). We'll be exploring this in upcoming posts.

Rauchg··on Now: realtime Node.js deployments
Yes. Just do `app.listen()` or pick `3000` or `8080` or `80` or…
Rauchg··on Now: realtime Node.js deployments
In order for you and your team to never rely on transient local state (either in the cloud or your own computer), we "start from scratch".

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`.

Rauchg··on Now: realtime Node.js deployments
There's no explicit concept of "now functions". You simply deploy HTTP/2 services to the cloud.

HTTP/2 significantly improves performance by introducing multiplexing and header compression. There's no need to introduce new concepts or APIs. REST away!

Rauchg··on Now: realtime Node.js deployments
Our focus is on empowering the realtime JavaScript cloud with its rich module ecosystem.

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!

Rauchg··on Now: realtime Node.js deployments
Our biggest focus is `npm install` performance. We have multiple caches to make it the best possible experience for you.

Every time you run `now` it's as if you had installed from scratch (including semver invalidations like ^ or ~). The focus is on reproducibility.

Rauchg··on Now: realtime Node.js deployments
All `/_src` links will link to a secure portion of the site with login + 2FA. Security is top of our mind.
Rauchg··on Now: realtime Node.js deployments
Compared to other providers, there's absolutely no setup involved. No Procfiles, ports, containers, dynos, processes, instances… Just type `now` where you have a `package.json`.
Rauchg··on Now: realtime Node.js deployments
CEO of https://zeit.co here! Happy to answer any questions throughout the day :)
Rauchg··on Require-from-Twitter
I was considering the source tweet as well :D
Rauchg··on Require-from-Twitter
My goal was for it to be entertaining and educational[1]. I love npm (which made this possible to begin with!)

[1] ES6 features (arg defaults, destructuring, modules, template literals, String.prototype.repeat), babel configuration and runtime compilation, async / await

Rauchg··on Real-Time Web Analytics Dashboard with NodeJs, Socket.io, and VueJs
- Built in reconnection.

- 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)

Rauchg··on My view on the current situation of Bitcoin and the Blockchain
Sure, but you also have to reduce the size of the incoming stream (by taking transactions off-chain).
Rauchg··on My view on the current situation of Bitcoin and the Blockchain
Increasing the block size is not the only way to make the system scale.

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.

Rauchg··on My view on the current situation of Bitcoin and the Blockchain
> The larger issue is that some of the core developers don't want to scale Bitcoin at all. They would rather have a more decentralized, less widely used Bitcoin.

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.

Rauchg··on Show HN: Collapse Comments on Hacker News
Love it. Suggestion: persist the collapse state to `localStorage`. This is enabled on Reddit through a Chrome Extension as well.
Rauchg··on Curl vs. Wget
I instinctively go to `wget` when I need to, uhm, get the file into my computer[1]. `curl -O` is a lot more effort :P

Other than that, curl is always better.

[1] Aliasing `wget` to ~`curl -O` might be a good idea :)

Rauchg··on Zero-Knowledge Contingent Payment
A lot of (manual) work went into making this simple demo happen.

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.

Rauchg··on Show HN: Claudia.js – deploy Node.js microservices to AWS more easily
Check out Micro as well: https://github.com/zeithq/micro.

It's also oriented around single-purpose (single-function) microservices, but pure HTTP.

Rauchg··on Wikipedia starts work on $2.5M internet search engine project to rival Google [pdf]
The biggest problem is the lack of data about what people are searching. It's a catch-22 that's very hard to break in the face of Google's search dominance and ubiquity.

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.

[1] http://webmasters.stackexchange.com/a/60350

Rauchg··on Don't Outsource Your Thinking (2015)
I wasn't aware of that quote, but it's wonderful. Thank you
Rauchg··on Don't Outsource Your Thinking (2015)
A lot of the media also wants to see the world thrive. "Us vs them" scenarios are counterproductive and cynical.
Rauchg··on Don't Outsource Your Thinking (2015)
The inline notes are now private. Just between you, the author and their editors.
← PreviousPage 6 of 10Next →