rattray

Have you found anything better for the area? This frustrates me too...

How do you handle very large OpenAPI specs? For example, I think stripe's is over a megabyte. What's the summarization strategy?

Previously discussed here 10mo ago: https://news.ycombinator.com/item?id=33220552

This was a funny title but not a nice post. Ick.

Probably depends on the biodegradable fiber? Organic cotton uses a _ton_ of water. I'm not sure about viscose/rayon/tencel but I imagine it's often less water-intensive but it can be pretty chemical-intensive.

I don't know how bad nylon is to produce, but the durability it adds to clothes is probably an overall net win for the environment; compared to other plastics we consume, it does a lot of work (I've worn some items for years).

Note Prana has recycled nylon in their Brion II line, but unfortunately the quality is way worse; it pills immediately. Environmentally, I'd much rather buy non-recycled plastics that last a lot longer, so I consume/waste less overall.

But the tldr is that I don't know :)

Stainless | Founding Engineer | NYC ONSITE | Full-time

Stainless is building the platform for high-quality, easy-to-use APIs.

Our first product is SDKs as a service – you send us your OpenAPI spec, and we generate pacakges in all the major languages and publish them to npm/pypi/etc (think `npm install your-company`). These SDKs are world-class: you get an idiomatic wrapper with autocomplete, types, etc. (I built a version of this at Stripe for their SDKs, and am now building a better version for everyone.)

Next, we want to make it easy to build amazing REST APIs. REST is simple and ubiquitous, but right now it’s also messy, chaotic, and hard to get right. We’re going to build great open-source standards and tooling that bring the benefits of GraphQL (types, field selection/expansion, standards) and gRPC (types, speed, versioning) to REST.

From there, we plan to build out a rich family of developer platform products – everything an API team would need to deliver a terrific DX to their partners and/or customers.

We’re about 1.5y old, under 5 people, have strong revenue, and are selling to companies you interact with every day. We’re backed by Sequoia, a bunch of (ex-)Stripe people, and founders of Next.js, Prisma, and Segment.

As a founding engineer, you’ll get autonomy to build great products, skilled peers, opportunity for tremendous impact, competitive salary, and a very competitive ownership stake.

We’re looking for exceptionally productive, thoughtful, tasteful, and kind people with a passion for making software development better for everyone. Want to build the future of API tooling? Say hi: alex at stainlessapi.com

Not OP, but I run, hike, bicycle, ski, backcountry ski, practice yoga, indoor rock climbing, and more in merino wool t-shirts, underwear, and socks.

I find Ibex makes the highest quality tees (their tencel/merino/nylon shirts are incredible for hot summers) and underwear. Icebreaker also makes a variety of good stuff.

I generally look for some amount of nylon for durability, but I have a few 100% merino shirts from icebreaker that I've worn intensively for years with no problems.

I did have some pilling issues with the merino/tencel blend from ibex which is a shame. Gorgeous fabric at first; still feels luxurious.

Laundry is a bigger deal since it's wash cold and dry flat with many of these; that can be a cost, equipment, and/or lifestyle adjustment.

I'm often able to wear the same clothes many days in a row without issue.

For pants, I prefer nylon+elastane blends, but it's hard to find. Prana used to make good things here but their Brion II line was a significant drop in quality.

To be fair, protobuf is a pretty poor/annoying match to many languages that aren't Go or Java, including TS. Optional types, for example, are very much not unique to Rust.

This seems like a big deal?

> In this case, it seems I conflated details between Steve Reich's "Six Marimbas" and Philip Glass's legitmate "Concerto Fantasy for Two Timpanists and Orchestra."

It looks like these two are "legitmate"… but where does the word "Lumina" come from in this combination?

The "fairytale" cases (IPO) are quite rare, but acquisition is a little less rare, and help support the portfolio.

Probably closer to 100/1, or worse - that's the gamble you (should) know you're taking if you accept venture capital.

It's not for everyone, but eastdakota is right that it's not for nobody.

Of note, they mention (ordering/emphasis mine):

> We remain committed to Zoekt, the open source code search engine, and will continue to upstream changes to it.

https://github.com/sourcegraph/zoekt

> The source code will remain publicly available.

> Individual devs will still be able to use Sourcegraph for free on public code at sourcegraph.com and within our self-hosted free tier on private code.

> Very few individual devs or companies used the limited variant of code search that was open source. The vast majority (99.9%+) used the enterprise product. Maintaining two variants going forward was a big burden on our engineering team that had very little benefit for users.

If anyone's looking for an open-source search tool for grepping across repos (or even one large repo) at insane speed, I highly recommend livegrep:

https://github.com/livegrep/livegrep

Demo at https://livegrep.com/search/linux

We used it at Stripe and it was quite popular; often, searching even a single repo was faster on livegrep than with ripgrep locally.

A post reviewing it: https://www.alexdebrie.com/posts/faster-code-search-livegrep...

A post by its creator, nelhage, on its impact: https://blog.nelhage.com/post/reflections-on-performance/ and another on its architecture: https://blog.nelhage.com/2015/02/regular-expression-search-w...

Stainless | Founding Engineer | NYC ONSITE | Full-time

Stainless is building the platform for high-quality, easy-to-use APIs.

Our first product is SDKs as a service – you send us your OpenAPI spec, and we generate pacakges in all the major languages and publish them to npm/pypi/etc (think `npm install your-company`). These SDKs are world-class: you get an idiomatic wrapper with autocomplete, types, etc. (I built a version of this at Stripe for their SDKs, and am now building a better version for everyone.)

