3,484 karma · joined October 24, 2011
> We all realise that that would be ~so much better~.
If tildes are omitted, then I have not intended to be sarcastic.
If you're looking at my profile to see which gender you should use to refer to me, go ahead and use the male gender.
See this explainer by the FSF: https://www.gnu.org/philosophy/categories.html
> Comparing this to what happens when using a normal browser, or in this case, Telegram, which uses the recommended SFSafariViewController:
> As you can see, a regular browser, or SFSafariViewController doesn’t run any JS code. SFSafariViewController is a great way for app developers to show third party web content to the user, without them leaving your app, while still preserving the privacy and comfort for the user.
1. Browsers should ship with a set of fonts used just in the web browser that web designers can count on. Right now, there isn't a font I can count on finding in Chrome on all platforms. This especially matters for non-English languages, where a different system font can lead to a website that looks very different.
2. Browsers should not load fonts installed in the operating system. It's a fingerprinting vulnerability. And it also causes issues where the system-installed font is unexpectedly different from platform to platform. For example, Arial is different across platforms, especially once you consider non-English languages.
There are a lot of rough edges when building a string representing an SQL query in the programming language that you're using. You have to be careful to avoid SQL injections, for starters. Do the bindings for PRQL innovate at this level?
"One out of every four users who visits a Stack Overflow question copies something within five minutes of hitting the page."
https://stackoverflow.blog/2021/12/30/how-often-do-people-ac...
- The Inmate Are Running The Asylum by Alan Cooper
- The Design of Everyday Things by Donald Norman
(and I'm sure there are many more good resources that are recent than that.)
It's very easy as tech-savvy people like us to underestimate how hard technology, even conventions like laundry symbols, are. I personally have printed out a legend explaining the laundry symbols and put them near to my washing machine, but I'm the only person I know who does that. Everyone else guesses or struggles to use laundry symbols correctly, or reads the text in English if it is provided.
Now, does that mean we should change all the laundry symbols just because one person shared a redesign on their blog? No. Changing something that is so well-established has significant downsides and risks. But I think it's perfectly legitimate to spot their difficulties, and to pursue better UX relentlessly, with testing with real users. That's what separates a good (UX) designer from an engineer who produces something that fits their mindset but not the mindset of actual users.
I tried it with a group of friends, but it didn't take off, sadly, for a couple of reasons. But I did not feel annoyed by them the way I do for WhatsApp voice messages. I hope Cappuccino takes off, I think it's a good idea that with good execution that deserves to succeed.
echo("${foo}"); // Will this print '${foo}' in PHP 9.0, or will it raise a syntax error?
echo("${(foo)}"); // Will this print '${(foo)}' in PHP 9.0, or will it raise a syntax error?
Personally, I would prefer it to raise a syntax error. Otherwise, code that runs one way in PHP < 9.0 will run a different way in PHP 9.0, failing silently. I would prefer it to fail loudly.https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+... (The bug also affects snap Chromium, hence the bug title)
<script>
let foo = "bar";
</script>
<script>
console.log(foo); // prints "bar"
console.log(window.foo); // prints "undefined"
</script>