2shortplanks

4 ms·

1.
by 2shortplanks 8d ago
On a practical matter, it seems like a bad idea to have codepoints that can take up to an arbitrary number of bytes - this just screams buffer overflow problems. So in practicality, you’re going to want an arbitrary limit on this (the artic
2.
by 2shortplanks 1y ago
This article skips a few important steps - how a faster CPU will have a demonstrable improvement on developer performance. I would agree with the idea that faster compile times can have a significant improvement in performance. 30s is long
3.
by 2shortplanks 2y ago
Whoa! STOP! At no point did anything say when I was creating stacks that this info would be public for other users of the site! I was shocked to find what I’d been ranking (which luckily was just chip flavors) available for anyone to see.
4.
by 2shortplanks 2y ago
One thing this article doesn’t mention is how this all falls apart when you spend time in more than one country. My UK bank (Barclays) won’t let me install their app on my US iPhone (i.e. my phone that uses a US based iCloud account). Tesc
5.
by 2shortplanks 2y ago
I’m really curious about the number of requests you end up making. I’d imagine that this would get expensive fast in a web app - AWS charge $0.40 per million read requests, so if you’re seeing ten request to your app server a second and tha
6.
by 2shortplanks 2y ago
A lot of this article seems to be conflating two things: 1. The ability for the code to process the error and recover from it 2. The ability to sensibly log, trace, and later for a human to understand the error after the fact The later of t
7.
by 2shortplanks 2y ago
Any randomly selected Linux machine is most likely to be a mobile phone, statistically speaking
8.
by 2shortplanks 2y ago
Fowler's Law on Unicode: There's always another bug, you just haven't found it yet. Dr Drang's script counts the number of _characters_ not the number of _glyphs_. This matters because there's more than one way to
9.
by 2shortplanks 2y ago
50% of the time doing something that has a one percent chance of killing you 69 times will kill you
10.
by 2shortplanks 3y ago
Before I put down cash I have basic questions, like “how do I type a square bracket?” and “how do I type a backtick?” The on-screen keyboard is pretty good, but makes coding and typing markdown hard. Will this solve this? Also, this seems t
11.
by 2shortplanks 3y ago
That’s actually one of the main reasons I like Obsidian - that I can easily use vscode with it. Obsidian’s backend is just markdown files on the file system which you’re free to edit with another editor at the same time as you have Obsidian
12.
by 2shortplanks 7y ago
I'd like to apologize on behalf of MaxMind for breaking your CI build. Let me assure you as a fellow programmer, I know how frustrating that can be! As you saw we've tried to reach out to the larger open source projects using Ge
13.
by 2shortplanks 7y ago
We apologize for not providing more notice. The CCPA was finalized in October, and it contains a number of ambiguities, particularly as it relates to our products. To arrive at our current interpretation, it has taken many weeks of working
14.
by 2shortplanks 7y ago
The problem with charging a fine is that by providing a mechanism for penance it reduces the pressure for those people who are prepared to pay fines to actually return the books on time. The more affluent therefore work under different rule
15.
by 2shortplanks 7y ago
My Grandmother loved the physical paper mail I used to send to her back home in the UK from https://www.pc2paper.co.uk/ She commented once that it took almost no time for the letter to get from the US to her. That's b