|
I have developed mobile apps for both Android & Apple.
In the past, Android Studio and Kotlin was the best.
Building hte UIs was very nice using the XML (normally I hate XML-anything).
Android apps had the same feeling as developing apps for early windows using MFC & Visual Studio C++.
Really not that bad once you learn some basics — but Android added many things (paths) to creating apps (Jetpack, Materials (UI framework) and it got really confusing to know which path to take.
iPhone apps were terrible when Swift first released — still using InterfaceBuilder (there were things you could only do with your mouse — adding button click events — & it was crazy)
Then iphone released SwiftUI and building the UI became so easy!!!
I couldn’t friggin’ believe it. It is like using the old Visual Studio C++ winform editor but even better. I love it. I can’t believe I love it because Xcode (IDE kind of sucks)
Building apps is like old winforms apps:
1) build UI
2) connect events
3) run the app *
*of course you still break things up into classes (Models) etc, but I’m just saying the basics of building a UI and wiring it up is elegant and beautiful.
The big problem is that you have to have a Mac to even try Xcode and SwiftUI — so you have to go all-in.
|
|
|
|
|
obermd wrote: At this point I think any mobile apps I'd write would be pointers to a website that's written to detect screen sizes and adjust.
Isn't that what most mobile apps are nowadays?
Disclaimer: I've never written a mobile app in my life, except in the days of (yikes!) Windows CE. That was before anything got connected.
I avoid installing apps on my phone if I can help it, and I shudder when I see people showing me their phones and the loads of apps they've installed, which ultimately are just horrible, touch-enabled UIs that just castrate what would be a much better experience on a large monitor using a mouse and keyboard.
And then every app insists on being granted access to your contacts, your call history, your photos, your location, etc. Most apps have zero need for any of that to function, so we know what that's really about.
|
|
|
|
|
One issue with training data is it's often pulled from copyrighted material, whether deliberately or through an automated process.
Another issue, probably overlooked but I mentioned it on the discussion is "model collapse"
You can't get good models if your training data is generated AI content as well. It is essentially incestuous, and leads to model collapse. AI models collapse when trained on recursively generated data | Nature[^]
I'm thinking regulations could actually solve both of these problems.
AI could avoid using data marked as NOT training data. Data generated by AI and copyrighted material could be marked that way, and flagged as off limits to automated processes that scrape. AI companies would have incentive, not only because of regulatory statutes, but perhaps more importantly so their own models don't get poisoned.
Thoughts?
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
modified 1-Aug-24 11:54am.
|
|
|
|
|
Because robots.txt works so well ...
Regulation is fine, as long as it can be enforced. If there's an enforcement mechanism that has sufficient teeth to discourage abuse of the regulations, the maybe it will encourage ethical behavior on the part of organizations creating and distributing AI.
I feel like we need an equivalent of Asimov's "Three Laws of Robotics", but for AI.
"A little song, a little dance, a little seltzer down your pants"
Chuckles the clown
|
|
|
|
|
There's definitely the problem of enforcement, but what I would say is that
A) It already behooves the AI companies to follow suit as it keeps their models from becoming incestuous and collapsing.
B) As far as people putting invalid tags on things - that's why I suggested tags marked NOT for consumption, because again, it typically incentivizes and otherwise doesn't really burden people to do it. It protects their copyrighted material in the first instance, and in the second, since the content is generated anyway marking it with tags is no bother.
C) In regards to actual teeth and where the regulatory statute might be leveled - if someone is knowingly producing generated content to poison other people's models and it flies in the face of said regulations it at the very least exposes the actors to civil, if not criminal liability. Civil liability in the states isn't so difficult to prove as a criminal case, relying on the standard of "a preponderance of evidence" rather than "no reasonable doubt". Such a case seems easy enough to make in many instances, although suing Russian actors from the states might be problematic. Still, that's a problem with the internet in general, and the argument that we shouldn't make a law because it can't always be enforced is pretty much a non starter, as that could apply to many laws already on the books.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
I'm not sure how the copyright material stuff should be worked out. I categorically disagree with the idea you just can't/shouldn't be able to train on copyrighted data.
If it is available to people for consumption then it should be available to feed to an algorithm. Piracy notwithstanding. But I'm not sure why you should have to buy all the media over and over again, even as an individual and that's kind of how we've been doing things for a bit.
I'm skeptical that regulation of the wild west would do more than make the natives restless and the cowboys chuckle.
The cost of trying to 'filter' all the content to not scoop that stuff up probably means that something purpose built (RISC?) to test content for model collapse against a model would be really useful.
|
|
|
|
|
jochance wrote: I categorically disagree with the idea you just can't/shouldn't be able to train on copyrighted data.
The danger in that, particularly where it pertains to code, is what if you indirectly rip from IBM's codebase via AI? Do you really want a behemoth like that coming after you with lawyers?
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Recognizing that how things work and how I think they should are two different wildebeasts...
Of course not, but I somewhat object to the idea that IBM (or anyone else) should own trivial bits of code. I can get onboard with a copyright across the whole of a system's code. But we'd never be on board with the idea someone can "own" singular or smaller groupings of lines in isolation and why would we? You and I have almost definitely typed some of the same lines of code before and we'd never even know it.
In my opinion, the ratio of code worthy of the protections of copyright is just super low. If it were a Far Side cartoon it would be a caveman courtroom drama over Thag copying his neighbor's stick figures from their cave drawings.
Most of the value isn't really in the code itself but whatever it is the code is doing. If you can rewrite that in another language or even the same one then you've effectively 'stolen' the value legitimately. Some of the best bits of problem solving code are just going to be the same (or close) no matter who/where they come from, especially if the problem itself can map to code in straightforward ways.
|
|
|
|
|
jochance wrote: If it were a Far Side cartoon it would be a caveman courtroom drama over Thag copying his neighbor's stick figures from their cave drawings.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Apparently there's a software patent for saving the portion of a screen that will be overlaid by something else so that it can be quickly restored later. Utterly deranged.
|
|
|
|
|
Lol wut? I wonder if that dates to really old ASCII based UI. It's the only thing off the top of my head that makes it make sense.
Hasbro bought a bunch of IP from Atari. Amongst it, I think, was Pac-Man.
This led to a short-lived claim and series of suits which were premised on the idea that any game featuring a protagonist in a maze like environment was a derivative work.
Bold move, Cotton.
|
|
|
|
|
And told me I am great to work with a wonderful person besides.
And now I'm all warm and fuzzy. 
Feels better than a paycheck when it happens.
Though I'll take the money
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
|
It crossed my mind.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
One atta-boy whipes out a whole bunch of oh-sh*ts.
A home without books is a body without soul. Marcus Tullius Cicero
PartsBin an Electronics Part Organizer - Release Version 1.4.0 (Many new features) JaxCoder.com
Latest Article: EventAggregator
|
|
|
|
|
And one castigation, especially if heard by others, can damage a relationship beyond repair.
|
|
|
|
|
In other words; Don't step on the toes of the person whose ass you'll have to kiss tomorrow.
A home without books is a body without soul. Marcus Tullius Cicero
PartsBin an Electronics Part Organizer - Release Version 1.4.0 (Many new features) JaxCoder.com
Latest Article: EventAggregator
|
|
|
|
|
It might turn out that way, but it applies just as much between a manager who needn't fear ever having to work for the person being chewed out. The best boss I ever had put it as, "So hard to build [trust], so easily destroyed."
|
|
|
|
|
No doubt, it definitely feels good! That's why I also use this tactic to motivate employees.
Think about it 
|
|
|
|
|
I mean, I don't think it was done with the intent to motivate me, as I'm pretty motivated to begin with - goes with loving the job. I think I just have a great client. 
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Reminds me of when a guy in the support department for our major development environment at that time sent me a Christmas greeting to his favorite customer: The bug reports from us (for all practical purposes: me) were exemplary: Clearly stated, reduced to the minimum required to reproduce the problem, and with lucid descriptions of how to progress to provoke the bug. If all customers had been like that, he would have been a happy man.
That is the single Christmas greeting I don't think I will ever forget.
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
Part of my job at the tiny company I work for is to look after the licenses we sell our customers and to help them get going, or upgrade to newer versions, that sort of thing, and I can absolutely do some of the more advanced tech support for any part of the code that I've actually written (and some I haven't).
Throughout the years some customers have gone out of their way to say how impressed they are with the support they're getting, our dedication to quickly finding solutions or going right ahead and implementing a bug fix that gets released within hours of a problem being reported. Those always make my day.
I never use a condescending tone, or treat customers like they're idiots, and always try to walk them through solutions just as if I was sitting right next to them at their desk and having a conversation.
|
|
|
|
|
Have you tested it? Any conclusions?
Quote: Did you know that research shows developers who use GitHub Copilot complete tasks 2X faster compared to benchmarks? Plus, the mental energy they save helps them feel more satisfied and have more fun with their work.
That's from an email I received from GitHub (MS)...
To be honest I can't say anythin good about Copilot - all 5 times I asked a question it bomarded me with total nonsence (and not working, and mostly not even compiling) code solutions, meanwhile not paying attention to the details but hanging on the recognized keywords (like picking 'working' from 'not working')...
However, I will form a firm oppinion after at least 50 times of using it...
"It never ceases to amaze me that a spacecraft launched in 1977 can be fixed remotely from Earth." ― Brian Cox
|
|
|
|
|
I may just be old and set in my ways, but I don't trust it (or any "AI") to write code, and even if I could, I doubt it would write code the way I write code. I don't like it, and I have little use for it. At best, it's a fancy google machine but stackoverflow, github and codeproject can typically answer my questions, and I trust them more.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
I was thinking that it may shorten search for documents/ideas as it should have scande a wast amount of code...
So it is either bad at finding things or the avarage of the code on the web is very low 
"It never ceases to amaze me that a spacecraft launched in 1977 can be fixed remotely from Earth." ― Brian Cox
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
