Originally posted by cl333r
View Post
Announcement
Collapse
No announcement yet.
Firefox 99 Available With Strengthened Linux Sandbox, Web MIDI
Collapse
X
-
Originally posted by curfew View PostIt will also increase your web traffic and make the browser run slower without you even realizing what is going on. The effort is probably pretty futile anyway as advertising companies can detect this kind of behavior and filter out scripted clicks if it makes sense business-wise. It also doesn't make your data any less valuable after that.
The worst-case scenario is the inflation of displaying ads and price per click going down to zero. (This is happening already anyway, though, based on what I read elsewhere.)
Comment
-
Originally posted by cl333r View PostI just have the impression MIDI to music is the same as an animated GIF to video.
MIDI as the actual serial protocol that is used to send control events between computers, control interface (keyboard, but also control consoles, etc.) and devices (synths and expander boxes, but also controlled lights, etc.)
Used to be transmitted over 5-pin DIN connector, nowadays you'll find it over USB or even over more high-performance lines (over network).
They have something in common in that .mid files use the MIDI protocol to store the list of notes that needs to be player, but MIDI is used for much much much more than that.
- Likes 6
Comment
-
Originally posted by cl333r View Post
I just have the impression MIDI to music is the same as an animated GIF to video.
Anyhow, the online use is mostly learning services for keyboards and drums.
- Likes 3
Comment
-
Now I am wondering what's Google intent when bringin up WebMIDI? What's their use-case for having it in the browser?
- web apps on a web-only device like Chromebooks, so artists could use them on the go without needing to fumble with solutions to run linux containers and/or android apps?
- sharing instrument over internet, e.g., online jam sessions?
- Likes 1
Comment
-
Originally posted by ⤐⤐⤐⤐ View PostFirefox for me is slow as fuck and often freezes the computer, Chrome on other hand flies high in the skies.
It is also very sharp with fractional scaling on Wayland.
(I also have a bunch of adblocking extensions which may help in getting rid of slow running scripts etc)
- Likes 2
Comment
-
Originally posted by MrCooper View PostHas anyone worked out when Firefox‘s version number will overtake Chrome‘s, at their current release schedules?
But that is futile, nothing beats being the first to 100 :P
- Likes 2
Comment
-
Originally posted by curfew View PostIt will also increase your web traffic and make the browser run slower without you even realizing what is going on. The effort is probably pretty futile anyway as advertising companies can detect this kind of behavior and filter out scripted clicks if it makes sense business-wise. It also doesn't make your data any less valuable after that.
The worst-case scenario is the inflation of displaying ads and price per click going down to zero. (This is happening already anyway, though, based on what I read elsewhere.)
as for fighting against the script clicking, you can disable it if you wish, the ads will still load, or you can set it to rarely happen in an effort to avoid click filtering. both of which are still better financially for the sire then blocking the ads. and as you stated clicks are becoming worth less and less anyways, so I don't think it's much of a concern.
Comment
-
The only advantages Firefox has over Chrome(ium) at this point of time are- Works almost perfectly under Wayland with proper hidpi scaling. Chrome(ium) completely fucks up its scaling on hidpi displays and I'm always forced to fucking down-res the display from 4K to 1080 instead as a workaround.
- Works with almost all known drivers under Wayland. i915, i965, crocus, iris, nouveau, amdgpu, radeon, zink, llvmpipe...you name it. Especially nouveau, and even under Optimus. Chrome(ium) throws a fucking fit when used under Optimus conditions with the nouveau driver under Wayland.
- Works with IMEs like fcitx5 and ibus under Wayland, which is bloody important for Chinese and Japanese input. Chrome(ium) completely ignores IMEs on Wayland
- Doesn't tear under Wayland and redraws scrolling content properly when the browser is set to use software rendering and software compositing. Try running Chrome(ium) with --disable-gpu-compositing (which is absolutely fucking neccessary when trying to use it with drivers like nouveau) or --disable-gpu and watch the browser contents tear itself to hell or skip some scrolls to the point where the content displayed in the browser is completely unreliable; more than half the time the link you are clicking on is not what you think it is, but is instead another portion of the content that missed its scroll.
Last edited by Sonadow; 05 April 2022, 09:20 PM.
- Likes 5
Comment
Comment