Comment Re:Frustration over being public? (Score 2) 611
Um, Assad?
Um, Assad?
Ethics is an interesting discussion. The road is a finite resource for which demand exceeds supply. As a result, there is already rationing taking place - in the form of waits times to use the road: congestion. This is, on the surface, very "fair" and "egalitarian", but also very wasteful of time, gasoline, pollution, and wear-and-tear on equipment.
On the other hand, a system that lets poor people get where they want to go, albeit by bus, faster and more cheaply than before also could be deemed "fair". You'd have only affluent people driving, so that would create a societal divide.
I guess my answer is: I don't know.
Thank you, finally a future subject who "gets it". You'll go far in my administration.
Are you sure about that? I would think that clogging the roads is an inefficient use of infrastructure.
If I were dictator, I'd toll the roads as high as need be until traffic levels come down to designed capacity. If there is some excess cash after paying for maintenance, this would subsidize a bus route along the same now-free-flowing highway(s). The bus would actually be attractive, since it would be cheap and fast instead of simply stuck in traffic.
Then I'd jail or execute my political rivals and invade Canada.
You mean like people who want to prevent people from using their public street because it makes it unpleasant to walk the dog?
People who use JPEG for images with text in them should be burned at the stake, slowly. Partly because it would solve a significant chunk of the population bomb - there are a lot of them around. But mostly because it is just WRONG. However an image handling protocol which can handle text reasonably well and photographic images very well, would be a very good thing.
We have more bandwidth
You clearly don't have to pay for serious bandwidth. If you were running a significant site, you might have remembered re-processing your GIFs to PNGs, partly because of the threat of patent bullshit, and partly to reduce your bandwidth costs. And the effect works in the other direction too - on my work site (currently moving from West Africa to Turkey) we have 1Mbps available for all business and personal purposes of the up to 180 POB (Personnel On Board). That's not going to be upgraded - why would it?) But chopping a considerable chunk off the size of each photographic image loaded would have a considerable effect.
You may not have a use case for this sort of change. But other people do.
As soon as Photoshop and Firefox/Chrome start supporting it I can see widespread adoption.
Irfanview would be the crunch application for me. And yes, I might well make a new payment (I've already brought one copy) if it would fund the writing of the module.
Up to 14 bits/pixel/channel (does that include the alpha-channel? If TFA included it, I missed it.) would certainly be a major step up from 8bppc in JPEG, though I do occasionally handle data from 16bppc astronomical sensors, and I wonder about HDR photography, so I wonder if pushing up to 16bppc is feasible. We do have FITS for handling the astronomical data, and TIFF for medical up-to-32bppc imaging, so it's not necessarily unworkable. Actually, considering that this is, by design, a lossy format
Bellard seriously knows his coding. Impressive breadth of contributions to the world over the years.
Are you having fun yet?