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

211–220 of 257 posts

Re: Figma’s Journey to TypeScript

#211

Post by summerlight »

makeitdouble wrote: post #7
resonious wrote: post #2

Surprising to hear Figma had a custom language for JS. Even more surprising that it was faster than TS. And then they migrate off it onto slower TS! Seems to happen a lot though. Company makes custom stuff early on, gets big, then migrates to something "standard".

It happened in the PHP community as well, facebook being the poster child, but Yahoo also had a fair number of internal optimizations and I saw a few other companies tweak their way to get better perf/security. Then comes a point where the community catches on and has bigger momentum than the company, so it makes sense to move to the standard implementation. I'd kinda see Google's Borg -> k8s move as slightly similar…

k8s is not allowed to use in the most projects utilizing the internal stack, at least yet. In fact, it hasn't reached to the feature parity level necessary to replace any big projects running on Borg.

Re: Figma’s Journey to TypeScript

#212

Post by CuriouslyC »

CharlesW wrote: post #170
CuriouslyC wrote: post #107

Earlier quoted context omitted.

Remix. Vite done right, mostly pre-configured out of the box.

> Remix. Vite done right… Remix is moving to Vite as its default compiler. https://remix.run/docs/en/main/guides/vite

I'm aware, I've been on the experimental vite branch for a while. It is literally "vite, done right"

Re: Figma’s Journey to TypeScript

#213

Post by CuriouslyC »

WuxiFingerHold wrote: post #171
CuriouslyC wrote: post #107

Earlier quoted context omitted.

Remix. Vite done right, mostly pre-configured out of the box.

Vue, Nuxt or Svelte are even better. No need to waste time and energy with React and it's peculiarities. However, if you want or must React, then Remix, hands down.

While I very much like svelte, it's not fully mature yet and it doesn't have a very deep ecosystem, plus the additional hiring time/cost basically means building anything other than a small scale solo project with it is going to end you up in the red.

On the Vue vs React debate, honestly it comes down to preferring templates vs components. Vue is simpler but there are good reasons for a lot of the React complexity, and React still has a stronger ecosystem and more developers.

Re: Figma’s Journey to TypeScript

#214

Post by CuriouslyC »

biinjo wrote: post #189
CuriouslyC wrote: post #106

Earlier quoted context omitted.

This is the reason that JS frameworks are a thing. Next is buggy and overbuilt, but Remix is pretty much plug and play, I strongly recommend checking it out.

Im surprised that Remix doesn’t get much love in the community. Or is it because Vercel and their influencer team is yelling so loud about Next that we can’t hear the Remix people?

I feel like Remix is rising pretty fast. The death of create-react-app has pushed people to frameworks and Next (while loudly marketed by Vercel) feels overweight and underpolished for people who just want something that focuses on the most common use cases with minimal setup / fiddling where remix shines.

Re: Figma’s Journey to TypeScript

#215

Post by vbezhenar »

summerlight wrote: post #211
makeitdouble wrote: post #7

Earlier quoted context omitted.

It happened in the PHP community as well, facebook being the poster child, but Yahoo also had a fair number of internal optimizations and I saw a few other companies tweak their way to get better perf/security. Then comes a point where the community catches on and has bigger momentum than the company, so it makes sense to move to the standard implementation. I'd kinda see Google's Borg -> k8s move as slightly similar…

k8s is not allowed to use in the most projects utilizing the internal stack, at least yet. In fact, it hasn't reached to the feature parity level necessary to replace any big projects running on Borg.

If other companies can run big projects on Kubernetes, so can Google.

Re: Figma’s Journey to TypeScript

#216

Post by phyrex »

makeitdouble wrote: post #93
the_duke wrote: post #37

Earlier quoted context omitted.

Isn't FB/Meta still on Hack + HVVM?

They are. At this point it's a completely different language with its own stack, as far as I know that will be a core component for the forseable future. Now they also have modern PHP and some other languages alongside with hack from what I understand.

I don’t think there’s any vanilla php in use at meta

Re: Figma’s Journey to TypeScript

#217

Post by steveklabnik »

iainmerrick wrote: post #204
eddd-ddde wrote: post #176

Earlier quoted context omitted.

Duck typing can lead to a false sense of security when you /think/ you have Foo when in reality you have Bar with the same shape. Also Typescript sucks at keeping track of type changes in a single scope. While in Rust I can assign string to foo and then update it with int, I can't in Typescript. This leads to worse types or worse code for the same operation. Combined with typescript's lack of statements as values, co…

While in Rust I can assign string to foo and then update it with int When do you need to do that? Can you give an example?

I suspect they're talking about shadowing. You can't change the type of an existing variable, but you can create a new variable with the same name but a different type.

Re: Figma’s Journey to TypeScript

#218

Post by csomar »

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.…

You want to do a lot but you don't want to pay for it. There is a shit ton of complexity on the web and the current frameworks (ie: NextJS/React/TypeScript) try to hide/manage this complexity but this only goes so far.

As soon as you hit an edge outside of their matrix of management you open the dark Pandora box of front-end development.

Re: Figma’s Journey to TypeScript

#219

Post by csomar »

cageface wrote: post #92
hparadiz wrote: post #83

Earlier quoted context omitted.

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.…

Never start with Webpack. Use Vite with a template and go from there.

I'd make the exact opposite suggestion: Always use WebPack. There will be a package in the future that has a particular WebPack configuration to make; and you don't want to figure out how to do that in another bundler.
Post reply on HN