Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I like it. Might start using it myself!

I use mm, cm, m, km every day, so why not Mm!


Yup, the ingenuity to pull this off fascinates me every day, too.

> Joe Biden said he would veto Medicare for all

Oh for... Joe Biden was literally the tiebreaker vote in the senate when the public option was still part of Obamacare and was stumping for it like crazy. MfA is one particular proposal from one particular faction of the party. We aren't talking about MfA specifically, and that's quite clear all the way upthread.

This kind of dissembling and trickery is what's driving me crazy in this thread. You just don't seem to be arguing in good faith. No, Joseph Biden Jr. is very clearly not opposed to government-provided health care, nor is any democrat in office right now that I'm aware of.

"Mostly" partisan. Good grief.


You were right that fuses were involved, just on a different model. See my edited comment.

>Does the birth rate discourse put pressure on you as an individual?

Implicitly, I think, yes. It builds on all of the other social pressures, big and small. I'm sure an entire humanities thesis could be written about how it all adds up over time.

I wrote another comment elsewhere in the thread talking about polarized opinions broadcasted on social media and how that also adds to the stress of it all. Nobody ever wants to talk about the "it was/is... fine, actually. kind of whatever. not great, but not horrible." possibility of pregnancy (and parenthood). It's always either the most wonderful, miraculous thing ever and you're insane for not wanting it, or it's the most horrible, irreversibly damaging thing ever and you're insane for wanting it.

And the thing is... it COULD be any of those outcomes! It could ruin your life. It could also make your life so much more fulfilling. There's simply no way to know for sure what it will be like for you without doing it. It is an enormous gamble, especially when you are the person who has to endure the pregnancy, and it is a gamble that you can't really walk away from. (Of course, you can give a child up for adoption, but there's a lot of social shame involved in that, especially if it is a wanted child that you're quite literally giving up on rearing.)


Amazing. Huge congrats to the Open Router team

Not really. They are two different paradigms. Use the one that is right for you.

SQLite is embedded for local applications with one writer mostly.

Postgres is for a client-server architecture with many writers.

When you start a project, you generally know which architecture you need.


SRE here, Strong disagree with do not fail readiness and liveness checks on upstream dependencies failing. There are several reason to do so and unless you have extreme start up time, what's the problem with restarting?

Maybe DNS has changed on you but you are stuck with bad local cache because you poorly respect TTLs (Looking at you Java), reseting the process will clear that cache away.

Maybe TCP connections are in stuck weird state, resetting the process generally helps with that.

Maybe someone gave you bad ENV VARs and you cannot connect to database, by refusing to progress the rollout, no outage generated.

So yea, if you not ready to do work including critical upstream dependencies, don't lie to system and say you are.


Ok, sure, but those LMS triangles are just for hue..

or rather, its not productive to "we should do better with artificial intelligence"

> Stripe is "just" a payments platform

Counterpoint: you can't just go to Visa/Mastercard or a merchant acquirer out there and set up an account on the same terms that Stripe can.

On the other hand, you can sign up to any LLM provider and get API access on terms that are the same or better (since I'm sure they don't appreciate having a middleman and would benefit from incentivizing direct usage) than OpenRouter gets.


Related: Stop Anthropomorphizing Intermediate Tokens as Reasoning/Thinking Traces![1]

[1]: https://arxiv.org/abs/2504.09762


> Microservice: If your service is ONLY exposing json data from some database model, then it should not exist at all IMO. Create a view and be done with it.

Yeah, this has nothing to do with Postgres. If the service is accessing a database that isn't internal to the service, then that database is already a standalone service in itself.


no one dead because we're willing to use our means to enforce a restriction on a scenario that is likely on our trajectory to kill everyone. We also use serious threats to prevent nuclear proliferation that endangers everyone

They should absolutely all be discussed. I just don't see a lot of rationale that supports that having kids is the "biggest accomplishment of a lifetime" though.

There is inherently nothing very special, unique or difficult about it. It has always been the normal things that happen to most humans and animals since the dawns of time.

If you respond to this, please use rationale and not feelings to describe why having kids is the "biggest achievement from your lifetime".


Ah, one of those "everybody knows" argument that is on the level of "everybody knows that Napoleon was short".

