cube00

One less app to manage, audit and provide end user support.

> These clouds must get the abuse happening under their own roof under control.

Similar to ad click fraud and scam ads, the cloud provider gets paid, why would they turn down the money?

> Music in the kitchen, sure, but I run Plexamp.

As much as I like Apple hardware I know unless I'm willing to go full Apple on hardware and services (eg. Apple Music in this example) I'm always going to have a mid experience trying to be on the fence of their walled garden.

> An issue with old iPads is getting OS updates.

I'd have the same concern with this device given Apple haven't committed to longer then usual support.

At least I already got my money's worth from the old iPad and being able to give it a new role on the kitchen bench was a bonus.

> believe me, there's a reason the industry moves slowly.

No profit in security/dependency upgrades. Propriety SCADA protocols to enforce full stack manufacturer lock in.

> Process forking isn't nearly as expensive as it was; modern kernels optimize it heavily.

When I start to dig into how complex async is to debug I'm really starting to come back around to regular forking.

> wave a re-hiring people

While they'll be some for the companies that cut too hard, I don't see a wave coming.

It seems the "kinda sorta" works level that AI vibing creates is seen as good enough by most companies.

While it's true they've always accepted mediocre software I feel AI vibed code is a step below that in terms of quality.

Of course if you're willing to put in the hard graft to carefully write detailed tests and then send your agents away until everything passes then you'll get a better result.

The automated tests I've seen the vibe tools pump out aren't there yet so you still need to put the effort in there.

I doubt anyone that wants to keep their job in big tech would ever publish something like that.

Interesting that it can only count iOS devices considering Apple is more privacy focused. What's the secret sauce that prevents Android phones being counted in the same way?

I would have thought Android's constant Wi-Fi scanning that Google uses for improving their indoor location services would be an easy give away.

> A lot of companies exists as of today cause a lot of people were able to just focus on building without constantly worrying about the fear of lay off.

Depends on the company, plenty have been run on a culture of fear for decades.

> Asos did not immediately respond to the BBC's requests for comment.

Amazing how companies think if they say nothing it'll somehow just go away. Couldn't even be bothered to reply to say they're looking into it.

If Joe average let their agents out like this they'd be in jail.

Interesting that Microsoft doesn't seem to have had a sandbox breach yet, you'd have to assume they're running similar agents, maybe a secure sandbox is possible.

Careful with this, it's made to look like it's from Apple with links back to their developer docs but I don't think it is. Text alignment doesn't work, randomly throws up full screen modals asking you to upload, feedback link shows the same about page as the acknowledgements link so there's no feedback form, drop downs are light grey text on white backgrounds.

Edit: It's actually the commentator's undisclosed own vibed project https://news.ycombinator.com/item?id=49101586

> anything heavier than a web browser

The way Chrome feasts on RAM, might need the cloud for that too.

I got a Google survey this week.

Which of the following are the reasons you chose Google Play related issues as one of the weaknesses?

The second option, written by Google was:

- Sudden account termination without actionable feedback or clear restoration guidance

They know they're killing accounts without due process, they don't care, why would they? They're the only game in town now the Android Developer Verification Program is in force.

Not needing 30MB of JS probably helps.

Enterprise security in depth.

I probably incorrectly read

> we provide that customer’s connection to the internet

as providing the DNS infra for their customers.

> There was no unauthorised access and no compromised systems. This was an overload attack, not an intrusion.

Hopefully your logging infra is rock solid and nothing has been dropped in the flood. It wouldn't be the first time a DOS was used to mask the actual attack by overwhelming the monitoring infra.

> Use a CNAME or ALIAS record instead of an A record. An A record ties your domain to one specific IP address on our platform. That fixed binding was exactly the problem during the attack: wherever we could change the address on short notice, availability could be restored, wherever we could not, only the blunt measure remained.

I don't understand how this helps. CNAMES have TTLs like A records and they eventually have to terminate at an A record somewhere so why pay for an extra hop?

> They did have a self-service app store you could use to install things.

We had this too. The apps were years out of date because they needed to be manually packaged for the internal store. The one person who was allowed to run the recorder to monitor the vendor installer (because that requires admin level to monitor other apps) to create the store install script has 1000 other package requests ahead of yours.

> Why on earth wouldn’t the respective government spend money to modernize a critical infrastructure like a nuclear power plant?

Same reason they don't modernize health care infrastructure. It's too expensive, people die if they get it wrong and they get voted out of office for their troubles.

> Stopped reading here. Author has little idea of the industry.

Which industry? The shopping affiliate industry feels just like the kind of industry to cut any corners it can to make a few more cents per transaction so they can offer "free" shopping agents and make their money off the commissions.

> Look, I don’t know where we are going.

As honest as it is I can't risk using this anywhere near production if this is the attitude.

> I sent an email to my friends with a link to the location and said, "check this out in a couple of months!"

This is an example of behaviour I personally find frustrating.

My internal thought process: There's nothing I can do with this email when I first get it, will I remember to check months later? Probably not.

> We had a slightly stupid moment when we thought we'd got it wrong, and the clock was running backwards - only to realise we were inside the clock and so were looking at it the wrong way.

I can heavily relate to this when debugging something that builds bottom up.

That's some nice cbf spelling of always and recognition on that slide.

> Also you want to reuse code via package management systems.

I thought everyone was on monorepos to "solve" that.

I was on a project trying to migrate off Oracle and they wanted to just dump all historic data to CSVs.

I pointed out they'd lose a lot of the integrity and audit features built into a database.

I get wanting to be free from Oracle but go to another database.

> The PRO version lives at tmog.store

https://tmog.org/pro.html

> When it went to flip into the backup, we discovered that the backup fiber had a break

Pretty grim that a life critical system wasn't designed to report that the backup fibre was unserviceable until they attempted to switch over to it.

I wonder how long it was down? Days, weeks, months?