Show HN: I built my wedding website using Polymer
maggieandcaleb.com
maggieandcaleb.com
Nice job on the site and best wishes to you and your bride.
Site looks great regardless. That's one of the great things about Polymer.
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.
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?
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?
You get a crazy amount of Flash of Content and things being resized and ordered around during page load. Quite distracting tbh.
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)
React is good too, but you need the right framework on top of it (or else it can be a bit tricky to setup properly).
Take a look at the app-drawer-template example and note the line that lazy loads element definitions when pages change: https://github.com/Polymer/app-drawer-template/blob/master/s...
If you use the CLI you can create a polymer.json file that lets you fragment up your site: https://github.com/Polymer/app-drawer-template/blob/master/p... This way you'll create separate vulcanized bundles and you can lazy load them right when the user clicks on the section, hopefully improving that first load experience.
Ignore the haters on HN. Congrats on the wedding!!!
This, ladies and gentlemen, is why I prefer Mithril, or at least React. Or heck, even the horrific, broken, awful mess that is angular 1 is better than this, for crying out loud!
I know that Polymer may make things easier as a designer, but newsflash: the end user doesn't give a damn. They want a fast, responsive, stylish site. And Polymer just isn't there.
I did my wedding website using wix because she wanted to build it (I did the sysadmin parts of it)
That said, Congratulations, on the wedding and the website.
So what do you think?
About using Polymer I mean. :)
Would love to get some insight as to how the experience was learning and building something in Polymer. I haven't heard much of Polymer lately.
Polymer: The polymer elements that Google provides are good. The polymer-cli is fantastic, it just works and I didn't have to configure gulp/grunt/browserify/webpack at all. The project needs no node modules, all dependencies come from bower! Non-google custom elements out there lack robust browser support and I find that I don't trust them out of the box.
Ecosystem: support for web components has come a ways in the past couple years but still has a ways to go. Chrome natively supports web components but every other non-blink browser uses polyfills, which slows things down. Firefox and WebKit are implementing part of the web components spec, so hopefully it'll get better soon.
It's an exciting technology that is very pleasant to code in. Learning the ropes and building the entire site took 20 hours, most of that was dealing with nitpicky browser support issues with scrolling and animation effects. I hope it continues to gains traction and I would definitely use it again!
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"
One idea I had was to create a template wedding website service. There are a few out there, but I think the idea can be done better.
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.
He's not forcing you to drive the car.
I RSVP'd, but can you guess under who?