The part you are leaving unsaid is that the vaccine reduced transmission even if it didn't prevent it completely.


I don't think a firm of people whose minds are weak to coercion experiencing shared psychosis caused by their text predictor models is AI "taking over" that firm.

The only thing keeping me on my apple watch is the wakeup.

One-to-many implementation. Stripe is one api to every bank. Openrouter is one api to every language model.

CDs are okay but I don’t prefer them due to lack of liquidity. There’s basically no reason to choose a CD over a HYSA at the same rate.

> As things settle down and commoditize, the value of switching on a dime diminishes as people lock into their favorite models

I can imagine just the opposite outcome from the same scenario: as people settle into their favorite but commoditized models, competition for marginal inference cost will take over. A company like OpenRouter that promises the cheapest tokens by the minutes becomes essential on the low-cost margin.

I think that OpenRouter and equivalents get pushed out of the market only if the froth calms down (as you posit) and winning models stay proprietary, perhaps with their own unique API surfaces.


I don't think this particular feature helps there, though. If you set your site up on Cloudflare, you'll probably explicitly want the proxy stuff, and that's very easy to set up. But if you buy a domain on Cloudflare, then you're already not looking specifically at the proxy products, you're looking at something else. And if you start configuring that domain in an admin panel that looks like it's offering you direct DNS configuration, and then you later realise that the DNS configuration has ended up completely different to how you set it up, then that's a bit weird. Like, if I set `CNAME` in DNS, then I expect the DNS CNAME record to be what I set it to.

Depending on your definition of space, this is what the Earth To Sky does to finance their helium balloons runs: https://www.earthtosky.store/about. I got a pendant for my partner, it was a nice gift.

Cue the N.I.C.E comparisons.

Sam has a real way with words when it comes to educational content.

Though he did find a legit Kubernetes bug while writing the post, so technically there was at least one new thing :)


Ruby can't render React code. JavaScript can. With GitHub it seems that they sometimes can do SSR for the React bits, but that must mean that they're then invoking a JavaScript interpreter within the Ruby process. Which means they have the overhead of two runtimes and the jank that comes with the IPC between the two.

It's just pointless hacks on hacks. GitHub didn't need React on the frontend and any potential resource savings of client side rendering were lost when they realized they need to do SSR on that stuff too.

I've encountered so much frontend jank as they expanded that portion of the stack whereas it was always excellent when it was just Ruby SSR and minimal JS on the frontend.


Yes, you should've clarified all the things you don't want :D

a) use the fastest means possible to save the human lives that were smashed into obvious by <insert weapons system here>, and

b) de-weaponize all the things - take the mirror from the warrior narcissist immediately - and "paint those F35's pink" (its a metaphor, relax) - disable their stealth, and have them and their pilots serve the human beings whose lives they have spent years obliterating, as amends to the rest of the human species whose lives they are making utterly miserable with their actions ...

But yeah, your ideas are cool too. I'm waxing philosophical because we all know, the bombs are going to continue to drop, no matter what we peace-makers say and do on HN ..


The other real fix is for apps to use the existing apis added in Android 10 to create regions where the OS will not prioritize navigation gestures over input to the app. https://developer.android.com/reference/android/view/View#se...

Yeah so here's the chaining, I went back to look at it.

The door is a sprite, declared in the VIEW, that is in the way of the strip of elevator shaft (declared in the PIC) that you have to step on in order to exit from the volcano (room 82) to room 83, which is the beginning of the endgame.

If you just look at the script, the fact that you can't just walk into the shaft is not visible. Once you've caused the explosion, all that happens is that a variable is set called causedEruption, and the door animation happens. Nothing else other than a look message uses the value of causedEruption in the script. So before we added in the VIEW and PIC files, the engine thought that the endgame was free once you stepped onto the volcano crater.

The PIC file is what tells you that that strip of the screen matters (it's the exit), and the VIEW file is what tells you that the door (a sprite) initially blocks access to it, and once it becomes open allows access to it.

So the engine had to look at the VIEW and PIC to deduce that causedEruption was the flag that mattered, which meant that the items you have to use to cause said explosion were needed for the endgame.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: