Chrome : Shiny and/or toxic?

Yesterday I installed Google's new toy: The Chrome webbrowser. The looks are very slim as it's using your full screen, nice fonts, no needless borders and I really like the tabs at the top! So it's shiny like chrome...
And Google claims that Chrome is also very fast. Indeed a lot of pages seems to render more quickly than FF or IE did. But I also noticed that on some sites pictures or other more advanced/heavy features are shown half or aren't loaded at all. That way it is easy to claim to have the fastest browser...
But remember how Google earns it's money! It sells adds on their search pages. The better the advertisements fits the fervour of the searcher, the higher the number of hits, the higher the fee. So Google looks for the adds based on your current search...and your previous searches. I think they also record the results you click on (if you look at the source code of a search result page, you can see that the links are not 'just links', but there is also a javascript function executed when you click on them). But until now Google only gathers information when using their search engine.
But what happens when you use a Google browser? When Google can track all your internet traffic by their own browser, they can show you advertisements based on your complete internet history, so matching your fascination even better, and thus earning more money.
Remember, Chrome (or Chromium) is shiny and toxic (wikipedia)!
Or am I just being paranoid?

Comments

Filtering in the APEX Interactive Grid

Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the APEX_IR.ADD_FILTER procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good old Employ

apex_application.g_f0x array processing in Oracle 12

If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one: then you disable the " Escape special characters " property and the result is an updatable multirecord form. That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for

Stop using validations for checking constraints !

If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department". And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function

Roels Blog

Search This Blog