These days, with LLM assisted development, with relatively simple GUIs, I would go towards platform native GUIs per platform. And then all the shared business logic goes in a shared "core", with the GUIs only serving as "dumb" inputs and outputs, with all business logic shared between them.
LLMs are quite good at tedious tasks such as keeping multiple GUIs in different languages in sync with each other.
You still need to test all of those separate GUIs though so it's still costing more.
You also generally don't want them to actually be in sync because there are actual UX differences between platforms that you need to align with to really be native. If you don't follow that then what's the point?
I think this was right at the beginning, in the GPT-3.5 era still.
I always wanted to put it behind an open SSH server as a "fake" honeypot of sorts, see what attackers and script kiddies do with it. But I guess by now someone's tried that already..
That's why downdetector shows a chart, which is basically a chart of how many people clicked "I'm having a problem with this service". Of course you get a small amount of people having issues, but if you suddenly see a big spike on the graph, it's a good sign that it's broken for many more people than usual.
Or at least: It's a sign that people were compelled to push a button.
I've seen it happen over and over again when a wireless provider like Verizon or a docsis provider like Spectrum has a widespread outage that is isolated to their service: People push the wrong button.
Verizon issue, other providers fine? Verizon spikes on downdetector, but so do reports of AT&T and T-Mobile problems.
Same with Spectrum: When it's screwed up for whatever reason, reports for other ISPs also spike.
This happens even when those other systems are completely unaffected and working just fine.
Downdetector does provide useful data, but it's not necessarily clean data that establishes anything clear on its own.
Its a great product when it works. When it doesn't, for example if they decide to freeze your money for no reason, it's not fun anymore. And there's plenty of reports of that happening to people.
You mean because they have automated AML/anti-fraud systems that all banks must have; every bank wrongly freezes accounts. To your mind, Revolut does that worse than others. I disagree, but without hard evidence, it's just our hunches at odds.
Yes, sure. But at my brick-and mortar bank I can go and talk to a flesh and bones human, instead of to an AI robot. Which is a much better service, when the anti-fraud thing does happen.
The revolut anti-fraud thing also seems to be less well done, being easier to trigger than other "real" banks.
Instagram already does charge for outgoing links, so I would assume that they found that they can sustainably make money with it there, and that it should work on FB too.
I thinks what's more happening is bespoke software made by people for themselves mostly, often with a user count of 1. That's quite a huge change, for users of that software. Of course such things are not replacing existing apps.
I guess, in practice this can also be likely be made to run google services, the same as they can run on custom ROMs. And it already lists Aurora store as a solution.
So it's definitely something for more tinkerer people, but still quite cool.
What? Niantic (Google) admitted they were training spatial AI models. I have not seen evidence that the data was a "foreign intelligence-gathering operation" and I would welcome a source.
Soo many more things than banking apps at this point. Things as normal as looking at train schedules, grocery store catalogues, ordering a taxi... sometimes have SafetyNet DRM.
When you publish apps on Google Play, the Play Developer Console even nags you to use harder obfuscation and implement Google's DRM to, allegedly, protect yourself and your users.
Can the EU finally make this shit illegal? Oh wait, they're pusing for mandatory DRM too... Fuck.
Fortunately, there are (at least for now) many, many banks to choose from, and you can tell the app-only ones to suck it. There's also almost no switching cost. The last time I changed banks, it was mostly done in an afternoon.
I do wonder how long the electronics, motor and little (plastic) gears in the drill would last with this. Especially since I'd suspect that it's designed for intermittent use, where it has time to cool down between each screw / hole drilling that you'd do normally. If you drive 2 miles in one go, that'll be a lot of heat that doesn't have time go anywhere.
Somehow I'd suspect that it won't last all that long...
I suspect there's very little power needed once you're up to speed and cruising, but constant stop-and-go and long uphill runs will certainly cause it to overheat.
It's brushless so brush wear isn't a problem, but these motors are air-cooled and will actually be cooler at high speed, low-demand. Lugging it up a hill would be a worst case.
LLMs are quite good at tedious tasks such as keeping multiple GUIs in different languages in sync with each other.
reply