31–40 of 120 posts
My hypothesis is that unlike other mediums like paper or video, the elastic nature of the web makes understanding the positioning paradigms/box model/etc a necessity that no visual tool can really abstract. By the time you understand all that, it's just faster to write and maintain code.
Earlier quoted context omitted.
I think you missed the gist? They are saying if you are saying "this piece needs to be more performant" you need to measure that first, before making your choice of what to make better. You are saying, "you can with an idea in mind optimize before you go and it will have better performance" but the current prevailing business logic is do not optimize until you know it's "the right thing". AKA premature optimization i…
I think GP is saying, if you are at a point in development where you can choose A or B, and A has foreseeable better performance or scalability, all else being equal choose A. A lot of assumptions there and real world is almost never that clear-cut. The general advice of "don't optimize until you've measured" is still almost always correct.
The issue of course being that when designing code, various design choices can have significant performance implications, and can be very hard to change once implemented and in production.
Earlier quoted context omitted.
Which is entirely inconsistent with the statement "Performance is never a justification for anything if you haven’t measured it".
Dude. This is just how people talk. It's called hyperbole and it's a rhetorical technique. Like "never talk to the cops without a lawyer". Really? Never? "Hi, nice to see you guys here. This is my husband. He's a policeman" "I would like to talk to my lawyer" Because we know the world isn't black and white we're able to interpret these statements. It's human speech. Lots of the details are left out because concisenes…
But what you mean is that you are able to interpret these statements.
Plenty of others, maybe less experienced, are not.
Next thing you know, they are spreading the word - "hey, did you know there's a new development methodology? The idea is that you completely ignore performance until after you've written some code. Yeah, you heard me - completely ignore!. It sounds crazy, but that's how it works!"
One absolute rule for success in software is that there are no absolute rules. From their post mortem https://medium.com/@gabriel_20625/technical-lessons-from-bui... > Performance is never a justification for anything if you haven’t measured it This just isn't true. Anyone with a reasonable amount of experience is often able to look ahead - well before any code is written - and see how performance could be better if…
I would love to get all these "Performance First! Its so easy" engineers in a room for a week. Hell, give em three weeks and they still wouldn't have a single line of code written. But they would still be arguing about the best way to deal with their upcoming 1 million hits per second.
Rule #1 of any business: Sales cures all. You know what's really hard to sell? A product that hasn't even made it out of the damn door yet.
I'm actually really disappointed that I found out about them because they're shutting down. This looks perfect to me because I've been wanting to make some sites fast but I don't have the time to expand my React skills currently. Does anyone have a good recommendation for an alternative?
Also, are you sure you need react?
I like the subtle nod through capitalization in the phrase "It’s been An Incredible Journey".
I'm actually really disappointed that I found out about them because they're shutting down. This looks perfect to me because I've been wanting to make some sites fast but I don't have the time to expand my React skills currently. Does anyone have a good recommendation for an alternative?
Framer X is supposed to have a similar feature set, but Mac only. Also, are you sure you need react?
Earlier quoted context omitted.
Though unlike an Incredible Journey, this is the right way to shut down: Open up your code and contribute what you did to society.
I think it isn't meant so much as a gift to society as it is a best-efforts gesture to your existing users regarding their sites and investment: > We’re releasing it open source both so you can keep using it, and so we can share our ideas about how to build UI tools
We've been writing HTML for a couple of decades now. There have been dozens (hundreds?) of WYSIWYG editors and nothing has really caught on. My hypothesis is that unlike other mediums like paper or video, the elastic nature of the web makes understanding the positioning paradigms/box model/etc a necessity that no visual tool can really abstract. By the time you understand all that, it's just faster to write and maint…
They're just not popular with the HN crowd.
Integrating with ClojureScript ended up working, but it was a real pain. That's less on them than us though, so I won't fault them for not supporting every language which compiles to JS.
However, PageDraw never worked in Firefox. Perhaps now that it's going open source, this can be prioritized, but it was a serious issue for me, since don't use anything else. Just for PageDraw, I installed Chromium; they had a desktop app, but it was much less stable than the site, in my experience.
PageDraw had some annoying bugs, as well. Invisible components in Figma would be imported as visible, but I could work around that. However, there were codegen issues with multi-states which required me to go into the code and make tweaks. I had reached out to Gabriel several times with reproduction cases and debug info, but never heard back.
Aside from that, a slew of UX issues (copied right from my notes):
* Add a "Select children" button when only one item is selected; it shows up when multiple are selected, but not one
* Add a "Delete branch" button which deletes the selected and all children
* Allow searching for component within project
* Allow viewing of an image's source, if it's imported from Figma
* Allow inter-project component references, so I can not have every screen in the same project
* Allow importing of path-based icons with overlaps from Figma; currently, they're all broken
* Allow selecting multiple items with overlapping properties and setting them all at once
I love the idea of PageDraw and I wanted so badly for it to help us with our app development and converting Figma designs to React code which we can use from ClojureScript. Alas, the experience was viable for neither me nor my designer.
Thanks for trying, PageDraw devs, and thanks even more for open sourcing your work as part of this shut down. Best of luck in your future endeavors.