> That would probably not trigger anyone’s midnight pager, but it would make it clear that relying on the deprecated functionality is a bug lurking in the code.
How do you know? This is a wild assertion. This idea is terrible. I thought it was common knowledge that difficult to reproduce, seemingly random bugs are much more difficult to find and fix than compiler errors.
If you're ready to break your api, break your api. Don't play games with me. If more people actually removed deprecated APIs in a timely manner, then people will start taking it more seriously.
> In case the sarcasm isn’t clear, it’s better to leave the warts. But it is also worthwhile to recognise that in terms of effectiveness for driving system change, signage and warnings are on the bottom of the tier list. We should not be surprised when they don’t work.
I thought I had read it. :) I thought the three `* * *` at the bottom was indicating I was about to start reading suggestions for the next article. So definitely a "Woosh" moment for me :D
Yeah, I agree - this sort of intermittent failure could be incredibly hard to track down, and will absolutely fuck with people's faith in their CI systems as well - a flappy test is the absolute worst kind of test.
I agree, maintainers should just break the API if they're going to do it.
At the same time, it's crazy that urllib (the library mentioned in the article), broke their API on a minor version. Python packaging documentation[1] provides the sensible guideline that API breaks should be on major versions.
I tried to use a USB-C HDMI dongle I had. But I assumed it was because the switch 2 was looking for something that could deliver enough power and actively cool it, like the first party dock does.
Thst is a badly phrased question. "What languages do you speak?", would be the question to ask.
Because even of you were thinking about spoken languages, what does "knowing" mean? I "know" Hungarian exists, I know how Hungarian sounds like, I know how Hungarian words look like, but that doesn't mean I speak or understand it. Now if it was clear they meant apoken languages we could infer from the context they want to know about our skills with different spoken languages and didn't read our CV, which at least where I am from always contains a languages level with a skill level (e.g. German A1, English B1)
Pretty amazing that this is still around. I used to be active on Elendor MUSH, but as far as I know it's been dead for years - I poke my head in once every year or two and there are always 0 players online.
Is the server available anywhere or is that too lost to the sands of time?
Sucks when MUD servers eventually shutdown and all of it is lost forever. I’ve found a few on github though and have been archiving as many as I can find.
Switch to a MIPS transflective or e-paper display as on a Pebble or Garmin, OLED and LCD displays on Apple and Samsung watches look pretty indoors (when they're not turned off to save power) but are hard to read outside (without excessive brightness) and are battery gobblers.
Just charged my Garmin Fenix for the first time in... 9 days (it was down at 18%, could get a few more days but it makes me nervous), most of the battery use went to some 11 hours of GPS activity recording and heart rate recording. Could get 30 days if I turned off the features the Pebble doesn't have.
Even Garmin has largely moved to AMOLED screens. They look great both indoors and outside and with modern technology they are not as battery hungry as they once were. Personally I find the battery life on my Apple Watch more than acceptable. I charge it while I’m showering and getting readying in the morning and have never had any issues even though I am a very heavy watch user and often use it independently of my phone.
I used to have a Pebble Time and agreed the battery life with those displays is nice, but honestly it doesn't bother me to put it on the charger every evening.
The only real benefit a longer battery life would have is not needing to bring a special charger if I go out of town for a few days, but I solved that years ago using a power bank that has qi and watch charging pads on it as my travel charger.
If anything, I'd switch back to a Pebble or similar because the Apple Watch does too much and I don't want that much gizmo on my person all the time. But the Pebble reboot products don't do it for me design-wise.
Just a tip with Apple watches: get the battery service at least once during the lifespan of your watch. It's $99 and Apple gives you a brand new watch.
With that battery service the watch should last you about 6-10 years judging by the current status of my Series 4.
Yes, a watch should be able to last a lot longer than that, but I think if you're buying Apple products you already have the expectation of a maximum 10 year lifespan just from software alone with just about the entire product lineup.
As long as it's minor scratching and not big chips or cracks, yes. Another huge plus to the battery service.
Another tip regarding scratches is that the higher tier finishes (Stainless Steel or Titanium in the Series 10) are, in my opinion, worth the price premium solely for the improved screen glass.
Apple barely mentions the spec nowadays, and I'm not sure why they don't tout it. A conspiracy theorist might say that it's because it keeps your watch looking new longer so they'd rather you be buying the cheap one frequently.
The sapphire crystal screen is the killer feature that justifies the upgraded models more than anything else: it's something like a whole extra number higher on the Mohs scale for hardness (scratch resistance).
I buy them on the refurbished store to lessen the pain of their ridiculously inflated price.
You may have an app draining your battery. Was having the same issue with my watch, I deleted a few apps and all of the sudden my watch was better. I can’t tell you what app was because it was just luck. I was creating space on my phone when it happened.
I wish I could better help my org see that. Luckily my boss agrees with me, but he's not in full control. Between the vendor lock-in, and the _almost but not quite api compatibility_ with OSS... I just dread as more teams adopt it.
Similarly, I would love if videos/blurays/streams/etc had a way to adjust volumes separate from each other. So many movies have such loud music and quiet dialog. So I'm constantly adjusting the volume between different scenes.
I was already an existing TMobile customer. I bought myself and my wife an iPhone 11 in cash when the phones were brand new. Never had a contract. Already had an LTE plan, didn't change that plan at all. Just bought two new phones from TMobile and had them slap the sims in.
Fast forward to a couple months ago, I happened to notice while browsing my TMobile account that my phone was being reported as "Carrier Locked" with subtext that said "This phone is not eligible to be unlocked". Not my wife's though, hers was listed as "Unlocked". It took over a month of being yanked around by TMobile reps telling me they had to "escalate but the issue will be fixed within a week". It never was.
They would ask me why I wanted it unlocked. I would just respond something respectful but firm along the lines of "Because it's my phone. I paid for it. You have no business locking my device"
The way I see it, it was either theft or false advertising, plain and simple. Either they stole the phone from me after I bought it. Or, they sold me a device as unlocked but never realized that promise. It should have NEVER been locked. It makes me mad just thinking about it. I don't understand why a carrier even has the power to remotely lock a phone that was never theirs to lock in the first place.
This is all to say: I agree with your observation. They deserve heavy handed regulation because they have proven they will abuse any inch you give them.
This made me nervous, I used their web site under accounts check unlock status. It shows unknown for ours. We bought our Android phones on Amazon. I guess that's why the status shows as unknown for ours.
Isn’t the phone itself the best place to check, rather than your carrier’s website?
It’ll vary per manufacturer exactly where to find the info on the phone, but it’ll be reliable. You can also use an IMEI checker website, although some of those are ridden with ads and upsells.
I looked on my phone first, went through information on the About screen, didn't see it, might have been tired last night and overlooked it, will check again today. I'm not sure I feel comfortable pasting my IEMI into a web site, I thought about doing that though.
No, after over a month of them saying "it'll take a week for it after I escalate" and then me calling a week later and starting the whole conversation over, one day it finally was unlocked. And I moved to a new carrier.
I tried to get T-Mobile to unlock my far out of contract iphone 6s a few years ago, which should be super simple. The first time I talked to a rep and confirming everything they said it should show as unlocked in a few days. A month later and it wasn't unlocked. I called again and went through the same steps with another rep, they said it would be unlocked for sure this time. Nope. Luckily my friend gave me their old unlocked iPhone and I switched carriers. That 6s is still locked, T-mobile is scummy.
even worse when they don't properly enforce it and instead silently truncate it.
There was a PayPal bug just a couple years ago where the reset-password page didn't enforce length like other pages did. So it allowed you to create an otherwise illegal password and then your account is completely locked out (I guess, unless you realized the truncation was happening...)
And so I would reset my password, generate a new one... and it would happen again. Took me a while to realize it was the length and not a special character I added messing up with bad encoding logic or something.
Thank you for confirming I'm not crazy. I remember having the same problem a few years back and looking up online if anyone had the same problem as me, but found nothing at the time.
How do you know? This is a wild assertion. This idea is terrible. I thought it was common knowledge that difficult to reproduce, seemingly random bugs are much more difficult to find and fix than compiler errors.
If you're ready to break your api, break your api. Don't play games with me. If more people actually removed deprecated APIs in a timely manner, then people will start taking it more seriously.