I've only need the "change key to flush components" trick very few times, and most of those where rush fixes for bugs that had a better "doing it right" fix at a different level.
953 karma · joined January 22, 2013
I've only need the "change key to flush components" trick very few times, and most of those where rush fixes for bugs that had a better "doing it right" fix at a different level.
Hasura is great at understanding relations and making joins feel effortless and TablePlus is so good at making table editing feel as fast as excel.
This looks like it's the thing, with some extra power thrown on top (formulas and nested layouts are nice!).
The UI looks drab, but maybe that's ok? It means the functionality needs to be so strong it doesn't matter. It also looks super snappy which matters most.
Something that Airtable has over relational database GUIs is lightweight enums and arrays of them. Sure you can model all that in SQL, but it's super useful to have it right inline. I hope this tool can pick up on a pattern like enum tables (like hasura) and provide UI that makes them look like tag list/select fields.
I think the low contrast on Google Maps is uniquely ridiculous. You don't have to go all the way to OSM / road atlas. I think Mapbox Streets, Apple Maps (somewhat) and Gaia Topo Lite (my go to) are all perfectly fine maps with roughly the same "feel".
Google Maps contrast is so ridiculous that I have a private app called "Kontrast Maps" that is just the Maps SDK with a high contrast style applied. Me and a friend with a visually impairment get a ton of use out of that. I would love to publish it if it weren't for the insane pricing on Maps iOS SDK.
I'm also disappointed enabling "High Contrast" in Apple operating systems doesn't apply a high contrast maps style. Seems like a super obvious accessibility feature.
With waldo.io and Checkly It joins the list of QA force multipliers that would make my life, as the sole developer in a bootstrapped startup trying to punch above it's weight, much easier. First, they give me a taste with a free plan, then hit me with production pricing we still can't justify.
If I have this right, 20 sessions is just a trial and 1000 sessions is very careful use.
If these scenarios are so easy to create, I would imagine you would make something like 50 (?), run them against every deploy (10 a day?). That's 15.000 replays, right?
So the 100$ plan is something like 10 scenarios at 3 deploys a day. That sounds too scaled back to get good use out of it. Or do I have the wrong idea about the intended use case?
I get it though: they all have reasonable pricing for a unique service that provides real, obvious value AND may actually be expensive to run. I'm just a little sad about not getting to use them.
With no theories to back this up whatsoever, here's my completely unsubstantiated gold-standard strategy for loading states:
1. Make it fast. Most of the examples are loading content. Is there any reason you need more than 100ms to do that? Buy a bigger database server and use a CDN/Edge. Prefetch some content. Unlike fancy skeleton designs, this is worth obsessing over and spending money on. Why "trick" users when you can just perform so well you don't have to.
2. Instantly give inline feedback that an action was started. Could be a spinner on the button, text below the button, a toast / non-modal overlay, a loading indicator in the top right... If you get your response in 100ms, you don't really need this, but the network could always be slow etc.
3. Wait some time (something like 1 second imho) to see if you can transition to new finished state
4. If the full transition can't happen in the timeout, transition to a full loading state. I don't think it even matters that much what kind. Could be a spinner screen, a skeleton screen. No modal overlays though unless a destructive/uninterruptible action like a booking or payment is taking place.
5. Show an indicator/overlay if network quality is bad. The user will not blame it on you and have no expectations for your app to behave particularly well.
Of course if you can just make a fast loading website, let the browser handle the transitions. It's already a fine loading experience.
I imagine it's quite a bit of engineering effort to make that not janky. I wonder how hard it is to make cross platform. Maybe other OSes have easier hooks? Easier permissions for sure.
I think almost straight copying landing page designs and layouts is basically fine and common practice. Using the same or very similar copy... not quite.
If someone could pull the autocomplete list out of fish and style it as a floating window that moves with the courser, that would be wonderful. Sounds more like a tool developed by one person than a venture funded startup though.
It's very possible (likely) this is all fine, but done in a way that feels strange/fishy. I haven't even gotten an email from travis. They must be in fire-extinguishing mode.
Edit: nevermind OAuth tokens are not org-scoped, only apps are
I guess you can proxy all that, but then what do you that the third party couldn't be doing for you? Can the user not accomplish the same thing through your proxy that they could through the key? It'll be easier to drop some requests than it is to revoke an API key I guess. You could use client-certificates, stuff along the lines of Cloudflare's API Shield etc but I would guess that only the top 5% of applications do this.
I've certainly done it/am doing it right now, which is likely why I'm writing such a defensive comment.
Honestly if an enterprising user/developer wants to do something like dump all data that is already accessible to them, more power to them.
All I want is a package manager that is correct, causes very few day to day issues and is going to work the same way for many years. Yet everyone seems to be optimizing disk usage and speed without even getting the basics (make it work, make it right) fully covered.
I don't understand why people are optimizing for disk space at all tbh. Like, have you ever edited a video project, used docker, installed Xcode? I cannot imagine what you must be doing for all node_modules combined to take up more than maybe 100 GB on disk.
pnpm seems to be the lightest of the bunch, which is nice but why even mess with symlinks and confuse other tools? Just put all the files in there, nest them and duplicate them and everything. I'll happily live with my 10 GB node_modules folder that never breaks and sometimes gives me a nice coffee break.
Possibly I'm actually just salty that Metro doesn't support symlinks and would otherwise be on the pnpm love-train.
For networking not sure if you can/should integrate Hetzner's native networking and load balancers or should do some kind of overlay network like fly.io.
For managed databases and other services it would be great for you if first and third party "in your cloud" solutions like Aiven, Elastic Cloud, Snowflake etc would support hetzner but I've never seen it. Fly.io seems like a nice model of offering semi-managed databases.
With those things in place, and hetzner's few regions, some costumers might need Cloudflare in front of their services, but that might not be a bad thing. Is Hetzner in "Bandwidth Alliance"?
I'd try to build it if I had the right technical/sysadmin background. Seems like a realistic task for someone with a small, scrappy team who does.
- one leader that can write to the db
- a ton of other hosts that can read from the "streamed" db and want to do so often/fast
- hosts send their writes (if they have any?) to the leader via some api call (?)
Is that right? If so, the solution makes a ton of sense. "Just use pg/MySQL" in that case would mean hundreds (thousands?) of read replicas, which doesn't sound fun, or every read over the network.
I also loved Copied because of it's sync and great iOS version but it's unsupported so wouldn't really recommend it.
The fact that remapping commands requires an exact, case sensitive match of the localized menu item label you have to type in by hand (and cannot copy to your clipboard) though...
I force quit apps all the time, sometimes even because I want them to restore their exact state. In a lot of apps, the macOS state restoration works great, possibly better than actually quitting them.
This way, TikTok can sustain a much broader base of content creators and react much quicker to shifting trends without being dependent on any popular creator's opinion.
A thing I've noticed lately is that a good chunk of the new apps I install on iOS show up with compatible versions in my Purchased list on the Mac App Store. That's probably due to Mac Catalyst and a little bit due to SwiftUI cross-platform. Most catalyst apps are in the same quality category as decent Electron apps. I still prefer those (both electron and catalyst) over a web app.
It was an interesting project because open source home automation feels very much like a hobby / non-work thing, but it was clearly created by someone with an enterprise java background. I believe there was a custom eclipse based IDE with probably at least one DSL for configuring your automation rules!