Skip to main content ↑ ↓
Topic: Keeping an eye on Opera (Read 169475 times)

Re: Keeping an eye on Opera

Reply #375 –
Quote from: Frenzie on
Anyway, Opera's better than Chromium; over the next months we'll see if it has anything on Iceweasel/Firefox with Tab Mix Plus as a secondary browser.
So far, O 24 Dev for Linux is surprisingly light here. With 7 tabs open, all the Opera processes together were only ~250 megs, better than what I would expect out of Chromium or Firefox. There was an odd issue in which Chrome's Peppeflash would crash everytime, so I had to download the PF from the Ubuntu repos and copy it /opt/google/chrome/PepperFlash, overwriting existing flashplayer. Other than that, it seems better behaved than standard Chromium as far as both resource usage and stability goes.

Re: Keeping an eye on Opera

Reply #376 –
Quote from: Sanguinemoon on

Quote from: Frenzie on
Anyway, Opera's better than Chromium; over the next months we'll see if it has anything on Iceweasel/Firefox with Tab Mix Plus as a secondary browser.
So far, O 24 Dev for Linux is surprisingly light here. With 7 tabs open, all the Opera processes together were only ~250 megs, better than what I would expect out of Chromium or Firefox.

Traitors!! :irked:

Sure that Chromium/Chrome is lacking featurewise and is heavy resourcewise - plus eerily Googleous -, but to me this makes it all the more obvious that anything too closely based on it has the same problems. Those things will never touch my machines! (despite of being available in AUR)

But I have tried and am trying sufficiently departed browsers, such as Qupzilla, Midori, Luakit, Otter. Single-process architecture performs better, there is more attention on interface responsiveness, configuration options, and features that used to be historically normal in browsers. That's good stuff.

The sad thing is when development on them slows down or halts, the way it seems to have happened for example with Luakit. The project was started with perfect plentiful detailed documentation, so anyone with sufficient skills can pick it up and continue, but yeah...

Re: Keeping an eye on Opera

Reply #378 –


Opera's desktop browser is continuing its irresistible march to the South.
Would be interesting to know how many old Presto browsers are still accounting for those fantastic 0,85%.

Re: Keeping an eye on Opera

Reply #379 –
The South is not bad. :irked:
As a whole, mobile browsers are getting a bigger share. It would be interesting to have statistics on desktop browsers only.

Re: Keeping an eye on Opera

Reply #381 –
Everybody means that.  :furious:
:coffee:

Re: Keeping an eye on Opera

Reply #382 –
I'm not sure what to make of this. The Opera crash reporter dialog hasn't been working for me for about a year. (Opera/Presto may crash infrequently, but it does crash on occasion.) But it just crashed and reporting actually worked. Was it just broken on my end?

Re: Keeping an eye on Opera

Reply #383 –
Quote from: krake on

Would be interesting to know how many old Presto browsers are still accounting for those fantastic 0,85%.

Don't these stats directly depend on how the user-agent identifies itself and isn't it so that Chropera inevitably identifies itself as Chrome? If yes, then this means that only Presto and Presto Mobile leave tracks as "Opera" in the stats.

Or is there some hidden little marker in the user-agent string to identify Chropera as "Opera"? In which case doesn't it mean that the stat-bots must update themselves to the fact? What motivation would the have for this? 

Quote from: Frenzie on

I'm not sure what to make of this. The Opera crash reporter dialog hasn't been working for me for about a year. (Opera/Presto may crash infrequently, but it does crash on occasion.) But it just crashed and reporting actually worked. Was it just broken on my end?

You report Presto's crashes? Warum?
[video]https://www.youtube.com/watch?v=YKKGxNzJnqQ[/video]

Goethe's lyrics :sing:
 

Re: Keeping an eye on Opera

Reply #384 –
Quote from: ersi on
Or is there some hidden little marker in the user-agent string to identify Chropera as "Opera"? In which case doesn't it mean that the stat-bots must update themselves to the fact? What motivation would the have for this?

Yes, just like every browser using the Webkit or Blink engine.

For example, I'm posting this from:
Code: [Select]
Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.143 Safari/537.36 OPR/23.0.1522.77

Note the very end.

Quote from: ersi on
You report Presto's crashes? Warum?

You have to press either "don't report" or "report" for it to restart, so that's one reason. :P

Re: Keeping an eye on Opera

Reply #385 –
Quote from: Frenzie on

Code: [Select]
Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.143 Safari/537.36 OPR/23.0.1522.77

Note the very end.

Ja. Und I note how the forum software registers this as Chrome among your other user data beside the post.

Re: Keeping an eye on Opera

Reply #386 –
Well, technically it stores the user agent and generates the display stuff on the fly. If I get around to modding the thing I probably intend to have it display the actual user agent on hover or something.

Re: Keeping an eye on Opera

Reply #387 –
That sounds cute.

But in terms of universal browser statistics on the web, do you know how the browser-sniffer data is organised and presented by those various stats organisations? Do they do anything more than just applying one of the major icons to the string and drawing a nice table with stats?

