pontilanda

ChatGPT is a joke for this. Any interesting/funny topics result into a judgmental response and refusal.

I asked to write a 100-words first message for a Tinder match who had "very talkative" in their bio. ChatGPT kept saying how it would be rude of me to send such message and both the other person. FFS.

Re: child labor.

It's awful but who sends these kids to work? What will a mother of 3 children do if she can't feed herself?

It's a terrible cycle but it takes ages to fix. No foreign company is benefitting from Bangladeshi kids making low-quality bricks for their village. What is the solution today? If you tell them they can't work, who will feed them today?

Are you personally going to donate your money to not only feed all these people, build schools and infrastructure, but also $20/hour to everyone involved in the process?

The point of bringing jobs to Kenya is that they can pay less. If you don't see that as a benefit, why should I, a business, go to the trouble of working with a Kenyan company rather than just do it locally?

I could pay a Kenyan $17 an hour, or I could pay a Kansan instead and get US government benefits. The same applies at every payment level. Your logic fails the moment you realize that not every person/worker on earth is equal.

Insisting on this sort of articles just goes to show how sheltered these offended people are. I live in the third world and I know people who are thankful to Coca Cola for their "$2 wages."

> That sounds overly dramatic

Try appending this piece of code to your `index.js` and let me know how it goes in Safari:

    const r = /(<!foo)/

The parser will encounter a syntax error and no code is executed.

Chrome already won, non-Apple users basically don't have a choice.

Please tell me how Chrome has "slowed down" after reaching the current market share years ago. It's not like Safari is the one making on-spec progress like Firefox did in 2005. Sounds like you're the one not understanding the early browser wars.

Google won the web years ago and it's still "innovating." By "is the new IE" people generally mean the 2007 IE, not the 1999 IE. I don’t think many complained about those shiny new ActiveX APIs in IE 3 and Chrome doesn't really have anything like that (even though they push features out with few signals from the rest of the platform)

> Also you should rethink your life if you consider yourself a Twitter/Reddit power user.

I'm not, but people can make money on those platforms nowadays, so don't be so judgmental.

Content. If your platform sucks, power users can hang around, using power tools.

This isn't so much of a problem on Twitter as much as Reddit, though. Their native experience is okay (it's just the users that are insufferable)

All that looks good on paper, but a lot of apps require full disk access and can easily run in the background, so how "trustable" can that really be in practice?

With iOS at least I know that apps really are sandboxed and cannot access anything unless I grant permission. No app can ever attempt to access my photos unless I explicitly pick a photo or grant partial/total access. Even then it's read-only or "write with confirmation, every time"

Chrome is not the the weakest / furthest behind major browser

Anyone who disagrees hasn't tried to develop a website on Chrome and Firefox only to find out Safari still doesn't support regex lookbehind (which means zero javascript will now run). It's only been available in Chrome for 5 years after all, no rush.

Super nice to scroll a 150-lines-long list of countries by swiping on a 1-inch-tall target on my huge screen.

Even now it's stupid they don't offer keyboard filtering.

Are you talking about the OTP delivered via unencrypted SMS? Surely Apple knows how to set up a link with a barebones encryption better than SMS’

I've been using Safari for years now and I still think it's poor in many areas.

URL autocompletion is an absolute joke. Detaching tabs has been browser-crashingly-bad for about a year. Still no way to tell whether the current page has already been bookmarked. Performance is pitiful on large pages (e.g. long PRs on GitHub) to the point typing is takes whole seconds longer. Pointless "apps" for web extensions, which make it unnecessarily complex for non-Apple developers to publish web extensions for Safari.

I only use it because it's not Google’s and because it integrates better than Firefox. If I didn't have an iPhone I would never think of using Safari on Mac.

If you don't trust Apple to enforce that, can you even prove that Apple won't act as a key logger too?

The sad thing about clickbait is that it works wonders, and you'll never guess what happens next!

> tests are much better at giving you a glimpse of what the code even does

Types do that, they tell you the expected input and expected output. No type nor test is all-encompassing of course, but it gives at least some information.

No test will guarantee that a function will never return a number. Types, if valid and without prototypal shenanigans, can.

Static as in "the page is pre-generated, not generated on every HTTP request"

It's the right setup for write rarely, read often scenarios.

Are tests useful? Because this is what TypeScript gives you: it helps you avoid regressions.

If I change a signature, tests fail. If I pass junk data, tests fail. It's like invisible live tests and people forget this.

As in the other recent discussion, yeah, you can live without tests and you can live in JS-land. Whether it's worth it it depends on you. TS and traditional testing lets me ship updates without even opening node or the browser.

Even cheaper than a flight and chump change compared to a private helicopter. Apples to oranges.

Bad programmers are all around us. It could have been fixed with a min() call

That also loses line breaks, as well as requiring significantly more steps for a single copy-paste.

It’s just because they were developed by white males /s

I badly need a "tour" mode

> This would amaze anyone from before the 70s.

I'm not saying that it's impossible, I'm just pointing out your smugness at the fact that it's not common knowledge.

> the Starlink stuff

You mean the stuff that requires a large, hot disc on your roof and therefore not in your pocket? Are we talking about the same things there?

> I'm pretty sure T-Mobile wouldn't have signed

You trust big companies too much, they make mistakes all the time.

What? My wifi barely reaches the other side of my room with a wall in between, how am I supposed to think 350 miles is within reason? Even with clear sky, your signal to a tower an order of magnitude closer would be unusable.

If you look at apple’s latest feature, even them, with specific hardware probably, requires minutes of open-sky pointing directly at the closest satellite, to transmit mere bytes of data.

That tells me that if your phone is just hanging in your pocket, indoors, with a 5G nearby, it’s not going to reach the satellite at in any shape or form.

Apple is ok but the Music app is still atrocious for streaming, so it’s not like they’re particularly better at it. They made zero improvements to network reliability issues since their streaming service was launched, which is totally laughable considering that network is the core of streaming.

As an Apple user, I’m aware of the insane limitations I have in every part outside their garden. Have you tried adding a ringtone?

Browsers and engines are also regularly patched to improve web compat. I remember V8 "recently" released an update to improve the performance of a very common module. The details escape me however.

> doesn't the new one the bank sends you usually have the same number?

Never happened to me using several European banks. Either way the date and CVV change so that's part of the new password.

> Yes it does. The more often you have to pick passwords, the more likely you are to pick weaker ones.

I don’t think so. People will just change the number at the end, it's not like they will stop using aDgTGdE and start using 11111112 simply because of rotation. It's more likely that they will append a ! or change helloworld to helloworld2. It's not a downgrade by any mean.

Plus such rotation even "guarantees" that the password isn't shared across services, unless they're all rotating with the same frequency and they all start with helloworld2

The interoperability boat has sailed. macOS has had an open Keychain for decades and Google eventually dropped support for it. I don't see them suddenly going back, sharing efforts and allowing cross compatibility.

What we need is just passwords to come front and center anywhere they are: We need a Password.app that I can open and access all I need. Keychain Access was exactly that but its UI is stuck in 2000.