MurphyA/hacker-news huggingface dataset:
by cyber1 | 2025-05-14 09:22:16+00:00
"Safe" Rust is generally a simple language compared to C++. The borrow checker rules are clean and consistent. However, writing in it isn't as simple or intuitive as what we've seen in decades of popular systems languages. If your data structures have clear dependencies—like an acyclic graph then there's no problem. But writing performant self-referential data structures, for example, is far from easy compared to C++, C, Zig, etc.

On the opposite, "Unsafe" Rust is not simple at all, but without it, we can't write many programs. It's comparable to C, maybe even worse in some ways. It's easy to break rules (aliasing for exmaple). Raw pointer manipulation is less ergonomic than in C, C++, Zig, or Go. But raw pointers are one of the most important concepts in CS. This part is very important for learning; we can't just close our eyes to it.

And I'm not even talking about Rust's open problems, such as: thread_local (still questionable), custom allocators (still nightly), Polonius (nightly, hope it succeeds), panic handling (not acceptable in kernel-level code), and "pin", which seems like a workaround (hack) for async and self-referential issues caused by a lack of proper language design early on — many learners struggle with it.

Rust is a good language, no doubt. But it feels like a temporary step. The learning curve heavily depends on the kind of task you're trying to solve. Some things are super easy and straightforward, while others are very hard, and the eventual solutions are not as simple, intuitive or understandable compared to, for example, C++, C, Zig, etc.

Languages like Mojo, Carbon (I hope it succeeds), and maybe Zig (not sure yet) are learning from Rust and other languages. One of them might become the next major general-purpose systems language for the coming decades with a much more pleasant learning curve.
by eliana_jordan | 2025-05-14 09:22:42+00:00
Hey HN, I’m Eliana.

I was a dive instructor who learned to code and ended up building two SaaS apps. Every time, I rebuilt the same things — dual roles, reviews, payments, admin dashboards — and it got repetitive fast.

So I built Peerquik, a Next.js boilerplate for full-featured P2P and B2C marketplaces (think Airbnb, Etsy, eBay, etc). It comes with 23+ prebuilt features and production-ready integrations.

Included:

Dual-role auth (buyers/sellers)

Google OAuth, email/password

Stripe payments + subscriptions + invoices

Ratings, reviews, favorites

Admin dashboard

Cron jobs, SEO (sitemap, robots), newsletter footer

Docker deploy (Coolify ready)

Currency converter, forms with CAPTCHA

Tons of reusable components

It's not just a template — it’s a working foundation for real apps. No vendor lock-in. You can host it on your own VPS or Vercel.

You can see it in action: https://beunderwater.com https://scubareputation.com

I use this exact boilerplate as the base for both projects.

The goal: save 500+ hours and help indie hackers ship faster without getting stuck on boilerplate.

Would love your thoughts and questions! https://peerquik.com
by jajko | 2025-05-14 09:23:19+00:00
Also host can't offer that date for another guest (at least it used to be like that). In case of cancelling 1 day prior then they either have a serious issue or another booking so thats not so punishing.

It may also affect internal ranking order by which they show properties to people, but who knows whats implemented internally right now, and what will be in place in 3 months.
by 0xEF | 2025-05-14 09:23:37+00:00
I still rock my OG Pebble and while I am excited they're coming back, I have no plans to upgrade.

Like you, my needs are simple; vibrating alarm, notifications, but with one key factor; I need a display that I can read in broad daylight that plays nice with my far-sighted eyes. The eInk display on the OG Pebbles hits the mark. Being able to read a text without pulling out my phone is also nice.

Plus they can be got on eBay for about $30 USD and a fresh battery is about $15, so they don't break the bank. The Rebble.io community's work is still functioning well enough for my use, as well.
by pjmlp | 2025-05-14 09:24:03+00:00
Note that some users of GC languages that support stack allocation, are used that it is a compiler error trying to have such a pointer/reference.

D example, https://godbolt.org/z/bbfbeb19a

> Error: returning `& my_value` escapes a reference to local variable `my_value`

C# example, https://godbolt.org/z/Y8MfYMMrT

