Yet they disabled the age-old shortcut command-shift-a, which brought up the Applications folder in the Finder. I used to use that because you could key-type the first few letters to find the app. They killed it.
However, 10.7 does add a keyboard search to the launchpad which 10.6 doesn't have. Makes launching apps about as fast as the old way.
If you're using phpMyAdmin, then you aren't doing the kind of in-depth database development where you run into the problems the GP is talking about.
Hell, if you're using phpMyAdmin, you're casual DB user probably just trying to support your small webapp or CMS installation.
And if you do use phpMyAdmin, you'd be much better off with a platform native database tool with MySQL support, such as SequelPro (OSX) or MySQL Workbench for (Windows,OSX)
Care share that web-based product for board meetings? I belong to some groups that could utilize a formalized system instead of ad-hocing it with Word via a projector.
The example I provided is the first of many treaties that cover patents. Most patent treaties essentially say "if you want us to respect patents filed in your country, you have to respect patents filed in ours".
What do you mean "out of nowhere"? France was the first country to pass 3-strike laws for copyright violations and has been pushing this crap for years./. covered this extensively 4 years ago... and I'm pretty sure it was on here even before that, but I'm too lazy to do more Googling.
I'm just surprised it's taken them this long to enforce the law.
Sounds more like her router isn't in bridged mode, so wired broadcast traffic isn't being sent out to wifi, essentially isolating the two networks for broadcast protocols.
She'd have the same problem with Windows until the router configuration is changed.
high dpi support? in osx it's a fucking joke, it's beyond shit
If anyone doesn't believe this, you should read the Mozilla bug on getting high DPI support on Mac OS X in Firefox. Basically, it's never going to happen because the API for doing it is so fucked up. ("But isn't it just rendering things at twice resolution?" Read the bug. It isn't. There are so many edge cases it isn't funny.)
Yet somehow, when my new laptop showed up in early July, Chrome had support for retina display in the beta channel, and had it in the mainstream release 2 weeks or so later.
Mozilla's inability to implement features is not a good indicator of how difficult the API is to use. A big part of Mozilla's problem is that they insist on using their own font rendering engine for both the window chrome as well as the contents, instead of relying on the OS to do it.
But a better way would be to put your computer on an exemption list in the load balancer to statically map you to the server to be tested.
mmhmmm.... and how would that happen exactly? My company is behind a firewall and appear as a single IP. How would you target my machine specifically? And when I need to switch to another server behind the load balancer, or switch back to "normal" operation? Are you honestly suggesting wasting the time of the various admins and approvers multiple times, not to mention making changes to a production environment, just so that a dev doesn't change his host file while troubleshooting?
The load balancer is managed by a complete different department in the client's company. My contacts don't have direct access and have to formally request changes that can take hours or more to get made. Neither my direct client, nor my company, has the access permissions to make the necessary changes directly.
Sounds to me like you work in the kind of shop where anyone has access to do anything (and hence break anything) any time they want to any system they want. And you accuse me of not following best practices????
IT here handles network, server admin, workstation deploy, network credentials, service and hardware provisioning, etc.
Dev is busy building apps, websites, and more for clients. Different projects have radically different architecture and infrastructure needs. Everything from a simple one-off HTML page to specialized Android builds to run on targeted embedded devices.
I have root acces to my workstation, and my workstation only. If I need to test something, I can test it on my workstation and not have to commit, get a deploy approved to staging environments, trigger the QA process, etc, etc. I don't, and shouldn't need, DNS admin abilities to do this. Screwing with DNS affects far more people around here than just me.
I have a real world example for you. I am working on a client's website we inherited a few months ago (~1 million visitors/month) troubleshooting some login issues. Because of the CMS, and a whole lot of legacy code, it currently requires absolute URLs to load resources. We were having a problem with sessions between servers. To isolate the problem, we needed to bypass the load balancer. However, because of absolute URL requirements, the site won't function properly if you visit www1.example.com. The only way for me to bypass the load balancer and ensure I was loading everything from one specific server was to edit my host file.
Now, short of DNS changes (which I don't have access to because it would affect at least 50 other people in my office and up to 1200 people across our corporate network) or admin access to my client's servers (even the client doesn't directly have this and has to submit formal request changes through their system engineering department) how should I go about guaranteeing I am targeting a specific server?
I usually do such trickery with internal DNS servers
Thats great, but I don't have control over our internal DNS. IT does. However, I do have control over the hostfiles on my local dev workstation, and from there I can toggle to point to my local machine.
See, too lazy to put in s1.realdomain.com and s2.realdomain.com to get to servers 1 and 2 directly. DNS solves it all, but only if you tell it to.
That assumes the app you're working responds the same to s1.example.com as it does to www.example.com. That's not always the case. And in the cases where it doesn't, you may not have the authority to change the underlying behavior.
no, but dev.realdomain.com might be... and yet I have to overwrite it to simulate on my local machine for development testing. Or perhaps I need to ensure when I load realdomain.com I go directly to a specific IP address instead of the default one that hits the load balancer.
There's a whole slew of reasons for having a hostsfile (especially for developers) that DNS doesn't solve.
Either Mozilla gets Firefox right and you are jumping up and down, or Mozilla screws up and you threaten to ditch the browser in favor Chrome.
Or I already did switch to chrome.
1) Rapid releases... Firefox should have just done rapid releases, or not. Their half-assed approach to "transitioning" towards rapid releases pissed off a lot of their user bases. And they still make a big show about the fact they're updating. Chrome has a simple little indicator that goes away as soon as you restart the browser.
2) Memory... FF memory bloat was a big deal for a long time. At least where Chrome had memory bloat and windows crashed, it didn't take down the whole browser. Again, FF waited too long to try to implement this.
3) Dev tools.... Firebug is great. Chrome's built-in tool is just as good. FF's new native inspector is a PITA and it fights with Firebug.
4) Synchronized Profiles.... Yes FF had it first, but Chrome makes it damn easy to setup and manage.
5) Security.... Why can't I temporarily accept an a self-signed ssl cert? Why do I have to go through multiple steps to "permanently allow this acception"? Compare this to Chrome's red warning screen with a single click for "I understand the risks".
6) HTML5 video..... FF's insistance on not doing any video other than Ogg was stupid and shortsided. If you're not going to bundle the codecs, offload the rendering to the OS. That's what the OS is there for after all. Most web video player packages out there will now auto-switch, giving Webkit HTML5 videos whereas FF still gets Flash players.
7) Retina Display..... I was seriously considering dropping Chrome as my primary browser on my new Mac because of this. The beta channel of Chrome did support it (but that brought other problems). However, the latest release of Chrome stable brings Retina Display support for my everyday browsing. Too bad FF.
8) Integrated search/address bar...... I know most/.ers hate this, but truthfully I've gotten very very used to it and as a result, I get pissed when I use a mobile browser and forget to use the correct input field to conduct a web search. You're telling the browser to go somewhere. Why do you need multiple always-on inputs to do that? Do you really need the extra input field just so you can specify which underlying destination identification process gets used to handle your request? No. The computer's smarter than that, and simpler UI is better here. This is why so many people type URLs into the Google homepage search field. They don't know why they would use the multiple input fields they're being presented with. Give them 1 field that's smart enough to do both use cases and you make it an easier experience.
9) Tabs..... Contrary to what/.ers moaned about... if the content of the field changes with the click of a tab, then the field should be within the tab, not outside of it. This is UI 101. FF fought against this and/.ers screamed bloody murder when they finally switched behaviors. Safari "solves" this by drawing their tabs inverted so that the address bar is within the tab and the viewing window is sperate. IE puts a tiny address bar next to the tab strip. Chrome is by far the right UI here.
10) Speaking of tabs.... And the dragging tabs off into new windows is still kludgy from a UI standpoint. Look at how Chrome does this compared to FF. As soon as my cursor moves the tab away from the strip, I get a new window. FF waits until I drop the tab, giving me a preview instead that looks like I'm dragging an image out of the browser, not moving a tab to a window.
Firefox was great. Mozilla offered a superior product for quite some time. They reminded everyone that there was still a lot of room for growth and improvement in the browser market. They forced MS to begin seriously developing IE again. Competition is a good thing in that it challenges all players to do better. But today? Meh... the Mozilla team is no longer top
Corning had been sitting on Gorilla glass since the 60s without putting anything into production. Then Apple came along in 2006 and said "we'll buy every gram you can possible produce".
I'd say Apple made the flat front possible. No-one else went shopping around to materials companies and said "I need X and am willing to pay for it". Everyone else put up with inferior materials until Apple changed the game.
The question is: can a competing product offer similar functionality without implementing those same design elements? If the answer is 'no', then the design patents should be invalid.
Yes, look at all the other Android, Windows, (even Palm and RIM if you want) devices out there that Apple isn't suing over.
And yet none of those pre-iPhone designs actually existed in the market.
Did Samsung show ALL their pre-iPhone designs? No, becuase you would see that the vast majority of their internal pre-iPhone designs didn't look anything like the iPhone. Just like none of their pre-iPhone releases looked like the iPhone.
The fact is, Samsung did not release a full-face touchscreen device until after the iPhone complete redirected the market. Combine this with the very similar styling, and copy-cat launcher iconography, and you have a court case.
You added a key new step there. Archiving is the same thing as moving something into a folder.
Labels by themselves are not (see my previous Google Docs example). Relying on labels exclusively requires new UI features to support certain types of workflows.
Give me Labels in addition to my folders and I'm happy to use them. Give me labels exclusively instead of folders and I'm not going to be happy. I limit my use of Google Docs precisely because this label issue prevents me from seeing what I feel is important when I first login to my documents.
The inadmissible evidence was revealed to the general public, not the court room. This is a civil trial, not a criminal one. There is far more leeway before the hammer of a mistrial comes down.
Wrong. Judges should not have to fear for their jobs just because they make an unpopular decision. Judges are expected to be neutral arbiters in a court of law, not the court of public opinion.
Slashdot Mirror
Yet they disabled the age-old shortcut command-shift-a, which brought up the Applications folder in the Finder. I used to use that because you could key-type the first few letters to find the app. They killed it.
However, 10.7 does add a keyboard search to the launchpad which 10.6 doesn't have. Makes launching apps about as fast as the old way.
If you're using phpMyAdmin, then you aren't doing the kind of in-depth database development where you run into the problems the GP is talking about.
Hell, if you're using phpMyAdmin, you're casual DB user probably just trying to support your small webapp or CMS installation.
And if you do use phpMyAdmin, you'd be much better off with a platform native database tool with MySQL support, such as SequelPro (OSX) or MySQL Workbench for (Windows,OSX)
Care share that web-based product for board meetings? I belong to some groups that could utilize a formalized system instead of ad-hocing it with Word via a projector.
The example I provided is the first of many treaties that cover patents. Most patent treaties essentially say "if you want us to respect patents filed in your country, you have to respect patents filed in ours".
STFU and learn how to use google before spouting off:
Here's just one example of a ratified patent treaty.
At one time Einsteins theories weren't testable either and were just neat thought experiments.
What do you mean "out of nowhere"? France was the first country to pass 3-strike laws for copyright violations and has been pushing this crap for years. /. covered this extensively 4 years ago... and I'm pretty sure it was on here even before that, but I'm too lazy to do more Googling.
I'm just surprised it's taken them this long to enforce the law.
Sounds more like her router isn't in bridged mode, so wired broadcast traffic isn't being sent out to wifi, essentially isolating the two networks for broadcast protocols.
She'd have the same problem with Windows until the router configuration is changed.
Yet somehow, when my new laptop showed up in early July, Chrome had support for retina display in the beta channel, and had it in the mainstream release 2 weeks or so later.
Mozilla's inability to implement features is not a good indicator of how difficult the API is to use. A big part of Mozilla's problem is that they insist on using their own font rendering engine for both the window chrome as well as the contents, instead of relying on the OS to do it.
Anything up to and including the entire planet being a blob of molten matter would be "not unprecedented".
Just because the world was really hot during the Jurassic does not mean that humans would enjoy living in that state again.
No, you invented the "need" as you declared the existing well-understood tools that have been available for decades to be unsuitable.
mmhmmm.... and how would that happen exactly? My company is behind a firewall and appear as a single IP. How would you target my machine specifically? And when I need to switch to another server behind the load balancer, or switch back to "normal" operation? Are you honestly suggesting wasting the time of the various admins and approvers multiple times, not to mention making changes to a production environment, just so that a dev doesn't change his host file while troubleshooting?
The load balancer is managed by a complete different department in the client's company. My contacts don't have direct access and have to formally request changes that can take hours or more to get made. Neither my direct client, nor my company, has the access permissions to make the necessary changes directly.
Sounds to me like you work in the kind of shop where anyone has access to do anything (and hence break anything) any time they want to any system they want. And you accuse me of not following best practices????
Tons of places don't mix IT and Dev.
IT here handles network, server admin, workstation deploy, network credentials, service and hardware provisioning, etc.
Dev is busy building apps, websites, and more for clients. Different projects have radically different architecture and infrastructure needs. Everything from a simple one-off HTML page to specialized Android builds to run on targeted embedded devices.
I have root acces to my workstation, and my workstation only. If I need to test something, I can test it on my workstation and not have to commit, get a deploy approved to staging environments, trigger the QA process, etc, etc. I don't, and shouldn't need, DNS admin abilities to do this. Screwing with DNS affects far more people around here than just me.
I have a real world example for you. I am working on a client's website we inherited a few months ago (~1 million visitors /month) troubleshooting some login issues. Because of the CMS, and a whole lot of legacy code, it currently requires absolute URLs to load resources. We were having a problem with sessions between servers. To isolate the problem, we needed to bypass the load balancer. However, because of absolute URL requirements, the site won't function properly if you visit www1.example.com. The only way for me to bypass the load balancer and ensure I was loading everything from one specific server was to edit my host file.
Now, short of DNS changes (which I don't have access to because it would affect at least 50 other people in my office and up to 1200 people across our corporate network) or admin access to my client's servers (even the client doesn't directly have this and has to submit formal request changes through their system engineering department) how should I go about guaranteeing I am targeting a specific server?
Thats great, but I don't have control over our internal DNS. IT does. However, I do have control over the hostfiles on my local dev workstation, and from there I can toggle to point to my local machine.
See, too lazy to put in s1.realdomain.com and s2.realdomain.com to get to servers 1 and 2 directly. DNS solves it all, but only if you tell it to.
That assumes the app you're working responds the same to s1.example.com as it does to www.example.com. That's not always the case. And in the cases where it doesn't, you may not have the authority to change the underlying behavior.
no, but dev.realdomain.com might be... and yet I have to overwrite it to simulate on my local machine for development testing. Or perhaps I need to ensure when I load realdomain.com I go directly to a specific IP address instead of the default one that hits the load balancer.
There's a whole slew of reasons for having a hostsfile (especially for developers) that DNS doesn't solve.
Why do you want x86 on a tablet if you don't want Windows?
If you want to run Linux well there's already Android on Atom and other processors.
Or I already did switch to chrome.
1) Rapid releases... Firefox should have just done rapid releases, or not. Their half-assed approach to "transitioning" towards rapid releases pissed off a lot of their user bases. And they still make a big show about the fact they're updating. Chrome has a simple little indicator that goes away as soon as you restart the browser.
2) Memory... FF memory bloat was a big deal for a long time. At least where Chrome had memory bloat and windows crashed, it didn't take down the whole browser. Again, FF waited too long to try to implement this.
3) Dev tools.... Firebug is great. Chrome's built-in tool is just as good. FF's new native inspector is a PITA and it fights with Firebug.
4) Synchronized Profiles.... Yes FF had it first, but Chrome makes it damn easy to setup and manage.
5) Security.... Why can't I temporarily accept an a self-signed ssl cert? Why do I have to go through multiple steps to "permanently allow this acception"? Compare this to Chrome's red warning screen with a single click for "I understand the risks".
6) HTML5 video..... FF's insistance on not doing any video other than Ogg was stupid and shortsided. If you're not going to bundle the codecs, offload the rendering to the OS. That's what the OS is there for after all. Most web video player packages out there will now auto-switch, giving Webkit HTML5 videos whereas FF still gets Flash players.
7) Retina Display..... I was seriously considering dropping Chrome as my primary browser on my new Mac because of this. The beta channel of Chrome did support it (but that brought other problems). However, the latest release of Chrome stable brings Retina Display support for my everyday browsing. Too bad FF.
8) Integrated search/address bar...... I know most /.ers hate this, but truthfully I've gotten very very used to it and as a result, I get pissed when I use a mobile browser and forget to use the correct input field to conduct a web search. You're telling the browser to go somewhere. Why do you need multiple always-on inputs to do that? Do you really need the extra input field just so you can specify which underlying destination identification process gets used to handle your request? No. The computer's smarter than that, and simpler UI is better here. This is why so many people type URLs into the Google homepage search field. They don't know why they would use the multiple input fields they're being presented with. Give them 1 field that's smart enough to do both use cases and you make it an easier experience.
9) Tabs..... Contrary to what /.ers moaned about... if the content of the field changes with the click of a tab, then the field should be within the tab, not outside of it. This is UI 101. FF fought against this and /.ers screamed bloody murder when they finally switched behaviors. Safari "solves" this by drawing their tabs inverted so that the address bar is within the tab and the viewing window is sperate. IE puts a tiny address bar next to the tab strip. Chrome is by far the right UI here.
10) Speaking of tabs.... And the dragging tabs off into new windows is still kludgy from a UI standpoint. Look at how Chrome does this compared to FF. As soon as my cursor moves the tab away from the strip, I get a new window. FF waits until I drop the tab, giving me a preview instead that looks like I'm dragging an image out of the browser, not moving a tab to a window.
Firefox was great. Mozilla offered a superior product for quite some time. They reminded everyone that there was still a lot of room for growth and improvement in the browser market. They forced MS to begin seriously developing IE again. Competition is a good thing in that it challenges all players to do better. But today? Meh... the Mozilla team is no longer top
Corning had been sitting on Gorilla glass since the 60s without putting anything into production. Then Apple came along in 2006 and said "we'll buy every gram you can possible produce".
Now almost every smartphone uses it.
I'd say Apple made the flat front possible. No-one else went shopping around to materials companies and said "I need X and am willing to pay for it". Everyone else put up with inferior materials until Apple changed the game.
Yes, look at all the other Android, Windows, (even Palm and RIM if you want) devices out there that Apple isn't suing over.
The metal rim around the side on the iPhone through iPhone 3GS is essentially flush with the surface of the device. I think you can agree that's a very different design than:
http://c2499022.cdn.cloudfiles.rackspacecloud.com/wp-content/uploads/2009/02/palm-centro-bell.jpg
I agree the Prada phone you showed looks pretty close to the iPhone 4. Did Prada apply for a Design Patent on it?
And yet none of those pre-iPhone designs actually existed in the market.
Did Samsung show ALL their pre-iPhone designs? No, becuase you would see that the vast majority of their internal pre-iPhone designs didn't look anything like the iPhone. Just like none of their pre-iPhone releases looked like the iPhone.
The fact is, Samsung did not release a full-face touchscreen device until after the iPhone complete redirected the market. Combine this with the very similar styling, and copy-cat launcher iconography, and you have a court case.
Design Patents != Functional Patents.
Design Patens are purely first to file.
You added a key new step there. Archiving is the same thing as moving something into a folder.
Labels by themselves are not (see my previous Google Docs example). Relying on labels exclusively requires new UI features to support certain types of workflows.
Give me Labels in addition to my folders and I'm happy to use them. Give me labels exclusively instead of folders and I'm not going to be happy. I limit my use of Google Docs precisely because this label issue prevents me from seeing what I feel is important when I first login to my documents.
The inadmissible evidence was revealed to the general public, not the court room.
This is a civil trial, not a criminal one. There is far more leeway before the hammer of a mistrial comes down.
Wrong. Judges should not have to fear for their jobs just because they make an unpopular decision. Judges are expected to be neutral arbiters in a court of law, not the court of public opinion.