uallo

9 ms·

61.
by uallo 3y ago
https://github.com/microsoft/TypeScript/issues/13219
62.
by uallo 3y ago
It may be unusual and has special semantics in Svelte, but it is JavaScript syntax after all. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
63.
by uallo 3y ago
What is stopping anyone from doing just that? Limiting factors include battery, security updates, software updates, performance, hardware durability. I still use a Pixel (first edition, released in 2016). Both performance and hardware durab
64.
by uallo 3y ago
Sure. I already use several rate limitation measures, return fake data for repeating offenders, and also outright block some others. It is still laughable that a somewhat "reputable" bot does not even know about basic HTTP headers
65.
by uallo 3y ago
Yet another bot that completely ignores the "429 Too Many Requests" response header and happily continues hammering your tiny little side project [1] to death. Luckily, I already block the IP address they're using as it has b
66.
by uallo 3y ago
https://docs.npmjs.com/cli/v9/using-npm/workspaces https://www.npmjs.com/package/patch-package
67.
by uallo 4y ago
tresorit can do that: https://support.tresorit.com/hc/en-us/articles/217103697-Exc...
68.
by uallo 4y ago
I run a small blog that is based on a tiny custom script and a single markdown file. It builds static HTML files and deploys them using rsync, it takes less than one second to build and deploy. There is absolutely no technical maintenance r
69.
by uallo 4y ago
> That refers to the formal (full firmware) updates, I'm talking about security updates that get pushed to the phone without you having to do anything. It is called "Android security patch level", that is not a full firmwa
70.
by uallo 4y ago
> so that continues pretty much for the life of the phone. I'm on a Pixel 1 with Android 10. Last security update it got was from October 2019 which is about three years after the phone was introduced. Is this supposed to be differe
71.
by uallo 4y ago
Off topic: This page is yet another example of many, many websites that display a useless horizontal scrollbar. Non-overlay scrollbars simply do not work with elements that are set to a width of 100vw. Using 100vw is almost always a mistake
72.
by uallo 4y ago
I recently learned that uBlock Origin can block that API, too. https://news.ycombinator.com/item?id=33997228
73.
by uallo 4y ago
They did the same thing to an account I used to access Bing Webmaster Tools. Instead of giving them anything, I now actively move friends and family away from Bing. Not that many of them used it in the first place, but now there are none le
74.
by uallo 4y ago
I'm on a Google Pixel from 2016 and have absolutely no idea what you are talking about. Firefox runs perfectly and I do not see any janky scrolling or otherwise bad performance at all. Scrolling in Chrome does not feel different either
75.
by uallo 4y ago
> This is in the works. Nice! Will it be exposed system-wide so that I can open PDFs from within any other app in Firefox?
76.
by uallo 4y ago
The author's website sets a root font size of 18px. That completely eliminates any benefit you may have by using rems "for accessibility". Setting the root font size with an absolute unit completely overwrites the users'
77.
by uallo 4y ago
That website currently weighs 9.50 kB. Hence, it cannot add too many more sites (without removing some other bits) before hitting its own arbitrary size limit.
78.
by uallo 4y ago
> In the last version of my site, selected elements – images, code blocks, quotes – were made wider than the page content area using negative margins. Yes, negative margins are often (not always!) a bad idea. Especially for something lik
79.
by uallo 4y ago
The problem with some of these is that they are terrible for accessibility. There is extremely low contrast, missing focus styling, invalid non-semantic HTML, ... Having a list of good examples only would be much more interesting than a l
80.
by uallo 4y ago
It may not live up to Google Translate (yet), but there is an official translation addon: https://addons.mozilla.org/en-US/firefox/addon/firefox-trans...
81.
by uallo 4y ago
Is it possible you are confusing container queries with something else? I don't think preprocessors and/or CSS methodologies have anything to do with that. I don't see any way they could solve the problem that container queri
82.
by uallo 4y ago
I'm not aware of any benchmarks. Neither am I aware of any performance deterioration in Safari 15.4+. What is your point exactly? That performance should be one of the most important aspects in browser engine development? I agree. He
83.
by uallo 4y ago
I was neither sharing an opinion nor did I claim anything. I asked OP to elaborate and referred them to content of the article. > You know why it never happened? Yes, I do. > Especially when all we have is their word. Does that mean y
84.
by uallo 4y ago
Can you elaborate or is this just an uninformed rant? The article that you are commenting on explicitly mentions the focus on performance while considering this feature. They even state to have been able to achieve "fantastic performan
85.
by uallo 4y ago
:has() can be described as "elements whose children match some selectors". Your expectation would have been (if I understand it correctly) "match elements with some selectors and get their (direct?) parent". Aside from r
86.
by uallo 4y ago
The group of people that go through the hassle of signing up and setting up everything again to avoid paying is probably equally small. If the account setup is so frictionless that a lot of people do it again and again, you should work on a
87.
by uallo 4y ago
> We dogfood the same API endpoint to prevent users who abuse disposable emails to create fake accounts for free trial credits. I usually use disposable emails to test services but don't want to be spammed. Often, I later upgrade to
88.
by uallo 4y ago
I've been a non-paying Feedly user since Google Reader shut down. I think their nagging is tolerable. I currently see no point in an upgrade as I don't miss any feature. I've also been a long-time user of Pocket. I would real
89.
by uallo 4y ago
Native dropdowns have much (much!) better UX and accessibility than most custom dropdowns built with JavaScript. Same goes for native form validation. And there are many more examples. Using JavaScript does not necessarily improve UX. Use t
90.
by uallo 4y ago
Tarball: Build, create tarball, push Git: Build, git commit, git push to some provider Those seem pretty similar to me. Maybe you are thinking that I could just use my own repository and push that to the remote. But I don't think that

More ›