Buf raises $93M to deprecate REST/JSON
1–10 of 91 posts
Re: Buf raises $93M to deprecate REST/JSON
#2The idea of "I'm raising money to get people to stop using REST/JSON" seems kinda weird to me. I get that they have a product and all but the general lead in here seems weird to me.
Re: Buf raises $93M to deprecate REST/JSON
#3Yay, an XML v2.
Re: Buf raises $93M to deprecate REST/JSON
#4The $93M number in the headline is somewhat misleading, as it's cumulative across all the rounds of funding. Can the title be changed to state that the specific round raised now is a $68M Series B?
Article quote:
> We just closed a $68M Series B co-led By Lux and Tiger Global, with participation from Greenoaks Capital Partners, Lightspeed, Addition, and Haystack.
Re: Buf raises $93M to deprecate REST/JSON
#5Hmm why do they need to raise so much cash every 9 months?
Also does anyone here use them and have any thoughts about their product?
Re: Buf raises $93M to deprecate REST/JSON
#6Lol. Imagine trying to capture a market that is already mostly happy with what it's got, and for free.
Re: Buf raises $93M to deprecate REST/JSON
#7Lol. Imagine trying to capture a market that is already mostly happy with what it's got, and for free.
[deleted]
Re: Buf raises $93M to deprecate REST/JSON
#8Lol. Imagine trying to capture a market that is already mostly happy with what it's got, and for free.
And to then provide roi on 93m
Re: Buf raises $93M to deprecate REST/JSON
#9Hmm why do they need to raise so much cash every 9 months? Also does anyone here use them and have any thoughts about their product?
I don't even know why they need so much money for what they do.
Based on their website, they solve the following problems:
- a central schema registery. Even if that's something you actually want, it's not a problem that requires $93M to solve, or a commercial company to operate
- communicating schema changes primarily via human-oriented sources like handwritten documentation on emails. I mean sure, if you are a masochist (or a sufficiently inefficient org), you might do just that. The rest of us here in the 21st century can check the schema into a Git repo instead.
- schema drift on the client end. Tough, this is what happens when you write software. Adding a third party won't help here.
- dependency management. For APIs? I cannot imagine a single case where that would help and your API isn't already a monstrosity.
Re: Buf raises $93M to deprecate REST/JSON
#10Yay, an XML v2.
More like WSDL.