2,340 karma · joined January 3, 2019
Now I have one in my work bag, at least one in the car, one in my main toolbox, a few hiding around other places in the garage, one in the kitchen, probably one upstairs, on in my desk drawer, etc.
No regrets. Life is better now.
I would argue that any input that doesn't have exactly one obviously correct output should result in an exception being raised. But Ruby often shies away from doing that. My interpretation is that they prefer to return _something_ rather than blowing up, so the show can go on.
I guess I sit at the opposite end of the philosophical spectrum from Ruby, so it's no wonder choices like this frustrate me. My personal philosophy is "explode early, explode often", because propagating invalid states only leads to future pain and suffering.
> [...] so much code now relies on its behavior, predictably or otherwise, that they couldn't change it.
I'm not denying this is a reason for keeping the questionably behaviour, but it's kind of funny because Ruby also introduces subtly backward-incompatible changes semi-regularly, including in "minor" releases. (Maybe that last bit is unfair, because I don't think that Ruby has ever claimed to follow semver.)
I guess this isn't super constructive, but to me the whole thing smells of not just a lack of discipline, but a lack of _interest_ in correctness that seems to be endemic in the Ruby community.
We ended up writing our own `TimeRange` class to paper over the base Range bugs that show up if you use it with times.
One awkward takeaway from the experience is that I've come to believe that sometimes it _is_ worth unit testing other people's code, counter to the popular advice.
Seems pretty irresponsible of Google to do that. And also, just... kind of lame. Google is slowly but surely changing their image from "tech wizard" to "kind of a joke", and they have nobody but themselves to blame.
The kind of imprisonment that Assange was subjected to is unambiguously torture, and was unambiguously administered for the purpose of revenge.
There is no natural "need" for the conditions he was subjected to (e.g. the cost of a larger cell is negligible), and no natural purpose other than to punish.
I am deliberately ignoring the question of guilt here, because I don't believe that we should torture _anyone_, regardless of the crime. The fact that we do this is a giant ugly stain on civilisation.
I've had the exact opposite experience, so I'm guessing it has a lot to do with the type of stuff you've (and I've) worked on.
One left out details in the diagrams in each step that they had deemed irrelevant to that step. This apparent attempt at simplifying the instructions stumped me for ages because I kept thinking I'd oriented pieces wrong due to the number of holes in the picture differing from the number of holes in the physical thing.
The other had switched some parts since the instructions were made, and hadn't bothered to update the instructions. This was a bit more obvious, but still kinda irritating for someone like me who is uncomfortable with uncertainty when I believe certainty should be attainable.
Whatever else can be said of IKEA, their manuals and quality control are excellent. I think of them as the McDonald's of furniture — it's never the best product, but it's damn good for the price, and you know exactly what you're going to get.
It's more math, though, and usually not worth it unless you're already planning to subdivide the surface further for some other reason.
One benefit off the top of my head is the extra isolation between component instances within this statically linked app: you can be shielded from many of the ways libwhatever might ruin everything because its linear memory can be totally isolated from the root component (and vice versa) with surprisingly little overhead.
The Wasm Component model takes security seriously, much in the way that Core Wasm does. Even without everything else it has to offer, this is something our craft is desperately in need of.
The cynic in me can't help but wonder if somebody is hoping to cash out via whatever investors haven't yet noticed the writing on the wall.
Should that last bit be: "advantage of effect handlers over coroutines"?
EDIT: Oh, maybe I should have read the rest of the article first. It might be going the other way than that one example suggested. :)
It's such a strange pattern that plays out again and again: developers insist that a permissive license is the way to go, until somebody (or company) they don't like exercises their rights.
Usually what said developers actually wanted was the GPL, because they realise in retrospect that they didn't want the company to be allowed to do this. But they didn't like it because it restricts recipients rights. So they want people to have those rights as long as they never actually exercise them? It's all very confusing.
I say this having contributed to and released my own projects under both permissive and copyleft licenses — based on what I'm actually willing for people to be able to do with the code.
That wasn't my experience of it. It's a brilliant show, to be sure, but at some point I felt the bleakness, particularly around Bojack's inability to help himself, became too much for me. Maybe different parts of the show resonate in different people.
How often is one of these accidental debts created? How often do customers just pay up because it's small enough that it's not worth fighting? How often does AWS (or Google or whoever) decide whether to forgive the debt based on PR damage control rather than the legitimacy of the debt? Jeez I hope someone leaks those numbers one day.
It reminds me of all those horror stories of hospital visits in the USA, where the first bill you receive is just a test to see if they can squeeze that much out of you, but if you know what you're doing or just can't pay then the actual bill is way lower. It's all just yucky.
If big cloud providers couldn't selectively choose which of these debts to enforce, I bet there would be a media shitstorm and then they would suddenly discover that it's not all thaaaaat hard to implement real time billing and hard caps after all.
In some jurisdictions I think that reduces the legitimacy of their claim that you actually owe them money.
EDIT: Even better, focus on the examples where Google "forgave" the debt; you could argue that those examples prove that Google knows it's at least partly their fault.
If you're running a business and you have lawyers, then fair enough — just play the game. But for individuals, it seems crazy that so many of us accept this sort of thing. Good luck contesting the charge with your credit card company when you already agreed to a contract that said Google could bill you thousands of dollars and then you used thousands of dollars worth of their service.
Big cloud providers are not your friend. They do not care if they destroy the lives of you and your family, unless it's happening so often that it's making mainstream news.
My advice is to go and delete your cloud accounts, and only use services that offer hard spending caps, and ideally prepaid accounts.
Maybe this doesn't leave many options. Oh well. Maybe if you can't afford big lawyers then you also can't afford the risks of using big cloud.
I remember back in school religiously saving new versions of Word documents so that if the newest version went bad I could start a fresh doc, then copy and paste sections from old versions via Notepad to cleanse the corruption. (Direct Word-to-Word could bring it across — I guess that tells us something about how they implemented copy+paste between documents, too!)
It all makes rational sense. It just feels weird to think about Python running on Mars before there's even people there.
Largely copied from my reply to a similar comment:
Trains requires long-term planning and alignment of a lot more people and organisations, all of whom have their own messy incentives. They're a political quagmire that you might never emerge from.
I'm trying to think of solutions that can be mostly built by the private sector and deployed with only modest legislative changes.
For the same reasons, a friend who works in mass transit talked me around to favouring better "smart bus" infrastructure over lobbying for more rail — at least in most cases where actually getting more rail is an unrealistic outcome.
I'm trying to think of solutions that can be mostly built by the private sector and deployed with only modest legislative changes.
Let's get a little bit crazy and imagine something very different from what we have today, but still only requiring a single driver. One truck cab at the front. Individual trailers have their own wheel motors, their own steering, and a small battery for short range manoeuvring (e.g. at a loading dock/port or). Trailers follow each other at a distance that allows for emergency braking, but close enough that they can be connected by high voltage cables for receiving power from a "battery car". Both the cab and individual trailers constantly communicate, and the moment any participant suspects that all is not right, the whole train tries to slow down and pull over.
If one trailer has a blowout or other issue, it can be left behind to be picked up by another convoy.
At a port or loading dock, the convoy disassembles and individual trailers are driven by remote control, either directly by a human or eventually by the "site AI", so that large articulated vehicles never have to enter the area.
I'm imagining ~12 trailer convoys to balance efficiency gains with disruption to local traffic.
It's a difficult position. On the one hand, these users are chewing up compute and bandwidth, without providing any ad revenue. On the other hand, if they leave, it contributes to a vicious cycle (or virtuous cycle, depending on your perspective) of eyeballs being elsewhere, and content creators looking elsewhere to reach those eyeballs.
Sure, initially content creators will be posting to YouTube as well, but even a moat like YouTube's can be filled in over time.