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

Modern Web Development

jtaby.com

Post reply on HN
Print view View original

41–50 of 87 posts

Re: Modern Web Development

#41

Post by monteslu »

untog wrote: post #40
monteslu wrote: post #39

Earlier quoted context omitted.

The Chrome beta on ICS is great, but it's only accessible to Chrome Beta needs to be backported to at least 2.3

AFAIK it also doesn't make any difference to apps that use webviews. I mean, it's just as well- if you changed the underlying engine without notifying devs insanity would ensue. But it would be good to be able to set a flag that says "use the decent engine".

You're correct. But no reason google couldn't add a ChromeWebView lib as part of the install of the new browser for PhoneGap to wrap.

Re: Modern Web Development

#44

Post by tagawa »

jtaby wrote: post #34
potch wrote: post #24

"Modern Web Development" does not mean "Works in Webkit", and it does a disservice to future/novice developers to reinforce that notion. What's dominant now was not in the not-too-distant past, and may not be in the not-too-distant future.

I acknowledge WebKit's monopoly on the mobile landscape today, I make no claim whether it's a good thing or a bad thing, that argument would distract from the reality that if you want to make a mobile web app work well, you need to build it on webkit and debug it on webkit

... and test it cross-browser. WebKit has a majority on mobile (around 75%) but not a monopoly. (Source: http://gs.statcounter.com/#mobile_browser-ww-monthly-201103-... )

Re: Modern Web Development

#45

Post by DrJokepu »

I'm not sure if docking to the right is really the best default; it really depends on your setup. On big, wide displays it's indeed a good way to do it. On small displays (notebooks) docking on the bottom is better. If you have multiple displays, detaching and moving the detached window to the other display works best. I think it's a good idea to assume the worst (tiny display) and dock to the bottom; the browser will remember your setting anyway so it's not like you'll need to do this all the time.

Re: Modern Web Development

#46

Post by mmahemoff »

micrypt wrote: post #6

A mild concern of mine with the "Google, if you’re listening" annotations. It's worth remembering that Chromium's an open-source project. If you really want something, send a patch.

Well, discussion is fine too and not every web developer is in a position to knock out some detailed C++.

But this is still a valid point in the sense that Chromium is run much more in the spirit of an open-source project than other large-scale commercial open source efforts. External patches do make their way into Chromium.

Re: Modern Web Development

#47

Post by r00fus »

DrJokepu wrote: post #45

I'm not sure if docking to the right is really the best default; it really depends on your setup. On big, wide displays it's indeed a good way to do it. On small displays (notebooks) docking on the bottom is better. If you have multiple displays, detaching and moving the detached window to the other display works best. I think it's a good idea to assume the worst (tiny display) and dock to the bottom; the browser wil…

How many netbooks have anything other than a 16:9 display (even the MB Air 11")? Vertical pixels are precious in landscape mode. Dock to the side is far more efficient with current reality of displays.

Let's put aside any frustration that 16x9 is even usable much less desirable for any office work.

Re: Modern Web Development

#48

Post by mmahemoff »

brettnak wrote: post #13
micrypt wrote: post #6

A mild concern of mine with the "Google, if you’re listening" annotations. It's worth remembering that Chromium's an open-source project. If you really want something, send a patch.

I'm probably not the only one, but I have no idea where the separation between Chromium and Chrome actually is. Can anyone enlighten me as to where the separation really is? Is Chrome a fork of Chromium, is Chromium an upstream? I know they actively work together in a lot of ways but how exactly?

http://code.google.com/p/chromium/wiki/ChromiumBrowserVsGoog...

Aside from the obvious - branding and stability - It's mainly the commercial stuff (MP3, PDF, Flash) which can't be distributed under Chromium's license.

Re: Modern Web Development

#49

Post by bicknergseng »

jtaby wrote: post #17
bicknergseng wrote: post #16

The custom scroll bar might look sorta cool, but it's completely unusable on Chrome. The scroll tracker disappears and it's basically impossible to find. I've ended up restarting at the top of the page just to be able to scroll properly.

Thanks for letting me know, I didn't realize I broke that. I just pushed up a fix

Dunno if you've had that fix go live yet, but it's still unusable. The actual little scroll tracker (what's the name for that thing?) isn't discernible from the background. When you scroll up and down, the bar turns white and the cursor is white. I'd send a ss, but I don't see anyone else complaining so it's probably a me problem. Might be because I'm on Linux.

Re: Modern Web Development

#50

Post by markkanof »

blhack wrote: post #30

This is worth getting your head around just for the console. I've been transitioning all of my projects from python cgi scripts (yuck), to shtml files, javascript clients, and APIs that run on node.js. For somebody like me, that has been writing python+cgi for the last 5 years, diving into javascript was daunting . Terrifying even. Console made this a lot, lot, lot easier. In javascript, you can call console.log("thi…

Also, don't forget the step through debugger. It's such a time saver to be able to set a couple of break points and then when they are hit you can hover your mouse over different variables and see a tool tip that shows the contents of that variable.
Post reply on HN