dventimihasura

10 ms·

31.
by dventimihasura 3y ago
Did you forget the link?
32.
by dventimihasura 3y ago
An enterprise company is a large company that's not a tech company: banks, health care, finance, manufacturing, retail, etc. The proverbial "FAANG" companies are not enterprise. Netflix is not enterprise. Walmart is. As for D
33.
by dventimihasura 3y ago
Wait...is it "almost 15 years" or "only 15 years"? Is node old and established or is it still the plucky upstart?
34.
by dventimihasura 3y ago
Interesting. Yeah, I also found Prisma to be a bit heavyweight. Postgraphile is nice, though. I wish it went beyond postgres.
35.
by dventimihasura 3y ago
At your startup, why did you choose Strawberry over, say, Prisma?
36.
by dventimihasura 3y ago
That may very well be a valid reason why people should build backends in node. But, people don't often listen to reason.
37.
by dventimihasura 3y ago
Are they more common, or less common, than Django and RoR?
38.
by dventimihasura 3y ago
sequelize seems to be much more popular than slonik. Is sequelize more or less the standard or at least market leader? https://trends.google.com/trends/explore?date=all&geo=US&q=S...
39.
by dventimihasura 3y ago
I'm not talking about the developers. I'm sure they're wonderful people. I'm talking about the organizations. I don't believe node has been as popular for backends in the last 15 years, especially at enterprise comp
40.
by dventimihasura 3y ago
I highly doubt it because I was talking about enterprise companies. I honestly have no idea how common node is in general, including other organizations, but when it comes to enterprise companies, I do have an idea. My idea is that node isn
41.
by dventimihasura 3y ago
I'm curious about that ecosystem, especially with regard to databased. I asked this elsewhere, but what're the main libraries for database access?
42.
by dventimihasura 3y ago
Well, I'm pretty sure I didn't say that nobody wrote node backends.
43.
by dventimihasura 3y ago
I could be wrong. That's one thing I'm trying to figure out. Setting that aside, like I said I don't really know that community, being mostly a Java developer. What're the go to database libraries? Is it sequelize, or so
44.
by dventimihasura 3y ago
> There are maaaany backends written in JavaScript (nodejs) Are there? I honestly don't know. I feel like it depends on how you count them. Are there JS/TS/nodejs "Backends For Frontends" (BFFs)? Yeah, I c
45.
by dventimihasura 3y ago
This is great, and I mean no disrespect, but aren't most servers written in anything but TypeScript? Java, Python, Ruby, .Net, Go, etc.? I recognize that changing it from "most servers" to "most GraphQL servers"
46.
by dventimihasura 3y ago
Hey, folks. I'm posting a blog article I wrote for my employer, Hasura. Sure sure, it's a bit of marketing, but honestly it's mostly an attempt to "start a conversation" as they say. I mean no disrespect, but in
47.
Building a GraphQL server with Netflix DGS: An unfiltered review(hasura.io)
1 points by dventimihasura 3y ago|1 comments
48.
by dventimihasura 3y ago
> your questions phrasing assumed that the person you responded to felt the same way about how quotation marks should be used. Questions don't assume things. People do. > The comment quite literally calls something wrong (&qu
49.
by dventimihasura 3y ago
It may be common, but that doesn't mean it's warranted. Logical fallacies, for example, are also common (so are spelling and grammar mistakes), and yet personally I prefer to commit them less often rather than more often. You th
50.
by dventimihasura 3y ago
> Making comments like "this is wrong, but I'm not gonna explain why" has no place here, imho. Who are you quoting?
51.
by dventimihasura 3y ago
Has anyone else used Netflix DGS outside of Netflix to build GraphQL servers? I'm wondering what the experience was like. Full disclosure: I work at a GraphQL company. But still, I'm genuinely curious. I was a longtime back-e
52.
by dventimihasura 3y ago
Jesus, and now you're erasing your tracks by deleting your comments, and those of other people along with it, like you just did in this sub-thread.
53.
by dventimihasura 3y ago
> This has been covered several times No, this has been covered exactly once. I asked 4 hours ago in this sub-thread this question, but you didn't answer it. I also asked again 3 hours ago in this sub-thread. I also asked a rel
54.
by dventimihasura 3y ago
> We don't need to know the author's definition. That was deferred to Kay We don't know that it was deferred to Kay. You just assumed that it was. > To which I asked: "Says who? You? Did you get a confirmation
55.
by dventimihasura 3y ago
> Increases. After all, the remainder is about how people do not understand OOP. The author says this about "subtyping" and "inheritance", terms that do not appear in Kay's definition at the top: Another term
56.
by dventimihasura 3y ago
> First thing you read. That's where definitions go. Says who? You? Did you get a confirmation from the article author that this was their intention? After all, the first thing you read in the article is a quote, but then there
57.
by dventimihasura 3y ago
> Which is why we are sticking to the definition as has been already defined. Has already been defined where exactly? Yes, evidently you believe it has been defined in the article, but where exactly in the article did that occur. Ple
58.
by dventimihasura 3y ago
> Let's break this down. As defined by context, OOP means: messaging, local retention and protection and hiding of state-process, and extreme late-binding of all things. Indeed, there exist other OOP definitions, but that is the on
59.
by dventimihasura 3y ago
You're free to use your own private definition of OOP, but nobody else is obliged to join you.
60.
by dventimihasura 3y ago
> Happy to, but it is not clear what I should study. You have not yet indicated what it is about OOP that you are talking about. I don't have to. That's already explained in the standard literature on the topics of the objec

More ›