Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Figma’s Journey to TypeScript

figma.com

Post reply on HN
Print view View original

151–160 of 257 posts

Re: Figma’s Journey to TypeScript

#151

Post by karaterobot »

croes wrote: post #85

Off topic: Does anyone know of any sites made with Figma so I can see what the UX is like? As a user I don't care about DX if the resulting UX is bad.

As mentioned, Figma is the de facto standard for UX design. Probably six or seven out of ten websites, apps, and desktop applications were designed on Figma, if they're relatively new. But Figma doesn't make sites, it's just a tool for designing them.

If you sign up for Figma, you can quickly get a sense of what it does. Some features are behind a paywall, but mostly things related to collaborating or managing large teams and design systems.

There are also approximately 1 billion Figma tutorial videos on Youtube that would show you the interface.

Re: Figma’s Journey to TypeScript

#152

Post by anamexis »

sod wrote: post #143
dimgl wrote: post #131

I like TypeScript and we have a full-stack system on TypeScript but it's not perfect. Configuring TypeScript for monorepos is a nightmare. Having to make sense of it with internal packages under a pnpm monorepo requires lots of manual tsconfig.json work to make all of the paths work with each other. And our production toolchain was basically unmaintainable until the excellent tsx package became available. It's also c…

Saying typescript is slow because zod is slow is like saying c++ is slow, because javascript is slow. Not to say that typescript is quick in any way (how could it be, as something written in javascript). But letting typescript execute code to infer types in a large scale application seems like a self inflicted issue.

What do you mean by that? I don't think Zod is doing anything special as far as the TS type system goes, although its types are necessarily complex to make its "magic" work. But it's not executing code to infer the types

Re: Figma’s Journey to TypeScript

#153

Post by alpinisme »

croes wrote: post #135
gryn wrote: post #109

Earlier quoted context omitted.

that's like asking if a pen or keyboard lead to bloat. depends on who's using them.

More like if AI leads to spam or if guns kill people. The latter one is harder if you only have a knife instead of an assault rifle.

No it’s more like, does vscode lead to better code than jetbrains? Figma doesn’t really provide meaningful constraints on a design that would let you identify it as Figma sourced, much as you won’t be able to tell whether a site was written in a particular IDE.

Re: Figma’s Journey to TypeScript

#154

Post by _dain_ »

quectophoton wrote: post #118
_dain_ wrote: post #81

Earlier quoted context omitted.

>I rarely see problems that are due to typing This is a fallacy similar to the Blub paradox: if your language has a weak[1] type system, then it isn't capable of recognizing many problems as "type error". But stronger type systems can express stronger invariants. So something that isn't a type error in one language will be a type error in another. This changes how the programmer conceives of problems. Example: missin…

Correct me if I'm wrong, but doesn't the Blub Paradox imply that languages dedicated to Code Golfing are at the pinnacle of expressiveness, and look down on everyone else's languages (for their extreme verbosity, compared to the golfing languages)?

No I don't think it's about compactness of expression, but rather what it's possible to express at all.

Re: Figma’s Journey to TypeScript

#155

Post by semireg »

hparadiz wrote: post #83
julik wrote: post #63

Earlier quoted context omitted.

It is actually a fairly indicative story. At the start there is a brilliant individual (Evan) who sets up an entire toolchain + core of the product. They then move on (or get pushed out, or get bored), and with the team (and the product) now being much bigger, things get replatformed to a more familiar, widely used stack. The success of these steps heavily depends on how robust the eng culture is at the organisation.…

It's ironic. For the past 5 years I've been writing type strict PHP. People love to shit on PHP yet I found that when I started using strict types my code quality improved, amount of lines needed to produce a result decreased, and necessary unit tests to produce the same result also decreased. Then a few months ago I decided to write a TS project from scratch. For the record I have 18 years of JavaScript experience.…

As a solo dev with a successful electron app I can say that the 5+ year journey from babel+flow+webpack to typescript+webpack, between two targets (main node and renderer chromium) not to mention native modules, node ABI, dual package jsons, electron itself as a giant shifting foundation… has been one of the most intimidating challenges in my dev career and I’m coming out the other side much stronger and confident. Props to everyone involved.

Re: Figma’s Journey to TypeScript

#156

Post by haolez »

mindfulmark wrote: post #60

It’s interesting to read comment threads of people that are dead set against Typescript. It’s a tool that has very few downsides and that improves nearly every single line of code you write. Either they’re scared to learn something new, not willing to take the time, or misunderstanding how useful it is. For anyone reading these comments and agreeing with Typescript naysayers, I would think more about why the commente…

It's not that it's bad. But sometimes the project and the team are not that big that its qualities matter. And you lose a little bit of readibility with type-intensive code.

And nicely written TypeScript looks awesome, but badly written TypeScript can be a huge mess, as it can with any language, but TypeScript purists sometimes forget that the language is just a part of a nicely written and designed system.

Re: Figma’s Journey to TypeScript

#157

Post by WuxiFingerHold »

dimgl wrote: post #131

I like TypeScript and we have a full-stack system on TypeScript but it's not perfect. Configuring TypeScript for monorepos is a nightmare. Having to make sense of it with internal packages under a pnpm monorepo requires lots of manual tsconfig.json work to make all of the paths work with each other. And our production toolchain was basically unmaintainable until the excellent tsx package became available. It's also c…

Zod is known to be slow. Typebox for example is much faster - not saying you should switch, but that it's not a Typescript issue or something that needs to be addressed by Typescript.

Your monorepo issues sound like you didn't use the same config in all the packages? If that's the case, enforcing the same config and coding standards would be the first thing I would fix. Again, not a Typescript issue. Or did you use ts-node before tsx? Yeah, tsx is much more robust. It just works.

Re: Figma’s Journey to TypeScript

#158

Post by tambourine_man »

salomonk_mur wrote: post #130
tambourine_man wrote: post #127

>… TypeScript, the industry standard language for the web This breaks my heart.

Why? It's the truth.

The frontend language for the web is JavaScript.

People who don’t like JavaScript but, for whatever reason, still want to write frontend apps have chosen to invent a new language that transpiles to it. To call that effort a standard is heartbreaking to me.

Re: Figma’s Journey to TypeScript

#159

Post by gedy »

8n4vidtmkvmk wrote: post #21
jumploops wrote: post #13

Earlier quoted context omitted.

They started with the goal of photoshop in the browser.

Photopea is great and replaced my need for PS. I only do light weed editing though

> light weed editing

Sounds like getting stoned and making a meme or something

Re: Figma’s Journey to TypeScript

#160

Post by iampims »

hparadiz wrote: post #86
59nadir wrote: post #53

Earlier quoted context omitted.

Meh, as far as I can see PHP has a ton of very active development around web services and frameworks, which is its core value proposition. PHP as a language should probably slow down in general but the people who use it don't seem to be really dying out or slowing down as much as the bubble leads us to believe.

People hate php for no reason. They talk about performance or whatever while building rest crud apps. Literally any language can handle that easily and your bottleneck is usually the database. I've scaled startups on PHP to hundreds of thousands of users running on a few cheap ec2 instances. But no one wants to build new php projects instead focusing on Go, Python, or Ruby. I honestly don't get it. PHP devs earn less…

The best thing about PHP: shared nothing architecture.

The worst thing about PHP: shared nothing architecture.

It works extremely well until it doesn’t really scale anymore.

Post reply on HN