> error CS8168: Cannot return local 'num' by reference because it is not a ref local
by Juliate | 2025-05-14 09:24:20+00:00
> "Key achievements" does not include numbers to describe impact.

And that's perfectly fine too.

Don't make up numbers just to satisfy the quantitative-obsessed people/recruiters, who won't make satisfying customers/bosses anyway.

Not only does it make no sense to make up numbers, but straight numbers are definitely suspect, depending on how they are put forward.

Both quanti and quali are important, and in some jobs, even engineering ones (especially in the glue/soft/transverse positions) quali is much more relevant than quanti.

If you have precise numbers, and it matches the discourse you want to put through, go ahead. If you don't, if your strength is not in this particular corner, there is no requirement to bend yourself into a box that does not fit.
by scotty79 | 2025-05-14 09:25:36+00:00
In-place mutability and stack allocation are for speed. This made them have variables and values inside them both as separate first-class citizens. The entire borrow checker is just for tracking variables access so that you don't need to clone values. I'd say that given this one guiding decision there are very little arbitrary ones in Rust. The rest of it pretty much had to be made exactly the way it is. Rust is more of a discovery than a construct.

C++ is just Rust without any attempt at tracking variable access and cloning which leads to a mess because people are too terrible at that to do that manually and ad-hoc. So Rust fixes that.
by nickd2001 | 2025-05-14 09:25:39+00:00
Remembering the dot-com crash of '01, when the tech jobs aint there, they simply aint there, and no amount of c.v / resume polishing will change that. No-one should take this personally. At times like that its maybe best to do something else to earn a living. 2001-3 I did a couple of ski seasons in a hotel, unrelated to tech. In early 2004 got a not-fantastically-paid-but-using-good-skills job with a startup, then mid-2005 a new job with a return to "proper rewards that recognised my skills". So, sometimes that market is down, and you gotta be flexible. People worry about forgetting all their skills. That didn't really happen to me, but I mucked about with Linux on the side, and that was useful for getting the next job. Not sure what today's equivalent is. AI muddies the waters here. Of course, when you have a family, being without tech compensation can be a problem. My answer to that is, its essential when entering the tech industry, to recognise it as a "feast-and-famine" / "manic-depressive" industry. One day it pays big bucks. Next day no jobs. So, manage expenses and financial commitment accordingly and put something aside.
by joshprice | 2025-05-14 09:25:53+00:00
I've talked about this a few times and this is the shortest answer to this question. The first part of this talk may help explain concisely where Ash fits at a higher level.

https://youtu.be/10VBTcN8gAo?feature=shared&t=133

Ash Framework was created to solve a fundamental problem in (web) application development for business apps. When you build a new app, you want to focus on the valuable, innovative parts - what's visible above the waterline of the iceberg. However, modern web applications require an enormous amount of "below the waterline" functionality that's essential but not where you want to spend your time.

Running a consultancy and building various client projects highlights this challenge. Everyone wants to focus on the core, valuable features, but must also deal with relatively boring, commodity problems that have been solved countless times before. This often means reinventing the wheel, which clients understandably see as low-value work.

Authentication is a perfect example - most customers don't even specify login functionality as a feature. Similarly, admin interfaces are considered table stakes for modern applications. The list is extensive: admin UIs, observability, security, and more. All important, but time spent there can feel wasteful when you'd rather be innovating.

Ash's primary goal is to keep you focused on the innovative work above the waterline while minimizing time spent below it. The framework accomplishes this by modelling your domain and deriving everything else.
by killerstorm | 2025-05-14 09:26:28+00:00
Yes, I think it might be a good solution where you have a context up to 10M of tokens and you do a lot of requests with that context. It might be relevant for agentic stuff which tends to produce long chat logs - especially with some gadgets on top, e.g. some 'episodes' might be completely removed as obsolete.

But I don't think it's a good solution for bigger amounts of data - as in that case it's more beneficial if that can be formed into independent memories.
by lyu07282 | 2025-05-14 09:26:30+00:00
This goes nowhere, but here is the last things I want say:

