I think on-device AI will show up more front and center but in a few more years.
A big issue to solve is battery life. Right now there's already a lot that goes on at night while the user sleeps with their phone plugged in. This helps to preserve battery life because you can run intensive tasks while hooked up to a power source.
If apps are doing a lot of AI stuff in the course of regular interaction, that could drain the battery fairly quickly.
Amazingly, I think the memory footprint of the phones will also need to get quite a bit larger to really support the big uses cases and workflows. (I do feel somewhat crazy that it is already possible to purchase an iPhone with 1TB of storage and 8GB of RAM).
2TB microsdxc cards have been available for a year or so, and 1TB cards have been available for several years and are even quite affordable. They work in many Android phones including my cheap Motorola. So it's Apple's sky-high premiums that has made their 1TB phones surprising.
> But I’ve seen enough repos that I know what good practices look like.
This is the danger - I get why you think it's true, but it's not true. I've mentored many many bootcamp grads. The biggest danger with y'all is you don't know what you don't know.
Even if you are a really good bootcamp grad and you have good taste and ability, you do not have experience. Software experience is measured really in years and decades, not months.
I agree. But I’m not making enterprise software - I’m making fun little apps where people can virtually try on clothes. As long as I keep my customers data secure (which I do), I think its okay to vibe code this stuff away.
Nowadays people throw the term "refactoring" around quite loosely, usually meaning "rewrite" when that was not at all the original meaning of the term!
A little bit like how "vibe coding" quickly went from one definition to another even though people should have known better.
Apples and oranges. It is a nice tool for closed-source Broadcom devices that OpenWRT will never support. Otherwise it has nowhere near the complexity and features.
I use Tomato too, but I wouldn't say it offers many benefits over OpenWrt. The main thing is that routers based on Broadcom chipsets often only work with very old Linux kernels (such as 2.6.xx kernels), as the drivers are closed source. For these routers, the primary third-party router OS choice is to use Tomato.
I have not but if there was enough interest I could make a rough go at it. It's not a very complicated setup.
It's basically Alpine Linux with some custom sysctl and interface settings, sch_cake with custom settings, cdg, netfilter, Unbound DNS with some local zones for limited spam filtering and a cron based refresh of common domain names, blackhole routes for known clowns and DoH/DoT IP addresses, chronyd for NTP, dnsmasq for static and dynamic DHCP, gratuitous arp cron job to lower latency and steal back my IP if someone tries to take it and restore quickly from ISP router failover all running on a Protectli VPN class small business firewall with cron snapshots/backups from another node.
My first pass would probably just be a static page with linked text files of the configurations and a brief synopsis of what each file or in some cases individual settings are performing.
This article is attempting to make some kind of statement about 996 and "look, now it's here!"
But this is plainly ridiculous. The Bay Area has been full of high achievers the entire time I've lived here (since the 20th century). All the startups I worked at, people would work Saturdays. Not all the time, of course, but it was quite common.
The article talks about how they are controlling for the variation across time, and they’re reporting a new signal. So even if everyone was working Saturdays before, everyone is more working Saturdays now. (Edited typos.)
A big issue to solve is battery life. Right now there's already a lot that goes on at night while the user sleeps with their phone plugged in. This helps to preserve battery life because you can run intensive tasks while hooked up to a power source.
If apps are doing a lot of AI stuff in the course of regular interaction, that could drain the battery fairly quickly.
Amazingly, I think the memory footprint of the phones will also need to get quite a bit larger to really support the big uses cases and workflows. (I do feel somewhat crazy that it is already possible to purchase an iPhone with 1TB of storage and 8GB of RAM).