Around 2014 I was in school and working at a bar where schedules were done by hand each week. I figured I could easily build a little web app to handle this.
The rules were impossible to encode because they didn't really exist. Building the schedule by hand allowed the manager to draw on their knowledge of everything from employee work ethic and personality to expected rushes (e.g. hockey nights) and reservations.
Right? I've never quite understood the question. There's no requirement that a smart TV be connected to the internet.
Something like a Roku is cheap, can handle your streaming services (including Jellyfin), and has no spying hardware. DIY HTPCs are of course the best option for control.
> Sure, HTPC would be the best, but they are quite a bit pricier.
Not necessarily. An Apple TV box is now $300. That's enough to buy a far more capable mini-PC. You can run an ordinary Linux distro on it with a "launcher" like Plasma Bigscreen. Alternatively, if you want to put some more work in, build LineageOS for x86_64 with an ARM translation layer and you get the best of both worlds. I recently did just that and I am delighted with the result.
I have my home server in the living room, connected to the TV. But I also have another TV and I wouldn't want to buy and maintain one more device just for that.
Last I checked there were no mics or cameras built into my Roku, but maybe we're concerned about different things. What are the "all the same things" you're talking about?
It sounds like the dev's reason for rejecting the issue is that the issue was opened on the documentation repo rather than the code repo.
On the one hand, it's understandable. No amount of documentation changes will fix the issue.
On the other hand, it's a pretty abrasive response. It wouldn't have taken any more effort to be a little more helpful and direct OP to the right repo: "Sorry, this is the wrong place for this to be addressed. Please bring it up here instead [link]."
If you actually read through, the option to disable the functionality was already present… just not documented. So it seems the documentation repo was the correct place to open it
Idempotency is a crucial trait in the world of web APIs (and any other system where commands that modify state might need to be retried due to communication failures). It's not a new word or concept, but it's certainly a niche one.
I think you're conflating general "boringness" with tech-specific features. Test driving solutions is useful but it tells you nothing about reliability.
Say it's 2012 and you need a new car. Toyota Corollas have generally proven to be incredibly reliable. The Tesla Model S is brand new: definitely not boring. On paper both meet your needs, so you test drive both. The Tesla is way more fun to drive, and that's appealing, but if you just want your car to work for a long time with predictable maintenance, you should take the Corolla.
Choosing the most appropriate tech is not mutually exclusive with choosing boring tech. In fact, "boring" (well-known, battle-tested) is very likely the most appropriate because it reduces unnecessary risk.
I'd welcome the ternary conditional operator but I hope exception handling never gets introduced (at least as I'm used to it from Java, C#, JS, etc.).
Exceptions should not be conflated with regular error handling, especially when they're allowed to bubble up from anywhere. I very much appreciate that functions that can return errors force the caller to deal with them, for the most part. True exceptions can already be thrown with panic, although I actually find it incredibly rare that I need to reach for that tool. I'd argue that when people talk about exceptions they almost always actually want "unhappy path" error handling.
Now, if Go wanted to add a sleeker way to handle those errors, similar to Rust's approach, I'd be very interested. Minimum three lines for every call to a function that returns an error does get a bit verbose, arguably hurting readability. A little sugar could improve readability without making error handling implicit.
The rules were impossible to encode because they didn't really exist. Building the schedule by hand allowed the manager to draw on their knowledge of everything from employee work ethic and personality to expected rushes (e.g. hockey nights) and reservations.
reply