HNHacker News
TopNewBestAskShowJobs

martypitt

1,312 karma · joined March 19, 2013

Software dev, working on Orbital (https://orbitalhq.com) and Taxi (https://taxilang.org)

Happy to chat. Ping me on marty [at] orbitalhq dot com

submissionscomments
martypitt··on Show HN: BillaBear – Self-Hosted SaaS Subscription Management and Billing
I really struggle with this attitude that companies that make their code available, but don't do it "open enough", are therefore "BadCompanies".

Companies are not obligated to make their source code available (excl: copy-left, where they are).

Those that do, often choose to do so in a way that balances aiding a community, and growing their business.

That's a good thing IMO. Being commercially savvy, and ensuring the company that authors software today, will be here tomorrow, is good for the software, and therefore, for it's community.

I don't understand where the sense of entitlement comes from that it's OK to shame/berate/insult a company who publishes their source code, because of the restrictions they elected to impose.

Companies like Lago are small startups, who need to pay the staff to author the software. They also created a company to generate profits. Electing to do so under an Open Core model is a good thing - as we get Open Source software as a side-effect.

They have no obligation to do so under a permissive license. That they do so under any license should be celebrated, IMO.

> many new YC open core companies are doing this now.

Great! Long may this continue. Companies that are open-core are beneficial for everyone. Splitting hairs over the license they elect seems ungrateful IMO.

martypitt··on OpenAPI v4 (aka Moonwalk) Proposal
One of the gripes I have about OpenAPI is that it has a very low signal-to-noise ratio. It was bad in JSON, it's just as bad in YAML, with an added whitespace pedantry.

It's great to see a number of alternatives listed in this thread - there's much more active development in this space then I was aware of, and I hope that some of it gets upstreamed back into OpenAPI.

I'll shamelessly plug our tool in this space - Taxi (https://github.com/taxilang/taxilang), which has a dedicated DSL (not YAML) you can either use standalone, or embeddedd within OpenAPI.

I also happen to think that (for internal teams at least), generating clients on ${apiSpec} is a form of tight coupling, where producer and consumer become tied together. If you can avoid it, you should, as it allows producers and consumers to stay loosely coupled and evolve independetly without the gymnastics of avoiding breaking changes.

I've talked about this before, with proposed solutions.[0]

[0]https://orbitalhq.com/blog/2023-01-16-using-semantic-metadat...

martypitt··on ECoute – AI Assisted Job Interview
Not my project, I don't endorse the ethics behind this, but love the ingenuity. :)
martypitt··on Ask HN: How do you not take criticism of your work personally?
> A high criticism tolerance is learned by understanding that ones self worth is not attached to output or delivery.

> You are not your lines of code.

These statements are sage advice. And while I believe them both to be correct, I personally struggle with remembering these things when it matters most.

martypitt··on Launch HN: Common Paper (YC W23) – SAFEs for Commercial Contracts
This sounds very interesting. Your website doesn't appear to be loading. (edit: It's now back up - thanks!)

However, the idea of standard, programmable contracts is awesome!

One question: In your example of being forced to use Oracle's paperwork - it's not clear how CommonPaper would solve that - wouldn't you still have been forced to use Oracle's contract?

martypitt··on Why we created Taxi, and why we felt the need for another schema language
> What happens when a consumer does not understand the producer’s domain and misuses the data?

That's a problem with or without Taxi/Orbital.

Today, it's generally left to consumers to pick the fields that look right, and hope they get it right. That's a risky approach. And, by leaving it to consumers, you run the risk on every new integration.

I think by asking producers to annotate their attributes with a strongly defined semantic contract, you reduce the risk of consumers getting it wrong.

Producers understand their data much better than consumers, so are better informed on how to map their attributes to a set of semantic contracts that consumers can leverage.

martypitt··on Why we created Taxi, and why we felt the need for another schema language
> it is even more expensive/slow to have producers try to continuously anticipate the needs of all possible current and future consumers

I agree, but I don't think Taxi encourages that. (I sure hope it doesn't).

All that's really happening is defining a system-agnostic set of terms, embedding those in producer schemas, and then letting consumers using those same terms to ask for data.

Those terms can be used to automate integration, and in many (but not all) cases, alleviate the need for low-value plumbing code.

Semantic Metadata is a growing trend in the data ecosystem (cube.dev is doing a nice job here too). The Agile folks have had Ubiquitous Language as a first class concept since day dot.

> an approach will work only in a company below a certain size/complexity/age I think that GraphQL federation is an example of mid-to-large companies trying to solve the federation problem, suggesting they both feel the pain, and are looking for solutions.

