Web Starter Kit • Hacker News Board

Re: Web Starter Kit

#11

Post by addyo » Thu, Jun 19, 2014, 6:12 PM UTC

Siecje wrote: post #6

I wonder what browsers versions they are going to support at launch.

We cover this in our browser support section: https://github.com/google/web-starter-kit#browser-support

Re: Web Starter Kit

#12

Post by addyo » Thu, Jun 19, 2014, 6:14 PM UTC

leke wrote: post #7

It's a good idea, but it's currently lacking the richness of bootstrap.

For sure. This is just a start and we don't intend on competing with Bootstrap in terms of UI components. We spent a long time evaluating many of the existing UI libraries available today and if a developer chooses to use one of them with the kit, they can. That's cool.

Re: Web Starter Kit

#13

Post by fidotron » Thu, Jun 19, 2014, 6:14 PM UTC

The web is now hamstrung by the HTML/CSS layout model more than anything else. The hackery required to attempt to imitate native mobile apps is horrific.

Google would be better off throwing efforts into a new layout engine leveraging raw JS and WebGL, but with a sane API, than these continuous attempts to push HTML into places where it doesn't work. If they don't lead it I can see someone else doing it in such a way that their core money maker of web scraping and indexing ceases to work.

Re: Web Starter Kit

#14

Post by ondrae » Thu, Jun 19, 2014, 6:17 PM UTC

Its interesting they are using GitHub instead of Google Code.

Re: Web Starter Kit

#15

Post by addyo » Thu, Jun 19, 2014, 6:18 PM UTC

fidotron wrote: post #13

The web is now hamstrung by the HTML/CSS layout model more than anything else. The hackery required to attempt to imitate native mobile apps is horrific. Google would be better off throwing efforts into a new layout engine leveraging raw JS and WebGL, but with a sane API, than these continuous attempts to push HTML into places where it doesn't work. If they don't lead it I can see someone else doing it in such a way…

On the Chrome team we're always looking at ways to better provide access to lower level primitives and machinery to enable you to do things like this. It's a multi-faceted problem however. If you have specific suggestions around alternative layout engines, discourse.specifiction.org is a great place to lay out your suggestions in more detail (not that HN isn't useful for this, but those interested in standards generally frequent the discussion board). Outside of layout engines, we're also looking at enabling developers to do more things they would like to with native hardware. Take a look at https://github.com/w3c-webmob/web-api-gap/tree/master/featur... for feature gaps and efforts to fill them.

Re: Web Starter Kit

#16

Post by marknutter » Thu, Jun 19, 2014, 6:20 PM UTC

fidotron wrote: post #13

The web is now hamstrung by the HTML/CSS layout model more than anything else. The hackery required to attempt to imitate native mobile apps is horrific. Google would be better off throwing efforts into a new layout engine leveraging raw JS and WebGL, but with a sane API, than these continuous attempts to push HTML into places where it doesn't work. If they don't lead it I can see someone else doing it in such a way…

> The web is now hamstrung by the HTML/CSS layout model more than anything else

Really? Because I find it far more intuitive and flexible than working with xibs, for instance.

Re: Web Starter Kit

#17

Post by pjmlp » Thu, Jun 19, 2014, 6:21 PM UTC

fidotron wrote: post #13

The web is now hamstrung by the HTML/CSS layout model more than anything else. The hackery required to attempt to imitate native mobile apps is horrific. Google would be better off throwing efforts into a new layout engine leveraging raw JS and WebGL, but with a sane API, than these continuous attempts to push HTML into places where it doesn't work. If they don't lead it I can see someone else doing it in such a way…

Web was never meant for applications. Other hypertext models like Hypercard and Xerox PARC experiments had better support.

I really hope that we can sort out this mess some day.

I personally like apps are making the network more relevant than the Web. What matters are communication protocols.

Re: Web Starter Kit

#18

Post by addyo » Thu, Jun 19, 2014, 6:22 PM UTC

ondrae wrote: post #14

Its interesting they are using GitHub instead of Google Code.

Google Code is great, but I personally love GitHub https://github.com/google https://github.com/googlechrome and so on.

Re: Web Starter Kit

#19

Post by [deleted] » Thu, Jun 19, 2014, 6:26 PM UTC

addyo wrote: post #10

dudus wrote: post #2

Twitter Bootstrap competitor?

Good question. We don't consider ourselves a Bootstrap competitor, but rather a combination of best practices and tooling when it comes to starting work on new multi-device/mobile web projects. Bootstrap, Zurb and similar libraries provide a great start for prototyping your apps, but one of the biggest challenges with them is that it’s (almost too) easy to get stuck using their styles, look and feel for the lifetime…

[deleted]

Re: Web Starter Kit

#20

Post by joshma » Thu, Jun 19, 2014, 6:27 PM UTC

addyo wrote: post #10

dudus wrote: post #2

Twitter Bootstrap competitor?

Good question. We don't consider ourselves a Bootstrap competitor, but rather a combination of best practices and tooling when it comes to starting work on new multi-device/mobile web projects. Bootstrap, Zurb and similar libraries provide a great start for prototyping your apps, but one of the biggest challenges with them is that it’s (almost too) easy to get stuck using their styles, look and feel for the lifetime…

Is there any way to use the tooling independently of web starter kit? Wasn't able to find a link on the site, are they just warnings you see once you start developing? Can the tooling account for JS changes and navigation between pages?

Sorry for the barrage of questions, just really hoping to find a decent tool to clean up CSS...