ewittern

6 ms·

1.
by ewittern 4y ago
Cool stuff, congrats on the launch! I am excited to learn about the details for complexity-based rate limits, as there are quite a few design considerations involved. For example, how to configure which (numeric) arguments in a GraphQL quer
2.
by ewittern 4y ago
We did research on solving the DOS issue using static analysis at IBM (cf. https://arxiv.org/pdf/2009.05632.pdf ). Our findings were that static analysis allows to determine (relatively strict) upper bounds on query com
3.
by ewittern 5y ago
In that regard, they are taking the language‘s name way too serious.
4.
by ewittern 8y ago
Principle 8 mentions "demand control", including "estimating the cost of a query before performing it". This is very much in line with GraphQL API Management work we are doing at IBM Research. I recently wrote about this
5.
by ewittern 8y ago
There are a few libraries that calculate complexity or cost of a GraphQL query, e.g., [1][2]. We think that differences of our approach are that we extract more diverse characteristics, allowing for a wider array of management policies, and
6.
by ewittern 10y ago
Hi Sean, there are two things: API Harmony is a research prototype we develop here at IBM Research. Using it, we explore things like mining API specifications, static code analysis of web API requests, or API recommendation. Some of this re
7.
by ewittern 10y ago
We are working on a IBM "catalog" at IBM Research called API Harmony: https://apiharmony-open.mybluemix.net/ One of our goals is to mine information about APIs, rather than relying on user input (hence the "c
8.
by ewittern 10y ago
Everything is relative. Like 60 lines of code (especially as compared to a single one). Or humor.
9.
by ewittern 10y ago
Shameless plug, I know, but I bet Inferno doesn't come close to my latest framework when it comes to the notorious task of writing a TODO app: https://github.com/ErikWittern/TODOit
10.
by ewittern 10y ago
In theory I agree, but TODOit is perfect, unfortunately.
11.
by ewittern 10y ago
Damn. The launch party was already in full swing when I hit the commit button, and so I missed this mistake...
12.
by ewittern 10y ago
Author here. If you have any questions, please go ahead and ask them either here or by filing issues.
13.
Hassle-free TODO application development(github.com)
27 points by ewittern 10y ago|6 comments
14.
by ewittern 10y ago
Mixing code with documentation is one concern. Another issue is that extracting the information needed to create a Swagger from source code is hard, especially when using dynamic languages (JavaScript, Python). One approach is to use dedica
15.
by ewittern 10y ago
What were the reasons people brought up against doing this?
16.
by ewittern 10y ago
Cool projects, thanks for pointing them out! So, the scrape-html-to Swagger one would basically allow you to keep Swagger up to date as you change the human-readable API documentation? In that case, someone still has to make sure the API do
17.
by ewittern 10y ago
What do you think about automatic generation of client-code in various languages? With regards to the bugs, were they a result of the implementation and the specification getting out of sync? Would automatic means for creating / mainta
18.
by ewittern 10y ago
Hi, the author here. I think its a good point you make. However, I believe being based on JSON or YAML, many of the specification formats provide at least some degree of readability. Also, one idea of them is to provide the basis for creati