martypitt··on Why we created Taxi, and why we felt the need for another schema language
Autogen tools do a nice job of creating GraphQL schemas from a single source.

We're looking more at how to compose / stitch multiple sources into a single queryable API. (ie., Stitch data from a DB, some REST APIs, and a Kafka topic).

In GraphQL, you need to write / maintain resolvers that handle the stitching for you - which means as upstream data sources change, resolvers need to be maintained too.

Smithy is nice, and we'll probably add first-class support in Orbital for it at some point. Taxi was around before Smithy, so we're the OG :)

martypitt··on Why we created Taxi, and why we felt the need for another schema language
Taxi was discussed 12 months ago here:

https://news.ycombinator.com/item?id=31524950

martypitt··on Why we created Taxi, and why we felt the need for another schema language
I agree that querying is where the real value is at, and Trustfall looks like an elegant approach.

While Taxi is all about documenting & augmenting specs, Orbital is the query engine (which is a bit similar to Trustfall) that consumes those specs.

Orbital's goal is to allow consumers to be able to query for data, without having to be aware of the specifics of the data sets / APIs / DBs, etc they're composing together.

IMO GraphQL does a nice job on the query side of keeping consumers away from the wiring, but shifts the obligation to middleware resolvers.

How data is wired together is ultimately an implementation detail, and one that changes. If consumers need to know about how stuff is connected, they're subject to breakages when those details change.

martypitt··on Why we created Taxi, and why we felt the need for another schema language
A descriptive type system is a big part of what makes Taxi work.

We took a lot of inspiration from GraphQL (because it's awesome), but I actually think we go further in the type system than GraphQL.

martypitt··on Why we created Taxi, and why we felt the need for another schema language
Enums, yep: https://taxilang.org/language-reference/types-and-models/#en...

Sum types, no, not yet.

martypitt··on Which kinds of GPT startups will thrive?
We're experimenting in this space, and I think our approach is a nice balance. (I'm clearly biased).

OpenAI is giving us a chat-based interface to our core product, which we didn't have to build ourselves. Our platform was exclusively developer focussed (automated API integration), which has value on it's own, but was limited in reach to a technical audience.

By adding a chat interface, we get to make our tooling available to a whole new type of audience - non developers, who can "chat" with their API estate.

I personally like this balance - using AI to lower barriers and widen the reach, but the underlying offering has value standalone.

martypitt··on Datomic is Free
They say the binaries are being made under Apache 2.

They don't say anything about the source code being published. That's why (to me) this is so interesting. I've never seen binaries released without source code before.

martypitt··on Datomic is Free
Sure, Maven makes this possible.

But Maven Central has strict rules around what can be published there. I just double checked and it's a requirement to publish the source as well as the binaries:

https://central.sonatype.org/publish/requirements/#supply-ja...

martypitt··on Datomic is Free
Only the binaries are made available, not the source, which is interesting.

I guess they don't claim to be open source, they're claiming to be free, which is - in itself - awesome.

Last time I checked, you couldn't push binaries to maven central, without also releasing the source. That may have changed.

martypitt··on Show HN: Matic: A reimagined robot vacuum that actually works
That's some pretty hefty pricing - $1500 / year, on subscription ... so I don't actually "own" the vacuum.

> Matic must be returned to us if you cancel your membership.

In comparison, the robot vac my family have been using for the past 3 years works great, and is currently £200 on Amazon.

martypitt··on Telemetry in Front-End Tools
What social contract is that?

As far as I'm aware, the contract of OSS is "you can fork this to change it, if you don't like it" (license permitting).

A big part of the reason people advocate for OSS is so they can read the source code to understand what's going on, and change the parts they don't like. Telemtry sits squarely under that usecase.

I agree that it's good manners for projects made users aware of telemetry, but there's no "contract" that implies they have to.

martypitt··on Launch HN: Frigade (YC W23) – Faster, better product onboarding
I'm your target customer, as we're thinking about building this right now.

