I would definitely not say that we re-invented pacing! One version of the question we looked at was: how low a pace rate can you pick for an ABR algorithm, without reducing video QoE? The part which takes work is this "without reducing video QoE" requirement. If you're interested, check out the paper!
We looked at latency-insensitive like YouTube and Netflix (which were a bit more than 50% of internet traffic last year [1]).
I'd bet you could do something similar with Meet and Zoom–my understanding is video bitrates for those services are lower than for e.g. Netflix which we showed are much lower than network capacities. But it might be tricky because of the latency-sensitivity angle, and we did not look into it in our paper.
One of the solutions they mention is underutilizing links. This is probably a good time to mention my thesis work, where we showed that streaming video traffic (which is the majority of the traffic on the internet) can pretty readily underutilize links on the internet today, without a downside to video QoE! https://sammy.brucespang.com
I'm not even finished with it, but it has still introduced me to Lisp, functional programming, artificial life, and web servers as well completely changed the way I program.
It's to make what was done (which is important to the paper) seem important and make who did it (which is less important to the paper) seem unimportant.
For a photoshop-like web design tool, it would probably be a poor idea to have it output to HTML + CSS, as it would be insanely difficult to get remotely decent HTML + CSS (especially HTML + CSS that responds to interaction well). Even if you managed that, any decent front-end developer would probably rewrite it themselves to get the best interaction, "bulletproof-ness", and optimization possible. What would be far more useful is a design tool that incorporates HTML + CSS by using them for the layout of the image, but doesn't attempt to write them decently. Doing so would make it easy to use CSS to quickly change something like the font, while not trying to write decent front-end code.
In addition, I'd love it if this tool had the following. Even if it only had one of these things, I'd probably buy it.
1. Way to easily deal with text. In photoshop, text is a pain to deal with, especially for things like navigation. If there was a way to easily style the text of a file with css in addition to a gui method, things would be much more pleasurable and efficient.
2. Decent ways to include header, sidebar, and footer elements. Currently, a designer has to duplicate these across multiple files which makes updating even a snippet of text an arduous process involving opening many files.
3. A common browser element palette. Currently the only solution (That I know of), is to get a psd with the elements pre-made and try and fit whatever you get with into a design, which makes things like adding decent amounts of text to buttons rather bothersome.
If a user searches for something like 27" iMac, there are no results, but if the user searches for 27 iMac, the 27" imac is found. It might be good to strip any "'s in the add field before searching.
I count calories and try to stick to a consistent limit, and bike around 8 miles Monday through Friday. It's probably the 8 miles of biking that provides the benefit.
True, but it's not just grid computing they're running automatically.
They also make it difficult to disable the grid computing (It's under "Support Digsby"), and they try to get the user to install six different pieces of crapware.
They do this under the guise of being ad free, but in reality they're advertising by sending out Announcements, which seems pretty shady to me.