Oh enough with this nonsense. The EU is no different than the US during the earlier period of the union when the states still retained most of their independent authority.
"See Google's latest post in the link where they say hi to us Slashdotters"
And you don't find the snarky stfu and go away tone of that and the previous post to be inappropriate? Also, a bug tracking forum is the normal place to make a feature request.
Demonstrably harder and more time consuming? It's fairly effortless to 'aim' for the period at the end of your post with the cursor let alone a whole tab. Moving to the top of the screen is also not a single movement. Since the cursor is hovering over the content I'm focused on which is the bottom fifth of the screen a single 1-1.5" push on the cursor will put it anywhere from the tabs to the location bar. I actually have to scoot my fingers back and give a slight extra push to reach to the top of the screen.
The 500+ comments on the story suggest that others felt the lack of openness in the project was newsworthy. Many feel that attitude (and not the minor feature) even justifies forking. Sorry that you disagree.
I work differently I guess. If I don't think a story is interesting I move on to the next one.
"No, 500 people starred the bug, out of 70 million."
I think you will find that is actually a pretty good sample. Especially since the pool who know what a bug tracker is and that it is possible to comment or star on one isn't anywhere near 70 million.
It's no big mystery. There are a few problems. The first is the plugin-container process crashes and locks the browser. The second is that it leaks memory badly. The third is that people leave tabs to open with the browser and so have to wait for them to all load. The fourth is really the first, people use a homepage that requires plug-in content to load.
I haven't seen hostility over their willingness to implement the feature or not (although anyone with an aesthetic 'rationale' for tab placement needs a serious priority change) the hostility is the justification they've given and the tone with which they've delivered it.
What is silly is rejecting a large quantity of potential users (for every one who could comment on an obscure bug tracker there are millions who wouldn't) by refusing to allow a simple configuration option when they like your fast rendering and javascript engine.
Most open source projects don't ignore feedback as a matter of policy either. it's one thing for a project to hear you out and decide to go their own way. It's quite another for them to boldly claim that they ignore your feedback from the get go.
The federal reserve generates the money, not the federal gov't. Although technically they purchase the paper bills from the treasury at cost (which is a few cents) most of the money they 'print' is electronic and the Federal Reserve can 'print' it all day long.
Tabs need to be interacted with FAR more often than the location bar and since the web is a point and click medium the need for key combos should be minimized.
Terminal servers supply remote graphical desktops these days grandpa;) I generally use the mouse when browsing as it is a visual point and click medium and outside a discussion forum my hands would rarely be on the keyboard when using a browser.
"Tabs on Top is the soul thing that made Chrome interesting."
That's kind of a silly assertion. Dramatically improved rendering speed is what made Chrome interesting. Without that improved performance it's kind of a limp noodle compared to the alternatives.
"Now, I wouldn't care if google made an option to allow the user to move the tabs to the bottom."
Virtually no dissent doesn't mean everyone wants them on bottom, the request is to add an option to move the tabs so dissent would be being opposed to there being an option at all.
This wasn't about showing that they aren't implementing this particular feature. It was about the developer stating that community feedback isn't a factor in their development and censoring further comment.
"Since when has it been required that an open source project accept and implement every feature request from users?"
I think saying that community comments have absolutely no impact on whether they CONSIDER a feature is a far cry from implemented every user feature request.
"when I don't even care whether they use it or not"
You might not care but Google certainly cares. If the browser doesn't gain enough market share it is useless to them.
"They are releasing a free browser and saying they don't want to change the way it looks."
No they are releasing a project as open and claiming they want to build a community around it. Now they are saying that the feedback from that community isn't considered at any level. This has little to do with the feature in question and everything to do with Google's statement that community feedback isn't considered.
It sounds like you are seriously over thinking the "meaning" of the positioning. There are things like terminal windows that put something in that location of the screen and it is further from where your mouse hovers on the content. That is more than enough justification for having AN OPTION to reposition the bar.
Slashdot Mirror
The constitution lost all meaning after the civil war. MUCH longer than 10yrs.
I think you'll find the civil war put an end to that. You aren't a citizen of state x anymore.
It's 27 completely independent nations! Now let me just add up all their populations for a comparison as if it were a single place...
"Counterfeit drugs are quite often fake in that they contain more, less, or an entirely different drug than advertised."
Or so the big pharma propoganda tells us. And yes, anything issued by the FDA or DEA falls under that umbrella.
Oh enough with this nonsense. The EU is no different than the US during the earlier period of the union when the states still retained most of their independent authority.
"See Google's latest post in the link where they say hi to us Slashdotters"
And you don't find the snarky stfu and go away tone of that and the previous post to be inappropriate? Also, a bug tracking forum is the normal place to make a feature request.
"The address bar shows the address that is open in the current tab"
Except when it doesn't. The address bar is for replacing the tab content with new content not figuring out what page you are on.
The only data related to the tab is the content in fact they are synonymous tab=page. The location bar is for changing the content.
Demonstrably harder and more time consuming? It's fairly effortless to 'aim' for the period at the end of your post with the cursor let alone a whole tab. Moving to the top of the screen is also not a single movement. Since the cursor is hovering over the content I'm focused on which is the bottom fifth of the screen a single 1-1.5" push on the cursor will put it anywhere from the tabs to the location bar. I actually have to scoot my fingers back and give a slight extra push to reach to the top of the screen.
The 500+ comments on the story suggest that others felt the lack of openness in the project was newsworthy. Many feel that attitude (and not the minor feature) even justifies forking. Sorry that you disagree.
I work differently I guess. If I don't think a story is interesting I move on to the next one.
you don't need to convince them, they already offer the option to do so.
"No, 500 people starred the bug, out of 70 million."
I think you will find that is actually a pretty good sample. Especially since the pool who know what a bug tracker is and that it is possible to comment or star on one isn't anywhere near 70 million.
It's no big mystery. There are a few problems. The first is the plugin-container process crashes and locks the browser. The second is that it leaks memory badly. The third is that people leave tabs to open with the browser and so have to wait for them to all load. The fourth is really the first, people use a homepage that requires plug-in content to load.
I haven't seen hostility over their willingness to implement the feature or not (although anyone with an aesthetic 'rationale' for tab placement needs a serious priority change) the hostility is the justification they've given and the tone with which they've delivered it.
What is silly is rejecting a large quantity of potential users (for every one who could comment on an obscure bug tracker there are millions who wouldn't) by refusing to allow a simple configuration option when they like your fast rendering and javascript engine.
Some people use Chrome for rendering performance.
by default, the request is for an OPTION to move the tabs which at least Firefox has.
Most open source projects don't ignore feedback as a matter of policy either. it's one thing for a project to hear you out and decide to go their own way. It's quite another for them to boldly claim that they ignore your feedback from the get go.
The federal reserve generates the money, not the federal gov't. Although technically they purchase the paper bills from the treasury at cost (which is a few cents) most of the money they 'print' is electronic and the Federal Reserve can 'print' it all day long.
Tabs need to be interacted with FAR more often than the location bar and since the web is a point and click medium the need for key combos should be minimized.
Terminal servers supply remote graphical desktops these days grandpa ;) I generally use the mouse when browsing as it is a visual point and click medium and outside a discussion forum my hands would rarely be on the keyboard when using a browser.
"Tabs on Top is the soul thing that made Chrome interesting."
That's kind of a silly assertion. Dramatically improved rendering speed is what made Chrome interesting. Without that improved performance it's kind of a limp noodle compared to the alternatives.
"Now, I wouldn't care if google made an option to allow the user to move the tabs to the bottom."
Virtually no dissent doesn't mean everyone wants them on bottom, the request is to add an option to move the tabs so dissent would be being opposed to there being an option at all.
This wasn't about showing that they aren't implementing this particular feature. It was about the developer stating that community feedback isn't a factor in their development and censoring further comment.
"Since when has it been required that an open source project accept and implement every feature request from users?"
I think saying that community comments have absolutely no impact on whether they CONSIDER a feature is a far cry from implemented every user feature request.
"when I don't even care whether they use it or not"
You might not care but Google certainly cares. If the browser doesn't gain enough market share it is useless to them.
"They are releasing a free browser and saying they don't want to change the way it looks."
No they are releasing a project as open and claiming they want to build a community around it. Now they are saying that the feedback from that community isn't considered at any level. This has little to do with the feature in question and everything to do with Google's statement that community feedback isn't considered.
It sounds like you are seriously over thinking the "meaning" of the positioning. There are things like terminal windows that put something in that location of the screen and it is further from where your mouse hovers on the content. That is more than enough justification for having AN OPTION to reposition the bar.