MurphyA/hacker-news huggingface dataset:
by acrooks | 2025-11-13 23:58:29+00:00
I’ve stayed >150 nights at Marriott hotels this year and was pleasantly surprised when Sonder started popping up as an option. But the thing I noticed is that, at least in the markets I visited, it was often MORE expensive than the local 4/5 star hotel. But with the hotel I got the guarantee of breakfast, a good gym, 24 hour reception, upgrades, laundry service, etc. As a result I never booked one.

My feeling with Sonder is similar to that of my feeling with Airbnb: it’s fantastic for those longer trips where you want some extra amenities in the room like a kitchen. But, for general business or short-term travel, I just don’t get it. It no longer wins on price, and it loses by an order of magnitude on convenience. Why not just pick a hotel?
by rileyphone | 2025-11-14 00:02:19+00:00
Pretty neat! Really like the design and minimalism. Oh, and the free hosted models :-) (but I assume that's just for the demo). Kind of confused by the open in cursor button but otherwise clean.

It seems like there's a lot of stuff out there that's similar, but it's all either focused on art/roleplay on the one hand, or enterprise teams on the other. Most prompts I see are shared as raw text on twitter or something, to be lost in my bookmarks...

Anyways, here's a prompt. Next time I see an actually useful one out there I'll hopefully remember to save it on Prom.

https://prom.dev/p/where-is-mama
by jmadeano | 2025-11-14 00:02:35+00:00
Great feature request. For the moment, you can go to www.tweeks.io/share/profile to manage your tweeks and share/install your own tweeks from one device to another.

We're also actively working on an update system that might be helpful here (i.e. if you create a tweek on computer A, install it on computer B, then update it on computer A, you might want it to update on computer B).
by sbuttgereit | 2025-11-14 00:02:42+00:00
I'm reading this thread and there are a few things that come to mind.

My sense is that SpaceX's goals with Starship are significantly more ambitious than what is being tried with New Glenn. I don't mean to underplay the difficulty of what Blue is facing with New Glenn, but if we take that "rapid reusability" goal seriously the problem set seems significantly larger and not so "been there, done that". This makes the development programs much more difficult to compare.... certainly on the surface of the public optics at the very least.

While it's one thing to talk about rockets, it's another altogether to look and the engineering and practices going into the manufacture process of those rockets. I'm not an engineer, but I do work in manufacturing and, at least looking from the outside, SpaceX seems to be dedicating some significant amount of effort into building a scalable manufacturing process. Many other efforts have always appeared to be more about "bespoke" production even if the designs of each unit produced are constant. I could be wrong and maybe it's just SpaceX is a lot more transparent (willingly or otherwise)... but looking in from the outside, they seem to be developing a very mass-production oriented rocket factory.

And if New Glenn is just finalizing things and Starship is just vaporware... well New Glenn still has to land a couple more boosters and re-fly one (or two?) to catch up to those vaporware numbers. :-) Sure, New Glenn has now flown a paying customer... but I think we'll see Starlink launches on Starship pretty soon... well before it gets to "final validation".
by icegreentea2 | 2025-11-14 00:02:57+00:00
Sonder has been bleeding cash ever since it went public (via SPAC).

https://companiesmarketcap.com/cad/sonder/cash-on-hand/

It's agreement with Marriot was "completed" in August 2024. It was absolutely a hail mary.

While they might describe it as a integration failure, I think what they were actually hoping for was:

a) integration into Marriot's reservation system would reduce operating costs. From my user perspective, it looked like the Sonder system got completely replaced (like I had to make a new account and upload new ID...).

b) "Somehow" the Marriot integration would lead to increased bookings.

Both their 2025 and 2024 annual filings indicate that they were well aware of where things were going. Honestly, the filings don't really paint an optimistic picture of their ability to succeed, even with the Marriot deal.
by amarant | 2025-11-14 00:03:06+00:00
I already regret reading this article. Don't get me wrong, it's well written, and I agree with most of it. But every time I read an article like this I get stuck in analysis paralysis for any code I need to write afterwards and that's just not very productive.

