Apple's tablets are great, but I think we're just pretty close to the limit for these entertainment devices.
I have a now 7(!) year old Tab S5e that I use to consume media, and it's 5.5mm thick, with 10 hours of battery, a 1600x2560 super AMOLED, and quad firing speakers.
Nothing on the market makes me feel I need an upgrade over what was a $400 mid range tablet, because I have an incredible media experience on all my streaming apps.
I purchased an EV this year, my highest priority was range per dollar, and the vehicle I selected happened to be new because of current market conditions. (Equinox EV for under 25k otd after incentives)
I agree, claude is an impressive agent but it seems like it's impatient and trying to make its own thing, tries to make its own tests when I already have them, etc. Maybe better for a new project.
GPT 5 (at least with cline) reads whatever you give it, then laser targets the required changes.
With High, as long as I actually provided enough relevant context it usually one shots the solution and sometimes even finds things I left out.
The only downside for me is it's extremely slow, but I still use it on anything nuanced.
The author implies they're a highschool aged programmer.
They're likely along for the ride with their parents and very online.
I'd probably do the same thing at their age.
I think they are fairly interchangeable,
In Roo Code, Claude uses the tools better, but I prefer gemini's coding style and brevity (except for comments, it loves to write comments)
Sometimes I mix and match if one fails or pursues a path I don't like.
I've been actively developing a commercially deployed SvelteKit application, and I'd like to share some thoughts on my experience.
What initially drew me to SvelteKit was its simplicity. After setting up the project, I could work on one HTML/JS/CSS file at a time, leveraging the benefits of a modern framework without the accompanying complexity. This approach reminded me of the early days of web development, where dropping HTML files into an Apache server was all it took to get things running.
However, it's disheartening to see Svelte shifting away from that straightforward paradigm. From the outset, Rich Harris positioned Svelte's ease of use and simplicity as its key selling points. The current version of SvelteKit isn't bad per se, but I found myself preferring the earlier iterations. Back then, I didn't have to deal with constructs like `+page` for routing. I could place Svelte files wherever I wanted, and they would render seamlessly, all while enjoying the advantages of a modern framework.
This change adds layers of complexity that weren't necessary before, potentially moving away from what made Svelte appealing in the first place. I picked it up because I already knew what I needed to know.
The default model on ollama is the 7b distillation.
Its ability to solve basic math problems with reasoning is pretty cool, but other models of that size (qwen 2.5, phi4) have been generally more useful to me.
These tiny models still strike me as toys, not a whole bunch of real-world utility.