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: Orbital – Dynamically unifying APIs and data with no glue code
This is a fair comment, and something I think we could do better at... bear with us, we're moving from entirely closed source, to Open Core.

I've partially tried to address this with the FAQ[0]. Maybe we could move the codebase around, so there's community/ and commerical/ top-level dirs, and associated licenses under there. (Naming TBD).

[0]https://github.com/orbitalapi/orbital/blob/develop/LICENSE_F...

martypitt··on Show HN: Orbital – Dynamically unifying APIs and data with no glue code
Currently, we don't have validations implemented.

We've spiked it in the past, and had some nice designs that attached validation rules semantically to the scalar types (which are very sharable), and models (which are more system-specific).

The early designs felt nice (albeit early), but the deal we were working on didn't eventuate, so we didn't push it through.

I think Validations become really interesting in both evaluation flows (ie., ingesting in a pipeline or through a mutating API), as well as quality scoring for data-at-rest.

I'm excited to explore these in more detail, given a use-case.

martypitt··on Show HN: Orbital – Dynamically unifying APIs and data with no glue code
We've been playing with LLM's and OpenAI to build integration from plain text.

There's a video of an early version of it in action here: https://www.loom.com/share/a78c70f0e2bd42a28b7cb0a5d175c3aa

I think what's nice about using LLM's to build Taxi queries (which is what's actually happening here) is that we're not having to push things like API Specs and DB Schemas to the LLM. Instead, we train it on the Taxi types that are available, get the LLM to build a Taxi query, and let Orbital generate the integration.

It means a lot less information is pushed out.

Still quite early, but it's really powerful.

martypitt··on Show HN: Orbital – Dynamically unifying APIs and data with no glue code
Thanks!

Yep, we have (early) SDK's for Typescript and the JVM, to submit the query directly.

Also, you can publish queries as standalone APIs, in a BFF-style pattern.

martypitt··on Writerside – a new technical writing environment from JetBrains
Jetbrains have a pretty decent Knowledge base inside YouTrack (their issue tracker tool)
martypitt··on Writerside – a new technical writing environment from JetBrains
Looking at the website, it seems like it's limited to MD, without support for MDX - which is a shame, as MDX has become a powerful tool in how we write documentation of late -- especially since their output strategy is "click to host this as a website" -- perfect for MDX.

Also, it seems even more odd that their markdown support is a custom flavour - adding support for things like tabs, and warning styles. (Unless I've missed something?)

It's unhelpful for a WYSIWYG tool to show you something of how it's rendered in a very small subset of the markdown ecosystem.

martypitt··on Tailwind vs. Semantic CSS
I love that idea, and would definitely use it.

In fact, if there's enough interest, I'd probably build it too...

martypitt··on Flexport will lay off 20% of the company starting Friday, leaked memo says
> With more than $1 billion in net cash, following this change, Flexport is now in a great position to take advantage of the opportunities in front of us to return to profitability as soon as the end of next year.

This feels like a tone-deaf statement to make in an email laying off 1 in 5 of your company.

"We're letting you go, but look how much cash we have!"

martypitt··on OpenAI is too cheap to beat
I agree with this.

However, what will be interesting is if the price of delivering ChatGPT-style experiences drops as the industry matures/advances, and their pricing moat erodes.

Unlike Uber - where prices are dictated by factors unlikely to move significantly (Labour / Vehicles / Fuel / etc), The LLM space doesn't have these types of overheads.

martypitt··on Cypress.io Blocking of Sorry Cypress and Currents
Can someone with a little more context expand here?

Cypress is MIT licensed, so I don't understand what Currents were doing that was so bad?

martypitt··on Krita fund has no corporate support
I've been toying with an idea of some kind of "Spotify for OSS" kinda thing - where software authors can make their binaries available, provided you have an active subscription (with the Spotify for OSS service).

Funds are then distributed based on usage (trackable at the package registry).

The idea being corporates buy a single license per head, rather than dealing with lots of donations etc.

Probably lots of reasons it wouldn't work, but it's a fun thought experiment.

martypitt··on Open Source does not win by being cheaper
This discussion is on the topic of Commercial, Open Source software.

If a company is wholey funded by the government through taxpayer dollars (as in your examples), then I agree - profit isn't the driving consideration.

But that's not what this conversation is about.

martypitt··on Open Source does not win by being cheaper
I'm happy for those companies that become commercially viable through pure open source - and those are some great examples - although they're not financially viable on their own:

- Firefox's primary income stream is embedding Google search.

- Linux is funded primarily through companies like Canonical and RedHat, which charge for premium features.

I'm sceptical that if either of those examples were to launch today, that they'd survive using the same strategies they used years ago. I'd wager that if Canonical launched today, it'd be as Open Core, which isn't far off what it's actual business model is.

However, those are great examples of companies whose primary focus is in shipping "The Thing", and finding a way to build a business around it. That's far better than making "The Thing" a side-hustle, which is what the React example was advocating.

martypitt··on Open Source does not win by being cheaper
> The best "open source " business is one that gets profit from doing something else and publishes some open source software on the side . Like react.

How is "Be a company that harvests personal data for profit, and publishes a javascript library on the side" a good model?

And, how is it better than:

"We build this thing. It's all we do. Here's the source. If you use some features, you gotta give us money?"

martypitt··on Open Source does not win by being cheaper
I think this is a great point.

I'd hate to see Open Source become even less commercially viable then it is today. I don't know the answer here, but I agree with the risks you've highlighted.

I think part of the issue is in mindsets of the community, where they see any Github source project, and immediately think "I'm entitled to use this without paying". I doubt that attitidue will shift, but I think it damages the ability for more companies to take a bet on being open.

Ultimately, when that happens - the users of the platform lose out.

martypitt··on Open Source does not win by being cheaper
> Open core are just companies that want to throw around the "look we are cool, open source" mantra , but in reality are dealers giving you the first dose free to hook you up in their business.

Strong disagree.

There are real material benefits to companies making their source code available - lots of them are espoused in this discussion. Things like Auditability, Debuggability, etc.

These aren't about appearances, it's about giving additional benefits to the users.

But it HAS to be backed by a sustainable business model. Otherwise, it's a hobby. Open Core, and other similar models, are about delivering the benefits of open source, with the security of knowing there's a viable business model sitting behind it.

Also, as a community - we should be far more open to paying open source companies than we are. Statements like:

> but in reality are dealers giving you the first dose free to hook you up in their business.

Exactly!

It's a business. They're paying salaries of people to create things to give you value. You should pay for it.

martypitt··on Open Source does not win by being cheaper
Fantastic article. I'd love to see more people championing statements like "Profit, not usage, is a measure of success".

I think there's a stigma about open source projects being run as commercial, profit-generating businesses, and I'm very happy to see more people championing the Commerical, Profitable OSS cause -- which everyone in the ecosystem benefits from. (More Profit == Keep Building More OSS).

I happen to like the Open Core model here, where businesses adopt OSI OSS licenses for the core, and Source Visible licenses for the rest - which gives the balance of visibility, auditability, etc, whilst still enabling the project to be revenue generating, delivering longevity as well.

martypitt··on JDK 21 Release Notes
I can't wait to see if/how tools like Reactor and Kotlin Coroutines adapt with Virtual Threads, and if they extend the tooling, or provide a migration path.

I've written a tonne of code on both Reactor and Coroutines, and would love something simpler, but dread the idea of migration.

martypitt··on RustRover – A standalone Rust IDE
I suffered that exact same issue for a very long time with IntelliJ.

If you haven't tried upgrading yet, I'd recommend it. They did a huge amount of work to address the issue, and from my experience, it's significantly better in 2023.2.

martypitt··on What is wrong with TOML? (2019)
I really like the way the author writes.

The article is great, and so are a few other links. Particularly enjoyed this[0] on the same site - The Norway Problem, which discusses parsing challenges in YAML.

[0] https://hitchdev.com/strictyaml/why/implicit-typing-removed/

martypitt··on Death by a Thousand Microservices
I think this is a great point, and shouldn't be just hand-waved away like you hit some bizarre edge case of Monoliths.

Monoliths can have crippling downsides -- just different flavours of downsides from Microservices. What you gain in network latency and DRYness, you can lose in Autonomy and Breadth of codebase.

Microservices vs Monoliths - just like everything else - is a question of tradeoffs, and making informed choices about when to apply them, and how to mitigate their downsides.

The slightly more nuanced point in the OP's article is that adopting any engineering practice and blindly following as though your identity is linked to it, is a bad move.

martypitt··on The Terraform Registry Terms of Service have been updated
Not the OP, but I suspect HN has trimmed the anchor link.

> https://github.com/opentffoundation/roadmap/issues/24#issuec...

That's the comment that made the issue clear -- specifically TOS were amended for https://registry.terraform.io to state:

> You may download providers, modules, policy libraries and/or other Services or Content from this website __solely for use with, or in support of, HashiCorp Terraform.__

ie., it looks like the intent is "You can't use OpenTF with registry.terraform.io".

IMO, that feels a little petty. But, I guess if OpenTF is taking a position of "Use us instead of Terraform", then they shouldn't expect to get the usage of Hashicorps infra.

martypitt··on Ubuntu Desktop: charting a course for the future
Out of interest, what have people moved to? I'm a pretty happy Ubuntu user (and the Snaps issue doesn't really bother me personally), but I'm curious if I'm missing out on something better elsewhere?
martypitt··on Monetizing Developer Tools
> If they see their project took off and they can earn some bucks by milking users later, that is cheating.

No, it isn't.

Open source developers are not under an obligation to continue providing their time for free. If they choose to pivot the project to some form of monetization, that's their right.

Previous versions remain available under previous licenses - that gift to the world remains, and stays available for communities to fork from, should they choose to.

If a project gains sufficient traction and delivers sufficient value that people depend on it, it's in everyone's best interest that the developer finds a way to monetize, so they're motivated to continue working on the project.

As you say, then the market will decide if it's a price worth paying, if they can live without the service, or if they'd rather take on the build burden themselves via a fork.

But Free Today does not entitle you to Free Forever.

martypitt··on Elixir Livebook is a secret weapon for documentation
That's fantastic. We use Kotlin to build Taxi (taxilang.org) and orbitalhq.com. this would be an awesome addition to our docs.

However, do I understand it correctly that this allows me to output verified, working code in my test suite, but its not a tool that I can embed in my docs to create runnable code samples? (which is what the OP is showing).

super valuable either way, just trying to validate understanding.

martypitt··on People who've received a black bar on Hacker News
Looks like this was pulled together with a degree of manual heavy lifting, for which the OP deserves our thanks.
martypitt··on Twitter has officially changed its logo to ‘X’
Meanwhile, the x.com domain seems to be somewhat shambolic.

As I write this, it hits a Godaddy parking page. According to this[0] tweet[1], it's been a Godaddy site, a dead link, a redirect, and now a godaddy site again.

Shambles.

[0] https://twitter.com/rothschildmd/status/1683289016723202050

[1] No, I'm not calling them X's. That name is saved for those who broke my heart, made me cry, and left me binge watching Notting Hill.

martypitt··on Twitter has officially changed its logo to ‘X’
This is actually really clever!
martypitt··on Custom instructions for ChatGPT
Just noticed this too. I wonder what the reasoning for that is - ie., is this related to specific jurisdiction laws, or just a geo-rollout to manage volume?
martypitt··on Show HN: BillaBear – Self-Hosted SaaS Subscription Management and Billing
Looks like pull requests are open.

Excited to see what you contribute.

← PreviousPage 5 of 8Next →