That was wonderful, thank you!
1,253 karma · joined April 15, 2013
I've never used it so can't speak from any experience, and unfortunately it doesn't seem particularly active (and doesn't mention a current status anywhere), and doesn't have a license, so shrug. When it's been posted here (https://news.ycombinator.com/item?id=40211891), people seemed pretty excited about it.
Specifically, "Users may link this kernel with closed-source binary drivers, including static libraries, for personal, internal, or evaluation use without being required to disclose the source code of the proprietary driver.".
Both Mithril and Preact use virtual DOMs:
David Lynch
I just learned about direct vs indirect eval (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...), which I imagine makes this a bit easier. The parent scope is only captured in a direct eval.
Surely this is feigning surprise. The oldest thing in that list is like 18 months old or something, and he's surprised to find literally any programmers that don't use them? I bet I could find a programmer out there who's never used Google, let alone brand new subscription AI services.
He last commented on HN four days ago: https://news.ycombinator.com/threads?id=idlewords
And regardless of the numbers, I also wonder at what rate people are actively switching to Bluetooth because they want to vs. because that's what their preferred phone line is forcing them into.
> why do you just take it?
Must be my insatiable masochism.
I mean, it's hard to say whether it's a bug in my reader, given that the RSS spec makes no mention of how relative links should work. I've variously used Newsbeuter, Newsboat, Newsblur, and The Old Reader and have never not had this problem.
(Edit: an example from this morning: Newsblur didn't know what to do with the footnote links in Dan Luu's blog [https://danluu.com/atom.xml]. Aside: Newsblur seems to be responding with 500s for about every other request today. sigh isn't technology wonderful?)
> Having RSS completely static means that hosting an RSS feed is super simple and does not require the increased attack potential of a dynamic service - something that the current federated web protocols completely fail at.
Pagination would work fine with static hosting. And "updates-since" requests wouldn't preclude static hosts from ignoring them and working exactly how they work now.
I agree with you about federated web protocols though - I'm pretty bummed ActivityPub requires an inbox, otherwise I think it would pretty much work with static hosting.
> I don't think creating a separate RSS-only web of links makes sense.
You're right, it doesn't really make sense. I think the crux of my frustration there is that we've got a syndication system that's bolted on top of the web, rather than properly integrated. It's probably the best that can be done though, without an entire separate hypertext system.
> Lots? Really? iframes are more dead than RSS, at least for anything outside of ads.
Youtube and Vimeo embeds are mostly where I see them.
>> or content that only makes sense with JS enabled
> Limiting RSS to static mostly-text content provides a lot of consistency.
I'm not complaining that feed items can't execute Javascript; I'm annoyed that sometimes the (textual) content of the post refers directly to other content that's only there after JS adds it. (I'm not blaming authors, this is just a problem of the content being written for a webpage and then being included in a different context. Again, an issue of the syndication system having been bolted onto the web.)
> Ugly, yes, but how is this a problem in practice? Just because it's not as hip as JSON?
No, I don't particularly love JSON either. XML does indeed work okay, but I pretty regularly (a couple times a year, maybe?) see broken feeds because of mis-escaped content. I think one of the feed generators of someone I follow produces bad CDATA tags too. Pretty hard to mess up JSON escaping (as much as HTML-in-JSON makes me shudder).
It was probably a mistake to resurrect this flame war about serialization formats. XML works, it's just a bummer.
Yeah! I'm with you. Although I don't use it, I really like some of the features of https://fraidyc.at/. For the majority of feeds I follow, I don't need to keep track of unread status, and high-frequency feeds would be much more bearable if they were grouped together to avoid taking over an aggregated listing. I feel like a lot of client defaults tend to hew too closely to email clients or something.
"Should" indeed. But a standard that isn't followed isn't exactly helpful to me.
> This is working as intended and not an issue. I don't think any alternatives would make sense.
Yeah, I agree that an alternative doesn't make sense for RSS in particular, but it's not hard to imagine an only-slightly-more-featureful syndication system where individual feed items are directly addressable.
It's just a shame that I've got this really nice, personalized feed reading interface, and I get pulled out of it every time I follow a link.
- every day I deal with broken links and broken images because my feed reader doesn't know from which URL it should resolve relative links
- there's no pagination mechanism, or way for a client to ask for "all posts since last Friday". If you want your feed to always have all posts available, you need to include the entirety of your archive in every feed response.
- if I want to follow any link I get kicked back out to a bloated web page
- lots of posts include iframes, or content that only makes sense with JS enabled
- XML
Despite this, I still love RSS. It's what we've got and we should continue to make the most of it. But it also sucks, and it's not any surprise that mostly only technical people use it. I think feeds are pretty much doomed to keep breaking and disappearing. Many of the replacements or pseudo-replacements that people come up with seem fine, but the problem - as always - is getting people to actually use it, which mostly never happens.