52 karma · joined November 13, 2017
You shouldn't believe in this. This is fact.
> even during weekends/free-time
It sounds illegal. In the US, you can really specify such clause in the contract?
What are the benefits of it? What git did not please?
Just stop using it. Use gRPC. It's binary -> faster. It's support TypeScript -> type safely. Type safety is a complex thing. If there is a type-safe instrument instead of type-unsafe, you should use it.
>If you have good integration tests, you don't need to explicitly check for types in JavaScript
It works only in the perfect world, where tests are always relevant and tests all cases. But we live in the imperfect world. With people, which may forget to update tests/documentation/etc. and things in something like JS still will works. But in the type-safe world things are different. If you forgot to add or deleted some fields - it'll break. If you pass wrong type - it'll break. Type is a test, that always actual.
What's the reason to write tests for things, that just should works? You shouldn't think about tests like "What error does it throw if I pass that type?" With type checking you just won't have that type of issues.
But it is.
Hype oriented programming as it is.
Nobody uses Rust in production. Why such thoughts in general?
But he still needs to know what they are talking about.
>ten seconds to load your inbox
>16 GB, i7, SSD, 100 MB/s internet etc.
>fine
This is the most effective way to consume content. It's not dead and won't be until more effective one.
No, it's damn hard.