Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Is Chrome the New IE? (2023)

magiclasso.co

Post reply on HN
Print view View original

201–210 of 316 posts

Re: Is Chrome the New IE? (2023)

#201

Post by fellowniusmonk »

Aloisius wrote: post #194
fellowniusmonk wrote: post #96

No not even close by every single possible measure. I was there, I suffered through it, Google would have to make TONS of hostile moves for that fact to change. I have no interest in the arguments of a closed source subscription service that wants me to switch to the bundled browser of the wealthiest company on earth's most popular consumer OS, lecturing me about using the 4th wealthiest company on earth's browser th…

Safari hasn't actually been particular far behind implementing industry standards. As far as I can tell, it's more that people seem to believe that Google dictates industry standards and base everything on when Chrome supports it as opposed to when it actually gets standardized. SSE's W3C draft standard in 2012. Supported in Safari in 2010. web sockets This one is true. IETF standard 2011. Supported fully in Safari 2…

This is very misleading, compare implementation timelines between browsers and you'll see that Safari has implemented many of these things year(s) after chromium, firefox and even opera. This of course was because they have tried as much as possible to push people to closed source/walled garden apps.

Re: Is Chrome the New IE? (2023)

#202

Post by nerdix »

lxgr wrote: post #151
rty32 wrote: post #128

Earlier quoted context omitted.

That's a very arrogant attitude. I'll give you one example: I sometimes can't open OpenAI API documentation due to some stupid Cloudflare captcha checks. No, on Firefox, however many times I click that checkbox, I can't go through the verification, just to read some static content. Not even if I disable adblock and tracking protection. I don't even see a checkbox at all on Chrome or Edge.

Cloudflare captchas are an excellent point. Sure, technically nobody is excluded: Just solve the captcha! Fraud heuristics are only reasonable, right? But it's all fun only as long as your situation occurs within the 90th or 95th percentile of all data labeled "good customer". Good luck if you're out side of that...

But thats not Chrome's fault.

I mostly use Chrome on Linux (fully Google distributed, closed source Chrome...so not Chromium) and I see those cloudflare captchas at a much higher rate than I do when using Windows or macOS.

Re: Is Chrome the New IE? (2023)

#203

Post by tapland »

dudhejffj wrote: post #175
bloppe wrote: post #163

Earlier quoted context omitted.

Am I the only one left happily using Firefox? You know, the only "major" browser that doesn't seem to have these conflicts of interest?

I use Firefox Mobile but have long abandoned the desktop offering. The only thing I feel like I get from the desktop version lately is a spiritual victory whereas the mobile browser actually has tangible features I prefer like add-ons and the search bar at the bottom.

On iOS it’s still safari backend though?

Re: Is Chrome the New IE? (2023)

#204

Post by steelframe »

When I parked a rental car in downtown SLC last week I had to find a way to pay to park. There was a kiosk with a functional screen, but the touchscreen part of it was broken, so I couldn't interact with it. I plopped my stuff down and sat on a concrete bench in the cold and dark to try to figure things out on my phone.

The QR code sent me to a website to install an app. Google Play store said the app was designed for an older version of Android and couldn't be installed on my device. I eventually found a "pay online" link hidden down the page a bit, then spent several minutes filling in my credit card number and what not. Then when I got to the part where I was to select the expiration month and year, the drop-down menus simply didn't work. I had no way to continue in my default browser, Firefox.

It had been 7 or 8 minutes, the cold was starting to numb my fingers, and I was no closer to actually paying for my parking space. I debated just canceling my appointment and driving away rather than risk a parking ticket, but I decided to give it just one more try in the Vanadium browser. Lo and behold, the drop-down menus worked, and after over 10 minutes of messing with a broken kiosk, a broken app, and a broken website, I was able to proceed to the point where I punched in my parking space number. Which, of course, wasn't marked.

