Bookmarking Adidas API guidelines by @zdne as an excellent starting point (even though I do have some disagreements) github.com/adidas-group/api-…
1
24
1
73
I see lots of people move to Angular or React from Swing or RCP apps, bypassing classical web development without knowing the tradeoffs
2
1
Agreed, the fragment is treated on the client, that’s clearly different. But query or matrix params or path elements … all the same to me
1
“Unfortunately, it's a feature we often engineer-away with single page apps” jakearchibald.com/2017/netfl… – Great post by @jaffathecake
7
10
I speak at a lot of conferences, sometimes for free, sometimes for money, and I completely agree. nitter.vloup.ch/aphyr/status/925…
1
7
1
32
Its existence is inevitable, so my guess is you push against formalizing and checking it. I tend to agree, for most use cases
2
The problem I have is with metadata that describes an ideal that may be (and will be) out of sync with reality
1
Then I’d argue it suffers from the IDL problem, too, unless checks are completely local to each participant in definition and implementation
1
Interesting, so you’re considering them for the distributed app’s state as a whole, not as internal to e.g. the server?
1
We sponsored and helped create EnhanceConf in London a while ago. Happy to do something similar again
2
Noch nicht, ist aber in Planung. Bis dahin hilft vielleicht das Transkript? innoq.com/de/podcast/035-mit…
1