It's very hard to imagine this being a better photo than one taken on a modern phone.
Also, I really, really hope you take them off when using the shared bathrooms at such an event. And you know, keep them off. Permanently.
2,465 karma · joined November 17, 2018
Also, I really, really hope you take them off when using the shared bathrooms at such an event. And you know, keep them off. Permanently.
What is _your_ default assumption re: use case? I honestly can't think of any use cases (outside of very niche a11y uses) that are not in some way offensive, though perhaps not 'perverted'.
This product is absolutely toxic, and I can't imagine myself or anyone I know being willing to associate or socialize with someone wearing them (again, excluding some very specific a11y use).
I think I have a fundamental objection to the idea that Fielding and Fielding alone got to decide what REST is. While there hasn't been any kind of formal counterproposal, in some sense REST is what we make of it. Re: http 400 codes, I think many of us really liked the general principle of "use http semantics!" and applied that to error codes as well. That's agreeing with the principle and extending it in new ways that we like and are "truer" to the principle, even if it wasn't intended.
In my mind this is sort of analogous to talking about the relationship between linux and unix. Linux is clearly not a genetic or copyright unix, but I've seen it said before that linux is the culmination of unix principles, in some cases extended beyond what was originally envisioned in ways that are innovative and genuine improvements (io_uring perhaps?).
The REST we have today - http semantics, specific error codes, etc - may be significantly different from what Fielding may have wanted, but IMO it implements the parts that really distinguish it from the RPC world of API architecture, and I think we're generally happy with that.
The example given in this section... is there actually a commonly used REST api that uses that particular key/structure? I wouldn't be _surprised_ if I came across that in some random API's documentation, but I hardly think it's the 'usual' thing to do.
The article later claims that that style is from https://stateless.co/hal_specification.html , which I think is a consultancy company whose major partners are all casinos (am I totally off on this?). The article also references (https://github.com/kevinswiber/siren which adds detail re: http methods embedded in the _links structure, but I'm not sure why that repo should be considered authoritative. 1300 stars for a just a spec is actually not bad though I think, so maybe.
Overall this article seems like slop produces from some kind of ai crawler that managed to dig up a couple of random links.
I am glad that it mentions rfc9457 though.
People shit on the node/npm ecosystem relentlessly for the typical inauditable deep dependency graph, and bun makes substantial improvements to that situation.
Edit: bun recently added an inbuilt api for manipulating images (resize, change formats, etc). Another good example of them adding native/faster functionality that replaces significant dependencies (in this case, likely sharp: https://www.npmjs.com/package/sharp?activeTab=versions)
EU regs forced apple to move to type-c. They appear to be moving towards either requiring replaceable batteries, or requiring a higher quality batter (larger % of original charge after 1000 cycles). Those both seem valuable to consumers, and coming from a position of regulatory strength.
Yes. But why would they provide that to their competitors? The winning move here is to allow gemini, but forbid everyone else. That's not a bad moat.
- offering to pay some nominal subsidy for all households electricity bills in the region.
- committing to only closed loop cooling
- if the location is amenable, then providing free heating to neighboring buildings.
- only building in blighted locations with no current economic value
Other random ideas: I wonder if anyone is considering building server racks directly into offshore windfarms. Replacing failed hardware is annoying, but surely more economical than in space where IIUC, there _is_ no plan to ever maintain hardware at all, just deorbit and replace. All the water is right there for cooling (though I'm sure saltwater has its own problems with corrosion). While the current US administration is clearly anti windmill, that might work nicely in Europe.
Unless they manage to build such a model, then their plan looks like they intend to be an AI _infrastructure_ company. Which is probably viable and healthy business! One with lots of competition and low margins that is completely misaligned with their current valuation.
Which is pretty important! It's my understanding that from all that money they raised during their IPO, a good amount of it went right back out the door again to pay off misc loans for the twitter acquisition. They may only have bought themselves 6 more months of time given their purported burn rate (mostly driven by AI investment), so they're going to need more loans really soon, or another major stock offering.
The reason why I chose that specific term to push on is that practically every SaaS has a ledger _somewhere_ in its stack to keep track of customer payments. I'll give you load bearing and substrate, but ledger IMO should be quite common. Certainly a career devoted to say compiler internals or some specific scientific product could avoid it, but I'd imagine a sizable majority of HN users have worked on some system that accepts online payments for services, necessitating some contact with something likely referred to as a ledger.
There's a certain ironic circularity to this comment given Torvalds' original email, describing his little project as:
> just a hobby, won't be big
(of course, I agree with you, no one is going to use a vibe-coded port of 0.11. A port of the latest kernel however....)
Mozilla makes a surprising amount of money, almost entirely from google.
> Product and service reviews are completely useless now too
One relatively minor counterpoint: amazon has seemed to resolve their review squatting issue. Several years ago, there were companies selling one type of product and getting 4* reviews, then swapping all of the product details for a completely unrelated product, presumably with a huge markup. So you might think you were buying a 4* say, hot water thermos, but if you actually read the reviews, they would all be for a USB charger or something. All the recent reviews would be much lower.
I haven't seen this in a while now. Or maybe they're just better at it :/
They don't even need to 'win' in the sense of maxing the benchmark. They can be 20% worse/50% cheaper and many of us (and our managers who approve our token budgets) will be in.
Deepseek is 30x cheaper for input/75x cheaper for output than sonnet on openrouter, and it's not a whole lot worse for many things.
> Kubernetes (the dog), who was not involved in this incident but whose photo in the #incident-response channel was auto-tagged by the Slack image classifier as “container orchestration diagram (confidence: 0.31)”
That config can be had for $5100 already: https://www.apple.com/shop/buy-mac/macbook-pro/14-inch-space...
Given that they haven’t actually built one, asserting the performance seems inappropriate, _especially_ the uptime which IIRC is far, far higher than is typical for proven designs, let alone a new one.