Live data from Hacker News

Polypane, The browser for ambitious web developers

polypane.app

131–140 of 141 posts

Re: Polypane, The browser for ambitious web developers

#131
post #54

Earlier quoted context omitted.

Can it emulate email rendering?

You need a farm of machines that run the actual mail clients, to do that reliably. https://www.emailonacid.com/ is such a service.

I hate this so much. I don't want to do this, as its not cost efficient for development

Re: Polypane, The browser for ambitious web developers

#132
post #130
post #124

Earlier quoted context omitted.

I don’t see how you can come to that conclusion with even a superficial reading of the homepage, unless you count ‘shows web pages’ as ‘almost all features’. And even then the homepage only lists about 30% of what Polypane does.

You can simulate mobile screens, toggle light/dark/print/other media modes, edit css, debug layout, run a11y and lighthouse tests, and download all the framework-specific devtools you want. Besides the multi-pane synced windows I don't really see a new feature here. It's a lot of advertising of little-known features that are already built-in to Firefox I'm not trying to shit on your product. It seems polished and pos…

> It just seems insincere for you to advertise browser features that are built in as features of your app specifically

Sorry but I honestly don't understand this line of reasoning. Advertising a product having a feature in no way means claiming other products do not have the same or similar features.

I could list dozens of things not in Firefox, Chrome or any other browser that Polypane has (and in fact, you list off a few that definitely aren't in Firefox. ) but even so, listing the features a specific product has is the whole point of a marketing website.

Do you also expect Apple to list HP and Acer laptop alongside their Macbooks because those also have screens and keyboards, or otherwise it would be insincere they advertise (on their own marketing website) the screen of a Macbook?

Re: Polypane, The browser for ambitious web developers

#133
post #74
post #17

Earlier quoted context omitted.

Happy to answer this. Polypane is a browser. If you don't keep your browser rendering engine up to date, you're opening yourself to a whole host of security issues (not to mention just generally diverging from what your end users use). Keeping that rendering engine up to date means dealing with a slew of potentially breaking changes with each new chromium version. So there's two reasons: 1. The only way to do that co…

If my users are using an old version of Chromium, I probably want to support that and test on it.

Sure. Chromium is an evergreen browser, which means it's continuously patched and updated in the background. Getting a pinned Chromium version takes quite a lot of work, and really only happens in very specific, controlled environments.

If you happen to work in such an environment you have vastly different considerations from the other 99% of developers building websites and apps on the public facing web.

Re: Polypane, The browser for ambitious web developers

#134

Earlier quoted context omitted.

Google has tens of thousands of engineers—one of them using Polypane at Google would be indicative of Polypane being used at Google.

If only a few engineers are using it out of their own volition that I don't think that justifies trying to imply that Google is a customer. Pretty misleading and underhanded I think.

I work at one of those companies (not google) and Polypane is actively banned as “not safe, shouldn’t be used at all”.

Not to take away from the product, which does look cool, but the “customer list” is definitely sketchy.

Re: Polypane, The browser for ambitious web developers

#135
post #12

Earlier quoted context omitted.

There's a huge list of things Polypane emulates beyond the screen size. For devices: - user agent - reported platform - device pixel ratio - rendering mode (mobile rendering and desktop rendering respond differently depending on your viewport meta tag) - default input device - orientation APIs Beyond that it can also emulate reading direction, page language, browser locale, user-configured default font-size, differen…

Correct me if I'm wrong, but aren't those all things chromium gives you for free? I open the inspector right here, click the devices button, and I can set all those

Yes. This is a fancy electron browser.

Re: Polypane, The browser for ambitious web developers

#136

Earlier quoted context omitted.

Google has tens of thousands of engineers—one of them using Polypane at Google would be indicative of Polypane being used at Google.

If only a few engineers are using it out of their own volition that I don't think that justifies trying to imply that Google is a customer. Pretty misleading and underhanded I think.

Fair point. I'm just explaining how Polypane might have rationalized the positioning.

Re: Polypane, The browser for ambitious web developers

#139
post #25

Earlier quoted context omitted.

Oh I wasn't even thinking about those things, but that's really cool! I was thinking more about different CSS implementation behavior, though that's less of a mobile-specific issue and more of a "every browser is different" issue. I don't have a list of differences off the top of my head, but I regularly find big enough differences that I don't rely on "responsive mode" or even (as mentioned) Apple's iOS simulator (b…

Using Polypane doesn't mean you can skip out on testing other rendering engines. That's such an important point that I even mention it on the homepage! So yeah, you should be testing (mobile) Safari and Firefox too. Chrome on android has some different APIs compared to Chrome on desktop, but rendering is identical. When developing your site, you can use Polypane Portal[1] to tunnel your local site to real devices whi…

I must admit i can't argue the subscription for polypane, if we already have browserstack subscription.

And only polypane that dont support other engines then also don't work.

Re: Polypane, The browser for ambitious web developers

#140
post #139
post #25

Earlier quoted context omitted.

Using Polypane doesn't mean you can skip out on testing other rendering engines. That's such an important point that I even mention it on the homepage! So yeah, you should be testing (mobile) Safari and Firefox too. Chrome on android has some different APIs compared to Chrome on desktop, but rendering is identical. When developing your site, you can use Polypane Portal[1] to tunnel your local site to real devices whi…

I must admit i can't argue the subscription for polypane, if we already have browserstack subscription. And only polypane that dont support other engines then also don't work.

This reasoning misses a very large portion of Polypane, which is that you use it while developing, not just testing. It's a replacement for your time in Chrome/Firefox/Safari, not your time testing across devices (real or through online tooling like Browserstack).

It does however minimise that device testing time. So it all depends on how valuable that time is for you.

Post reply on HN