Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Quitting Dgraph Labs

discuss.dgraph.io

Post reply on HN
Print view View original

81–90 of 94 posts

Re: Quitting Dgraph Labs

#81

Post by traceroute66 »

glenngillen wrote: post #46
traceroute66 wrote: post #14

Doesn't come as much of a surprise really. $employer had a need for some of the bits of Dgraph that are unfortunately hidden behind a paywall (bits that IMHO should have been in the community version as they were not particularly enterprisey, but hey such is life). A frustrating conversation with Dgraph sales-droid ensued: Us: We need access to X/Y/Z features, but on-prem Droid: But Cloud Us: Cloud = No-go because X/…

I’m not sure why you think this is their fault, or why you think the enterprisey-ness of a feature determines whether it should be behind a paywall. Clearly it was valuable enough for you to want it. People should pay for value. Especially if they want companies to stick around for the long haul to support the technology.

> I’m not sure why you think this is their fault

I think you missed the point. What I was making a point about was first the tin-eared nature of the salesdroid (i.e. "cloud cloud cloud cloud" despite me explaining why not). Second about the price point of on-prem. Of course I will "pay for value" but there is a difference between paying and paying through the nose.

Basically it gave the impression that Dgraph was so up itself that it thought it could dictate how their customers should run their IT and thought it was special enough to be able to ask silly money prices.

Re: Quitting Dgraph Labs

#82

Post by throwaway4354 »

jandrewrogers wrote: post #74
sangnoir wrote: post #71

Earlier quoted context omitted.

>...only me and him can pick those bugs Brittle or hard-to-grok code that other engineers avoid is a code smell. Eng leadership/senior engineers ought to prioritize refactoring that code ASAP

There wasn't any implication that the code is "brittle" or hard to grok due to a defect in the software architecture. It may be approximately optimal from the perspective of software maintainability relative to functionality and performance. All code has non-local side effects, but in most software that is buried below the noise floor of inefficiency. Some types of software are intrinsically difficult to understand e…

Yep this so much. It is not that code is brittle but problem space is hard. What seems like an obvious fix may break other vendors that depend on same behavior etc.

Having said all of that. Modesty is a thing and many engineers wouldn't word things the way Manish worded in aforementioned blog.

Re: Quitting Dgraph Labs

#83

Post by mrjn »

dannyw wrote: post #76
mrjn wrote: post #47

Earlier quoted context omitted.

> And two, we lost a couple of deals last quarter due to engineering challenges I can help solve in weeks but would take my team months on their own. Some of these problems wouldn’t get solved without my help. Those were not my words. Those were the literal words used by my Engineering manager out of desperation to convey to me that the team needs my help in solving these problems. I'm not sure why you would take the…

As a lurker, I'd suggest you stop talking because you're not helping your case. As a leader/CEO/CTO, people judge you based on your ability to lead the team, not your personal technical skills. Your posts are throwing away the former in an attempt to demonstrate the latter.

That sentence is being taken out of context. So, I clarified the context.

Moreover, the team in question -- I have spent countless hours working with them -- and they know exactly what I meant. No one ever complained about this blog post or this particular sentence. They knew exactly where I was coming from.

If Glassdoor is a benchmark for the effectiveness of leaders, then might as well vote for whatever Russian trolls tell you to vote for.

People are free to make their own judgments.

Re: Quitting Dgraph Labs

#85

Post by danhab99 »

eudoxus wrote: post #72
danhab99 wrote: post #66

Earlier quoted context omitted.

> I'm not sure what "eat section 13 of Mongo's license" means Buncha weeks ago I had a paranoid fit about the legalities of this app I wanna try to launch. I read some conserning things about the MongoDB license, mainly that the open source initiative didn't approve it bc Mongo pulled out. I read the controvertial paragraph and now I am 80% convinced that I'm not allowed to self-host a MongoDB server for my own profi…