Both have the same motivation. It makes them win more elections. Republicans want voter ID laws because it makes it harder for people without an ID to vote, and those people tend to not vote for republicans. Democrats are against voter ID laws because it makes it easier for people without an ID to vote, and those people tend to vote for democrats.

There is no feasible way to increase access to photo IDs, in red states that introduce(d) voter ID laws its republicans who make it harder for people. There is no national ID in the US and its again republicans who make it impossible to change that.

Election fraud is not a real issue, there is no evidence of any wide-spread voter fraud. There are many other ways identity is established at polling places and it is almost impossible to do without anyone noticing. There are lists of voters, if you go and it shows you already voted, it would be immediately obvious.

These are all things you could easily research for yourself
by julik | 2025-05-14 09:27:37+00:00
FBW with servo delay, manual trim that you do not use often etc. would be a severe problem in a situation like this, especially for a guy who was captain on an IL-76 (where the yoke is the size of a cab truck steering wheel and has direct feedback from actuators). He "should have been able". Also AFL "should have" provided training in direct mode flying. The OAK "should have" provided an SOP for resetting the flight control computers into normal mode, or some kind of alternate mode which at least would provide auto-trim. Etc. etc. etc.

It is very tempting to say "pilot error" but if you drive a car and the way the steering wheel responds to your input drastically changes in an instant, without you having experienced that way of the steering wheel reacting - is it your "error"?
by explodes | 2025-05-14 09:27:59+00:00
I had quite a similar experience. During the 3rd attempt at learning, everything seemed to click and I was able to be effective at writing a few programs.

This is all despite a long career as a programmer. Seems like some things just take repetition.

The "Dagger" dependency injection framework for the JVM took me 3 'learning attempts' to understand as well. May say more about myself than about learning something somewhat complicated.
by tsukikage | 2025-05-14 09:28:12+00:00
It's not a "just" if the fix cripples performance; it's a tradeoff. It is forced to hurt everything everywhere because the processor alone has no mechanism to determine when the mitigation is actually required and when it is not. It is 2025 and security is part of our world; we need to bake it right into how we think about processor/software interaction instead of attempting to bolt it on after the fact. We learned that lesson for internet facing software decades ago. It's about time we learned it here as well.
by aziaziazi | 2025-05-14 09:28:19+00:00
> The commenter I responded to said that people don't need to eat animal products to live at optimal health, which is laughable

That is still technically incorrect and is refuted by observing healthy old vegans that consume supplements from cultivated-bacteria only for decades.

Those bacteria also develop in some animals digestive system as you already know, and eating those animals has been for a long time our main source of b12. The other (minor but non trivial) one has been non-washed fruits and plants human consumed during millennia, and that’s still how grazing animals ingest a bit everyday. The non grazing animals are widely supplemented with cultivated-b12. We’re producing around 80T/year for that which isn’t much we animals only need around 10mg/year. I'm not discussing the "non-natural" qualification of supplementation, just the fact it's today a very white practice to live an healthy (human or non human animal) life by ingesting only bacteria sourced B12.

> we've cracked the code on the "essential" nutrients

Yes we did, and the last of that nutrient has precisely been vitamin b12 which led to two Nobel prizes : https://pubmed.ncbi.nlm.nih.gov/23183296/
by lazide | 2025-05-14 09:28:47+00:00
Yup. The challenge I think a lot of people are having is that ‘01 was 24 years ago, so for a sizable percentage of the industry (80-90%?) it’s outside of their living memory. Certainly outside of their professional experience.

It’s a harsh change from the prior ‘always get a raise when you change jobs, barely have to interview, change jobs every year’ type bubble that has been expanding for a very long time.
by throwaway290 | 2025-05-14 09:28:56+00:00
> It was forcibly dissolved from within as regions began literally just declaring their independence and refusing to recognize central authority

It's disputed. Some say it was top down, like USSR could roll tanks as usual when republics protested but it didn't. See https://en.wikipedia.org/wiki/Dissolution_of_the_Soviet_Unio... and talk https://en.wikipedia.org/wiki/Talk:Dissolution_of_the_Soviet...
by arcanemachiner | 2025-05-14 09:29:17+00:00
If you've tried to make a JSON API with Phoenix, it can be pretty cumbersome to generate an OpenAPI spec for the project. It's a very manual and tedious process, even when working with OpenApiSpex (the go-to Elixir library for generating an OpenAPI specs). And if your code implementation changes, then you often have to update your spec to match it.

