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

Chrome DevTools in 2016 and Beyond

developers.google.com

Post reply on HN
Print view View original

11–20 of 59 posts

Re: Chrome DevTools in 2016 and Beyond

#11

Post by bobajeff »

lucb1e wrote: post #6

They mention "Progressive web apps" and link to some info, but I can't figure out what the difference is from a normal webpage. Do they mean "web apps that use some stuff that was recently added to most modern web browsers"?

According to google a progressive web app is a website that progressively becomes an app the more you interact with it.

So I guess at first visit you get things like service workers and notifications. Then after like 5 or so visits you get to install it to the home screen and the address bar optionally gets hidden or played around with or something.

Re: Chrome DevTools in 2016 and Beyond

#13

Post by rpastuszak »

bobajeff wrote: post #11
lucb1e wrote: post #6

They mention "Progressive web apps" and link to some info, but I can't figure out what the difference is from a normal webpage. Do they mean "web apps that use some stuff that was recently added to most modern web browsers"?

According to google a progressive web app is a website that progressively becomes an app the more you interact with it. So I guess at first visit you get things like service workers and notifications. Then after like 5 or so visits you get to install it to the home screen and the address bar optionally gets hidden or played around with or something.

It used to be 2 visits in 5 min (assuming web manifest, https and service workers are enabled).

But, I guess, these things are subject to change.

Re: Chrome DevTools in 2016 and Beyond

#14

Post by Jgrubb »

m4tta wrote: post #12
kylec wrote: post #9

Scrolling is broken in Safari on this page. Maybe the page authors should spend less time in the Chrome dev tools and more in the dev tools of other browsers.

Safari is the new IE.

They really are doing themselves a long term disservice by letting this meme be absolutely true.

Re: Chrome DevTools in 2016 and Beyond

#16

Post by sotojuan »

lucb1e wrote: post #8
pfooti wrote: post #7

Earlier quoted context omitted.

Generally, a "progressive web app" is something that behaves a bit like a regular native app, when the browser supports it and user allows it. This includes using serviceworkers to cache data for offline (and low bandwidth) use, making a home-screen icon that launches a standalone (from the task switcher perspective) window with no browser frame, and so on.

Pretty much what I thought, thanks! I'm a fan of the concept, hating apps that could easily have been webpages (public transport apps are often a good example), so it sounds like a good idea to give this a name and promote it. It's too bad that this name sounds like Microsoft came up with it in the early 2000s, but oh well.

It's an awesome idea and one that is actually not too hard to implement, at least partially. Problem is browser support of the APIs, with Safari lagging behind.

Re: Chrome DevTools in 2016 and Beyond

#17

Post by sotojuan »

fokinsean wrote: post #2

Excited to see better support for App Cache and Service Workers. I still have a bad taste in my mouth from trying to integrate them into one of my applications.

Probably not a good answer, but if you use Webpack, Service Worker support is a plugin away:

https://github.com/NekR/offline-plugin

Re: Chrome DevTools in 2016 and Beyond

#18

Post by kayone »

m4tta wrote: post #12
kylec wrote: post #9

Scrolling is broken in Safari on this page. Maybe the page authors should spend less time in the Chrome dev tools and more in the dev tools of other browsers.

Safari is the new IE.

Scrolls fine in Firefox, Edge, and IE11, so yeah. It's Safari.

Re: Chrome DevTools in 2016 and Beyond

#19

Post by pfooti »

sotojuan wrote: post #16
lucb1e wrote: post #8

Earlier quoted context omitted.

Pretty much what I thought, thanks! I'm a fan of the concept, hating apps that could easily have been webpages (public transport apps are often a good example), so it sounds like a good idea to give this a name and promote it. It's too bad that this name sounds like Microsoft came up with it in the early 2000s, but oh well.

It's an awesome idea and one that is actually not too hard to implement, at least partially. Problem is browser support of the APIs, with Safari lagging behind.

Yah, the tricky bit is safari access. I'd love to put a bunch of time into using service workers, push notifications, and so on to make an app-like experience for my users (it's a forum / social network thingy for teachers), but mobile safari really puts a crimp in those plans. Instead I have my own homegrown cache and other hairy tricks that are nonstandard, but work on safari.

Re: Chrome DevTools in 2016 and Beyond

#20

Post by afarrell »

purplerabbit wrote: post #3

Very happy about debugging Node.js in DevTools. Hard to imagine any third-party debugging applications having that amount of features and polish...

I usually try to pop into the debugger from within unit or integration tests, but have found this to be very slow and unreliable when doing it over a port. Have you found your experience to be different?What is your setup to debug mocha.js (or another framework) tests in chrome?
Post reply on HN