/tech/ - Technology

Hell,_It's_about_time.-_J6-3l3hCm0.mp4
[Hide] (1.1MB, 1152x720, 00:07)

That took long enough, I'm glad to see this probably won't be another JPEG 2000 situation.

>>19124
Yeah, makes me happy. Finally. Just took years of fighting against Google with their fucking AVIF WEBP shittery.

png.png
[Hide] (3.4KB, 400x300)

jpg.jpg
[Hide] (3.2KB, 400x300)

gif.gif
[Hide] (4.1KB, 400x300)

>>19116 (OP) 
>let me guess, you need more

vecthrst.webp
[Hide] (12.3KB, 710x531)

>>19128
SVG when? Imageboards supported Flash through its entire run just fine, and many now support PDF. We don't need to put up with jaggies.

>>19128
I crossposted over here like a faggot cuz zzzchan has so little traffic and was also unreachable for me at times. (Yeah I know crossposting is not cool)
https://kohlchan.net/int/res/28443423.html
Already talked about that in depth there.

>>19132
It's complicated. In an <img> tag it's safe but what if you open it directly under the source address or download it and open it again? You'd need at least an svg sanitizer. For reasons like this it hasn't taken off as a user content format. The rendering speed is also less predictable than with raster graphics.

>>19132
Vector graphics are soulless. They're literally what spawned/enabled flat abstract UIs and the corporate "art" style. Any pictures with at least 0.01% artistic value use raster graphics as Kami intended.

>>19150
Shut the fuck up, retard. Corpo shit has nothing no to with vector graphics existing.

>>19150
Vector graphics and raster graphics have different uses. All letters on your screen are vector graphics. Most icons too unless you're using Windows. How complex vector graphics can get at what size and speed depends on the format and techniques used. SVG is kinda shitty compared to binary formats. Lots of xml trash. It's just the best we have that is widely implemented.
However vector graphics fulfill a really important role and in theory can depict literally everything a raster graphic can. Flat shapes are just the most simple thing to draw. However it's the same situation with raster graphics and shitty lines, text containing color antialiasing (makes sense on screens where it matches the monitor rgb pixel layout but not in a .png that is displayed on different monitors and often scaled) or whatever.

Qoi-logo-black.svg.png
[Hide] (26.4KB, 1280x579)

>more convoluted image formats with marginal filesize gains
No thanks.
If there's one image format that needs to be supported it's QOI. The spec is so simple you can't possibly fuck it up.

>>19153
>supported by nothing and made as a joke by guy who calls himself clueless
>anon brings it in jxl thread and is probably serious about it

Yukio-Miyamoto-4-768x830.webp
[Hide] (63.8KB, 768x830)

Yukio-Miyamoto-5-768x830.webp
[Hide] (134.7KB, 768x830)

>>19150
You have absolutely zero idea of what you're talking about. If carefully used, even Flash's old capabilities of simple linear/radial gradients are astonishingly versatile, and most professional vector software since the late '90s has far more sophisticated mesh gradients (admittedly not supported by mainline SVG in browsers, though PDF does) that can replicate essentially any kind of photographic or painterly content in the hands of a skilled artist.
>flat abstract UIs
All of which relied almost entirely on incredibly janky and bloated raster assets at the implementation level, even on HiDPI modes in Mac OS 10.7/Windows 8/GNOME 3 at peak phone cancer. And this is still true of the latest Android/iOS.

>>19154 
>lossless raster compression
Literally the most worthless type of codec for the web. Anything it can compress well (that didn't originate from a vector workflow to begin with!) can be trivially autovectorized, anything that can't will not compress.

Oh, also

>>19157
This is a little different, the main goal isn't to unify multiple standards though it JPEG XL does that as well, but simply to upgrade the technology in any way whatsoever.

Web image formats haven't been updated across all browsers since WebP in 2010 (not universally supported in browsers until 2020), built on the VP8 codec from 2008. JPEG in turn dates from 1992, built around basically just the h.261 codec from 1988. Needless to say, video codecs in web browsers have advanced considerably since the 1980s vintage.

vector_feathering.mp4
[Hide] (716.3KB, 1280x720, 00:05)

>>19159
>They're literally what spawned/enabled flat abstract UIs and the corporate "art" style
Some of that came from the hacky way SVG handled glows and shadows, which involved rasterizing the vector image into a bitmap and applying a gaussian blur to that bitmap. https://web.archive.org/web/20250814121344/https://rive.app/blog/how-rive-reinvented-feathering-for-the-vectorian-era is a pretty good article on it, from the perspective of some guys who rolled their own vector graphics format for a Flash replacement with an open source runtime but a closed source editor (sadly). Vid related is a demonstration of their vector feathering implementation that I ripped from the article.

>>19161
Yeah, that's disgusting. Don't use filters in SVG. They are raster based. Only use vector based features.
SVG wasn't even the first or only vector graphics format. At the time things went SVG it had retarded competitors like VML. I bet you don't even remember how bad things were. With no serious contenders SVG won by default. Maybe we'll get a better format one day. We can only hope.
https://en.wikipedia.org/wiki/Vector_Markup_Language

>>19162
I mean, Flash was right there, they could've just sent that to the ISO the same way they did with PDF & OpenType, but whatever, at least we have something that works and all the browsers support it. Or, speaking of PDF, they could've done what the NeWS people were tinkering with back before X killed it, and just dumped the entire SGML/XML idea to replace HTML/CSS/JS entirely with PostScript.
>With no serious contenders SVG won by default. Maybe we'll get a better format one day. We can only hope.
I don't think a single "file format" in the sense of SVG or Flash, where you can right-click on it to save and look at in your DE's image viewer is going to happen. Instead, when exporting vector assets for the web, you now target a mishmash of SVG, CSS, HTML5 <canvas>, and 2D WebGL/WebGPU.

>>19165
I'm not sure how declarative Flash is. The interpreted nature of PostScript is still a problem. Constantly these fucking sandbox escape vulnerabilities. It's hell.

>Instead, when exporting vector assets for the web
Most of the time people save to svg or rasterize.

>>19165
I think fonts are still used for symbols on many websites.

>>19166
It'd be no worse than the current problems with JS, or various other VM languages like Java itself that support quite fine grained permissions. I think the tradeoff would've been worth it, to gain a unified, far more elegant and powerful system, also extending throughout the OS much better.
>I'm not sure how declarative Flash is
Excepting, e.g., ActionScript? Completely. On the subject of PDF, partly for that exact reason Adobe shifted both PDF and Illustrator away from PostScript in 2000, to a new completely declarative internal data format.

>>19168
Java got removed from the web for good reasons.

>On the subject of PDF, partly for that exact reason Adobe shifted both PDF and Illustrator away from PostScript in 2000, to a new completely declarative internal data format.
It's very possible you're right. I have no clue about the internals of Flash. All I know is that most of it is proprietary and hard to work with using third party tools.
It just didn't happen. Without making a formal open image format it's not something that just happens randomly.