With Ash, the same data used to model your application is also used to derive the data needed to build the OpenAPI spec. So there's a real value proposition there IMO. It eliminates much of the problems of keeping your spec in line with your code, since they are both modeled in a single location.

Disclaimer: I only learned this by working through the book, so I haven't actually gotten to experience anything off the happy path.
by PaulRobinson | 2025-05-14 09:29:20+00:00
As many people seem confused, it seems that this framework is a declarative framework (think: expressing a solution like you would in SQL or Prolog), in Elixir, that seems to have the goal of separating out core logic from control flows within web apps, APIs and so on.

Over the course of 15+ years of playing with Rails, I've come to the view of CRUD being a poor choice for most real-world applications and MVC being a useful but often-abused concept. That took me down a bit of a rabbit hole of trying to think about DDD within the constraints of an opinionated framework that thinks CRUD and MVC are the thing that makes you go fast. I, on the other hand, want the thing that makes it easy to extend and maintain. I want actual events to be modeled for all sorts of real-World reasons.

I've been learning Elixir recently because it's something new, the actor model appeals from a concurrency perspective to some of the problems I want to solve, and because Phoenix looks like an interesting and elegant web app framework. However, there was a nag in the back of my head that I'd just end up hitting the same frustrations: I was, and am, ready for that and seeing if anything about Elixir + Phoenix makes life easier than Rails made it.

Ash seems to be a good candidate for part of the puzzle. A declarative framework that brings some packages for useful, often-needed parts of the puzzle (like authentication, authorization, and so on), and it seems to encourage a way of thinking about some key DDD concepts. Resources sound like domains or bounded contexts. Declarative style sounds like it might lend itself to event modeling more easily. Calculated values are a nudge towards "view models".

Never tried, I'm early on my journey, but I think the Ash book will be the first thing I pick up after I've finished the Elixir and Phoenix books I'm reading through. Curious to hear stories from people further down this journey, though!
by toddydrinker | 2025-05-14 09:29:38+00:00
> staying with friends in Hyderabad, flies and all.

Hmm... flies and all?

> send one of his servants out in the morning to buy it for us.

Hmmm..... one. servants?

> This palm juice alcohol is very primitive and probably something monkeys drank.

Hmm... primitive? monkeys?

Sorry, but I got an uncomfortable feeling from reading your comment. I think my insula cortex activated upon detecting chromatocrat type verbiage.
by drysine | 2025-05-14 09:30:58+00:00
>Crimea is Ukraine. Donetsk is Ukraine. Luhansk is Ukraine. Zaporizhia is Ukraine. Kherson is Ukraine. Odesa is Ukraine. Kharkiv is Ukraine.

You see that's the difference between us. You care about control of territory, but do it staying perfectly safe while other people are dying. I care about ordinary people's lives and want this meat-grinder stop right now.

I'd suggest that you google the word "Бусифікація"[0], it was the word of the year in 2024 according to a dictionary of modern Ukrainian slang. Come and see this video[1], for example, and listen to the pure terror in the screams of that man being forcibly mobilized to fight for the territory you care about so much.

There was really heartbreaking one where a man was screaming "I want to live" and some old woman was desperately and futilely trying to help him get free. Thank God, I haven't bookmarked any of such videos.

[0] https://uk.wikipedia.org/wiki/Бусифікація

[1] https://t.me/ASupersharij/37513
by Tistron | 2025-05-14 09:31:04+00:00
"Powered by Bear ʕ•ᴥ•ʔ" -> "A privacy-first, no-nonsense, super-fast blogging platform No trackers, no javascript, no stylesheets. Just your words."

Yet, about 30% of the source of TFA is a stylesheet. I guess they mean no external stylesheet?
by thomc | 2025-05-14 09:31:49+00:00
I have used them for the following:

* Holding a bandage in place

* Temporary clothing fix (broken fly, broken strap)

* Keeping hotel curtains together to block out light

* Popping a SIM tray

* Pinning something inside clothing when travelling in risky areas

It is rare to need one, but they take up no space so I pop one in my bag.*
by lenkite | 2025-05-14 09:32:22+00:00
Maybe they should not remove APIs for open source apps then. If you can vet the source code and the app has been built from the source code you vetted, then there is no point in removing capabilities for reasons other than market monopolization and extinguishing features for non-Google developers. After all, these security rules don't apply to Google themselves.

(btw, not singling out Google - IMHO Apple is bad here too. This duopoly in the smartphone space is a major PITA)
by short_sells_poo | 2025-05-14 09:32:49+00:00
I think the comment you reply to perhaps fundamentally misunderstands the economics of public transport. You raise good points about the benefits of having central planning for these things, but IMO the most important factor the people often mis is: public transport is not meant to be a revenue generator.

Where almost all the efforts tend to collapse is the misguided and frankly idiotic notion that public transport should be directly self-funding or even profitable.

The benefits of a well functioning public transport - and Switzerland is definitely a great example - are huge, but indirect. It is a force multiplier, it makes the economy function much better by allowing people to get to where they need to be en-masse and efficiently. It multiplies the number of people that can get to the city center and shop there, and by making this journey fast, safe and reliable, people will be more inclined to do it and spend money there. The $1 that is spent on public transport comes back in multiples in terms of commerce that it enables.

Artificially crippling it by forcing it to generate revenue at the source will reduce these indirect benefits.

The tragedy is that the indirect benefits are more difficult to quantify, and often get ignored in the face of punchy public hysteria about how much money is "wasted" on public transport...

NB: I'm not saying that it should be a money sink, cost control is an important function in any organization. It's about the primary objective that public transport should fulfil.
by dazzawazza | 2025-05-14 09:33:08+00:00
When I give short talks at schools about game dev I try to make it super clear that we are all born game designers. We all make up games as children and a large part of that is story telling.

Every child has seen a face in a cloud and 'designed' something outside of themselves. This is where teachers are amazing. Teachers know how to nurture that against the pressure of society crushing it.

It was python+pygame that got one of my kids to learn to program and minecraft modding that got another to learn. Neither code now but that wasn't the point.
by ben_w | 2025-05-14 09:33:25+00:00
JumpCrisscross said "half century"; while I would doubt the "practically every" part of their claim and like you would instead reduce that to somewhere between "lots" and "most", your list has a lot of stuff from before 1975.

You can definitely have CD-ROMs and I think it's fair to give you DNA sequencing (though that's not really one single thing), but everything else is questionable or just not correct when I look up the history of those exact things on the same source you link to above — their own wikipedia pages.

As for "questionable":

- Cellular phone service: depends what you count as such, given people have been working on the predecessors to what's now called 1G since about the invention of the radio; but 1G itself would be Japan in 1979, so if that's your cut-off-point, then you could have it I guess.

- Laptop: only if you're counting the Portal R2E CCMC, because the first clamshell laptop was the Grid Compass. While the founder of the company and designer of the laptop were British, they were doing the work in the USA.

As for "just no":

- Basic oxygen steelmaking: 1856 for the first demonstration in the UK, 1940s for industrialisation in Austria

- Float glass: 1950s

- Orbital satellite: 1957

- High speed railway: depends what you mean by "high speed", but you could easily claim 1938 or several different points in the 1950s

- Public key cryptography: 1973 in secret in the UK, but they were classified for ages and only the US invention of the same a few years later made it commercially available, so the "lab" part in the lab-to-home path was definitely American.

- Orbital space station: 1971 (I'd count this as a paradigm shift even if there's no living rooms anywhere in sight here)

- Direct satellite television: why did you put this in your list? Not only is the first ever satellite TV broadcast the USA's Telstar in 1962, the first direct broadcast satellite was ATS-6 in 1974: https://en.wikipedia.org/wiki/ATS-6

- Self-driving car: Even the SOTA in self driving cars is not "paradigm-shifting", so it's not really been invented yet at the level required to be on this list