Menu_Overview
Prompt: Here's a blueprint of my new house and a photo of my existing furniture. Show me some interior design options.
When I charge my watch at the end of the day, I usually have plenty to spare, but not always enough to make it through to the morning (especially if I tracked an exercise). Even if a new watch got 24hrs of battery life, I would still have to charge it at night so I wouldn't really matter. I'd guess that 18hrs it a balance that keeps people content and gives Apple's engineers enough room to fit in all the features they want.
Of course, I would love to be able to track a long exercise or a 10-hour hike...but there's a different price tier for that.
If your portfolio's content is simple enough for one page, or just a unique pages, go for just HTML! You will like it. Static HTML files (with a bit of JS) will be easy to deploy and better for SEO and performance.
That said, you might quickly find you want something with more capabilities.
Through my experience, you're eventually going to want some sort of template engine. Want to reuse the same "article" layout or you want a for-loop over a list of articles? Templates. Your template engine could be as simple as Pug or Handlebars templates, no client-side rendering needed yet. Compile your templates and deploy your HTML files.
Pug (or other template engines) will probably carry you a long ways. The next step would be some sort of static site generator. This is basically the same as Pug, with with extra options and more structure. Hugo and Jekyll are popular, but there are a lot of options. Deploys are the same: build locally, deploy, or set it up with some hoster like Netlify or Vercel to build and deploy automatically (and for free!).
The next level is something like Nuxt, Vuepress, or Next, which can generate static websites, but also give you fancy things like client-side rendering for fancy page transitions (although there is now a native way to accomplish this with just HTML and CSS!). My blog articles are written in Markdown so they are easy to port to other frameworks or themes. This is the approach that I use because I like to stay up to date with Vue...but you'll spend a lot more time "upgrading" things instead of building or writing. Just my experience.
I considered it a few times, but like, it only spaced the payments out over 6 weeks and I had to unfreeze my credit report so...it wasn't a big win.
I miss my old iPad mini 4. I guess I could try the 11" iPad, but I think I'd prefer it to be smaller.
False. Obviously this depends on the work, but an LLM is going to get you 80-90% of the way there. It can get you 100% of the way there, but I wouldn't trust it, and you still need to proof read.
In the best of times, it is about as good as a junior engineer. If you approach it like you're pair programming with a junior dev that costs <$20/mo then you're approaching it correctly.
Only issue I have is syncing. There is no wireless sync, right? I have to plug it in to sync my library and tack on extra files.
The Overdrive/Libby support is excellent, though.
JS is probably where you should look. You might be able to find a good PHP drawing library but I've never come across that in my work. Lots of image converting libraries out there (usually just a wrapper around ImageMagik), but "drawing images" usually a client-side thing and you'll find more support for it.
In JS, you'll draw the image to a `<canvas>` element, which can then be downloaded as a PNG. You could go the SVG route, too, depending on the art style. Canvas is the safer bet.
> producing many copies by repeated direct impression
Of course, VitePress can be used for all sorta of stuff. My old website used to be based on it. If you click through the sites using VitePress you can see the similarities and what you get for free with the default theme.