MurphyA/hacker-news huggingface dataset:
by daft_pink | 2025-12-14 01:37:53+00:00
The reason I don’t use DuckDuckGo is that when you sell keyword based ads on your platform, it really isn’t private. If you’ve ever worked with keyword based ads, they might be anonymous, but anything you are searching is showing up somewhere to some third party.

I really like Kagi, becuase I can pay for the search and my searches aren’t being leaked to third parties.
by CharlieDigital | 2025-12-14 01:38:37+00:00
> I made a passionate case...

My experience is that it is less about passion and more about reason.

There's a lot of good research and writing on this topic. This paper, in particular has been really helpful for my cause: https://dl.acm.org/doi/pdf/10.1145/3593856.3595909

It has a lot going for it: 1) it's from Google, 2) it's easy to read and digest, 3) it makes a really clear case for monoliths.
by pizlonator | 2025-12-14 01:39:07+00:00
> "If I don't make big claims, no one will notice."

I am making big claims because there are big claims to be made.

> he statements about the actual security benefits should be independently verified -this hasn't happened yet

I don't know what this means. Folks other than me have independently verified my claims, just not exhaustively. No memory safe language runtime has been exhaustively verified, save maybe Spark. So you're either saying something that isn't true at all, or that could be said for any memory safe language runtime.
by iamnothere | 2025-12-14 01:39:23+00:00
If I entrust money to someone who I know to be a thief, and then he runs off with it, how am I not at least partially culpable for my own negligence? Obviously the thief is the criminal and deserves to be punished and to pay restitution, but the idiot who should know better isn’t blameless.

One can express a need for regulation while also being aghast that people are still falling for the cloud scam, despite the overwhelming evidence that it is indeed a scam.
by tomhow | 2025-12-14 01:39:30+00:00
Please don’t introduce off-topic flame bait on HN. The guidelines make it clear we're aiming for something better here. https://news.ycombinator.com/newsguidelines.html

We detached this subthread from https://news.ycombinator.com/item?id=46255900 and marked it off topic.
by kstrauser | 2025-12-14 01:40:28+00:00
The latter passes each item in the list into the child processes’s argv, as-is, without the shell parsing them. That means this would delete a single item named “~/ some file”, spaces and all, instead of three items named “~/“, “some”, and “file”.

Edit: I’m typing this on my phone, so brevity won over explicitness. The latter probably wouldn’t expand ~. Imagine a file named “/home/me/ some file” for a better example.
by tomhow | 2025-12-14 01:40:36+00:00
Could you please stop posting unsubstantive comments and flamebait? You've unfortunately been doing it repeatedly. It's not what this site is for, and destroys what it is for. Eventually we have to ban accounts that keep posting like this.

If you wouldn't mind reviewing https://news.ycombinator.com/newsguidelines.html and taking the intended spirit of the site more to heart, we'd be grateful.
by tonymet | 2025-12-14 01:41:19+00:00
You lose the Google content , since the export is lossy (docs , sheets, slides , etc) . And most of the value is collaborative . You’ll lose anything that you contribute to that’s not in your account . You’ll lose credentials (eg sso to third parties ), messaging access .

You’ll lose indexing and metadata , like Google Drive search , Google Photos search , thumbnails .

It’s a myth to assume the value is in the backup. Most of the value you have is in the access and the application
by machomaster | 2025-12-14 01:44:41+00:00
> that's not going to be documented anywhere but you'll need to talk people at various embassies.

