HN user
I use Chrome on my Android and Mac. For a while I've appreciated the seemingly built-in anti-hijacking measure that always does what I expect on the second Back press. (The first Back may pop up a subscription box for example, but the second will always return me to where I came from).
I actually felt that this was a solved problem, so I'm surprised to see so many people still suffer getting stuck in redirect loops.
Didn't they add name pronunciation guidance a few years ago?
https://www.macrumors.com/how-to/correct-siri-pronunciation-...
I'm curious though if that affects recognition as well as audio generation.
Floods - remove "Don't drown" and add "Stay out of the attic". Plenty have died trying to seek shelter in an attic.
And if we're talking Expo, that's only for prebuilds of course; once you've got the native app installed then you can absolutely code and see updates in near real-time on both Android and iOS devices.
Quick plug for https://pistepal.app/ - that's my own contribution to the space. Features location sharing and nav/directions, and priced lower than the competition yet with perhaps a richer / more focussed feature set. Interested to hear feedback and ideas!
You can accidentally push to a branch. You can't accidentally push to a tag.
Hey Dan, I think you're going to love what I've built.
The next release (a couple of days out) displays the relative altitude for all of your buddies - so you can immediately see who's above or below you.
On the iPhone, that info also lives in a Live Activity on the lock screen so you don't have to take your gloves off to see that essential info! (Android lock screen support will be coming right after).
If you'd like to help test the feature out, I'd really appreciate it - just drop me a message via https://pistepal.app/support and I'll link you up with an annual subscription.
Cheers!
That's a great idea. A lock screen widget could work really well here, showing the relative elevations of your buddies. You'd have to take your phone out - but you wouldn't have to take your gloves off!
Specifically above or below? Or you're after "give me directions to my pals".. what's the use-case for above/below?
https://pistepal.app/ - a ski map app - built at breakneck speed over the last few months. I believe this is the only ski map app that offers turn-by-turn navigation!
Screenshots in the App Stores, e.g. https://apps.apple.com/us/app/pistepal/id6754510927
Still a little bit rough around the edges but hopefully will be / is in decent enough shape for the start of the ski season (just about happening now..)
Currently figuring out the right balance of free tier & daily trial. Priced at $10/month and therefore significantly undercutting the competition, hopefully this is enough to gain entry into the market. (May need a more generous daily trial though, admittedly 10 minutes is not really enough to actually try it out on the mountain).
Seems ad spend is necessary to get any kind of traction...
Feedback welcome!
Here's one - https://apps.apple.com/us/app/pistepal/id6754510927
The app is definitely still a bit rough around the edges but it was developed in breakneck speed over the last few months - I've probably seen an overall 5x acceleration over pre-agentic development speed.
That's not the issue at hand here.
Add "Without compromising quality then"!
Terrible analogy. I don't commit jank. If the LLM comes out with nonsense, I'll fix it first.
I use it all the time, and it has accelerated my output massively.
Now, I don't trust the output - I review everything, and it often goes wrong. You have to know how to use it. But I would never go back. Often it comes up with more elegant solutions than I would have. And when you're working with a new platform, or some unfamiliar library that it already knows, it's an absolute godsend.
I'm also damn proud of my own hand-crafted code, but to avoid LLMs out of principal? That's just luddite.
20+ years of experience across game dev, mobile and web apps, in case you feel it relevant.
If you don't know which table your ID came from you're probably doing something wrong to begin with. (Why hey there you overly normalized schema..)
Does it though? I've developed in remote VMs before and the advantages are clear, but having a fully containerized development environment is really nice too because you can tear the whole thing down and rebuild at the drop of a hat. You can achieve that with a VM and scripts, but a Dockerfile is very lightweight and standard.
Edit: Unless you literally mean "editing code in a container with vi". In which case yes I'd go for the VM too!
Google Home's Nest integration is recent and top-notch though.
Hopefully in a year they'll have rolled out the Gemini integration and things will be back on track.
Ironically I think I'd rather query a database with anything other than SQL ¯\_(ツ)_/¯
It's incredibly ironic
I think it's fair and reasonable to assume that the AI companies will at some point start licensing their source content. Through gov/legal oversight or not remains to be seen, but OpenAI are already beginning to do so:
https://searchengineland.com/openais-growing-list-of-partner...
hah
So basically you're saying that the 3 day gap between your first post and your demonstrated understanding is actually reasonable, assuming you spent those 3 days immersed in understanding the code & design at play.
The k code explained: https://chatgpt.com/share/67036e8e-17dc-800f-96c4-1fac8b291f...
It can be done, it was done, but it doesn't scale.
If you want layers of failsafe and redundancy (as we would do it today), it requires higher level abstractions, e.g. writing in at least C if not C++ or Rust, instead of hand-coded assembler like they did back then.
So yes simple got us there, but it's not useful to repeat the exercise like that again.
With a statement like that one wonders if Hezbollah leadership itself has been infiltrated.
It can be pretty awkward to work with, although I've not found anything comparable, free, and cross-platform.
Sometimes the FK links in cells break. Other times views don't get invalidated when pressing refresh until a reboot. There are different refresh buttons all over the place for different contexts. Lots of minor quibbles despite almost weekly updates. It does have a gamut of features though - and it's free and cross-platform though, so it's one of those love-hate relationships for me.
Haskell?
Similarly, found a bug in clang around 2010 that would only happen with max optimization. Actually did manage to track down the root cause; an array access would fail if the index > 255. It went something like this: on ARM (this was building for iPhone) the LDA (Load Accumulator) instruction can store the memory offset (array index) within the instruction itself if it would fit within 1 byte, otherwise the offset would have to get loaded from a memory location pointed to by a given register. One of the two cases was faulty.
Was just about to report this, but my Mac got upgraded to the next version of OS X, which magically solved the problem. What does the OS upgrade have to do with compiling? In the world of Macs, Xcode was also upgraded along with the OS, and in the newer version it was already fixed. Dangit!
Brings a whole new meaning to bus factor