Re: Keeping an eye on Opera

Reply #388 –
Quote from: ersi on
But in terms of universal browser statistics on the web, do you know how the browser-sniffer data is organised and presented by those various stats organisations? Do they do anything more than just applying one of the major icons to the string and drawing a nice table with stats?

I wouldn't count on it, but to be fair knowing the popularity of rendering engines is in many ways more relevant than knowing the specific browsers involved. Then again, stuff like Google Analytics is full of Javascript, so I guess at least some of it has to serve some kind of useful detection purpose…

Re: Keeping an eye on Opera

Reply #389 –
If Chromium and Opera/Blink block your GPU for some reason, you can test GPU acceleration with:
Code: [Select]
opera-developer --ignore-gpu-blacklist


Apparently Chromium blacklisted everything ATI back in 2011. They unblocked newer fglrx but apparently never unblocked any of the newer really quite nice open-source Gallium drivers (cf. Mozilla which did).

Code: [Select]
Driver Information
Initialization time	142
Sandboxed	false
GPU0	VENDOR = 0x1002, DEVICE= 0x6810
Optimus	false
AMD switchable	false
Driver vendor	Mesa
Driver version	10.2.6
Driver date	
Pixel shader version	1.30
Vertex shader version	1.30
Machine model name	
Machine model version	
GL_VENDOR	VMware, Inc.
GL_RENDERER	Gallium 0.4 on llvmpipe (LLVM 3.4, 128 bits)
GL_VERSION	3.0 Mesa 10.2.6
GL_EXTENSIONS	GL_ARB_multisample GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_copy_texture GL_EXT_polygon_offset GL_EXT_subtexture GL_EXT_texture_object GL_EXT_vertex_array GL_EXT_compiled_vertex_array GL_EXT_texture GL_EXT_texture3D GL_IBM_rasterpos_clip GL_ARB_point_parameters GL_EXT_draw_range_elements GL_EXT_packed_pixels GL_EXT_point_parameters GL_EXT_rescale_normal GL_EXT_separate_specular_color GL_EXT_texture_edge_clamp GL_SGIS_generate_mipmap GL_SGIS_texture_border_clamp GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_ARB_framebuffer_sRGB GL_ARB_multitexture GL_EXT_framebuffer_sRGB GL_IBM_multimode_draw_arrays GL_IBM_texture_mirrored_repeat GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_transpose_matrix GL_EXT_blend_func_separate GL_EXT_fog_coord GL_EXT_multi_draw_arrays GL_EXT_secondary_color GL_EXT_texture_env_add GL_EXT_texture_lod_bias GL_INGR_blend_func_separate GL_NV_blend_square GL_NV_light_max_exponent GL_NV_texgen_reflection GL_NV_texture_env_combine4 GL_S3_s3tc GL_SUN_multi_draw_arrays GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_EXT_framebuffer_object GL_EXT_texture_compression_s3tc GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_MESA_window_pos GL_NV_packed_depth_stencil GL_NV_texture_rectangle GL_ARB_depth_texture GL_ARB_occlusion_query GL_ARB_shadow GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_mirrored_repeat GL_ARB_window_pos GL_EXT_stencil_two_side GL_EXT_texture_cube_map GL_NV_depth_clamp GL_NV_fog_distance GL_APPLE_packed_pixels GL_APPLE_vertex_array_object GL_ARB_draw_buffers GL_ARB_fragment_program GL_ARB_fragment_shader GL_ARB_shader_objects GL_ARB_vertex_program GL_ARB_vertex_shader GL_ATI_draw_buffers GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_MESA_pack_invert GL_MESA_ycbcr_texture GL_NV_primitive_restart GL_ARB_depth_clamp GL_ARB_fragment_program_shadow GL_ARB_half_float_pixel GL_ARB_occlusion_query2 GL_ARB_point_sprite GL_ARB_shading_language_100 GL_ARB_sync GL_ARB_texture_non_power_of_two GL_ARB_vertex_buffer_object GL_ATI_blend_equation_separate GL_EXT_blend_equation_separate GL_OES_read_format GL_ARB_color_buffer_float GL_ARB_pixel_buffer_object GL_ARB_texture_compression_rgtc GL_ARB_texture_float GL_ARB_texture_rectangle GL_ATI_texture_compression_3dc GL_EXT_packed_float GL_EXT_pixel_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_rgtc GL_EXT_texture_mirror_clamp GL_EXT_texture_rectangle GL_EXT_texture_sRGB GL_EXT_texture_shared_exponent GL_ARB_framebuffer_object GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_packed_depth_stencil GL_ARB_vertex_array_object GL_ATI_separate_stencil GL_ATI_texture_mirror_once GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_gpu_program_parameters GL_EXT_texture_array GL_EXT_texture_compression_latc GL_EXT_texture_integer GL_EXT_texture_sRGB_decode GL_EXT_timer_query GL_OES_EGL_image GL_ARB_copy_buffer GL_ARB_depth_buffer_float GL_ARB_draw_instanced GL_ARB_half_float_vertex GL_ARB_instanced_arrays GL_ARB_map_buffer_range GL_ARB_texture_rg GL_ARB_texture_swizzle GL_ARB_vertex_array_bgra GL_EXT_texture_swizzle GL_EXT_vertex_array_bgra GL_NV_conditional_render GL_AMD_conservative_depth GL_AMD_draw_buffers_blend GL_AMD_seamless_cubemap_per_texture GL_ARB_ES2_compatibility GL_ARB_blend_func_extended GL_ARB_debug_output GL_ARB_draw_buffers_blend GL_ARB_draw_elements_base_vertex GL_ARB_explicit_attrib_location GL_ARB_fragment_coord_conventions GL_ARB_provoking_vertex GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_shader_texture_lod GL_ARB_texture_multisample GL_ARB_texture_rgb10_a2ui GL_ARB_uniform_buffer_object GL_ARB_vertex_type_2_10_10_10_rev GL_EXT_provoking_vertex GL_EXT_texture_snorm GL_MESA_texture_signed_rgba GL_ARB_get_program_binary GL_ARB_robustness GL_ARB_separate_shader_objects GL_ARB_shader_bit_encoding GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_NV_vdpau_interop GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ARB_conservative_depth GL_ARB_internalformat_query GL_ARB_map_buffer_alignment GL_ARB_shading_language_420pack GL_ARB_shading_language_packing GL_ARB_texture_storage GL_ARB_transform_feedback_instanced GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_transform_feedback GL_AMD_shader_trinary_minmax GL_ARB_clear_buffer_object GL_ARB_invalidate_subdata GL_ARB_texture_storage_multisample GL_ARB_vertex_attrib_binding GL_KHR_debug GL_ARB_multi_bind GL_ARB_texture_mirror_clamp_to_edge GL_ARB_vertex_type_10f_11f_11f_rev GL_EXT_shader_integer_mix
Window system binding vendor	SGI
Window system binding version	1.4
Window system binding extensions	GLX_ARB_create_context GLX_ARB_create_context_profile GLX_ARB_fbconfig_float GLX_ARB_framebuffer_sRGB GLX_ARB_multisample GLX_EXT_create_context_es2_profile GLX_EXT_framebuffer_sRGB GLX_EXT_import_context GLX_EXT_texture_from_pixmap GLX_EXT_visual_info GLX_EXT_visual_rating GLX_MESA_copy_sub_buffer GLX_OML_swap_method GLX_SGI_swap_control GLX_SGIS_multisample GLX_SGIX_fbconfig GLX_SGIX_pbuffer GLX_SGIX_visual_select_group GLX_INTEL_swap_event
Direct rendering	Yes
Reset notification strategy	0x8261
GPU process crash count	0


