6 ms·
What nonsense! Gave up after reading this. """ Where typical internet maps take 30+ seconds to load after each pan and zoom """ What typical maps are the talk
by injidup 4y ago
What nonsense! Gave up after reading this.
"""
Where typical internet maps take 30+ seconds to load after each pan and zoom
"""
What typical maps are the talking about?
- jhugo 4y agoYeah, it was really hard to take it seriously after reading that.
- krstffr 4y agoA bit sad as the thing that made me decide to not even try their app (which looked cool!) was the abysmal performance (in FF).
- nik736 4y agoUsing Firefox their maps are taking a long time to load after each pan and zoom. lol.
- 8n4vidtmkvmk 4y agothey meant they take 30 seconds whereas competitors take 300ms. just a little slip up
- kart23 4y agoironically, performance is terrible with most of their demos, and I'm using chrome on a decently powerful desktop. https://felt.com/map/San-Diego-Zoo-Virtual-Tour-LC3QHLPxR4ywZsX6opbW0A https://felt.com/map/San-Diego-Zoo-Virtual-Tour-LC3QHLPxR4yw...
- sen 4y agoWow the performance on that is absolutely terrible. I'm on a gaming PC and it bogged me down so hard the tab started freezing up.
- Traubenfuchs 4y agoPerformance is so bad, the page crashes regularly and repeatedly on my iPhone 13 pro. It‘s unusable.
- deleted 4y ago[deleted]
- schleck8 4y agohttps://felt.com/map/Appalachian-Trail-Thru-Hike-9BZ2GWGGKQ1G9Cd1jxjy9AtSB https://felt.com/map/Appalachian-Trail-Thru-Hike-9BZ2GWGGKQ1... I just loaded this big map on a pixel 4a and while it was laggy, it still responded and didn't crash
- hbn 4y agoIt seems like they don't support Safari or anything other than Chrome (and all browsers on iOS are technically Safari) I tried it in Safari on my i9 late-2019 MBP and (after dismissing the warning message) I was barely able to move around.
- lionkor 4y agoi7-9700k @ 4.9 GHz, RTX 2070 here, no other tabs open, absolutely unusable still. Firefox Nightly with hardware acceleration. Yikes.
- deleted 4y ago[deleted]
- cnity 4y agoAfter a bit of an inspection, it looks like they segment the viewport into multiple canvas elements. I don't think repositioning loads of canvas elements by translating the parent div in CSS is the most performant approach, but I may be wrong. It would likely be more performant if the map view was a single canvas and panning, segmentation and so on was done in a buffer and rendered to the canvas by blitting the pre-rendered sections, or something along those lines. Maybe even rendering the sections to WebGL textures and using a WebGL context for the canvas.
- ev0lv 4y agoThis guy codes! No seriously, this is great feedback for the devs.
- aschleck 4y agoYou're right that using canvas/WebGL will be much faster. It seems the embeddable Google Maps JS library recently moved in this direction, though it appears they kept the layers of stacked divs (almost certainly for backwards compatibility with existing users who have HTML layers that need to be kept in sync.) But something fun to notice with Felt is that the rendering library (LeafletJS) is using transform3d to do 2d translations (instead of just using translate), so you may wonder "why?" At least in Chrome (and it seems in Safari) if you use transform3d the browser is more likely to keep the div in its own layer. This will reduce a lot of the paint/compositing time, and make the frame rate dramatically better. Of course in this case the micro-optimizations are irrelevant in comparison to Felt's JS performance problems (which on my machine appears to be due to projecting 2000 points from lat/lng space to pixel space every frame.) Choosing to project points every frame is super confusing because the whole point of the translate/transform3d optimization is to avoid having to recalculate pixel space during the latency-sensitive pan interaction. Odd.
- tagyro 4y agoafter the initial load and warning to switch to chrome, it's running pretty smooth in safari on a m1 macbook air
- madeofpalk 4y agoOn my MBP w/M1 Pro, it's terribly unresponsive trying to zoom.
- cr3ative 4y agoThis is... unusable, on a decent Macbook Pro using Chrome.
- CamelRocketFish 4y agoI was exactly the same. As soon as I read that hyperbole I immediately closed the page. You’re either dishonest or perform terrible tests which means I’m not going to trust much else of what you write on your landing page.
- ryanbrunner 4y agoMaybe they started this project in the late 90s with the goal to unseat Mapquest.
- zimpenfish 4y agoGiven the context, "Never wait for a dataset to load again. Where typical internet maps take 30+ seconds to load after each pan and zoom, ...", it seems to be specifically talking about loading and rendering new bits of data taking 30+ seconds when you pan and zoom, not just panning and zooming the map itself.