I know Roku doesn’t exactly have the greatest track record but I’ve owned them relatively trouble free since at least 2010, having refreshed them all once or twice since.
Way back when Apple and Amazon were fighting Roku was the only one that had both on it.
I prefer all my TVs stay dumb, so I just plug a Roku box or stick into them. No more having to get a new TV because the Netflix app stopped working or whatever.
I hate the Amazon Stick UI and don’t want to pay 3x the cost for an Apple box- but I absolutely will eject from Roku completely if they start doing this stuff.
The Roku of 2010 was not primarily deriving its earnings from ads and selling subscriptions to people, though. Apparently just selling devices / licensing an OS was not a growth industry.
I have never come across a post on HN that was so scarily describing my current day to day and with a comment I agree with so wholeheartedly.
I’ve spent the majority of my career in tech with a finance angle to it, mostly sales and use tax compliance.
What I never fully appreciated was how much those accountants, controllers, and lawyers were rubbing off on me.
I was recently advising a pretty old startup on their ledgering system and was beyond appalled at what it looks like when a bunch of engineers with no finance or accounting background build an accounting system.
We don’t have to find magical accountant engineers either, it will wholly suffice if we sit actual accountants in with our engineering team during the design process.
After my design of their complete overhaul I had a friend who is a CPA completely review my work, we found a few holes in certain scenarios, but by and large we were good.
Money is a difficult engineering problem because with money comes all the human goofery that surrounds it.
My personal hobbies as well as an off-road race we started amongst friends years ago accidentally becoming insanely popular has lead to me getting to know and becoming friends with auto related content creators, TV personalities, and professional drivers through the last decade.
- A bunch of money came in just before but especially during the pandemic and the capitalists want ROI.
- This means the creators don’t get to do all of the fun stuff they used to do, and now have to justify and get approval for projects that they used to just do on a whim.
- Things get “grown-up” quick and the internal culture goes from likeminded folks “just figuring it out” to planning, meetings, and being forced to produce more repeatable and formulaic content on tighter schedules. Sometimes working with brands you do not want to work with, but have to.
- A lot of these deals happened 2-4 years ago and earn-out clauses have hit their expiration. Now they can bail and realize as much gain as they can.
- Some people are leaving because they realize how royally screwed they’ve gotten.
Finally, the whole industry is a grind. I’m only tangentially related to it as a hobby and seeing what my friends have to do seems EXHAUSTING.
THIS is the real problem. For _most_ projects upgrading from 8 to 9 meant just adding a few packages that were removed from default JDK with Jigsaw. That part is generally fine, even with OSGi hell.
The Javax -> Jakarta changes for validation, EE, XML, etc. are a damn nightmare!
And if you're using microservices it's either a total migration (a no go for anyone minimizing bugs and outages), or a slow one-by-one trudge, if you use some commons between them that commons will need to support both javax and jakarta together, superbly fun
I do both. I’ve got lots of not computer hobbies (and kids) and I have tinker projects. I usually use early morning a couple days a week for tinker time as I’m an early riser.
It does. Primarily, worker threads query the DB for jobs to pick up. They can write state back when running a job, and they can have configurable (per job type) retry rules.
So in your case, the crash would likely leave it in an open/running state if it was already picked up, at which point timeout/retry rules would kick in after a restart.
If the job wasn’t running yet, just queued, then it would be business as usual upon restart.
I have a 15 year old Brother black and white laser all-in-one and a 6 year old black and white laser with Wi-Fi still on the starter toner in my office.
They work on Linux, Mac, and Windows. I can print to the Wi-Fi one from my iPhone.
In over 20 combined years I’ve never had a paper jam, magically been out of toner, or found myself in a pinch. The new(er) one has a very low power deep sleep so I don’t even have to fully turn it off.
I’ll probably never buy another printer, but as long as Brother doesn’t turn heel, my next printer will 100% be from them.
Even if your old one does start to go bad, I discovered it can be more effective to repair than replace for a multifunction printer/scanner. My old Brother was on the fritz a year ago. After being shocked by prices for new ones, I found a printer repair shop across the Bay from me. They fixed it for much less than the price of a new one. And they told me to keep it as long as I can because it’s such a good piece of hardware.
I bought a basic B&W brother toner printer back in college and it's still kicking on the original toner. I love the thing because it just freaking works, always worked out of the box on Windows/Mac and Linux with no additional drivers (there is one but it worked fine without them).
I've got the HL-L2300D and I recommend it to anyone that just 'needs a damn printer'.
I follow it pretty closely. I don’t have any automation setup for changelogs or anything at this point, but it’s pretty easy for me, as back in ye old SVN/Trac days there were similar FIX, etc. semantics.
I often have trouble with enough room to have a meaningful subject but the time I include commit scope and Jira ticket number, but I don’t mind, I normally use the body anyway.
I’ve been using it for a long time and I’d happily pay $100 for it.
It can consume swagger/openapi docs and generate calls. It can generate code snippets and cURL requests. You can extract values from one response body to use as a variable in another request, the built in features go on and on- and there’s a decent extension ecosystem/write your own.
Most importantly, it just works, and it works well and quickly, with pretty much any auth scheme I’ve ever had to deal with.
I’ve only got really a couple of nits with the stand-alone version.
I still can’t figure out how to make it “use the same auth scheme” for every single request globally. Each request requires the auth config, but this is solved by just copying an existing request and starting from that. This could very well be my lack of knowledge, though I feel like I know the tool well.
The .paw file is binary and doesn’t do well checked into source control if you’ve got more than one person using it.
The Teams version, which requires a monthly sub kinda/sorta mimics a git style branch strategy for merging different members changes and handles the team problem pretty well.
All in all though, it is absolutely and BY FAR the best request tool I’ve ever used. A great combination of simple just get out of the way and advanced automation strategies. I use it every day.
EDIT TO ADD:
I forgot to mention their license is still a lifetime license. I paid them $50, probably 6 years ago now, and have never been forced to pay them another dime. I’d pay per major version or do the IntelliJ perpetual fallback if it came to it, but I’ve never once been bait and switched (looking at you Tower2).
Way back when Apple and Amazon were fighting Roku was the only one that had both on it.
I prefer all my TVs stay dumb, so I just plug a Roku box or stick into them. No more having to get a new TV because the Netflix app stopped working or whatever.
I hate the Amazon Stick UI and don’t want to pay 3x the cost for an Apple box- but I absolutely will eject from Roku completely if they start doing this stuff.