It's not clueless or sloppy. They are most likely using https://en.wikipedia.org/wiki/JSON_Web_Token which is a well-defined standard and extremely common in the authentication world because it makes a ton of sense. It lets your authentication server be mostly stateless instead of storing tons of sessions unnecessarily.
k8s saves a TON of time if you need to run on more than 1 machine and you use a managed solution (by AWS/GCP/Azure) and only use it as a glorified docker container orchestrator. Ingress solves how to route HTTP traffic coming into your domain. PersistentVolume solves how and where to store data. LivenessCheck solves how to restart your crapware when it freezes. Just don't go crazy with it unless you actually need the fancy stuff.
"k8s saves a TON of time if you need to run on more than 1 machine and you use a managed solution (by AWS/GCP/Azure) and only use it as a glorified docker container orchestrator."
How? Just use AppService / EC2 for managed machines. Scales just as well.
"Ingress solves how to route HTTP traffic coming into your domain."
This is actually helpful and "easier" out of the box than putting nginx in front of statically hosted sites, so I will reluctantly give you this one.
"PersistentVolume solves how and where to store data."
You need a DB most of the time. Managed DBs are easier.
"LivenessCheck solves how to restart your crapware when it freezes. Just don't go crazy with it unless you actually need the fancy stuff."
Our crapware doesn't freeze. Needs a custom Health Check endpoint. Can just as easily restart the instance when that check fails.
K8S is a ton of extra overhead for no gain. We have this debate at work all the time. Great resume builder though.
> How? Just use AppService / EC2 for managed machines. Scales just as well.
It's not about scaling. It's about being able to make a docker image, run that locally on your developer laptop (even if it's a mac) and running the exact same thing in production. Sure you can use docker on top of EC2 but why would you? Just use the ready to go solution you can just buy (managed k8s) and avoid the lock-in. Again, it's critical that you use managed k8s. Don't roll it yourself on top of EC2.
> You need a DB most of the time. Managed DBs are easier.
Sure. Using k8s for your app isn't stopping you from doing that if you want. We deploy 1 database server per testing environment, which kubernetes makes easy to do. For production we use a managed database, but they're too expensive for testing environments.
> Our crapware doesn't freeze. Needs a custom Health Check endpoint. Can just as easily restart the instance when that check fails.
Mine doesn't either. But I have to run plenty of software that isn't mine.
> K8S is a ton of extra overhead for no gain
If you used managed k8s you're just trading server management for kubernetes resource management. I've migrated our system from Ansible + Cloud VMs to kubernetes several years ago, after running it for years before, and things have become significantly easier to maintain and our costs are roughly the same as before. Less vendor lock-in, too. It would take me an about an afternoon to switch between any of the major managed kubernetes offerings, and some of our clients have expressed preferences for a specific cloud.
Hey, thanks for the reply. I am being slow because it looks like if comments are deeply nested, the "reply" cooldown gets longer, so I am just replying now.
We use .NET/React for the most part, so I haven't had an issue with Mac/PC - we have multiple teams and, for example, a team helping is all on Macs - they can run stuff fine from bash. Azure Data Studio let's them access Postgres (and would let them access SQL Server) if needed. React only has issues with file pathing sometimes, so most of the time it's fine. I find that devs also get lost in setting up Docket/K8S locally, especially when people roll scripts to set up the whole environment in one command.
Still, I am genuinely arguing to help me fill the gaps where I might be incorrect, so I really appreciate your replies.
I saw a slide somewhere recently - there are already plans for this as an artillery shell or missile. I think it was combined with ordinary ordnance- drone is ejected before main weapon payload towards end of "flight". Drone helps pick highest value target then is used after for damage assessment. Presumably then it self destructs or/or kamikazees
Cruise missiles with submunition dispensers are not exactly a new concept. It's certainly possible in theory to stick some smart loitering munitions in a Tomahawk but that's going to be extremely expensive and not reusable.
Actually consumer saftey in e-bikes seems to be higher in China than in the US. Radpower bikes go up to 32km/h, while ebikes in china are legally limited to 25km/h. There's further restrictions on the weight and battery life, along with some other stuff I can't read because I don't speak Chinese. https://www.sjgrand.cn/how-legally-drive-ebike-china/
I wish lawyers would lose their license when they're obviously attacking people (or in this case companies) in bad faith. This is ridiculous, go grieve like a normal person.
It would be nice if rad power could get their fees paid for this obviously frivolous law suit, but they will probably settle because the steinsapirs can run up the costs way beyond any reasonable jury verdict
Me not buying their products doesn't stop my users from doing so, or my employer from demanding we support them. Also you've clearly never been on the submitting side of the app store, this "careful curation" often misses blatant violations and instead nags for weeks on minor or non-existent issues while refusing to elaborate.
> As we saw, plain keyset pagination offers no facility to jump a certain percentage into the results except through client guesswork. However the PostgreSQL statistics collector maintains per-column histograms of value distribution. We can use these estimates in conjunction with limits and small offsets to get fast random-access pagination through a hybrid approach.
Jumping to a specific page is a bit of an ambiguous / undefined term in this case. Like asking for a specific page in a book that's still being written. Maybe today the plot twist occurred on page 100, but then the author decides chapter 1 needs more backstory, and now the plot twist happens on page 115.
Unless you can guarantee your data is static, or that the sorting order cannot be mutated and only append later values, the concept of what data belongs in which page could be changing every millisecond.
Do you really need to jump to an arbitrary page and land on the exact item? For many applications an approximate jump is fine. If your column is fairly uniformly distributed you can guess the index for any arbitrary page.
You don't, but instead you can jump to an arbitrary place in the results. For example, you could show results starting from the letter P, or show results starting from 2022-04-02.
But the entire concept is that this is an adaptation to the fact that data may be added to or removed from the database. If that's true, there would be no benefit in jumping to a specific page - there's no guarantee that that page will display any particular data.
For starters, that you only want HN to be used the way you want to use it; which for sure it not the way I want to use it and more than likely significant number of other users too. If that’s not gatekeeping, then what is?