Here's hoping my recognising the issue will soften the blow this time! Mayhaps this comment might save someone else from a similar fate
by josephg | 2025-11-14 00:03:53+00:00
> The compiler is also relatively slow. Would Rust have been worth working with on 30+ year old hardware?

As I understand it, a lot of the slowness of the rust compiler comes about from llvm. And how rust and llvm interoperate. Rustc creates and sends gigabytes of stuff to llvm - which passes all of that to its optimizer. If you skip all that work - for example by running cargo check - the compiler is an order of magnitude faster.

If rust were invented in the 90s, it wouldn’t have used llvm. Rust could still have been implemented, and we’d probably have a much faster compiler as a result. But it would have missed out on all the benefits of llvm too. It would have needed its own backend to be written - which would have been more work. And the compiler probably wouldn’t have been as good at low level optimisations. And it probably wouldn’t have out of the box support for so many target platforms. At least, not from day 1.
by rtpg | 2025-11-14 00:04:11+00:00
To be honest I feel like "this code is easier to review and less likely to require rollbacks" is even more of a valuable take from this article, just in terms of "hey, don't you like it when things don't have to be rolled back?"

Security issues are like bad etc too, just we've heard the security spiel so many times at this point. I just think it's nicer to write most stuff in Rust.
by xrd | 2025-11-14 00:04:11+00:00
That's a good point. Email is much worse than slack.

But I still think it is impossible to manage all the things happening in slack. And the expectation is that it was said in slack, so you should know about it! Whereas, I definitely go through and review PRs and if there is a culture and management agreement around good PRs, then I can easily understand how things work, how things have changed, etc. I never get that from slack. And, I never got it from email either, fairly.
by VHRanger | 2025-11-14 00:05:23+00:00
I'm not saying we could detect it from the text alone!

The side channel signals (who posted it, where, etc.) are more valuable in tagging than raw text classifier scores.

That's why I said our definition of slop can include all types of genAI: it's about *thoughtless use of a tool* more than the tool being used.

And also that regardless of the method, your model can be used to generate slop.
by mrandish | 2025-11-14 00:05:52+00:00
Yep, even high quality 24-bit uncompressed imagery often benefits from dithering, especially if it's synthetically generated and, even if it's natural imagery, if it's processed or manipulated - even mildly - it'll probably benefit from dithering. If it's a digital photograph, it was probably already dithered during the de-bayering process.
by tuetuopay | 2025-11-14 00:06:28+00:00
How is Go memory safe? Memory safety does not mean "leaking memory".

It's absolutely possible to compute wrong pointer offsets. It's absolutely possible to dereference nil. It's absolutely possible to bork ownership and have multiple thread trample a struct. It's absolutely possible to reinterpret memory the wrong way.

I do agree that UAF is not possible (in most cases) due to the GC. That array indexing out of bounds is not possible. But it is by no means "memory safe" to the level Rust is.
by syncsynchalt | 2025-11-14 00:06:40+00:00
It's not about the delay, they can take as long as they want to build what they want to build. I object to their attempt to use patents to block competitors for decades when they didn't even have a product yet.

Fortunately it was challenged and the USPTO invalidated patent 8,678,321: https://cdn.geekwire.com/wp-content/uploads/2015/09/2015-08-...
by vacuity | 2025-11-14 00:06:53+00:00
Rust has the twin features of significant technical merits and a powerful hype machine. In truth, it's neither the devil nor the best thing since sliced bread. It has enough traction that the tooling and developer experience are always improving, and appeals to a wide range of uses. Rust was lucky enough to get noticed when it was decent pre 1.0, which motivated the community to make it excellent at 1.0, and it's been making history ever since. I think Rust got critical mass because it had a bold vision and focused on developer experience enough to get buy in on improving its performance and robustness. Ada is wonderful, but it's less pretty, and doesn't make pretensions. In that sense, Rust was built for the hype, but the language has benefitted greatly from all the attention.
by JackSlateur | 2025-11-14 00:07:01+00:00
Those are orange vs apple, just like the rate of rollbacks

They compare something new, which rewrite existing stuff (not only but still) with some decades-years-old cruft

In they new code, they know what they want

They can also start with state-of-the-art unit testing that may not exist in the early 2000

So .. yeah, those numbers ..