Oddly enough, a test like http://dinohunt2.ivank.net/ runs smoothly in Opera/Presto,  in Iceweasel, as well as in chromium --ignore-gpu-blacklist, but not in Opera Developer.

Re: Keeping an eye on Opera

Reply #390 –
I don't know when it happened exactly, but Opera/Blink is in some subtle ways more Opera-like than it was at first. Several of its keyboard shortcuts (like F8 to the addressbar) have returned to the default installation and flip back/forward seems to work well. I haven't started Chromium for Blink testing in weeks.

Re: Keeping an eye on Opera

Reply #394 –
Amazing! :up:

Re: Keeping an eye on Opera

Reply #395 –
https://share.opera.com/e461b3ceb3f7486cae781c6dd1544d7b[/quote]
But seems to have lost its ability to import bookmarks for at least a couple releases already. For a browser so heavily invested in the mobile market, I would think syncing would be job one. Who really cares if the latest version if Chromium can do a few things no website has actually implemented yet if there's not an obvious way to carry your bookmarks wherever you go?

Re: Keeping an eye on Opera

Reply #397 –
I'm getting near to the point of dropping Opera presto and moving permanently to firefox.
So many sites that I visit are no longer working correctly with presto and it's beginning to get tedious using "open with ff" so often.
The start and end to every story is the same. But what comes in between you have yourself to blame.

Re: Keeping an eye on Opera

Reply #398 –
So in Firefox, how would one do something that's extremely simple in Opera like
Code: [Select]
Button6, "InFx"="Execute program, "firefox", "%u", "InFx", "Firefox""

In other words, I want to execute a program on my computer (like another browser, youtube-dl, etc.) with the URL of the page I'm looking at as an argument.

And while we're at it, can it be done in Opera/Blink?

Re: Keeping an eye on Opera

Reply #399 –
Quote from: Frenzie on

Quote from: ersi on
Or is there some hidden little marker in the user-agent string to identify Chropera as "Opera"? In which case doesn't it mean that the stat-bots must update themselves to the fact? What motivation would the have for this?

Yes, just like every browser using the Webkit or Blink engine.

Well...
Code: [Select]
Mozilla/5.0 (X11; NetBSD) AppleWebKit/537.6+ Midori/"0"."4"