This is absolutely not how bureaucracy works. In cases when there are special visas (like USA's talent visas), they are well documented. There are no special under-table visas that are given to people who a clerk at the Embassy likes.

> there is the digital nomad visa, for which while tied to a country, it doesn't even make sense that it would only allow to stay in one country.

Once again, we are talking about reality, about how things are, instead of how things ought to be in your mind...

E.g. check Portugal D7 / digital-nomad visas: https://www.portugalist.com/d7-vs-d8/

> The term “Digital Nomad Visa” can create a lot of confusion as many other countries offer digital nomad visas that are temporary, and do not offer a path to permanent residency or citizenship. Some also don’t require you to pay taxes. Portugal’s Digital Nomad Visa is aimed at those that want to live in Portugal more or less full-time and make Portugal their home. In return for downsides like physical stay requirements and being taxed on your worldwide income, you do get access to the public healthcare system and you can later qualify for permanent residency and Portuguese citizenship.

> this being done purposefully suggests you have read that somewhere. got a reference?

Can't really provide you with the proof of something (work to unify EU visas) that doesn't exist. You can just check how the system works and how purposefully visas are left to be decided on the National level.

Even with the EU-level status of long-term residents ( https://en.wikipedia.org/wiki/Long-term_resident_(European_U... ), the details depend on the individual country. And even then, this is how it goes e.g. in Finland ( https://migri.fi/en/permanent-residence-permits ):

> If your stay in another Schengen country takes more than 90 days, you must apply for a national residence permit of that country.

> Your P-EU permit granted by Finland will expire if another EU Member State grants you a long-term resident's EU residence permit for third-country nationals (a P-EU permit).

So it's the same limit again.
by magicalhippo | 2025-12-14 01:45:24+00:00
> Taking said dependency does not turn a microservice into a monoloth.

True. However one of the core tenets of microservices is that they should be independently deployable[1][2].

If taking on such a shared dependency does not interfere with them being independently deployable then all is good and you still have a set of microservices.

However if that shared dependency couples the services so that if one needs a new version of the shared dependency then all do, well you suddenly those services are no longer microservices but a distributed monolith.

[1]: https://martinfowler.com/microservices/

[2]: https://www.oreilly.com/content/a-quick-and-simple-definitio...
by amitav1 | 2025-12-14 01:45:39+00:00
I feel like it's more "if you don't sprint through the middle of the freeway and instead cross at the crosswalk, you're safe from cars". Also, there's not some genie sprinkling fairy dust on all of the political posts that's making them go up to the top, it's because that's what most people interact the most with. If you have atypical tastes (as most people on this website do), then you shouldn't be surprised when content tailored for typical tastes do not fit your tastes. After enough time on Twitter, even the For You becomes a bit better, with only occasional political posts.
by AlotOfReading | 2025-12-14 01:46:08+00:00
You'd be surprised at the places that have electricity, like houses in middle of nowhere, central asia. One of the challenges with engineering technology for the global south is that poverty is wildly different for different people. I met a professor working on flatpack windmills to pump water/electricity. The major challenges he kept seeing in the the Andes weren't the sorts of longevity/efficiency/logistics issues we usually solve with standard engineering, but how the products interacted with local politics and society.
Show HN: A game engine that transpiles your scripts to Rust for native perf
by TiernanDeFranco | 2025-12-14 01:46:21+00:00
Hey all, I've been developing Perro Engine, a unique game engine written in Rust that allows you to use C#, TypeScript, or the engine DSL: Pup, to script your game, and the engine will transpile your scripts into Rust modules that interop with the engine without running different runtimes, interpreters, or VMs.

Doing this essentially gives you much more performance than a scripting layer since there's no bytecode having to be decoded and no runtime bloat.

It also allows for each language to support all the same features and access to the engines internal APIs because you don't have to worry about them ACTUALLY being implemented in that language and interfacing with the Rust core, it just IS Rust and it's just calling native functions in the api.

Let it be known that of course this means it is not REALLY C# or TypeScript that's unning, it's just the familiar syntax to avoid writing game logic in Rust if you don't want to. If you need to for performance reasons (like very specifically managing memory allocaiton, clones, borrows) then you are able to write a Rust script natively as if it was any other game script, it just needs to follow the structure and conventions the engine expects.

I'd appreciate any feedback and am happy to answer any questions, and if you don't mind starring the repo that'd be great!
by threethirtytwo | 2025-12-14 01:46:43+00:00
I don't agree.

Protobuf works best if you have a monorepo. If each of your services lives within it's own repo then upgrades to one repo can be merged onto the main branch that potentially breaks things in other repos. Protobuf cannot check for this.

Second the other safety check protobuf uses is backwards compatibility. But that's a arbitrary restriction right? It's better to not even have to worry about backwards compatability at all then it is to maintain it.

Categorically these problems don't even exist in the monolith world. I'm not taking a side in the monolith vs. microservices debate. All I'm saying is for this aspect monoliths are categorically better.
by kstrauser | 2025-12-14 01:46:55+00:00
I signed up for a new account a month ago for a specific purpose, and the default timeline was full of literal Nazi crap, like dumb 1488 references, and blaming weather on Jews, and other bullshit like that. I did absolutely nothing to get that. I signed up and that’s what it showed me until I went on a spree of blocking stuff.
by adwn | 2025-12-14 01:47:36+00:00
How do you interpret these numbers? If your point is that we can simply overprovision photovoltaik arrays by a factor of 6.67, then that would make solar the most expensive power generation method by far.

And it only gets worse the more households transition to heatpumps, because the consumption in winter is so lopsided. For example, I heat my home with a heatpump, and I have 10 kWp of solar arrays on my roof. In the last week of July, we consumed 84 kWh and generated 230 kWh (273 %). In the last week of November, we consumed 341 khW and generated 40 kWh (11 %). This means we'd need roughly 10 times as much PV area to match demand (10 roofs?), and huge batteries because most of that consumption is in the evening, at night, and in the morning.

Of course, utility-scale and residential solar behave a bit differently, and it becomes more complicated if wind is factored in. But it shows that you can't just overprovision PV a little to fix the main problem of solar power: that it is most abundant in summer, and most in demand in winter.
by kalasoo | 2025-12-14 01:48:58+00:00
> In my work, the bigger bottleneck to productivity is that very few people can correctly articulate requirements.

Totally agree. I’ve tried to explain this in many places: AI coding (and creative tools in general) will ultimately remain tools. Only people who can clearly and thoughtfully articulate requirements will be able to fully leverage them.

Another hot take: the “one-person company.” Headcount isn’t the key variable. With AI, the real constraint is how well you can understand a problem and clearly define a solution.

- If a problem can be clearly defined and fully understood by one person, then one person is enough to solve it.

- If a problem is more complex and requires two fundamentally different areas of expertise, then it will likely take two capable people to solve it—no more, no less.
by anonymousiam | 2025-12-14 01:49:57+00:00
Saved my life

At 15 years old, I stupidly rode my bike across the street in front of my high school on a red light. It looked safe, but a car was speeding in the opposite lane, and I had to turn back to avoid being killed. So now I was in the lane I had just crossed and another speeding car hit me, throwing me (and my bike) about 40'. I was dead on the street, and a stranger stopped to give me CPR. After a month in the hospital with a broken back, and the doctors scratching their heads because I wasn't a paraplegic, I was eventually okay.

I never got to thank him. All I ever learned about him is that his name is Mark.
by conradev | 2025-12-14 01:50:49+00:00
I would very much love that. I like `jq` itself as a standard, even though I don't know how well it maps. Areas where I'd want to use Lite³:

- Microcontrollers. I find myself reaching for https://github.com/siara-cc/sqlite_micro_logger_c/tree/maste... because SQLite is just too big

- Shared memory regions/mapped files. Use it to share state between processes. Could you make mutations across processes/threads lock-free?

- Caching GPU-friendly data (i.e. image cache). I'm not sure if the current API surface/structure is page alignment friendly
by PunchyHamster | 2025-12-14 01:51:47+00:00
> He even mentioned how unpopular making things configurable is in the UI community.

Inability to imagine someone might have different idea about what's useful is general plague of UI/UX industry. And there seem to be zero care given to usage by user that have to use the app longer than 30 seconds a day. Productivity vs learning time curve is basically flat, and low, with exception being pretty much "the tools made by X for X" like programming IDEs
by functionmouse | 2025-12-14 01:51:52+00:00
Every dollar Wall Street takes from Main Street is spent on getting better at taking dollars from Main Street.

From Wikipedia:

Overexploitation, also called overharvesting or ecological overshoot, refers to harvesting a renewable resource to the point of diminishing returns.[2] Continued overexploitation can lead to the destruction of the resource, as it will be unable to replenish itself. The term applies to various natural resources such as water aquifers, grazing pastures and forests, wild medicinal plants, fish stocks, and other wildlife.

https://en.wikipedia.org/wiki/Overexploitation
by XorNot | 2025-12-14 01:52:16+00:00
Although the funniest thing about the holodeck these days is LLMs have answered a question: can you have realistic non-sentient avatars? Evidently yes, and holodeck authorship is likely a bunch of prompt engineering, with really advanced stuff happening when someone trains a new model or something.

Similarly in Stat Wars with droids: Obi-Wan is right, droids can't think and deserve no real moral consideration because they're just advanced language models in bodies (C3PO insisting on proper protocol because he's a protocol droid is the engineering attempt to keep the LLM on track).
by xboxnolifes | 2025-12-14 01:54:10+00:00
You can keep using an older version for a while. You shouldn't need to redeploy everything at once. If you can't keep using the older version, you did it wrong.

And ideally, your logging library should rarely need to update. If you need unique integrations per service, use a plug-in architecture and keep the plug-ins local to each service.
by matklad | 2025-12-14 01:55:43+00:00
It is the other way around --- it is _relatively_ easy to re-use the storage engine, but plug your custom state machine (implemented in Zig). We have two state machines, an accounting one, and a simple echo one here: https://github.com/tigerbeetle/tigerbeetle/blob/main/src/tes....

I am not aware of any "serious" state machine other than accounting one though.
by echelon | 2025-12-14 01:56:05+00:00
What would the equivalent be with LLMs?

I spend all of my time with image and video models and have very thin knowledge when it comes to running, fine tuning, etc. with language models.

How would one start with training an LLM on the entire corpus of one's writings? What model would you use? What scripts and tools?

Has anyone had good results with this?

Do you need to subsequently add system prompts, or does it just write like you out of the box?

How could you make it answer your phone, for instance? Or discord messages? Would that sound natural, or is that too far out of domain?
by theamk | 2025-12-14 01:56:10+00:00
Please don't use "sh" python library!

By default (1) captures stdout and stderr of all processes and (2) create tty for processs stdout.

Those are really bad defaults. The tty on stdout means many programs run in "interactive" rather then "batch" mode: programs which use pager get output truncated, auto-colors may get enabled and emit ESC controls into output streams (or not, depending on user's distro... fun!). And captured stderr means warnings and progress messages just disappear.

For example, this hangs forever without any output, at least if executed from interactive terminal:

from sh import man print(man("tty"))

Compare to "subprocess" which does the right thing and returns manpage as a string:

import subprocess subprocess.check_output(["man", "tty"], text=True)

Can you fix "sh"? sure, you need to bake in option to disable tty. But you've got to do it in _every_ script, or you'll see failure sooner or later. So it's much easier, not to mention safer, to simply use "subprocess". And as a bonus, one less dependency!

(Fun fact: back when "sh" first appeared, everyone was using "git log" as an example of why tty was bad (it was silently truncating data). They fixed it.. by disabling tty only for "git" command. So my example uses "man" :) )
by jagrsw | 2025-12-14 01:56:19+00:00
To clarify the position, my concern isn't that the project is bad - it's that security engineering is a two-front war. You have to add new protections (memory safety) without breaking existing contracts (like ld.so behavior).

When a project makes 'big claims' about safety, less technical users might interpret that as 'production ready'. My caution is caused by the fact that modifying the runtime is high-risk territory where regressions can introduce vulns that are distinct from the memory safety issues you are solving.

The goal is to prevent the regression in the first place. I'm looking forward to seeing how the verification matures and rooting for it.
by FreezeInTheDark | 2025-12-14 01:56:33+00:00
One thing that strikes me about the author's experience is how unusable Azure appears to be in all this. Like, this hits somewhat close to me as I also run a couple web projects, also written in Rust, on a serverless architecture, and frankly couldn't imagine wanting to spend the time to run them any other way. AWS Lambda for compute, and Dynamo for DB, have a perpetual free tier and it's been running practically without me touching it for years.

The AWS Rust SDK also seemed very mature to me when I was using it ... compare to:

>the only option for a database instance with a free plan was [...] serverless Microsoft SQL Server (MSSQL)

>the MSSQL connection required TLS and this hadn’t been implemented in the sqlx connector I chose to use for my Rust-based functions. I wasted two weeks implementing TLS support in sqlx

That is insane. Not to mention the later bit with sudden, unexplained availability and the only hint that it might to be related to a _future_ deprecation? Like, imagine if this were a critical service for you. Professional malpractice on Microsoft's part.

This isn't really the main point of the article, and I did find the stuff on self-hosting interesting, but it does seem like this could have been avoided if Azure had lived up to its peers.
by corysama | 2025-12-14 01:56:35+00:00
A trope in the first season of HBO’s Silicon Valley is literally every company other than the main characters professing their mission statement to be “Making the world a better place through (technobabble)”

The subtle running joke was that while the main characters technobabble was fake, every other background SV startup was “Making the world a better place through Paxos-based distributed consensus” and other real world serious tech.
by machomaster | 2025-12-14 01:57:37+00:00
In this case, the more applicable are:

1. "Peter principle": "people in a hierarchy and organizations tend to rise to 'a level of respective incompetence' "

2. "Parkinson's law": "Work expands to fill the available time".

So people are filling all the available the time and working tirelessly to reach their personal and organizational levels of incompetency; working hard without stopping to think if what they are doing should be done at all. And nobody is stopping them, nobody asks why (with the real analysis of positives, negatives, risks).

Incompetent + driven is the worst combination there can be.
by Lvl999Noob | 2025-12-14 01:57:44+00:00
And for the opposite, where you keep your main pipeline in shell but want to use python for some parts of it, there is pypyp.

https://pypi.org/project/pypyp/

It takes cares of the input and output boilerplate so you can focus on the actual code that you wanted python for.

> seq 1 5 | pyp 'sum(map(int, lines))' > ls | pyp 'Path(x).suffix'
by roughly | 2025-12-14 01:57:48+00:00
One of the things you get an intuition for after using these systems is when to start a new conversation, and the basic rule of thumb is “always.” Use a conversation for one and only one task or question, and then start a new one. For longer projects, have the LLM write down a plan or checklist, and then have it tackle each step in a new conversation. The LLM context collapse happens well before you hit the token limits, and things like ground rules and whatnot stop influencing the LLMs outputs after a couple tens of thousands of tokens in my experience.

(Similar guidance goes for writing tools & whatnot - give the LLM exactly and only what it needs back from a tool, don’t try to make it act like a deterministic program. Whether or not they’re capital-I intelligent, they’re pretty fucking stupid.)
by mikestew | 2025-12-14 01:57:49+00:00
It's still published, I get a print issue probably every quarter, yeah. I flip through really quickly before it gets tossed in the recycling bin. Sometimes I flip quickly enough that it doesn't even make it into the house before it goes to recycling.

It used to be great, then turned into kind of an airport magazine (you know, the kind you'll read on the plane but not subscribe to), and after it got bought out it's garbage now (see above: I mean this literally). Personally, I'm extra miffed that they took Trail Running magazine with them.

Why do I continue to subscribe? Because along with Outside magazine they (I forget who "they" are, exactly) bought the Gaia GPS app which I use extensively. So I'm basically buying the Gaia subscription and get a shitty print magazine thrown in for free (oh, yeah, and access to their online edition, which redefines "garbage". It's awful, I could spend pages on the topic.) I am currently reevaluating how much I really use Gaia GPS, and what a suitable alternative would be. In many cases, Footpath (an HN user creation, IIRC) might do the trick.
by p_ing | 2025-12-14 01:59:17+00:00
There's not enough information to come to a conclusion as to what the 503s originated from. There is enough information for manufactured outrage, of course.

I don't see why one would want to run in-the-clear over the Azure network for SQL connections.

The author was doing hobby projects. Granted, hobby projects should run on any platform, but Azure seems to have less of that free tier you can get elsewhere.