Earlier quoted context omitted.
As a former figma engineer, let me be the first to say that Evan Wallace is, in fact, a legend. A true 100x-er. There's still parts of the codebase basically no one at Figma really understands that Evan wrote back in the day. One example of that is something like he adapted a shader we use internally to render font glyphs, which no one has touched ever since. The engineer who told me this had spent a few days trying…
I don’t know anything about shaders and this is not personal against Evan, but if someone wrotes code that nobody understands, isn’t it bad thing and not good thing? I thought similarly (admired) many years ago, that those people are wizards and that is cool, but the older I get, less I think so. You often can write the same thing so that it is also easier for others to understand. In most cases, when we talk about c…
Figma files for proposed IPO
81–90 of 255 posts
Re: Figma files for proposed IPO
#82They don't link to the Form S-1 prospectus from their announcement, but it's publicly available at https://www.sec.gov/Archives/edgar/data/1579878/000162828025... Their highlighted metrics page: $821M LTM revenue, 46% YoY revenue growth, 18% non-GAAP operating margin, 91% gross margin. It's an incredible success story, and the engineering they did upfront (primarily led by co-founder Evan Wallace) that set the stage…
As a former figma engineer, let me be the first to say that Evan Wallace is, in fact, a legend. A true 100x-er. There's still parts of the codebase basically no one at Figma really understands that Evan wrote back in the day. One example of that is something like he adapted a shader we use internally to render font glyphs, which no one has touched ever since. The engineer who told me this had spent a few days trying…
I worked extensively in the parts of the Figma where Evan wrote a lot of foundational code, and have also worked directly with him on building the plugin API.
One of Evan's strong points as a CTO is that he was very pragmatic and that was reflected in his code. Things that could be simple were simple, things that needed complexity did not shy away from it.
While all codebases have early decisions that later get changed, I'd say that largely speaking, Figma's editor codebase was built upon foundations that stood the test of time. This includes choices such as the APIs used to build product code, interact with multiplayer, the balance between using OOP v.s. more functional or JS-like patterns, the balance between writing code in C++/WASM v.s. JS, etc. Many of these choices can be credited to Evan directly or his influence.
Subsequent engineers that joined were able to build upon the product without causing a spiraling mess of complexity thanks to those good decisions made early on. In my opinion, this is why Figma was able to ship complex new features without being bogged down by exploding tech debt, and a major contributing factor to the business's success as a whole.
Re: Figma files for proposed IPO
#83Earlier quoted context omitted.
Is this alignment the issue with your application? Are there design alternatives that would be impacted less by some rendering engine differences? What about other browsers? Versions? Platforms? OS? Resolution/screen size? My huge frontend team can't handle this, even before we used Figma. Isn't the problem trying to get this "web platform" do something it was never meant to do? How would this be solved by Figma usin…
I've been fighting the way figma interprets fonts for years. It's not too bad at my current company, but at my last company things would look great in figma but with the exact same styles applied they'd be wrong in every browser. That's the sort of thing people are complaining about here. I'm sure there's something fundamentally wrong with the font files. In both cases, they're not standard, widely available fonts. W…
Re: Figma files for proposed IPO
#84Earlier quoted context omitted.
As a former figma engineer, let me be the first to say that Evan Wallace is, in fact, a legend. A true 100x-er. There's still parts of the codebase basically no one at Figma really understands that Evan wrote back in the day. One example of that is something like he adapted a shader we use internally to render font glyphs, which no one has touched ever since. The engineer who told me this had spent a few days trying…
I don’t mean this to throw shade, but isn’t the whole point of writing code that someone else can understand it? I worked with some crazy smart people when I was in academia, and when one of them left it was not worth trying to maintain what they left behind because it was so often inscrutable.
Re: Figma files for proposed IPO
#85Re: Figma files for proposed IPO
#86Is this an IPO where participants (public) will make long term money of it’s already at the top and this is the final stage of “finding someone to hold the bag” and in this case eventually — the public i.e the retail trader, mostly?
Re: Figma files for proposed IPO
#87Earlier quoted context omitted.
As a former figma engineer, let me be the first to say that Evan Wallace is, in fact, a legend. A true 100x-er. There's still parts of the codebase basically no one at Figma really understands that Evan wrote back in the day. One example of that is something like he adapted a shader we use internally to render font glyphs, which no one has touched ever since. The engineer who told me this had spent a few days trying…
I don’t mean this to throw shade, but isn’t the whole point of writing code that someone else can understand it? I worked with some crazy smart people when I was in academia, and when one of them left it was not worth trying to maintain what they left behind because it was so often inscrutable.
Any code that involves parsing old school binary file formats is going to look ugly to modern day developers who are used to JSON everything, even if the code is actually very well structured.
Re: Figma files for proposed IPO
#88They don't link to the Form S-1 prospectus from their announcement, but it's publicly available at https://www.sec.gov/Archives/edgar/data/1579878/000162828025... Their highlighted metrics page: $821M LTM revenue, 46% YoY revenue growth, 18% non-GAAP operating margin, 91% gross margin. It's an incredible success story, and the engineering they did upfront (primarily led by co-founder Evan Wallace) that set the stage…
I was one of their first Enterprise customers way back in 2017’ish-give-or-take. The brilliance of the system he built was that it allowed for real time collaboration. Which was god send from the Sketch -> Zeplin -> Invision -> Avocode (version management) ‘stack’ that lost Enterprise design orgs were using. Which was already a large leap from what Adobe was expecting us to do with Photoshop/Illustrator (after they d…
> It wasn’t lost on us that Sketch is/was much much smoother with its usage of Mac OS’s native shape rendering. It’s just that the benefits far outweighed the small drop in snappiness.
yep, even though i personally prefer sketch, if i was running a company i'd most likely go with figma as well because of the collaborative capabilities; its just a huge productivity boost for collaborative teamsRe: Figma files for proposed IPO
#89There's a president-for-life clause: "Immediately following the completion of this offering, and assuming no exercise of the underwriters’ over-allotment option, Dylan Field, our Chair of our Board of Directors, Chief Executive Officer, and President will hold or have the ability to control approximately % of the voting power of our outstanding capital stock, including % of the voting power pursuant to the Wallace Pr…
That generally makes me more inclined to invest as I find that the biggest problem with a lot of public companies is they manage to Wall Street which means putting the short term over the long term, and those are often at odds with each other.
There's a good reason public shareholders historically demanded accountability - maybe it's fine for now, but all it takes is some management that you can't kick out, paying themselves extortionate salaries and driving the company into the ground at the same time to recognise the problems with "owning" a company you have no right to actually control (via replacing management and so on)
Re: Figma files for proposed IPO
#90[flagged]
Figma's enshittification started back when there were talks of Adobe taking over, it's already bloated beyond reason.