317 karma · joined December 29, 2016
The Soviet Union doesn't have statistics on this because Soviet Union doesn't exist.
Apple is arguing as if accessing their platform for free was a crime. This makes sense, since they have costs associated with reviews, code signing and distribution. But that is of their own making. Walled gardens should be outlawed.
Yeah you don't want an object oriented kid.
(I'm going to treat checked exceptions same as unchecked, because you don't _have to_ use checked or they can be trivially broken by using the Exception superclass)
At the beginning you often take shortcuts and ignore error handling in order to get the happy path to work. Once it is working, it is very easy to overlook some exceptions that should be handled, leading to unexpected runtime errors.
Using the Result monad (say in Rust), you can easily just add .unwrap() after any call that produces a Result to get the happy path working. After you're done with that, its easy to find all the places you took shortcuts and fix them.
To me, the ergonomics of a language is exactly this gap between how concise the "take all the shortcuts" code is and how easy it is to transform into production code where all the possible error states are properly accounted for.
SOAP is essentially the same as REST -- you have request/response for every resource. Its just more verbose and inscrutable thanks to XML and all the schemas.
GraphQL on the other hand enables new interactions that were not possible or practical with either of the two.
Sure, if you try to shoehorn an API that does not fit the database, it can be challenging, but you can always start with the simple case, doing multiple queries to the DB for one GraphQL request and only later see what is actually used and could benefit from optimizing.
You have more opportunities to optimize. With REST, if a client needs to list some resource and then access all of them one by one, it is going to be n+1 requests and you can't do anything on the back end to change that. With GraphQL you can look at the query holistically and optimize as needed.
All in all it feels to me that GraphQL gives the client the ability to better communicate the intent of what they are trying to do. Declarative over imperative.
1) Either they can't describe what they are doing (bad, how do you find customers then?) 2) Or they do anything and everything (worse, if there is no goal, there can be no drive)
I want my work to mean something. I want to be able to say things like: "I help people to book taxis in an accountable way" (Uber)
Some people from Jetbrains have looked into it and concluded it was the font rendering in IDEA bringing down the entire system.
Do you think this change can improve this? Because it certainly sounds like it.
In most of EU you never swipe. I have swiped maybe 2x in my life and only because the chip did not work. (The swipe then did not work either...) You either use chip/pin or contactless and pin over 20eur
I understood the point that it may be an overkill for static binary deployments, but how is that dangerous?