1y ago

Are we There yet? Current adoption status of various technologies

github.com GitHub - avidseeker/awesome-areweyet: Current adoption status of various technologies

Current adoption status of various technologies. Contribute to avidseeker/awesome-areweyet development by creating an account on GitHub.

Are we Wayland yet? Are we JPEGXL yet? Are we Rust yet?

I’ve gathered a meta-tracker for the adoption state of futuristic technologies.

Technology @lemmy.ml

Are we There yet? Current adoption status of various technologies

github.com /avidseeker/awesome-areweyet

35 0

Technology @lemmy.world

Are we

<INSERT_TECHNOLOGY_NAME>

yet?

github.com /avidseeker/awesome-areweyet

88 11

You're viewing a single thread.

33 comments

A reminder: Google added support for and then subsequently dropped JPEGXL support in Chrome. Fuck Google.
- If google had a baby she would drop it on its head.
  
  Out of malicious boredom.
  
  If Google had a baby she would ~~drop it on its head~~ spike it at the ground
- #8377 of useful thing Google killed.
  RIP Stadia 🙏
  
  Never even bothered with stadia after they killed inbox
  
  Stadia wasn't that good. Change my mind.
  
  I played high-end games I couldn't otherwise play, often at a discount, and then they refunded me at the end anyway. Pretty sweet deal
  
  Well you have to state why it wasn't good. It was incredibly region-dependent, but if you live near one of their endpoints the latency wasn't noticeable and the quality was great, as it was for me.
  In the end I got to play a bunch of games for free, and have an extra controller I still use, so there's that. They made us whole, at least, after they shut down (I even imported my into the breach save game into Steam with Google takeout after)
- Well of course. Those bastards want everyone to use their stupid WebP format.
  On a related note, how does JPEGXL compare to PNG? Does it support layers?
  
  I think so.
  https://cloudinary.com/blog/how_jpeg_xl_compares_to_other_image_codecs
  
  I will check that link out. Thank you. :)
  
  What is it with this obsession with JPEG-XL? I keep seeing it mentioned on lots of threads, but as a user, the benefits seem marginal? Like: would be nice, but I'd expect more significant benefits from something that's brought up this often - so which benefits am I missing?
  
  Honestly? I agree with you that the benefits seem kind of marginal. But I still think it's a fascinating thing. :)
  Edit:
  On doing some reading about it and trying it out for myself, the file size reductions are hardly marginal. It's actually quite impressive. Still, it seems for most people, including myself, that jpeg for lossy & png for lossless is more than adequate, especially with how cheap storage is nowadays.
  (And, frankly, I appreciate seeing at a glance if an image is lossy or lossless, but I imagine that's a priority most people don't have. Lol.)
  
  Yeah that's what I mean - it's not that the file size reduction is minimal, but that the benefits of that are fine, but not earth-shattering.
  
  Yeah, I can agree with that.
  
  What's wrong with webp if its Foss?
  
  Because it's yet another example of Google's near-monopoly over the Web's architecture. It's not healthy for good web development. It's like the 90s and Microsoft all over again.
  I mean, fuck, we're already getting websites that've been "optimized" for Chromium-based browsers—in other words, semi-broken for non-Chromium browsers.
  
  If its FOSS, then it can't be a monopoly, by definition
  
  I said a near-monopoly. Also, even if it's foss, by creating the format, they established the baseline parameters of that format.
  That gives them a significant degree of control.
   
  Edit: I also hate it because so many of the programs I use don't support it, so I constantly have to copy > paste into image editor program > Save as PNG.
  Though admittedly this is mostly an adoption thing. Still, it's a major problem.
  
  Google has discovered that FOSS software under their full control is better than pure proprietary software for monopoly abuse and rent seeking. With FOSS software, they enjoy the automatic popularity that they otherwise would have had to market very hard for. At the same time, none of Google's free software is truly free. Google devs regularly neglect and reject overwhelming user requirements (jpegxl in chrome is probably the best example of this) and choose designs that clearly favor the company monetarily. It isn't even practical for normal people to fork their projects.
  Google often uses their 'FOSS' projects to twist open standards or the market to their advantage. Android and Chrome are very significant players in this regard. Using Chrome, Google even managed to make the W3C standard too complicated for others to make alternative browsers easily. Google has similar ambitions in the multimedia market. They want to replace the monopolistic media formats with quasi-monopolistic formats like webp and av1 instead of truly open ones like jpegxl.

33 comments