lyxsus
No user record in our sample, but lyxsus has activity below (stories or comments). Likely we have partial data — the full bulk-load will fill profiles in.
No user record in our sample, but lyxsus has activity below (stories or comments). Likely we have partial data — the full bulk-load will fill profiles in.
Why not? It may be stupid, but I'm buying it if material feels right to my skin.
Location: Buenos Aires, Argentina Remote: Yes Willing to relocate: Depends Technologies: JavaScript/TypeScript, NodeJS, React, Graphl, Relay, Apollo, Nextjs, Python, Postgres, Mongodb, Couchdb, Dynamodb and etc and etc.…
This is incredible. I really want it to take off.
omg. ok, adopting some F features is an interesting idea. but why are they trying to make that thing with syntax happen?
Oh, I would like to see a look on your face when just in about 100-200 years from now it will be mature enough for a "web scale".
Understood, thank you. Yes, that's not solvable with just OWL (though it might help a little) or any other popular reasoners I know. There're papers, proposals and experimental implementations for generating…
so if it tries to have a unified ontology that's why it's destined to fail, but if it's designed to working with many small ontologies… that's why it will fail! lol, but you can't have it both ways. In SW, the…
There're a lot of wrong perspectives on the topic in this thread, but this one I like the most. When someone starts to talk about "agreeing on a single schema/ontology" it's a solid indicator that that someone needs to…
Isn’t it similar to linear types in haskell?
We’re not, but your point is still valid.
Location: Saint-Petersburg, Russia Remote: Yes Willing to relocate: Yes Technologies: Javascript/TypeScript, React (Relay/Redux/Apollo), Postgresql/Mysql/NoSQLs, K8S, Python Résumé/CV:…
As a non-US citizen, I have 3 questions: 1. WTF 2. Is it even enforceable? 3. Does anybody know recent examples?
I would say use XML Schema at least. DTD looks alien to XML anyway.
It doesn't affect data model encoded in document even a tiny bit. Namespace prefixes are irrelevant. If changing these prefixes breaks the program, the program is incorrect.
> This breaks people's mental models of how XML works, and correspondingly, breaks people's code that manipulates XML. Because they usually have incorrect mental model. Blaming namespaces for name ambiguity would be the…
Sure, but what’s the end goal here? I just don’t get what prevents the history to repeat itself if it lifts off. And considering current web, which of these problems are technically unsolvable at the moment? We can have…
Why?
Why don’t you just quote the word “by”? I agree with the word “by”. I fully support it and appreciate how precise and representative it is with respect to the topic. Thank you for walking that path with me, I am…
In general. In general what? You can't take an advantage of having an abundant amount of data about data sources, schema and query you're about to execute (in general)? The original example simply illustrates that if…
Amazing. Original comment I've reacted to: > Yeah, right. Because that SQL query will just magically write itself. Oh, just did, sorry > Especially if that ad-hoc GraphQL query requests extra fields Just did, whoops…
Ok, so you've failed to provide an example, I'll make you a big favour just this time. > If you need to get user, then 5 of his posts, then 50 of comments for each post That was the original database structure, right?…
No, because then I won't get anything from this conversation. Please, tell me, what else can I say to make you use a practical illustration of your position constructed on top of original example? I believe it's the…
So you gave me an example of a nested query that is not infinitely recursive and even admitted it. The one that as I said before you have an ability to easily identify before execution, just as any possible variations…
Ping me when you’ll be able to show infinitely recursive query in graphql. Until that, I agree, there’s no point to continue, and have a good luck with that :)))
If you’re a backend developer, it’s just more work to do, unless you really make use of gql abstractions, they’re kind of more expressive than raw rest. For clients - instant exploitability, type safety, much more…