I’ve looked at Casa. It wasn't CasaOS, but now I'm remembering.. I think they supported casa's marketplace conventions.. so that's how as a new project it had a big marketplace as they sort of piggy backed all the apps that casa supported onto their own marketplace.
I like these conventions. Another personal practice I us the body for is where I’ve relied on any webpages; blogs, issue reports, stack overlap pages etc to help the commit come together.
The example of using one library over another, especially if research has gone into which to choose, regularly involves say finding a good article that compares the alternatives.
I’ll say though that I usually include links to more notable references, I won’t usually commit refs to a libraries own docs and more obvious stuff; revealing and keeping references to resources found that went towards getting it done are what I keep and add to commit body.
Maybe there’s spaces for useful references to be added to the spec/conventions.
Personally I usually show links like this after the body message.
Firstly, I really want this also and am supportive of an opinionated decision to put something at say Temporal.DateTime() that would be logical for developers to use ‘most of the time’.
However my guess is that the spec designers saw this lack of specivity as part of the problem.
A key issue of dates and times is that we use them culturally in day to day use in very imprecise ways and much is inferred from the context of use.
The concepts of zoned time and “wall clock” time are irreducable and it’s likely much code will be improved by forcing the developer to be explicit with the form of time they want to use and need for their particular use case.
I think this is why it’s so explicitly specified right now.
But I agree; I’ve often struggled with how verbose js can be.
Maybe with time (pun intended), more syntactic sugar and shorter conventions can be added to expand what has been an incredible effort to fix deep rooted issues.
My thought is half cynical. As LLM crawlers seek to mop up absolutely everything, companies themselves start to worry more about keeping their own data secret. Maybe this is a reason for shifts like this; as encrypted and other privacy-preserving products become more in demand across the board.
I could totally wrong, but my assumption is that you’d get a small dedicated box (mini PC) that has an display port/hdmi/lightning port and usb ports and plug that into your TV like you would an Apple TV.
A remote control with wifi would work pretty easily by being connected into usb port, just like a wireless mouse.
I wonder if you can then use Netflix and other streaming services? I have a Chromecast device and could probably just switch the HDMI to use that. I can use Netflix on my Linux laptop but I haven't tried Disney and I would very much doubt Apple+ would work on KDE.
> Great! We always need help. In order to find something that you find fun and rewarding to work on, a good first step is to find out which itch you have with Plasma Bigscreen, and how it can be scratched. What's nagging you? Now give us a shout-out, best via the Plasma mailing list. You can also make yourself known in the Matrix channel. There's plenty to do, tasks for every skill and level, and you'll find it's fun to work on and learn from each other.
reply