Readit News logoReadit News
ioasuncvinvaer commented on I'm too dumb for Zig's new IO interface   openmymind.net/Im-Too-Dum... · Posted by u/begoon
BobbyJo · 4 days ago
A signal is something you use to discern something in lue of direct information. In the case of docs, just look at them and if they suck, or are good, it doesn't really matter where they came from. That being said, Ill take AI generated docs over no docs, and no docs is very common.
ioasuncvinvaer · 4 days ago
But how do you know if you can trust the docs if they are AI generated?
ioasuncvinvaer commented on I'm too dumb for Zig's new IO interface   openmymind.net/Im-Too-Dum... · Posted by u/begoon
pixl97 · 4 days ago
I mean, the quality of docs before AI was pretty low quality and forums everywhere were filled with complaints about it, except in the case of a few exceptional pieces of software. If this is the case, just having docs at all seems to be a signal of low quality.
ioasuncvinvaer · 4 days ago
No! Well written docs are a sign of quality. Obviously AI generated docs make me question whether they are actually correct which makes them useless.
ioasuncvinvaer commented on I'm too dumb for Zig's new IO interface   openmymind.net/Im-Too-Dum... · Posted by u/begoon
throwawaymaths · 4 days ago
> you're much more likely to build confusing, difficult-to-use APIs.

have not found this to be the case with zig in general. you could easily make the opposite argument, that documenting things (especially quirks) can give you license to build confusing APIs.

ioasuncvinvaer · 4 days ago
I think some documentation and a handful of examples would have helped the author of the article. How is the experience when porting to the new standard library improved by not including documentation?
ioasuncvinvaer commented on I'm too dumb for Zig's new IO interface   openmymind.net/Im-Too-Dum... · Posted by u/begoon
BobbyJo · 4 days ago
Just because and AI produced it doesn't mean it is slop.
ioasuncvinvaer · 4 days ago
But it is a pretty good signal of low quality.
ioasuncvinvaer commented on XSLT removal will break multiple government and regulatory sites   github.com/whatwg/html/is... · Posted by u/colejohnson66
basscomm · 4 days ago
Because you can do things with XSLT that you can't do with pure HTML

For instance, I can provide an XML file that is a list of widgets, and then I can use to XSLT to give you a table with the values sorted in some way. I can't do that with plain HTML, I'd have to invoke Javascript or something.

ioasuncvinvaer · 4 days ago
When you program a list of widgets you can program it against anything though. Whether its xml or html.
ioasuncvinvaer commented on XSLT removal will break multiple government and regulatory sites   github.com/whatwg/html/is... · Posted by u/colejohnson66
sennalen · 4 days ago
keeping data orthogonal to presentation
ioasuncvinvaer · 4 days ago
How is html not data?
ioasuncvinvaer commented on XSLT removal will break multiple government and regulatory sites   github.com/whatwg/html/is... · Posted by u/colejohnson66
Izkata · 4 days ago
You're thinking of XML, not XSLT. XSLT is a language for transforming XML into other structures.
ioasuncvinvaer · 4 days ago
But why would a server send me xml instead of html? From the thread you can see that the servers already serve html so why is there a second way to present that content via xslt?
ioasuncvinvaer commented on XSLT removal will break multiple government and regulatory sites   github.com/whatwg/html/is... · Posted by u/colejohnson66
youngtaff · 4 days ago
How do you create a HTML RSS feed?
ioasuncvinvaer · 4 days ago
By rendering it on the server and serving it to the client.
ioasuncvinvaer commented on XSLT removal will break multiple government and regulatory sites   github.com/whatwg/html/is... · Posted by u/colejohnson66
troupo · 4 days ago
> WHATWG have removed features before, e.g. frameset, font, and applet elements from HTML.

font: supported in all browsers https://caniuse.com/?search=font

frameset: supported in all browsers https://caniuse.com/?search=frameset

applet: supported in all browsers https://caniuse.com/?search=applet

> All of them were rarely used and had better alternatives available.

"Rarely used" is not enough of a justification

ioasuncvinvaer · 4 days ago
So a feature was removed from the spec and it is still supported. I don't see how it would be bad to remove XSLT then?
ioasuncvinvaer commented on XSLT removal will break multiple government and regulatory sites   github.com/whatwg/html/is... · Posted by u/colejohnson66
mmastrac · 5 days ago
It really should just be compiled to WASM and used with some sort of DOM bridge.
ioasuncvinvaer · 4 days ago
The google people provided exactly that. A WASM polyfill.

u/ioasuncvinvaer

KarmaCake day58October 23, 2023View Original