That rust is saner than c++ is a given anyway :)
by pinkmuffinere | 2025-11-14 00:07:05+00:00
> Software patents are mostly garbage and unneeded. And I say that having some in my name (I actually tried to get my name off them, but our lawyers said it's not possible)

I want to know about these patents that you want your name off of! What were they for? Why do you want your name removed? This is the opening to a great story, please tell!
by malwrar | 2025-11-14 00:07:12+00:00
I think our full understanding of the spectrum of these threats will lead to the construction of robust safeguards against them. Reputational attacks at scale are a weakness of the current platforms within which we consume news, form community, and build trust. Computer attacks described in the article are caused by sloppy design/implementation brought into existence by folks whose daily incentives are less about making safe code and more about delivering features. "Designer pathogens" have been described as an accessible form of terrorism since far before AI has existed. All of these threats and similar have existed since before AI, and will continue to exist if AI is snapped out of existence right now. The excuse for not preventing/addressing them has always been about knowledge and development resources, which current generative AI tech addresses.
by WalterBright | 2025-11-14 00:07:13+00:00
In the 60s, my dad told me that the greatest coming inventions would be:

1. a TV you could hang on the wall like a picture

2. a typewriter that would enable correcting what you wrote

He was right!

(I remember when my dad was writing a book, my mom spent endless hours retyping the revised manuscripts. It seemed like a hellish task to me. I'm glad that job is gone.)
by bgwalter | 2025-11-14 00:07:58+00:00
Further up they refer to Android C/C++ code, not C/C++ in general:

"We adopted Rust for its security and are seeing a 1000x reduction in memory safety vulnerability density compared to Android’s C and C++ code."

Which means they had a pretty poor code base. If they had spent more time on engineering and less time on features that are canceled after 12 months anyway, they could have written better C/C++.
by Rohansi | 2025-11-14 00:08:01+00:00
How would a server-side anti-cheat work? You wouldn't be able to detect ESP or other information leaks. Best you can do is see how good they are vs. everyone else but how do you know if someone is cheating or just really good? Most cheaters are not blatantly cheating so it is hard to know for sure. Even something like aimbotting is almost always adjustable in cheat software to have varying levels of accuracy.
by hamasho | 2025-11-14 00:08:13+00:00
I really hope your product fly. I'm easily distracted and generally like simple websites.

I want to know what plugins or scripts other Hacker News users use to block annoying segments. Beside uBlock Origin, I use kill-sticky[1] to hide sticky items like dialogs or headers (though sometimes it's wrong), SponsorBlock to skip sponsor segments, DeArrow to change YouTube thumbnails and titles to be less clickbaity. And I use Firefox's Reader View sometime too.

[1] https://addons.mozilla.org/en-US/firefox/addon/kill-sticky/

[2] https://addons.mozilla.org/en-US/firefox/addon/sponsorblock/

[3] https://addons.mozilla.org/en-US/firefox/addon/youtube-recom...

[4] https://dearrow.ajay.app/

Edit: And I just found this new Kagi's AI-slop detection on the Hacker News. I'll definitely try!

[5] https://news.ycombinator.com/item?id=45919067
by itopaloglu83 | 2025-11-14 00:08:33+00:00
Designing a car that is easy to maintain and diagnose is a lot harder than it seems and manufacturers are incentivized to focus on new sales than maintenance.

Well, then we ended up weird designs that expects you take and engine out to change an alternator or estimates that are way off.

It’s quite dishonest that all the problems of the entire sector is being merged into “nobody wants to work anymore” style conversation with a lot of fine prints.
by deffyweffy | 2025-11-14 00:08:35+00:00
We also have the same word in English, as "sonder".

> noun, the feeling one has on realizing that every other individual one sees has a life as full and real as one’s own, in which they are the central character and others, including oneself, have secondary or insignificant roles.

https://www.dictionary.com/browse/sonder
by IncreasePosts | 2025-11-14 00:09:09+00:00
Generally speaking, the purpose of a program is not to minimize the number of memory safety bugs. All other things being equal, yes, having fewer memory safety bugs is better than having more. But perhaps you're trading legible bugs for illegible bugs? The rust implementation is most likely going to be more complex than the c implementation (which is fair since it almost eliminated a whole class of bugs), and in that complexity there is extra room for non-memory safety related bugs.

There's probably also 500x more people who know c to a given level then know rust to a given level.

If we have an analyzer that can find memory safety bugs in C, we could also just put that in the CI pipeline, or as a pre-submit hook before you're allowed to add code to a code base.
by _carbyau_ | 2025-11-14 00:09:47+00:00
I'm not sure how to abuse the return system. It's not like I pirate anything from Steam. And I used the return process through Steam - exactly once, as mentioned above. If I wasn't meant to do a thing, then I would think the process should not let me do it. But I returned it in good faith, for a game that managed to make me rage quit in less than an hour - I like to think at least that I am usually patient but I wasn't putting up with that shit.

If a Valve employee with rights to look into it is reading this - I'd love to know what I did so wrong. But given that human explanations from modern software based corporations are non-existent, I will assume I was treated as per their returns policy.

And the outcome has worked in Steams favour. I buy for (account) life now, for better or for worse. As previously mentioned, I don't care about the money so much as the social.

But my decision making process to drop the significant money required for Steam hardware will assume the return/warranty is worth precisely zero.
by mrandish | 2025-11-14 00:09:53+00:00
A related bit of tech trivia is that digital audio also often involves dithering, and not just decimated or compressed audio. Even very high-quality studio mastered audio benefits from an audio specific kind of dithering called noise shaping. Depending on the content, studio mixing engineers may choose different noise shaping algorithms.

https://en.wikipedia.org/wiki/Noise_shaping
by crote | 2025-11-14 00:10:04+00:00
That sounds a lot like the issues some Linux distros are running into, where they expect to be able to ship one single blessed pre-compiled version of every library, and have each app load it dynamically at runtime.

But that's just not how Rust works: it's trying to fit a square peg in a round hole, and it isn't Cargo's fault that you have trouble with it.
by moralestapia | 2025-11-14 00:10:32+00:00
Wrong.

Don't worry, I happen to be knowledgeable about this.

Some key differences that come to mind (obviously YMMV):

Home insurance stops almost as soon as you stop paying vs. corporate insurance which is usually a bit more lenient and even has things like "tail coverage" in place.

The regulatory protections that apply to home insurance are very different to the ones applying to corporate insurance.

It's not uncommon for corporate insurance to cover events that happened while the company was insured, even if by the time the claim is filed the policy has been canceled.

Insurance is considered an asset of a company, and a judge can rule over what happens to them. This come into play particularly when bankruptcy is involved.

Many commercial insurance contracts, under some situations, cannot be canceled by the insurer, even if the company stops paying their premiums.

Anyway, I know on a naive approach it's easy to think that "all insurance is the same", but once you scratch a bit more than the surface of it you'll see it's a very complex affair!
by icegreentea2 | 2025-11-14 00:10:32+00:00
When I first booked with Sonder back in 2023 in Montreal, they were $20-40 less per night. This year, things were about break even.

At least in Montreal, the Sonder offered a very nice location in the city (especially taking into account my office location) where there were very little chain hotels nearby. I saw it as a "more predictable AirBnB".

Bummer, I really liked being able to stay in that area.
by alentred | 2025-11-14 00:10:52+00:00
If I remember it well, every once in a while a new cool feature was also breaking stuff, doubling the chances of getting to the top page here. But truth being told, GitHub was fixing those at light speed too and it was very interesting to follow their progress. Their delivery pipeline (per branch, deliver when ready, etc.) sounded very much innovative by then and I think inspired many people.
by verdverm | 2025-11-14 00:11:25+00:00
people can abstract and reason about issues like...

1. Until this is possible without lock-in to a specific IDE, it's going to be heavily gated by adoption and network effect.

2. What are you going to do about communication with non-devs who don't use any IDE? Do I now have multiple chat tools I need to give attention to?

3. Bringing the attention economy to our primary work tool is probably a bad idea in the long run, given the evidence we have more broadly about the impact of the attention economy

4. They are also proposing a new version control database, which makes adoption and interoperability an even harder task. https://zed.dev/blog/sequoia-backs-zed#introducing-deltadb-o...

5. We are in an AI hype cycle, which comes with a lot of experiments and baggage. We're seeing both fandom and rational pushback against this experiment (and others)
by fragmede | 2025-11-14 00:12:09+00:00
> we detected a highly sophisticated cyber espionage operation conducted by a Chinese state-sponsored group we've designated GTG-1002

How about calling them something like xXxDragonSlayer69xXx instead? GTG-1002 is almost respectable a name. But xXxDragonSlayer69xXx? is hate to be named that.
by efskap | 2025-11-14 00:12:38+00:00
Photo sites like Flickr do extract EXIF data and show it next to the image, but who knows if the scraping picked them up.

Looks like specific f-stops don't actually make a difference for stable diffusion at least: https://old.reddit.com/r/StableDiffusion/comments/1adgcf3/co...
by tuetuopay | 2025-11-14 00:12:39+00:00
Uuuh how so?

Cargo is a blessing for any source-available project. All bundled up, a `cargo build` away. Because don't you dare say CMake or autotools are better, that's just the stockholm syndrome kicking in because you're familiar with it.

Seriously, how a CMakeLists.txt can even be compared to a Cargo.toml file? One is imperative full of arcane conditions everywhere filled with boilerplate, while Cargo.toml is a declarative manifest of the package?

Though there is one very sore point when distributing software, and that is for distribution package maintainers, because the whole ecosystem has been built around the C model and dynamic linking. That is not even the fault of cargo, since Rust's ABI is not stable thus dynamic linking would not work most of the time. Another thorn is generic stuff, which needs to be monomorphized, and as such don't work with dynamic linking (without Box<dyn>); C++ actually has the same issue and is why there are so many "header only" libraries for it.
by justapassenger | 2025-11-14 00:15:07+00:00
None of them were cancelled. But none of them exist in any form or shape remotely reassembling the product - therefore - vaporware. It's that simple.

But also, since you're telling me there had been no material impacts to the customers timelines, sorry, I don't think you're arguing in good faith, so I'm not going to engage here anymore.
by consumer451 | 2025-11-14 00:15:34+00:00
There is a lot to talk about here. However, the bolts that fired from the landing legs into the ship's deck were really neat. [0]

It was likely one of the simplest things involved, but SpaceX never did this. It seems far simpler than SpaceX's OctaGrabber. I think you can buy something similar at Home Depot? (edit: I just meant the explosive nail gun)

[0] https://www.youtube.com/live/iheyXgtG7EI?si=zXnZ_lMAEoWjzpzg...
by eternityforest | 2025-11-14 00:16:10+00:00
These would be the best thing ever for small cheap IoT devices, assuming they can make them cheaply and they can be assembled the same way you assemble normal SMD capacitors.

I don't think energy density is that much of a limitation, because current batteries have to be over provisioned to avoid deep cycling, and then over provisioned some more to account for calendar aging, unless it's a nearly disposable product.
by immibis | 2025-11-14 00:16:58+00:00
If you're concerned about money ending up at companies that are taxed by countries that mass murder people, you should be as pissed about Google, Microsoft, DuckDuckGo, Boeing, Airbus, Walmart, Nvidia, etc... there is almost no company you should not be pissed off by.

I would be happy that Google is getting some competition. It seems Yandex created a search engine that actually works, at least in some scenarios. It's known to be significantly less censored than Google, unless the Russian government cares about the topic you're searching for (which is why Kagi will never use it exclusively).
by 0xbadcafebee | 2025-11-14 00:17:01+00:00
> it means you can't run autoscaling, can't depend on spot instances which in an outage you can lose and can't replace

Yes, this is part of designing for reliability. If you use spot or autoscaling, you can't assume you will have high availability in those components. They're optimizations, like a cache. A cache can disappear, and this can have a destabilizing effect on your architecture if you don't plan for it.

This lack of planning is pretty common, unfortunately. Whether it's in a software component or system architecture, people often use a thing without understanding the implications of it. Then when AWS API calls become unavailable, half the internet falls over... because nobody planned for "what happens when the control plane disappears". (This is actually a critical safety consideration in other systems)