HNHacker News
TopNewBestAskShowJobs

Rauchg

3,589 karma · joined December 8, 2009

Guillermo Rauch. https://twitter.com/rauchg https://vercel.com
submissionscomments
Rauchg··on Serverless Docker Beta
For the duration of the warm phase (i.e.: while the process is running), we ascertain healthfulness via `SYN` packets as a baseline.

Because you give us your code under the constraint that it will expose data over a port, we have a much better safety baseline than stock schedulers, that operate under the assumption that the process describe by `CMD` is a black box.

We will describe this in more detail in coming weeks. One of our priorities is to minimize the cognitive load on the developer necessary to run a healthy service at scale.

Rauchg··on Show HN: Sapper.js – towards a better web app framework
One of the authors of Next.js here. I want to clarify that all the points against Next.js are virtues! They probably just arise from Rich not being so familiar with it (or not having looked at the examples/ directory extensively: https://github.com/zeit/next.js/tree/canary/examples)

1. I think this point is trying to say that we don't have special "mask files" inside `pages/`, which is an idea worth exploring. Right now, Next.js instead gives you full flexibility on how you want to match the routes on your server (as it should be). For example, `your-domain.com/xyz` can even first perform a database query before deciding what page to render it with (if any).

2. What the author points out as a weakness here is that you can handle server things directly in your server code (`server.js` using micro or express for example). That sounds like the right thing to do to me, and if you don't want that, you still can do something like:

  // pages/my-server-page-only.js
  export default ({ req, res }) => res.end('hi')
3. "To use the client-side router, links can't be standard <a> tags." This is by design. Magically overloading `<a>` to add client-specific behavior sounds like the days of jQuery or TurboLinks. If you want client-side behavior, wrap `<a>` in the higher-order `<Link>` component. There also very important properties of the `<Link>` like `<Link prefetch>` that are simply not part of the `<a>` standard definition.

Also noteworthy: the entire ZEIT Documentation is written in Markdown with React components. It's open source: https://github.com/zeit/docs

On size: the Next.js and React teams are both working towards really interesting solutions to ship only the code that's necessary, without resorting to templating as the main strategy. Our team actually spends more time on the 'compiler' parts of Next.js than the 'framework API' parts. (the API has barely changed since the initial 0.1 release in fact).

Additionally, since Next.js uses React as peer dependencies, you'll also get to do `yarn add next react react-dom-lite` https://github.com/jquense/react-dom-lite in the future.

Overall, I think Sapper is an excellent framework for Svelte users. I'm looking forward to seeing more Next.js-like frameworks.

For Vue users: check out https://nuxtjs.org/!

Rauchg··on How Firefox Got Fast Again
I've been extremely happy with Firefox Nightly. Highly recommend it to everyone here
Rauchg··on Next.js 3.0 Preview: Static Exports and Dynamic Imports
That's the opposite of what that page is trying to explain. We'll take a look at the wording in case it's confusing.

tl;DR: You can do any sort of routing! We use a /:org/:project scheme similar to GitHub at https://zeit.co :)

Some examples:

- https://github.com/zeit/next.js/tree/master/examples/paramet...

- https://github.com/zeit/next.js/tree/master/examples/with-ne...

- https://github.com/zeit/next.js/tree/master/examples/with-pr...

Rauchg··on Next.js 3.0 Preview: Static Exports and Dynamic Imports
1. We have plenty of examples with interoperation with Redux. Check out the `./examples` folder :)

We currently use global state at https://zeit.co to keep the authenticated user in memory without re-checking for every page transition.

You can think of Next.js's Router as a "strict subset" of RR. Definitely possible for us to simplify our codebase by switching to RR in the future.

2. Nothing about this framework is dependent on now.sh. We, however, did design now.sh to make deployment of applications as this as easy, fast and scalable as possible with collaboration in mind.

Rauchg··on Next.js 3.0 Preview: Static Exports and Dynamic Imports
1. Embraces React exclusively[1]. We at ZEIT think the React Component model is the de-facto component model of the web and mobile.

In practical terms, this means that every "page" or "entry point" to your app is just an exported component `function` or `class`. `export default () => <p>My component!</p>`.

At the expense of a storm of HN downvotes, it's "more PHP than Meteor" :)

2. No data layer built in, syncing, Models, etc. We added an extra lifecycle hook called `getInitialProps` (think of it as the counterpart to `getInitialState`) whose contract is returning data as a `Promise`.

This allows you to combine and compose different approaches to data retrieval. It works just as well with REST as it does with GraphQL or Socket.IO or server-sent-events or offline-only or…

3. It hides configuration details but allows you to tap into them.

It's powered by `Babel` and `webpack`, which are exposed as a single command (`next` and `next build`), but you can completely override and customize them.

