Totally hear you on the need to make the elements styleable. That's the next phase of work that's being undertaken, specifically starting with <select>. Take a look at the talk that's linked from the article for a more in-depth explanation of the future phases.
Specifically, there were audits flagged as "not applicable" and the alpha version of Lighthouse was instead flagging them as failures. That's why it looked like it was telling you to add audio or images—it was actually saying those audits are not applicable because your site doesn't use audio or images. I think that bug has been fixed in Lighthouse but feel free to reply to this comment if you're still seeing it.
We've also temporarily turned off the PWA audits—they were having some bugs of their own based on the infrastructure they were running on. Based on the feedback in this thread we'll look into making them configurable so folks can choose if they want to run them.
We'll also be opening up the repo shortly so folks can file bugs there directly.
Hey folks, I wanted to share a quick status update to let y'all know which issues we're seeing and working on. Apologies for the hiccups and thank you all for trying the beta!
Ah yeah that's something we want to fix. If you're signed in it keeps the report around but if you're signed-out it's stateless. It's definitely on our to-do list to fix.
Yep that's our bad. We accidentally started prefixing all of the urls with https we've fixed the bug but haven't shipped it yet cuz we're in code freeze
Heyo! One of the web.dev devs here. The new web.dev site is an experiment from our team to see if we can improve the interactivity of our docs. We link to developers.google.com/web in a number of places. Over time, if folks seem to enjoy the web.dev model, we may explore moving more of our docs over there. But for now it's just a fun experiment
I think you can bring the time to initial interactive experience way down by using Polymer CLI. Looking at wedding-app.html it looks like it's loading a lot of elements which aren't on screen yet.
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!!!
I didn't see the author at any point question the performance of their JS framework. More specifically, it seems like the author is using Ember for their apps. My (very rough) understanding is that Ember tends to have a lot of issues running on V8. Due to the way Ember is written, V8 tends to have a hard time optimizing for it.
Where the other libraries all cluster around the same framerate, Ember is running in the single frames. I know that benchmarks can be written in a way to make one library look pathological so this is just one data point, but I wanted to throw it out there. I agree that it would be great if V8 and Ember played better together :)
Nothing publicly released that I know of but I may be out of the loop :)
But it should be possible to stamp a template into a custom element (if it requires one) and get all the markup in place server side. If you're not using Shadow DOM this becomes even easier.
I think so. At this point all browsers are on board with shipping Custom Elements and Shadow DOM and Template has already shipped everywhere. The holdout is HTML Imports and the Chrome team is currently working on a revision to that spec to build it on top of the ES2015 module loader so it's not contentious (https://github.com/w3c/webcomponents/blob/gh-pages/proposals...). But HTML Imports is not a requirement for Web Components, the big win is Custom Elements, so seeing everyone get on board with that is awesome :)
It looks like this library, like gfx and move.js, will accept a cubic-bezier string for easing. I wrote a module which wraps all of Robert Penner's easing equations into cubic-beziers for ease of use:
This is totally awesome! Here is some constructive feedback:
It took me 3 visits to the site to figure out how to add something to my shelf. The little pin would probably be better served if it were below the short description next to the 'Book Profile' and 'Book Website' links on the browse page. Though since adding a book is really the primary action you want your user to take I'd say make it a really obvious button that goes underneath the image of the book cover.
Also once I've clicked on a book to learn more about it, there's no little pin icon on the in-depth description page. Again I'd suggest making it really prominent and obvious. I went back and forth between browse and the description page several times looking for it. I need the brain dead 'Add this thing' button. Your pages are minimal, which is great, because it means that you can make that button obvious very easily. I think there was a good HN article a while back about making the most important item on the page obvious. IMO adding something to my shelf is the most important user action because after I've added just one book I now feel like I have a bit of a virtual stake in that profile I just created and I will definitely come back to build my collection :)
Great idea! Thanks for creating it
P.S. Also just noticed that the hacker shelf logo and title text does not link anywhere. I'd suggest that take the user home.
Well this article was written by the author of SwfObject which is, last I checked, the default way of embedding a Flash object on the page so I presume he actually does know a thing or two about the Flash ecosystem.
I felt the exact same way for a very, very long time. A few things changed my mind.
The first was the realization that Adobe wasn't going to make any more cool fun stuff for me. I feel like they've just lost their way with all that and now that I look back on it, it seems like Macromedia actually made all the aspects of Flash that I enjoy. The most recent thing Adobe has done for me is Stage3D but even that is so technical that they're relying on 3rd parties like Away3D to build the friendly API on top of it.
The second was doing a project that was as close to an art piece as I've ever come doing ad agency work that was entirely in HTML/CSS3 and JS. It was actually this project if you want to see some pictures: http://inchwormstudio.com/?portfolio=samsung-coast-to-coast-...
What I found while I was doing that project was that the web has changed a lot while I've been doing Flash and I didn't realize how much annoying obtuse boilerplate I had to write in AS3 that just becomes total cake when you're using HTML for markup, CSS for style and JS for slick transitions and communication. My main love affair is with HTML and JS, I still think CSS is...CSS. With HTML I'm getting all the great structural stuff that Flex devs love, without the mind numblingly elaborate class structures they have to deal with. With good JS libraries like jQuery I'm getting the cross browser DOM support that I need because I just don't have those sea legs yet. And when you combine it all you can work really, really fast. I spent the whole first half of that project cursing JavaScript up and down the office. I would make little examples showing how setInterval loses scope and demo it for my team and be like "look! this stuff is retarded! I want AS3 back!" Then one day I had to build this twitter widget, and I sat down and I just cranked it out in no time. And I thought, 'You know, if I had been doing this in Flash I would have spent so much time dealing with URLLoaders and cross policy files and coreLib for JSON parsing...' It just felt like things had gone smoother because I wasn't fighting against the web to make it fit inside my Flash app. And that was about the time that I felt like I got over the hump, and from there it was all downhill.
It totally had warts and I got stung by IE transparency bugs but in the end we sorted it all out and now I know how to deal with those issues. And to be honest, they were pretty minimal. The Facebook API was far worse than the cross browser stuff.
If you're making the transition then read this: http://jqfundamentals.com/
I read it start to finish and it made things so much easier for me. Then once you're comfortable with jQuery, leave it behind and try the other stuff. It feels like there is SO much more to experiment with in the JS world than the AS world and I think that's largely because the community is exponentially larger. Hope that's helpful.
As someone who has pretty much exclusively developed for Flash over the past 6 years in both AS2 and AS3 I think it's important for the more resistant members of my community to try and look at this change with some optimism.
First of all let's look at the current state of Adobe and the entire Flash/Flex/Air ecosystem. Around the time that AS3 came out everyone was griping about how hard it was and what a pain in the ass the static typing was. They were used to the forgiving nature of AS2. But eventually pretty much everyone converted and fell in love with AS3. The departure from AS2 to AS3 is like learning a whole new language, like stepping up from JavaScript to a watered down version of Java. I think that everyone's resistance was not based on how much better 3 was than 2, but really because we just didn't want to change. I don't know any Flash devs with CS degrees. They're all artists and designers and musicians who somehow got into development. For us, changing to a new language is difficult because we're self taught and didn't go through years of higher education in C and Python and Java. Once we got comfortable with a flavor of AS we just didn't want to move. But didn't you learn a whole lot going from 2 to 3? Trust me, when you go back and see what people are doing with JavaScript it'll be a little painful at first but then you'll get over the hump and have that same enthusiasm for it that you did for AS3 and the reason will be because the JS community is on fire these days and they're making so much cool shit you'll quickly forget about being forced to live off the junk that Adobe produces.
And let's talk about that junk for a sec. Let's talk about Adobe as a whole and what they've become. Because I feel like at some point they totally lost their way and tried to turn the whole thing into some messed up flavor of Java. Case in point: text. For years we've struggled with getting the right fonts to show up on a page and getting text to flow properly. Their solution, after literally like a decade of us begging for it, was the Text Layout Framework. Rather than just enhancing the embed button they gave us the biggest pile of over engineered shit and to this day I've never seen a project that actually uses it. Adobe spends so much time building dumb features and tools that are totally half baked and then they basically hold a studio's hand to build a demo for MAX and then they waste a shitload of time trying to jam their way into some market and in the end I still can't get my fucking textfields to work and it's 2011. I'm completely over being tied to the whims of that company because for them, it's all one big land grab and they're trying to get into every market possible. They're stretched, their features are watered down, and half the people in there have never done a real world project and are just applying their CS degrees to problems they don't actually understand.
Finally, I just want to say that we need to look forward to our future successes. Because right now each of us probably does not have a sparkling track record of amazing web apps or mobile apps that are not tied directly to the Flash platform. A friend of mine who has been doing Flash way longer than myself just recently launched an app that went to number 1 in the iOS store. He actually wrote it all in C++ but now he's really eager to learn Objective-C. I think this illustrates two points: 1) You don't have to do JavaScript if you don't want to. Learn Ruby or Python or Objective-C. Take this as an opportunity to broaden your horizons. You don't want to slooooowly sunset with a language and end up being the only COBOL guy left in the area code, so consider it a blessing that Flash is getting the rug pulled out from under it. 2) As soon as you start seeing success in a new language you will very quickly forget about Flash. It's kind of like getting into a new relationship. It sucks right now, but it won't always suck, and when it stops sucking it'll be awesome again.
Totally hear you on the need to make the elements styleable. That's the next phase of work that's being undertaken, specifically starting with <select>. Take a look at the talk that's linked from the article for a more in-depth explanation of the future phases.