Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: I built my wedding website using Polymer

maggieandcaleb.com

Post reply on HN
Print view View original

61–70 of 75 posts

Re: Show HN: I built my wedding website using Polymer

#61

Post by abricot »

stephenr wrote: post #54
fusiongyro wrote: post #52

Earlier quoted context omitted.

"To learn" and "for fun" are perfectly sufficient explanations, even if you don't understand them.

But his point is that the site isn't doing anything that couldn't be achieved without js. This would be like if a mechanic said he was going to replace your wheels with wooden ones he made himself because he wants to learn how to be a carpenter.

No, it would be like if a mechanic replaced the wheels on his own car with wooden ones to try it out. Nothing wrong with that.

He's not forcing you to drive the car.

Re: Show HN: I built my wedding website using Polymer

#62

Post by thiht »

micheljansen wrote: post #58

Cool and thanks for sharing. Not as a criticism to you specifically, but a worry I have about technology like Polymer in general: I opened your site and was staring at an empty grey screen for a good 5 seconds. Maybe your server is busy because of all the HN attention, but I am worried about the future of the web when these kinds of things are becoming normal and acceptable.

I encounter the same issue with every single website written using a modern frontend framework: Angular, React, whatever...

They're considered to be faster but they look so sluggish at loading, I wonder why this is considered acceptable when it's clearly not.

Is it a fundamental issue with this kind of frameworks, or is it due to a bad usage by developers?

Re: Show HN: I built my wedding website using Polymer

#64

Post by caleblloyd »

micheljansen wrote: post #58

Cool and thanks for sharing. Not as a criticism to you specifically, but a worry I have about technology like Polymer in general: I opened your site and was staring at an empty grey screen for a good 5 seconds. Maybe your server is busy because of all the HN attention, but I am worried about the future of the web when these kinds of things are becoming normal and acceptable.

Yes, the initial load is heavy. I think lots of it may be device rendering time after the page is loaded- chrome is the only browser that natively renders web components and every other non-blink browser has to wait for polyfills to load. The JS has got to be hard on mobile CPUs especially.

HTTP/2 with server push would help, but I'm hosting on dreamhost shared hosting and they're not HTTP/2 enabled yet. I am using the bundled build option in Polymer which concatenates most of the components, but there's still a lot of assets to serve.

Chrome service worker is working though! Load the site in chrome, then go into airplane mode and hit refresh. (not chrome for iOS though, that's WebKit underneath)

Re: Show HN: I built my wedding website using Polymer

#65

Post by Mithaldu »

caleblloyd wrote: post #64
micheljansen wrote: post #58

Cool and thanks for sharing. Not as a criticism to you specifically, but a worry I have about technology like Polymer in general: I opened your site and was staring at an empty grey screen for a good 5 seconds. Maybe your server is busy because of all the HN attention, but I am worried about the future of the web when these kinds of things are becoming normal and acceptable.

Yes, the initial load is heavy. I think lots of it may be device rendering time after the page is loaded- chrome is the only browser that natively renders web components and every other non-blink browser has to wait for polyfills to load. The JS has got to be hard on mobile CPUs especially. HTTP/2 with server push would help, but I'm hosting on dreamhost shared hosting and they're not HTTP/2 enabled yet. I am using t…

There's also a simple problem in that you're, on that page, not doing much more than showing simple HTML, however in browsers with JS off, for whatever reason, it shows absolutely nothing. Not even a message that JS is required.

Re: Show HN: I built my wedding website using Polymer

#66

Post by caleblloyd »

fazza99 wrote: post #63

It's brave of you to open the comments without a password. Post some of the better ones here.

Best Attendees: "Obama", "Donald Trump (guest is Hillary Clinton)", "Ghandi", "Clint Eastwood"

Best Other Party Members: "Aunt Mimi and her 12 cats"

Best Song: "Never Gonna Give You Up", "Hot cross buns", "Team America World Police", "Happy Birthday"

Best Message: Lots of congratulations and nice words, "Please provide a jacuzzi for my table"

Re: Show HN: I built my wedding website using Polymer

#68

Post by brianwawok »

owenconti wrote: post #28
brianwawok wrote: post #24

Earlier quoted context omitted.

Want to know what happens when your server goes down? 600 angry bridezillas. No thanks

Static sites hosted on s3? Low risk of an outage, could be worth the risk

Hey more risk is more profit ;) I would just be afraid of that market, hah.

Re: Show HN: I built my wedding website using Polymer

#69

Post by ghrifter »

thiht wrote: post #62
micheljansen wrote: post #58

Cool and thanks for sharing. Not as a criticism to you specifically, but a worry I have about technology like Polymer in general: I opened your site and was staring at an empty grey screen for a good 5 seconds. Maybe your server is busy because of all the HN attention, but I am worried about the future of the web when these kinds of things are becoming normal and acceptable.

I encounter the same issue with every single website written using a modern frontend framework: Angular, React, whatever... They're considered to be faster but they look so sluggish at loading, I wonder why this is considered acceptable when it's clearly not. Is it a fundamental issue with this kind of frameworks, or is it due to a bad usage by developers?

One thing I'm disliking is the amount of sites using React.

You get a crazy amount of Flash of Content and things being resized and ordered around during page load. Quite distracting tbh.

Re: Show HN: I built my wedding website using Polymer

#70

Post by fizzbatter »

thiht wrote: post #62
micheljansen wrote: post #58

Cool and thanks for sharing. Not as a criticism to you specifically, but a worry I have about technology like Polymer in general: I opened your site and was staring at an empty grey screen for a good 5 seconds. Maybe your server is busy because of all the HN attention, but I am worried about the future of the web when these kinds of things are becoming normal and acceptable.

I encounter the same issue with every single website written using a modern frontend framework: Angular, React, whatever... They're considered to be faster but they look so sluggish at loading, I wonder why this is considered acceptable when it's clearly not. Is it a fundamental issue with this kind of frameworks, or is it due to a bad usage by developers?

Bad frameworks and/or bad usage. Ie, a lot of frameworks don't have good/any serverside support. React does, fwiw.

From my perspective, a good React site is rendered on the server in most scenarios. Meaning the first page you get is pure html and 100% complete. The JS will load and link everything up, but it's nothing that you'll know. If you click a link before the js loads, it should point to a real url and give you full html again. When the js does finally load, json can be used to load new pages, modifying the content with react, etc.

This is also nice because web crawlers (all of them) get simple html, and if a user has JS turned off, they still a lot of your content, perhaps missing some of your UX.

I've implemented a couple content heavy sites like this and it's a nice UX. Performs just as you expect in most scenarios. The only complaint i think that could be valid, is that there is, indeed, a fair amount of JS, which on mobile devices is definitely worse off than if it were just static content.

This is my benchmark for frontend frameworks for the future. Can i compile it, efficiently, on the server before giving it to the user?

Post reply on HN