These are just some ideas. We created it to power the team collaboration aspects of our Web UI (https://zeit.co). We are committed to supporting it because we use it and we love it.

[1] Also React alternatives like Inferno and Preact (https://github.com/zeit/next.js/tree/master/examples/using-p...)

Rauchg··on Faster, leaner and better Next.js
We recently launched a bunch of really exciting performance improvements for Next.js. Would love to answer any questions about them or the framework in general!
Rauchg··on Next.js 2.0
Thank you @jonknee.

https://twitter.com/rauchg/status/846474015178866689

Rauchg··on Hyper – A terminal emulator based on JavaScript, HTML and CSS
In terms of crashes, it's amazingly stable. We do have a few bugs with some glyphs still, but please give it a try!
Rauchg··on Hyper – A terminal emulator based on JavaScript, HTML and CSS
Every single day.
Rauchg··on Hyper – A terminal emulator based on JavaScript, HTML and CSS
I'm pretty confident that we will get to the point where the performance difference with your terminal will be undistinguishable.

Working hard on this, and at some point hopefully you can't tell that it's a browser.

Rauchg··on Hyper – A terminal emulator based on JavaScript, HTML and CSS
Extensibility was a huge motivation behind it.

See my other answer here: https://news.ycombinator.com/item?id=13516047

Rauchg··on Hyper – A terminal emulator based on JavaScript, HTML and CSS
We've made a ton of progress with glyphs that were not displaying properly, and more fixes are coming!
Rauchg··on Hyper – A terminal emulator based on JavaScript, HTML and CSS
This will be possible by holding a key down in the future. Thanks for your feedback
Rauchg··on Hyper – A terminal emulator based on JavaScript, HTML and CSS
The demo is more than an animated cursor. The demo is showing that:

- you can override any output coming from the terminal and choose not to display it (in this case the "command not found" output is overridden)

- you can lay out an arbitrary `canvas` element on top and have complete freedom to style however you want.

The idea behind Hyper is that you can do everything as plugins. Instead of creating an experimental terminal like TermKit, my decision was to ship a _useful_ terminal and let it be arbitrarily and infinitely extended.

Disclosure: author of Hyper

Rauchg··on Proof of Stake
My gut tells me the opposite. Here are some unscientific reasons why.

Proof of stake: the mechanism to secure the coins, uses the coins it's trying to secure. Circular.

Proof of work is simpler to describe and implement, which is attractive. Joining, then leaving, then joining and catching up is easy. Blockchain reorgs are easy.

Compare the length of Bitcoin's whitepaper and any PoS whitepaper, or the cited link even.

It'd be interesting for the author to share his intuitions for why it might be better.

Rauchg··on Next.js – A small framework for server-rendered universal JavaScript apps
I wonder if it's related to the animated gif? I've had it open for many hours as well, and it looks like this: http://i.imgur.com/E05vChB.png
Rauchg··on Next.js – A small framework for server-rendered universal JavaScript apps
Anything specifically comes to mind? We are constantly iterating and improving.
Rauchg··on Next.js – A small framework for server-rendered universal JavaScript apps
You can use a full URL? Also, typically you want to query a different API server. We query microservices, specifically.
Rauchg··on The Hyper Plan
It's actually very similar goals and look as st, with the difference that it's extensible through a plugins interface.

Give it a try :)

Rauchg··on Ask HN: Alternatives to AWS?
If you want to focus on the code and not the servers, give a try to https://zeit.co/now

Disclosure: co-founder and CEO

Rauchg··on DDoSCoin: Cryptocurrency with malicious proof of work
Despite this malicious use-case, it's entirely possible that the underlying proof-of-work technique (using the target server's TLS signatures for validation) can inspire some noble applications or smart contracts :)

As a somewhat contrived example, instead of blindly trusting that a certain monitoring system like "Uptime Robot" is checking your servers (or going through an expensive access_log based verification), you could verify their proof-of-connection.

Rauchg··on Show HN: Auto install npm dependencies as you code
Very cool! The Webpack equivalent: https://github.com/ericclemmons/npm-install-webpack-plugin
Rauchg··on Failsafe – failure handling with retries, circuit breakers and fallbacks
We use `async-retry` which implements `node-retry` in a way that's friendly to usage with `Promise` and `async/await`.

https://github.com/zeit/async-retry

Rauchg··on Just A New Fractal Detail In The Big Picture (2015)
For different versions of this argument see: https://en.wikipedia.org/wiki/AI_effect.

Bostrom said: "A lot of cutting edge AI has filtered into general applications, often without being called AI because once something becomes useful enough and common enough it's not labelled AI anymore".

Finally, the problem with all these articles is the lack of precise definition for the terminology involved (it reminds me of debates about "consciousness").

Recipe: make a slight twist on the interpretation of the already-vague definition of the term and a new essay emerges.

In this case, the author is equating "AI" to "Abstraction". All the things he mentions he doesn't understand, he could understand by looking them up and talking to the experts, but he doesn't have to, because the appropriate simple interfaces are in place. That's intelligence in its general form, where's the artificial part?

Rauchg··on Zeit.world: free global DNS
We've been getting lots of great feedback and usage on our OSS tier. Improvements are coming. Many of the limits are in place to prevent abuse.
Rauchg··on Zeit.world: free global DNS
Please see my reply above.
Rauchg··on Zeit.world: free global DNS
We charge individuals and teams according to their growing capacity needs (number of deployments, bandwidth, storage, etc).

Check out https://zeit.co/now#pricing.

Rauchg··on Zeit.world: free global DNS
Co-founder of ▲ZEIT here. There's no catch. If you deploy with https://zeit.co/now, DNS is free.

Here's a little .gif showing the entire process if you're curious: https://twitter.com/rauchg/status/746093788272037888.

Rauchg··on Async and Await
I'm glad `unhandledRejection` exists (and I thank you for your work).

Unlike Chrome, without setting up the handler manually, you still don't find out about unhandled rejections. Maybe it's something we could enable during development (`NODE_ENV` = 'development' perhaps).

← PreviousPage 5 of 10Next →