Your idea sounds a fantastic way to make a system incredibly complicated with no actual gain other than a billing dystopia.
4,280 karma · joined July 19, 2023
Your idea sounds a fantastic way to make a system incredibly complicated with no actual gain other than a billing dystopia.
1. Company stuffs ads down my throat.
2. I use adblocker
3. Company blocks me
4. I ignore company.
The whole problem starts at (1) which is "create a business supported only by advertising revenue". That says your actual product is worth fuck all.
New wing mirror cost me £25!
Granted that's a problem but really it shows everything is a matter of perspective.
Regardless of what stands, it's pretty damn good at the moment. I have a pocket computer that talks to people all over the world. So I have two messaging apps on it? I'm not even bothered.
The thing is I don't actually really dial anyone with their phone number any more other than close family. Most of the time I will use whatsapp video calls because said other person is usually somewhere that roaming doesn't work and is tethered on a WiFi hotspot instead. Granted that uses name resolution via phone number but it doesn't need to.
I mean they do truly useful stuff already using ML just not LLMs
What they don't do is sell you a lie a year before release then deliver shit (like every other fucking vendor).
The point is bad news spreads to "I won't bother".
I actually have a cheap Columbia synthetic down jacket and it's lighter, packs better and warmer than the really expensive proper duck down one I had before.
Those big ass SQL boxes cost serious money.
Back in the dark ages had an "OS" which had a simple "task table". This was a circular linked list with enough space after each pointer to store the CPU state for a task and some stack. There was one element per task. The task interrupt would fire every 100ms, the registers/stack pointer/PC would be dumped to that, the list followed and the next task picked up and loaded into the CPU, then it'd return from interrupt and off it'd go again. You could call YIELD at any point if you didn't want the rest of your time slice. If you had something that needed to handle an interrupt from the CTC or an NMI, it would disable interrupts until it was done.
Notably you didn't tend to create new tasks. They were hard coded in at assembly time!
Edit: we also had an 8031 version as well.
Which is my point about it serving the needs of the publisher, not the end user.
I don't want to run another virtual machine that eats up RAM, has worse performance and battery life than something natively compiled and generally serves only the interests of the person servicing it to me.
I want apps that are 100% native and work when occasionally connected. And I want the www to go back to servicing content, not apps and garbage to me.
I don't want a gigabyte RAM footprint Electron app that ships Rust in webassembly to read emails when my current mail client used 77 meg of RAM and just works. I don't want 50 browser engines running on my phone.
I think as an industry we've lost our way and turned to crack smoking crazy.