I just checked out Appcues (didn't know about it until this post), and got sticker shock at the cost.

IMO, $299/mth is high for the value this delivers, however it's possible I don't have a full appreciation of what you're doing yet.

Also, we're a startup, so I'm keen to understand when your pricing kicks in.

Have signed up for your beta!

martypitt··on TypeScript 5.0
I remember this well.

From the outside, it seemed a fantastic example of collaboration between two separate (competing?) teams. It took humility and pragmatism for the Angular team to abandon AtScript and recognise TS as the better long-term bet.

martypitt··on TypeScript 5.0
Congrats to the Typescript team.

The rate of innovation from them is really impressive.

Fantastic to finally see Decorators shed their "experimental" label (they've been the stable backbone of Angular for years).

martypitt··on Docker is deleting Open Source organisations - what you need to know
I think it's an interesting challenge with FOSS infrastructure in general, and I'm surprised it isn't more of an issue.

Docker's storage is heavier than most, but what about other repositories like maven central, and npm? There must be significant costs associated with running those.

These tools are all the backbone of modern software dev, and need a business model. It's reasonable that consumers should pay for the benefit. I think Docker have screwed the execution of this transition, but the overall pattern of "someone has to pay" is one I support.

Personally, I pay for Docker. I use it every day, and get value from it.

The argument that the OP makes is really valid though - OSS needs distribution channels, which need to be funded - and expecting the publisher to pay for this isn't always appropriate.

I'd like to see something like the equivalent of CNCF which I can buy a subscription from, and it funnels money to the comapnies and developers that keep me in a job -- almost a Spotify model for OSS and it's supporting infrastructure.

martypitt··on Docker is deleting Open Source organisations - what you need to know
Gitlab have been increasing pricing heavily recently, especially in storage-heavy areas such as containers.

I don't think they're likely to be a cost-effective differentiator against what Docker are now charging.

martypitt··on Developer marketing for early-stage startups – what we’ve learned
Often "Developer Advocate" or similar is the title.

draft.dev is a company that does this full time (not affiliated).

martypitt··on Architecture diagrams should be code
I agree very strongly with this, but I build tools in this space, so I'm obviously biased.

IMO, Architecture Diagrams should be code, but there's additional value in describing those diagrams in a way that lets us use metadata to interact with the systems they're describing.

ie: OpenAPI describes an API, and lets me interact with it - it's limited in that it doesn't descirbe how two independent APIs (eg., Microservices) are related. I also believe that OpenAPI has a very poor signal-to-noise ratio, meaning it's hard to read & grok.

I'm one of the creators of Taxi (https://taxilang.org), which provides a language for modelling systems and data.

We also build Voyager (https://voyager.vyne.co) which visualises those models into pretty diagrams.

We also build Vyne (https://vyne.co), which lets you use those some models to run queries against those systems, and handles all the integration for you.

If you're interested in anything in this space, hit me up.

martypitt··on Ask HN: Why do startups avoid Java?
We've built a huge stack in it. (Well, Kotlin). Love it, and hiring is easy.
martypitt··on ReScript 10.0
They discuss this in their docs.

https://rescript-lang.org/docs/manual/latest/introduction#di...

Seems like a type system for Javascript, built with a differing set of opinions than Typescript.

Looks like they also offer some form of TS interop:

https://rescript-lang.org/docs/gentype/latest/introduction

martypitt··on GitLab SaaS Free Tier FAQ
Just in case anyone from Gitlab is monitoring this thread, there remain issues[0][1][2] in the artifacts listed both in the UI, and returned from the API, resulting in artifacts unable to be deleted.

It's clear that the gitlab dev team are aware of these issues, but given they've been open for years, I'm not convinced they'll be resolved before the pricing changes kick in, in a little over a months time.

If not addressed, according to the FAQ, teams builds will start failing, as they'll be unable to publish artifacts, and unable to manage the artifacts, essentially leaving them blocked.

0: https://gitlab.com/gitlab-org/gitlab/-/issues/373806 1: https://gitlab.com/gitlab-org/gitlab/-/issues/363010 2: https://gitlab.com/gitlab-org/gitlab/-/issues/228681

martypitt··on GitLab SaaS Free Tier FAQ
I might be alone, but I'm really struggling with this line of fixes from Gitlab.

To be clear - I'm all for Gitlab charging, I think that's fair and reasonable.

However, if they're gonna charge for artifact storage, they need to provide first-class tooling to manage the storage.

My experience is almost exactly the same as the OP's. Huge artefact storage from builds, the scripts to clean up don't work.

> The async operation to delete artifacts can take a while. How do I tell if something has succeeded or failed then? Last time I ran the scripts, no errors were mentioned, but nothing was tidied up.

Cleaning this stuff up shouldn't be via hacky scripts or community projects. It should be a mandatory requirement for managing an aspect of my account that's about to become very very expensive.

martypitt··on Starting October 19, storage limit will be enforced on all Gitlab Free accounts
We're affected by this change, and have been trying to get support in forums, but can't get hold of anyone.

Build Artifacts are listed as part of what contributes to the quota (which is fair enough), but there's no way (that I could find in the docs) to manage build artifacts that are stored.

I suspect we have a large historic storage, which we don't use / need, but there's no way to browse this, no way to verify it, and no way to delete what we don't need.

I'm dreading getting a big ole bill in a few months for storage we had no way to opt out of.

← PreviousPage 6 of 8Next →