everydaypanos

By Safari, I meant the engine, not the app.

Are there any people who actually prefer no PWAs at all over Safari-engine PWAs?

Why Safari can’t just launch from a Home Screen bookmark even if the user has chosen another “default browser”?

PWAs are already a separate “island” of storage and share nothing with Safari App…

Microsoft does it all the time with Edge on Windows.

Click on any book other than the first. Resize the window. Awkwardly jumps to first book..

> Your non-technical family members and friends will likely fall for these at some point. For their sake, disable them.

As the famous proverb says "give a man a fish and you feed him for a day; teach a man to fish and you feed him for a lifetime". The best way to "fix" phishing attacks and malware is by making people more "technical". The only way to eliminate these phenomena is by educating people about what a Push Notification really is and that you simply don't have to click it.

The Web needs to be a competitive platform for apps next to the closed and "gated" App Stores. I think that we should not dumb down web browsers to simple page viewers.

During the deflationary two year COVID pandemic they made zero price reductions.

If I remember correctly they even removed C1 instances thus increasing the price of their “cheapest” option from ~€3 to ~6€.

Today, all the “cost savings” that were supposedly made during the deflationary era are gone and we have to “adjust” again to even higher prices.

Been waiting for this for so long. Especially the BroadcastChanel feature since there is currently no way for PWAs installed twice on the Home Screen to “share” data between them. Hope that BC fixes that

reCaptcha and translate are also down. Even search is affected it is super slow.

Imagine how much code like this is inside our "lightweight" browsers.

All the code reviews that passed this on to production make you wonder how competent these browser makers actually are..

I think that the browser should not treat every input field as a personal info form for the current user. There are plenty of cases of web apps I can think of where disabling autocomplete is best user experience overall.

Any ARM providers close to the Scaleway's pricing?

Nice guide and love that it included WebPack for modern development.

I think the SVG with prefers media queries is not covering all cases, for example Chrome Anonymous dark “theme” and other user selected “themes” are impossible to check how they paint the background of the favicon area. So..the perfect solution in my view is still somewhere out there..

I wonder how much of Wave's death was from resistance from inside Google(GMail team, or even other execs). Fear for the destruction of GMail even from another Google product.

He lost me when he described Canada using a dictionary-like wording but also adding some pretty personal perspective. Describing an entire country as Socialist seems super opinionated to me.

Client-side navigation is quite tricky to get right - since there is no definition of right. Browser back buttons and scroll positions between back and fourth page loads are not standards-based things and the only way to study them is by just using the browser.

The only fashion that I have come to hate in client side navigation is endless scrolling on product pages. In my view it is completely pointless and hitting the back button NEVER returns you to the exact point you were. On product pages I think page-based pagination is the only way to go. Amazon does that. I think only feeds are a use-case where infinite scrolling makes sense.

P.S. I wonder if client-side ajax calls are GZIP compressed🧐

I can't understand why would somebody order something from Google and then use the chat "support" app to ask where their package is. All packages have tracking numbers and as soon as they are "on their way" you just contact the Courier or use their site to track it precisely. Why escalate it to the seller who has no idea where the package actually is?