Next, we want to make it easy to build amazing REST APIs. REST is simple and ubiquitous, but right now it’s also messy, chaotic, and hard to get right. We’re going to build great open-source standards and tooling that bring the benefits of GraphQL (types, field selection/expansion, standards) and gRPC (types, speed, versioning) to REST.

From there, we plan to build out a rich family of developer platform products – everything an API team would need to deliver a terrific DX to their partners and/or customers.

We’re about a year old, under 5 people, have strong revenue, and are selling to companies you interact with every day. We’re backed by Sequoia, a bunch of (ex-)Stripe people, and founders of Next.js, Prisma, and Segment.

As a founding engineer, you’ll get autonomy to build great products, skilled peers, opportunity for tremendous impact, competitive salary, and a very competitive ownership stake.

We’re looking for exceptionally productive, thoughtful, tasteful, and kind people with a passion for making software development better for everyone. Want to build the future of API tooling? Say hi: alex at stainlessapi.com

Bit of a spoiler, but I did find this a fun followup worth skimming:

> So the commit I had bisected to was the wrong one again – it exposed a latent bug simply because it ran the same code as a sleep.

The fix was by someone else, and is here: https://lore.kernel.org/stable/20230615091830.RxMV2xf_@linut...

How's the quality?

I have to say I'm impressed at the breadth of their SDK support (even Elixir) and how idiomatic they seem at first glance in each language (though too bad there's no python types yet).

Really nice to see all the examples too.

Pretty wild that in comparison, "Twilio Sendgrid" doesn't even have a single code snippet on their homepage, and once a Rubyist clicks "Least more" and scrolls they're greeted with this: `sg.client.mail._('send').post(request_body: mail.to_json)`

Nit, by then it would have been public market investors, not VCs, for the most part.

Agreed, it's hard to get a sense for what using this would actually be like. Prose describing code just doesn't work for most developers, myself including.

dup of https://news.ycombinator.com/item?id=36201593 I think

He's got a book! ...in Japanese. I hope someone can help him translate it into English so more people can learn about this kind of thing and he can be rewarded for his adventures.

Stainless | Founding Engineer | NYC ONSITE | Full-time Stainless is building the platform for high-quality, easy-to-use APIs.

Our first product is SDKs as a service – you send us your OpenAPI spec, and we generate pacakges in all the major languages and publish them to npm/pypi/etc (think `npm install your-company`). These SDKs are world-class: you get an idiomatic wrapper with autocomplete, types, etc. (I built a version of this at Stripe for their SDKs, and am now building a better version for everyone.)

Next, we want to make it easy to build amazing REST APIs. REST is simple and ubiquitous, but right now it’s also messy, chaotic, and hard to get right. We’re going to build great open-source standards and tooling that bring the benefits of GraphQL (types, field selection/expansion, standards) and gRPC (types, speed, versioning) to REST.

From there, we plan to build out a rich family of developer platform products – everything an API team would need to deliver a terrific DX to their partners and/or customers.

We’re about a year old, under 5 people, have strong revenue, and are selling to companies you interact with every day. We’re backed by Sequoia, a bunch of (ex-)Stripe people, and founders of Next.js, Prisma, and Segment.

As a founding engineer, you’ll get autonomy to build great products, skilled peers, opportunity for tremendous impact, competitive salary, and a very competitive ownership stake.

We’re looking for exceptionally productive, thoughtful, tasteful, and kind people with a passion for making software development better for everyone. Want to build the future of API tooling? Say hi: alex at stainlessapi.com

FWIW, there are a few companies cropping up now doing better codegen for client libraries. I'm starting one of them: https://stainlessapi.com

Unfortunately we don't yet have a "try now" button, and our codegen is still closed-source, but you can see some of the libraries we've generated for companies like Modern Treasury and sign up for the waitlist on our homepage.

Always happy to chat codegen over email etc.

Interesting – what behavior would you want there? Statically filled area, or a shifting area depending on the other pixels?

Interesting - how would that work for a company that wanted to run their own codex model, on-prem, trained on their own code? Perhaps also trained on their dependencies?

Stainless | Founding Engineer | NYC ONSITE | Full-time Stainless is building the platform for high-quality, easy-to-use APIs.

Our first product is SDKs as a service – you send us your OpenAPI spec, and we generate pacakges in all the major languages and publish them to npm/pypi/etc (think `npm install your-company`). These SDKs are world-class: you get an idiomatic wrapper with autocomplete, types, etc. (I built a version of this at Stripe for their SDKs, and am now building a better version for everyone.)

Next, we want to make it easy to build amazing REST APIs. REST is simple and ubiquitous, but right now it’s also messy, chaotic, and hard to get right. We’re going to build great open-source standards and tooling that bring the benefits of GraphQL (types, field selection/expansion, standards) and gRPC (types, speed, versioning) to REST.

From there, we plan to build out a rich family of developer platform products – everything an API team would need to deliver a terrific DX to their partners and/or customers.

We’re about a year old, under 5 people, have strong revenue, and are selling to companies you interact with every day. We’re backed by Sequoia, a bunch of (ex-)Stripe people, and founders of Next.js, Prisma, and Segment.

As a founding engineer, you’ll get autonomy to build great products, skilled peers, opportunity for tremendous impact, competitive salary, and a very competitive ownership stake.

We’re looking for exceptionally productive, thoughtful, tasteful, and kind people with a passion for making software development better for everyone. Want to build the future of API tooling? Say hi: alex at stainlessapi.com

I think they maybe just haven't updated that website much since before they launched the browser, whose website is here: https://arc.net/

I've been using it for a while and it's solid.

Ruff is faster than many tools which don't do type checking.

Ruff works well regardless of whether you use type hints.

TIL: https://openai.com/research/point-e

Came out back in Dec '22