IANAL but from what I know about Mongos current license (Server Side Public License) the restrictions of section 13 only apply if you are making a service with the express interest in providing DB functionality directly to your customers/users. IE: If you are making a Database as a Service platform, similar to Mongo Atlas or AWS RDS. If you are just using mongo as a backend DB to fulfill some other internal requireme…

Arite, now the tally is even. I've heard the same number of people say to me that it's safe to use Mongo to power an app so long as I don't expose it, as have told me that I can't because I have to opensource all of my code that interacts with Mongo.

Re: Quitting Dgraph Labs

#86

Post by alittletooraph »

danhab99 wrote: post #85
eudoxus wrote: post #72

Earlier quoted context omitted.

IANAL but from what I know about Mongos current license (Server Side Public License) the restrictions of section 13 only apply if you are making a service with the express interest in providing DB functionality directly to your customers/users. IE: If you are making a Database as a Service platform, similar to Mongo Atlas or AWS RDS. If you are just using mongo as a backend DB to fulfill some other internal requireme…

Arite, now the tally is even. I've heard the same number of people say to me that it's safe to use Mongo to power an app so long as I don't expose it, as have told me that I can't because I have to opensource all of my code that interacts with Mongo.

Euxodus is right. As long as you’re not building a product where the primary value of it is just delivering MongoDB as a service, you’re fine. There’s an FAQ that addresses that and more here https://www.mongodb.com/licensing/server-side-public-license...

Re: Quitting Dgraph Labs

#87

Post by nikolay »

lriuui0x0 wrote: post #84
nikolay wrote: post #79

Earlier quoted context omitted.

Actually, they are not that hard to kill if you know them well.

Cockroaches or CockroachDB?

I guess, both. Cockroaches are not so smart in the end, in fact, they often become victims of their powerful drives, which can be exploited for their own demise. I'm sure knowing the architect and behavior of the DB can be exploited in a similar way! I'm joking, of course.

Re: Quitting Dgraph Labs

#88

Post by darkcoderrises »

mrjn wrote: post #34
ctvo wrote: post #27

I've followed Dgraph off and on. I enjoy looking through their open sourced work. A lot of it is interesting. Manish seems to be THAT person. The technically competent, unwavering to the technical vision, doesn't work well with others person at your company. He went on to found a startup so he could do what he wants, and unfortunately has now realized board members are very similar to managers at Google. Here's a blo…

Manish here. I don't know who you are or what your motivations are. Glassdoor Reviews are anonymous (read trolls) and a lot of them were created post the layoffs, to create a story that would take the blame away from the hired CEO. Read between the lines about why the layoffs happened in the first place. If not, read this: https://www.glassdoor.com/Reviews/Employee-Review-Dgraph-Lab... When you have nothing to say ab…

Dude. I worked for you. You are that person. Your company didn't get built. It's a failure. Lol

Re: Quitting Dgraph Labs

#89

Post by darkcoderrises »

throw10920 wrote: post #38
ctvo wrote: post #27

I've followed Dgraph off and on. I enjoy looking through their open sourced work. A lot of it is interesting. Manish seems to be THAT person. The technically competent, unwavering to the technical vision, doesn't work well with others person at your company. He went on to found a startup so he could do what he wants, and unfortunately has now realized board members are very similar to managers at Google. Here's a blo…

If he is "THAT person" then why is the (rest of the) core Dgraph team also leaving and joining his new project?

Most people are not joining his new project. Source: I was part of the core team.

Re: Quitting Dgraph Labs

#90

Post by 2StepsOutOfLine »

metadat wrote: post #49
stevage wrote: post #6

Terrible new name though. Outcaste manages to both combine the negative associations of being a reject and the Indian caste system, and permanently remind users of the project's troubled history.

Is it really that bad? *cough* CockroachLabs / CockroachDB *cough*

Also, the company behind Traefik.

Containous.

It doesn't sound bad in your head, but then you say it out loud. (Yes even the CEO pronounces it that way in videos too)

Post reply on HN