dewitt

Hasn't Dropbox lost market value every quarter since they went public while growth has been flat and operating at a loss?

I'm not saying the HN crowd didn't miss a $10B opportunity, but they also weren't exactly wrong.

Maybe the parent's point is that AAPL could buy QCOM outright three times over with cash on hand alone, so nothing could possibly move Apple's needle much anymore, except sales or lack thereof.

> Org-mode looks very similar to markdown. Almost so that I would call it pointlessly different.

Just a minor note on this: Org-mode was created in 2003 (the syntax a bit earlier) and Markdown in 2004, so I think this was a case of parallel evolution, each unaware of the other, not intentional deviation.

Edit: And the use cases were different. Org was designed as a syntax for an outliner, and Markdown was designed as a syntax for prose. Both are plain text and optimized for readability in their pre-processed form, but maybe it's the fact that they are so similar that's remarkable.

Email me. : ) We're hiring. I'm dewitt@ all the obvious places.

Is this something like what you're looking for?

https://github.com/knative/serving/blob/master/docs/spec/ove...

Or a little higher-level:

https://docs.google.com/presentation/d/1CbwVC7W2JaSxRyltU8CS...

There are a lot of technical docs in the individual repositories. You can get started, for example, with the serving docs under:

https://github.com/knative/serving/tree/master/docs

Same for the other repos, like build and eventing.

Thanks for asking!

Just to amplify jacques_chester's reply, yes, we do see products being built on Knative components. Google is doing that (serverless container support in GCF, serverless add-on in GKE), and you can see similar announcements being made from partners in this thread.

These are early days of course, but given that the goal is to codify the commonalities (the 80% we all do roughly the same anyway) and to improve customer workload portability overall, I hope to see new products built using Knative, and existing products re-base on Knative as well.

Good questions, btw!

We have several days of keynotes at GCP Next and way more to share throughout the week. But for the curious, there's a serverless spotlight session at 1:55 today that will cover this, as well as a Knative-specific talk at 4:35.

We decided to announce this first thing with the blog posts just to get the word out as soon as possible and give our amazing partners (Pivotal, SAP, RedHat, IBM, and more) a chance to share their news as well.

And frankly, it's just more fun to run an open source project out in the open, so we were pretty keen to flip the git repo bits to public as early as we could. : )

Indeed. Much of what we open sourced in Knative came from what we learned from running GAE and GCF. Which is important: this isn't a side project for us, this is based on real-world experience doing it at scale for huge customers. You don't run a serverless stack for 10+ years without taking away a few lessons. : )

Huge thanks to Pivotal for being an amazing development partner. Pivotal's deep experience with enterprise customers and developing products like riff brought real-world knowledge and technical leadership to Knative early on. We're super grateful for the opportunity to have worked together on this!

I'd love to see a PR that documents Knative on EKS!

One of the goals is to make the components loosely coupled at the top (so a product can choose among them as needed), and also pluggable at the bottom (so you can swap out implementations as needed, for example logging and monitoring).

I expect that some of this will end up upstreamed into Kubernetes proper if it's broadly useful (autoscaler work, to pick an example), but this is still super early so let's see what people want.

And yes, we're documenting the control plane APIs, the data plane requirements, and the contract for serverless container environments, with the hope that they can be reimplemented consistently wherever needed.

One of the explicit goals is workload portability, so separating spec from implementation is critical.

Thanks to everyone who played a part of this! The Google team is also watching this thread. Happy to answer any questions people have.

Point made. I think you're right. : )

Sure. I'd even put Gibson, Wallace, Stephenson, Asimov, and Martin on my own subjective list, just on pure influence and enjoyment. The other ones though are at least in the running by most objective criteria, I'd imagine.

I love Franzen. But not in a class by himself, at least not in a half-century.

Him too.

> "Donna Tartt, one of the best American novelists to emerge in the last 50 years, has published just three novels since 1992. Jonathan Franzen, the only American novelist who is her equal."

Pynchon. DeLillo. McCarthy. Roth...

Edit: Morrison. Updike. Mailer...

Yeah, I actually dislike it every time myself, though that's not hugely important to me, nor why I commented.

There was some interesting commentary in this thread about cultural appropriation and whatnot, which seems to me to be beside the point. My intent was only this: if there are other people rightly upset by something, it doesn't matter if you're not, it doesn't even matter if the majority are not, it's still valuable to have empathy for those those that are. That's all.

I'm not opposed to offending others. : ) Just be aware when you do, and why you're doing it. The parent post simply seemed blithely unaware of how deeply hurtful the phrase can be to people. (Imagine typing that phrase out every day when literally your own great great great grandparents were dragged here in chains and were considered the personal property of someone. That's simply f'ed up and would suck beyond belief, and not even being willing to acknowledge that harm is crazy to me.)

Well I don't really get Instagram or Snapchat either, but they created something that has made tens of millions of people happy, and turned a thousand other people into millionaires (or billionaires!) basically overnight. By that measure, what have you or I ever done...?

I think this research is spot on, and can't wait to have it on my phone. And I love taking photos the old fashioned way, too.

Yes. Imagine looking at a 2x2 brick [0] and a 2x4 brick [1] head on.

[0] https://brickset.com/parts/design-3003

[1] https://brickset.com/parts/design-3001

Good point about ThinkPenguin's target demographic. I think you're right—I presumed too much about his business without looking first.

(Sorry I upset you, btw.)

Seems incredibly ill-advised to be publicly discussing what is sure to result in legal action. Even as one-sided as this is, the best he can do is incriminate himself. The other side will wait until due process requires them to disclose their case. At best he's trying to rally opinion (why?), at worst he's just seeking attention, and either way he's just making things worse on himself.

As a CEO he just associated his company with poor decision making.

If this guy has a lawyer, he should consider listening to them.

But IANAL, so who knows.

Thanks!

But did they fix ctrl-space? [1]

As an emacs user, this single issue has been the show-stopper that prevented me from investing in bash on windows, even though I would like to.

[1] https://superuser.com/questions/1088250/windows-10-linux-bas...

Here are the new Always Free usage limits:

https://cloud.google.com/free/docs/always-free-usage-limits

They are (IMO) quite generous. Definitely sufficient to get a good feel for the platform and run some personal workloads.

Disclaimer: Nothing to do with this launch, but I do work on GCP.

Yes, there is an entirely new Always Free Products tier.

https://cloud.google.com/free/

"Use these products for free up to the specified usage limits during and past the free trial. These usage limits do not expire, but are subject to change."

Includes gratis usage of App Engine, Compute Engine, Cloud Datastore, Cloud Storage, Container Engine, and much much more.

Yes, it can be used for image compression:

https://research.googleblog.com/2016/09/image-compression-wi...

Here's the paper:

https://arxiv.org/abs/1608.05148

(No connection to the authors, just found it super cool when I read it a few months back.)

I don't think anyone would argue against the advantage of being there in person.

The question to me is this: can we make it better for people who can't be there? (I.e., raise the foundation, not debate the ceiling.)

I'd be very interested in better understanding what it takes to make something like YC work remotely. Indeed, if I ever left my own job to start a company again, this is the space I'd like to explore most.

It feels to me that there's an incredible untapped potential of talent that simply can not relocate or even come to an office on a regular basis (due to disability, economic reasons, visa status, age, family obligations, etc).

If we can unlock that potential then there is so much more we can do as a society.

If anyone at YC (or anyone else) is interested in talking, please reach out.