1,312 karma · joined March 19, 2013
Happy to chat. Ping me on marty [at] orbitalhq dot com
You've only presented half the story. They're also Open Source (Apache 2.0), with code on github.
As you mention, some features are gated, but they seem to have a fairly solid OSS offering.
we have the same strategy for testing against Kafka., etc.
where we care about data, we seed the db with data for a specific group of tests. Otherwise, we just nuke the db between each test.
Prior to doing this, we'd use in-memory db for tests, and a real db for runtime, using JPA / Hibernate to make things transferrable. But this was leaky, and some things would pass in tests then fail at runtime (or vice versa)
TestContainers has been so much better, as we're running against a real version of the database, so much smaller chance of test and runtime diverging.
It's a tool that sparks strong opinions, which is a testament to its significance and the impact it has made. You've created something that people are passionate about, whether they're for or against it.
Personally, I'm firmly in Team Lombok. I believe the negative feedback it receives is disproportionate.
For those of us who use it, Lombok significantly improves our coding experience. For those who don't, it's entirely optional and doesn't interfere with their workflow.
Thanks again for creating something that made me enjoy coding in Java :)
Performance: 81 / Accesssibility: 93 / Best Practices: 96 / SEO: 100
Performance is on the lower side, but the others are all tracking pretty well!
Another problem we've never worked out the solution to, is how to send a termination - signalling "there are no more events coming". We always end up having to roll our own, though it felt like something that should've been handled at the protocol layer.
Most commonly the restrictions prevent you from launching a competing offering. In their case, you can't offer database-as-a-service using their code.
BSL typically also restricts production use - though it looks like ReadySet has relaxed that restriction.
Finally, BSL reverts to a traditional open source license after a set period of time - in their case Apache 2 after 4 years. This means that code written today is licensed under BSL for 4 years, then automatically reverts to Apahce 2 thereafter.
The only other thing is to log in, with an email address. Given how questionable the site seems, I bailed.
Sure, Podcast ≠ Spotify, just as Git ≠ Github. But people choose to distribute their code on Github for exactly the same reason the people choose to distribute their podcasts on Spotify - reach.
That exact reach is what Drew argues so articulately against - in fact he expressly calls out marketing on Twitter and Facebook as a "mistake", and damaging against the FOSS community. He goes on to encourage people to prefer open infrastructure with lesser reach, even if that comes at the expense of effectiveness:
> Such projects would prefer to exacerbate the network effects problem rather than risk some of its social capital on a less popular platform. To me, this is selfish and unethical outright.
It's hard to see how that same argument doesn't extend to promoting your software on podcasts which are primarily distributed via Spotify, Apple Podcasts, etc.
On the topic of Activism, I think I'd agree with you, if he was on Spotify podcasts promoting other "Free" podcast platforms.
But he's not - he's promoting a programming language.
Fair call.
But after reading that article, I was definitely left feeling judged because I choose to do exactly the things he's talking about, for exactly the reasons he's suggesting. Maybe that's on me, but I certainly felt his standards imposed on me, disclaimer or not.
Also, given the conviction with which he argues with in the article, that disclaimer feels a little weak -- kinda like when someone says "No offence, but... <very offensive thing>".
He claims that authors promoting their open source software on channels like Twitter, Hacker news, LinkedIn or even Github is "selfish and unethical outright":
> Many projects choose to prioritize access to the established audience that large commercial platforms provide, in order to maximize their odds of becoming popular, and enjoying some of the knock-on effects of that popularity, such as more contributions.
> To me, this is selfish and unethical outright, though you may have different ethical standards.
I find Zealotry like this tough, and promotes a definition of FOSS that feels hostile against those who want to simply build something cool, and share it with the world - (or even more controversially, make money from FOSS).
Given such a strong view, it's really surprising that he then posts stuff like "Can I be on your podcast"[1] to try to promote Hare - his programming language.
He didn't ask for podcasts that aren't distributed on platforms like Spotify or Apple Podcasts. In fact - he's right there with several appearances promoting Hare.
That feels like hypocrisy.
[1]: https://drewdevault.com/2023/11/09/Can-I-be-on-your-podcast....
Pretty standard bootstrap story - used consultancy to get us out the door. These days, we're (nearly) self sustained through license revenue, with a small amount of consulting (1-2 projects a year).
It's been a tough ride, and in hindsight, I wish I hadn't pivoted away from consulting quite as early as I had, however we've managed to stay alive, so - so far - independent, which has been nice.
It's appeared in every Star Wars and Indianna Jones movie, along with countless others.
Really cool 4-minute documentary on BBC for those who can view it:
https://www.bbc.co.uk/iplayer/episode/p07p5l6y/inside-cinema...
However this comment feels off:
> In software ideas are cheap. Value is almost always created in execution of ideas.
I've heard this phrase around things like "I have this cool idea for a startup - will you sign my NDA before I tell you about it?"
However, when you're open sourcing your software, you're not just providing an idea, but a significant portion of execution of that idea too.
Sure, code isn't the full execution - that expands to sales / marketing / support / etc.
However, the article is a little glib towards the value of the code, suggesting it's worthless without sales / marketing /etc. I don't think that's true.
@DanHulton - tell us all the tale.
It's definitely worth the one-off price tag, and the fact they include future updates (like Catalyst) is incredible.
Regardless, imperfect as it is, a GH project with 20k stars feels more credible than one with 200.
(I write this as someone who works full time on a GH repo with 200 stars! :D)
20k stars in a single year is a very impressive feat.
Congrats to the team at Plane, and thanks for this.
Also, it's an informal social proof, which drives trust. The more stars, the more legit something seems.
This feels like a "we need to be doing something in AI" play.
You're gonna have to walk me through that one.
Clean UI (almost bordering on a rip-off of Postman.. but I guess familiarity helps users get going faster).
Lovely to see that things aren't held behind a Login button, ala Postman and Insomnia (Kong really misread the room on their latest update).
Login and accounts seem like they're there, but very clearly optional.
Nicely done, Hoppscotch team!
Also, importing JSON in typescript is another cool thing I learnt about.
Thanks for writing this up!
It's a little less clear to me how you monetize this type of stack. Given such an impressive fundraise, in a tough climate, I wonder what the market opportunity the VC's have backed is.
BTW: At the time of writing, the link to Charm Cloud in your blog post is broken.
At a language-to-language feature level, there's some core differences:
GraphQL-without-resolvers still relies on imperative joins defined somewhere. AFAIK, Wundergraph pushes this to the query layer. GraphQL Mesh pushes this to .yaml files. This means that as the sources change, there's centralized config needs to be updated in lock-step, or things break. This means the API producer is now obligated to work closely with consumers to release changes.
TaxiQL infers join logic by introspecting the schemas. This is especially powerful where joins require hops across multiple sources (eg., Id resolution where services use different ID schemes). Because type metadata is embedded at the producer schemas, producers are free to make changes and the query layer adapts.
GraphQL promotes a single graph that everyone cherry-picks from. TaxiQL lets query authors define their own data contract, and own data shapes. This moves transformation of code into the query layer, which we think is a better place for it.
GraphQL doesn't allow extensibility in the language. (We've seen others hack around this with framework-specific annotations, but that's always felt quite awkward). TaxiQL supports extensibility, adding custom functionality into the query layer, and ships with a pretty rich stdlib for things like avg(), first(), last(), etc.
eg:
type ImdbFilmReview extends FilmReview
type RottenTomatoesFilmReview extends FilmReview
Which allows you to query for either "All film reviews", or just a subset.We've found that actually covers about 80% of use cases.
However, some users have asked for more control in the query langugae, which we're working on improving the TaxiQL query syntax for this right now.
Here's what it looks like:
find { Film[] } as {
id : FilmId
rottenTomatoesReviews : RottenTomatoes::FilmReview[]
imdbFilmReview : Imdb::FilmReview[]
}