1) I am able to run the model on my iPhone and get good results. Not as good as Gemini in the cloud, but good.
2) I love the “mobile actions” tool calls that allow the LLM to turn on the flashlight, open maps, etc. It would be fun if they added Siri Shortcuts support. I want the personal automation that Apple promised but never delivered.
3) I am so excited for local models to be normalized. I build little apps for teachers and there are stringent privacy laws involved that mean I strongly prefer writing code that runs fully client-side when possible. When I develop apps and websites, I want easy API access to on-device models for free. I know it sort of exists on iOS and Chrome right now, but as far as I’m aware it’s not particularly good yet.
Does relying on larger players result in better overall uptime for smaller players? AWS is providing me better uptime than if I assembled something myself because I am less resourced and less talented than that massive team.
If so, is it a good or bad trade to have more overall uptime but when things go down it all goes down together?
It’s been many years since I built a website using Django. At the time, my favorite feature was that it provided a built-in admin UI with no extra work. So helpful!
Now that I live in the JavaScript ecosystem, I don’t have an equivalent tool.
I’ve been working on promoting my seating chart app for teachers, Shuffle Buddy, on social media. I had a 1M view pop on TikTok when I first launched and have now been clawing along to try for continued engagement.
It’s reassuring to know that social media posts are hard for everyone and that it isn’t supposed to be easy. I keep looking for ways to create content that is genuinely beneficial to teachers and also convinces them to try my app, but it’s hard.
The solution I built for this is Leopard. It is a Scratch → JavaScript converter. You can take an existing Scratch project and convert it to JavaScript code and then keep working, or use the Leopard library to create a new project from (ahem) scratch, following all the same conventions as a Scratch project.
I have aphantasia and have long thought that my lack of a mind’s eye might be an asset for programming, much like how a blind person will typically have better-than-average hearing.
If programming is best done through abstract thought and doesn’t benefit from pictures, then I’ve been training since the day I was born.
The design of this blog post is lovely! Despite seemingly having no right to be. It goes against all of my design instincts, but it somehow nails a vibe while remaining pleasant and easy on the eyes. I love it!
I was expecting this to refer to different ways to represent the same diff. (For example, you could represent a change from `console.log(“hello”)` as `console.log('hello')` as +'-“ … +’-“ or as +'hello'-“hello”)
I don’t have a specific example in mind, but it seems reasonable that different languages could benefit from different ways of representing the same diff.
Totally agree. I’ll also add that although I am often tempted to work alone, sharing my work or ideas or output with someone else boosts motivation a lot.
Complete novice question: Would it be possible to build a language that could read your source code and tell you, at compile time, which expressions have values that depend on RNG? And on cryptographically secure RNG?
So that you could annotate a variable as needing to be cryptographically secure and the language could check that, somewhere along the way, its value depends on an adequate RNG function?
As I understand it, the hard part of a masonry layout is ensuring that items are laid out with the first items near the top of the screen and the last items near the bottom of the screen.
If you just plop your items into columns, the first items will all appear in the first column and the last items will all appear in the last column (left to right), which is not the behavior you want.
To my knowledge, the correct behavior cannot currently be created in CSS alone. (Or if it can, it must be a wild hack.)
Hi HN! A few years ago, I began creating Leopard, a Scratch to JavaScript code converter. (Since then, I've received help from a few awesome open-source contributors. Thank you!)
I started using Scratch when I was in 2nd grade. I made over 500 games and projects, working with Scratch all the way into high school. I eventually moved on to JavaScript, but the transition was a difficult one. Much of the JavaScript world was unfamiliar, and learning to do everything new all at once was challenging.
Leopard is meant to be a transition tool that helps ease this learning process. It outputs human-readable JavaScript that is as close to a 1-to-1 translation as possible.
You can enter any Scratch project URL to convert it. If you don't have one on hand, here are a few examples:
Or, if that’s too hard, leave the orbit the same but slow the spin down a little so each day is longer. A 0.35% decrease in spin speed seems fine right?