primitives VS TypeScript

Fast forward to a week ago, I cloned the Reach UI and Radix UI codebase and started exploring. Large codebases are always difficult to comprehend. With some digging around and reverse engineering, I was able to create the first component listed in the Reach UI docs, the Accordion.

Hi HN! I'm Vlad, a designer and engineer on the Radix team (https://radix-ui.com). We just launched Radix Themes, an open source component library for building modern, accessible React apps.

Radix Themes is built on top of Radix Primitives (https://radix-ui.com/primitives), which companies like Vercel, CodeSandbox, and Supabase, among others, already use to power their interfaces.

Our goal is to help you focus on your product and build it faster instead of re-inventing common designs and working on the UI components over and over.

Under the hood, Radix Themes is built with TypeScript, React and vanilla CSS. All design tokens are CSS variables that you can tweak, overwrite, or use to build your own custom components with any styling solution that you like.

The idea to build Radix Themes emerged while working on our own design system at WorkOS (https://workos.com), which is the company behind Radix. There was hundreds of design details and edge cases that we had to take care of, so it still didn't feel like a solved problem.

We also were obsessed with getting the developer experience right. For every component we asked ourselves—what is the right API? What are the right props and parts? What should, and more importantly, shouldn’t be a part of this component? What API would make the code easy to understand and maintain, and what would put you into a messy situation that could bite when you don’t expect it?

With this approach, we used our own, battle-tested components that serve our paying users to kickstart Radix Themes.

I hope that you find Radix Themes useful. Right now, there’s 45 components, hundreds of carefully crafted variants, a few simple and powerful primitives for layout, and an extensive token system.

I would love to hear your feedback on our work and learn about your experiences with building UIs.

Other things that led me to choose this path were: Most libraries that are ports, official or not, use the original name (e.g. Svelte Material UI); Radix UI's license is fairly permissive (https://github.com/radix-ui/primitives/blob/main/LICENSE), which is why I also don't think it matters that it's a company behind it. Same as why I don't see an issue with the name Preact, for example.

For a react project I recommend https://radix-ui.com, it's got pretty good defaults

radix-ui.com

This is really cool, Radix UI uses a similar hook internally for their components. I like your implementation though.

Remix is a dream. Once combined with Radix Form Component it'll be freaking heaven. https://github.com/radix-ui/primitives/blob/form-rfc/rfcs/2023-radix-form-primitive.md

Looks like radix-ui.com, but a bit more boring tbh

While we were fighting against the modules, we forgot one small detail - their built-in typings. Esbuild can't do this at all yet. Unbelievable, but the tsc, native TS compiler, also does not provide a typings concat feature. Got around this problem: we've introduced [a utility to combine typings](tsc-dts-fix of zx own code, and applied some monkey patches for external libdefs squashed via dts-bundle-generator.

Regular expressions are part of the language, so it's not so unreasonable that TypeScript should parse them and take their semantics into account. Indeed, TypeScript 5.5 will include [new support for syntax checking of regular expressions](https://github.com/microsoft/TypeScript/pull/55600), and presumably they'll eventually be able to solve the problem the GP highlighted on top of those foundations.

Dedicated syntax for creating unique subsets of a type that denote a particular refinement is a longstanding ask[2] - and very useful, we've experimented with implementations.[3]

I don't think it has any relation to runtime type checking at all. It's refinement types, [4] or newtypes[5] depending on the details and how you shape it.

[1] https://github.com/microsoft/TypeScript/blob/main/src/compil...

GitHub | Website

Learning Curve and Developer Tooling sCrypt is an embedded Domain Specific Language (eDSL) based on TypeScript. It is strictly a subset of TypeScript, so all sCrypt code is valid TypeScript. TypeScript is chosen as the host language because it provides an easy, familiar language (JavaScript), but with type safety. There’s an abundance of learning materials available for TypeScript and thus sCrypt, including online tutorials, courses, documentation, and community support. This makes it relatively easy for beginners to start learning. It also has a vast ecosystem with numerous libraries and frameworks (e.g., React, Angular, Vue) that can simplify development and integration with Web2 applications.

As a JavaScript or TypeScript developer, you might have come across the terms type and interface when working with complex data structures or defining custom types. While both serve similar purposes, they have distinct characteristics that influence when to use them. In this blog post, we'll delve into the differences between types and interfaces in TypeScript, providing examples to aid your understanding.

TypeScript helps you in many ways in the context of a JavaScript app. It makes it easier to consume interfaces of any type.

In this guide, we'll be extracting information from Amazon product pages using the power of TypeScript in combination with the Cheerio and Crawlee libraries. We'll explore how to retrieve and extract detailed product data such as titles, prices, image URLs, and more from Amazon's vast marketplace. We'll also discuss handling potential blocking issues that may arise during the scraping process.

TypeScript