Our great sponsors
-
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
TypeScript type system is Turing complete which means it can implement any logic, for example, computing Fibonacci sequence. Does that mean your types need to be that complex? I don’t think so.
My impression is that TypeScript’s complexity is caused by JS libs created years before TS got popular — Lodash, Ramda, Redux, and many many more. These libs were designed without keeping static types in mind, that’s why their typings, created afterwards, are very challenging to understand. Good code is a code easy to read — that’s why you’d better keep your types simple.
My impression is that TypeScript’s complexity is caused by JS libs created years before TS got popular — Lodash, Ramda, Redux, and many many more. These libs were designed without keeping static types in mind, that’s why their typings, created afterwards, are very challenging to understand. Good code is a code easy to read — that’s why you’d better keep your types simple.
My impression is that TypeScript’s complexity is caused by JS libs created years before TS got popular — Lodash, Ramda, Redux, and many many more. These libs were designed without keeping static types in mind, that’s why their typings, created afterwards, are very challenging to understand. Good code is a code easy to read — that’s why you’d better keep your types simple.
My impression is that TypeScript’s complexity is caused by JS libs created years before TS got popular — Lodash, Ramda, Redux, and many many more. These libs were designed without keeping static types in mind, that’s why their typings, created afterwards, are very challenging to understand. Good code is a code easy to read — that’s why you’d better keep your types simple.
Related posts
- I created a CLI tool that writes unit tests with GPT-4 (with one command, I created tests for Lodash repo with 90% code coverage and found 13 bugs)
- FP and JavaScript/TypeScript
- Show HN: ModernDash – A TypeScript-First utility library inspired by Lodash
- ModernDash – A TypeScript-First utility library inspired by Lodash
- ModernDash | A Typescript-First utility library inspired by Lodash. Optimized for modern browsers.