amomchilov

8 ms·

1.
by amomchilov 4d ago
Yeah it really baffles me why a symbol like `!` was spent on this, which could be more useful for more a more commonly used feature. I just checked, my main side project only has less than 10 things that return never. `-> Never` reads ev
2.
by amomchilov 2mo ago
Different incentives.
3.
by amomchilov 3mo ago
I don’t know how you could keep the two isolated, without drastically dropping up the utility of LLMs. Part of their wonder is how they can behave differently depending on the data they’re working with. We like that feature when the data is
4.
by amomchilov 3mo ago
No benefits to modules? Oh come on. Hard to take seriously.
5.
by amomchilov 3mo ago
“It’s so much magic! Now if you’ll excuse me, I have to go use my generic container library rewritten in 50 layers of preprocessor macros.”
6.
by amomchilov 4mo ago
How big is the risk of condensation when you bring a cold laptop inside? All their spec sheets say they support up to x% _non-condensing_ humidity, which I’m guessing is about the dew point?
7.
by amomchilov 4mo ago
I agree with all the motives you describe, yet come to the exact opposite conclusion. The overwhelmingly common case is for an error in a nested call to be bubbled up to be handled by a parent call. If you make this common case look similar
8.
by amomchilov 6mo ago
Next up: “all the characters you need fit on a single keyboard!”
9.
by amomchilov 6mo ago
I never understood the appeal of this talking point. It’s just an accounting trick that moves the complexity to the standard library. For example, SmallTalk is a class based OO system, yet this postcard doesn’t slow you how to create a clas
10.
by amomchilov 6mo ago
Some amount? Sure. But not at this scale. If people were just going to do it anyway, these gambling companies wouldn’t be pouring billions into advertising to stimulate demand
11.
by amomchilov 6mo ago
That makes digitization even more important, you sold me.
12.
by amomchilov 7mo ago
They don’t, by default. That’s something you have to implement yourself. It’s a common misconception that comes from the standard library data structures, which almost all do implement CoW
13.
by amomchilov 9mo ago
Recent macOS versions zero out memory on free, which improves the efficacy of memory compression. Apparently it’s a net performance gain in the average case
14.
by amomchilov 9mo ago
The industry assures us they’re just filling demand that already existed, that used to be fulfilled by a black market anyway. So now it’s all above board and taxed and hunky dory. It’s a bit odd they spend a lot of money on advertising to s
15.
by amomchilov 9mo ago
FWIW, AoC is very non-representative of real-world string manipulation problems. The AoC format goes out of its way to express all problem inputs and outputs in simple strings with only basic ASCII text, just for compatibility with the most
16.
by amomchilov 10mo ago
Are you suggesting that the test for whether they should “allow” a feature is whether your mom can figure it out? Why?
17.
by amomchilov 10mo ago
You just reminded me of Perian. What a throwback! https://en.wikipedia.org/wiki/Perian
18.
by amomchilov 10mo ago
Typed exceptions are unlike typed parameters or return values. They don’t just describe the interface of your function, but expose details about its implementation and constrain future changes. That’s a huge limitation when writing librarie
19.
by amomchilov 11mo ago
Dynamic languages can execute code without type annotations, so you _can_ just dismiss types as redundant metadata. But I don’t think that’s wise. I find types really useful as a human reader of the code. Whether you write document them or
20.
by amomchilov 1y ago
This is the eternal selection pressure that slows new C++ adoption. The kinds of places still waiting C++ aren’t usually the ones that put much emphasis on using a compiler from the past decade. Java 8 and C++98 will be here forever lol
21.
by amomchilov 1y ago
Stacked diffs are a core part of my workflow, letting me “work ahead” without being blocked waiting for reviews. Setting them up in git is not to bad. Adding a change to the bottom of the stack, and restacking everything on top… that’s hell
22.
by amomchilov 1y ago
Ah yes, [a Dutch toilet]( https://noplacelikeanywhere.com/destinations/dutch-toilets-a... )! A most regrettable invention.
23.
by amomchilov 1y ago
I would be more than happy to see gift cards disappear. Limited strings-attached IOU that’s worse in every way than the cash paid for them.
24.
by amomchilov 2y ago
The unrefactorable ball of mud problem is real, which is why both Stripe and Shopify have highly statically typed code bases (via Sorbet). Btw Stripe uses Ruby, but not Rails.
25.
by amomchilov 2y ago
How many declarations did it have in C++ in total? Technically those were all unsafe, just implicitly so.
26.
by amomchilov 2y ago
Exactly, you write them with AI
27.
by amomchilov 2y ago
Such is the issue with bad defaults. Opting into the sensible thing makes most of your code ugly, instead of just the exceptions.
28.
by amomchilov 2y ago
Engagggge. Consume the slop. Shareholders demand it!
29.
by amomchilov 2y ago
I hope your train of thought proceeds to the next station along that line: “oh yeah, because that doesn’t scale, obviously.” It’s the same reason why it’s better to sponsor a “we’ll double your donation up to $X” charity campaign, than to j
30.
by amomchilov 2y ago
It's a temporary and incremental improvement over the previous stylesheet, which was also green (for reasons still unknown): https://docs.ruby-lang.org/en/3.3/String.html The goal was to move in the right dir

More ›