At that point I looked up and down the side of the street and noticed a post with numbers for two spots behind me. I noted which number was bigger to infer whether my space would be one higher than the higher or one lower than the lower and punched that in. After my appointment I came out to find the car parked behind me had a parking ticket, while my car didn't. So I guess I managed to punch the right sequence of buttons on my phone to avoid a parking fine.

However the fact remains that I couldn't legally park my car in Salt Lake City unless I was in possession of a functioning smartphone and was running a Chrome-based browser on it.

Not sure if this is more a story of Chrome being the only browser that's tested and/or compatible with critical services I need to use to function in a major U.S. city or if it's a story about municipalities like Salt Lake City making things as difficult as possible for people so as to collect more revenue from fines.

Re: Is Chrome the New IE? (2023)

#205

Post by 1over137 »

steelframe wrote: post #204

When I parked a rental car in downtown SLC last week I had to find a way to pay to park. There was a kiosk with a functional screen, but the touchscreen part of it was broken, so I couldn't interact with it. I plopped my stuff down and sat on a concrete bench in the cold and dark to try to figure things out on my phone. The QR code sent me to a website to install an app. Google Play store said the app was designed fo…

The machines don’t take cash?

Re: Is Chrome the New IE? (2023)

#206

Post by MBCook »

int_19h wrote: post #145
gtk40 wrote: post #104

Earlier quoted context omitted.

I manage websites for a couple of non-profits. A very high percentage of traffic is from Safari (mostly on iOS) -- 40% on one site. Only testing in Chrome seems like a bad idea.

It really depends on where in the world we're talking about. iOS is big in some places (like US) but insignificant in others.

It also depends on the kind of site. The more the operator thinks you should be using a desktop, the worse it is.

Re: Is Chrome the New IE? (2023)

#207

Post by Aloisius »

fellowniusmonk wrote: post #201
Aloisius wrote: post #194

Earlier quoted context omitted.

Safari hasn't actually been particular far behind implementing industry standards. As far as I can tell, it's more that people seem to believe that Google dictates industry standards and base everything on when Chrome supports it as opposed to when it actually gets standardized. SSE's W3C draft standard in 2012. Supported in Safari in 2010. web sockets This one is true. IETF standard 2011. Supported fully in Safari 2…

This is very misleading, compare implementation timelines between browsers and you'll see that Safari has implemented many of these things year(s) after chromium, firefox and even opera. This of course was because they have tried as much as possible to push people to closed source/walled garden apps.

I'd argue calling non-standard chrome/firefox/opera features "standards" is misleading.

Re: Is Chrome the New IE? (2023)

#208

Post by hombre_fatal »

PeterStuer wrote: post #166

As a Firefox mainliner for 'legacy' reasons to be fair, I often have to revert to Chrome to get sites to work. I guess there are a lott of dev shops out there that just test on Chrome/Edge (and maybe Safari)

Besides, Firefox has its own problems.

The craziest is its permissive same origin policy compared to Chrome/Safari, like how `window.top.location.href = 'https://example.com';` works from inside a cross origin iframe to redirect the parent.

Re: Is Chrome the New IE? (2023)

#209

Post by wannacboatmovie »

steelframe wrote: post #204

When I parked a rental car in downtown SLC last week I had to find a way to pay to park. There was a kiosk with a functional screen, but the touchscreen part of it was broken, so I couldn't interact with it. I plopped my stuff down and sat on a concrete bench in the cold and dark to try to figure things out on my phone. The QR code sent me to a website to install an app. Google Play store said the app was designed fo…

Front end developers bear the responsibility for this nonsense, and many of the guilty post in this very forum!

There is nothing in what you described that couldn't be accomplished with late 90s-era technology.

Why is an app needed? A simple web page with basic HTML, enter number plate or space number, enter payment info, submit, done. No browser features introduced in the last 20 years are needed. The only improvement is enhancements to security - so we're up to TLS 1.3.

Do we really need spinning pinwheels and bleeding edge web standards to process a simple payment?

Post reply on HN