MurphyA/hacker-news huggingface dataset:
by user_7832 | 2025-05-14 11:31:26+00:00
…which is totally understandable… if the hiring manager had communicated that. They could’ve easily mailed back “Hi this proposal seems much more detailed than what we need for evaluation, please save yourself some time and energy.”

The author may have had issues (I personally don’t count “need clear instructions” as an issue - edit - I see they didn’t adhere to the TUI prompt), but the hiring manager definitely did.
by avinassh | 2025-05-14 11:31:27+00:00
> I remember the first post by the Neon team here on HN. I think I commented at the time that I thought it was a great idea.

Same! I remember it too. I found it quite fascinating. Separation of storage and compute was something new to me, and I was asking them about Pageserver [0]. I also asked for career advice on how to get into database development [1].

Two years later, I ended up working on very similar disaggregated storage at Turso database.

Congrats to the Neon team!

[0] - https://news.ycombinator.com/item?id=31756671

[1] - https://news.ycombinator.com/item?id=31756510
by kjuulh | 2025-05-14 11:32:31+00:00
Congratulations to the Neon team.

To be honest this is a little sad for me. I'd hoped that Neon would be able to fill the vacuum left by CockroachDB going "business source"

Being bought by DataBricks makes Neon far less interesting to me. I simply don't trust such a large organisation that has previously had issues acquiring companies, to really care about what is pretty much the most important infrastructure I've got.

There certainly is enough demand for a more "modern" postgresql, but pretty much all of the direct alternatives are straying far from its roots. Whether it be pricing, compatibility, source available etc.

Back when I was looking at alternatives to postgres these were considered:

1. AWS RDS: We were already on AWS RDS, but it is expensive, and has scaling and operations issues

2. AWS Aurora: The one that ended up being recommended, solved some operations issues, but came with other niche downsides. Pretty much the same downsides as other wire compatible postgresql alternatives

3. CockroachDB: Was very interesting, wire compatible, but had deeper compatibility issues, was open source at the time, it didn't fit with our tooling

4. Neon: Was considered to be too immature at the time, but certainly interesting, looked to be able to solve most of our challenges, maybe except for some of the operations problems with postgresql, I didn't look deeper into it at the time

5. Yugabyte: interesting technology, had some of the same compatibility issues, but less that the others, as they're also using the query engine from postgresql as far as I can tell.

There are also various self hosting utilities for PostgreSQL I looked at, specifically CloudPG, but we didn't have the resources to maintain a stateful deployment of kubernetes and postgres ourselves. It would fulfill most of our requirements, but with extra maintenance burden, both for Kubernetes and PostgreSQL.

Hosting PostgreSQL by itself, didn't have mature enough replication and operations features by itself at that point. It is steadily maturing, but as we'd got many databases manual upgrades and patches would be very time consuming, as PostgreSQL has some not so nice upgrade quirks. You basically have to unload and reload all data during major upgrades. Unless you use extensions and other services to circumvent this issue.
by deng | 2025-05-14 11:32:44+00:00
The problem with the SyncThing Android app is that it's just a wrapper around SyncThing, which is a Go library, but SAF does not give you simple file descriptors you can use in native code. Instead, you get "content://" URLs, and you need a Java/Kotlin bridge to convert these to file descriptors. That would need to be done in SyncThing itself (EDIT: or some other trickery, because it seems like syncthing-fork made it work somehow).

However, AFAIK, this problem would not apply to the NextCloud app.
by dwattttt | 2025-05-14 11:33:06+00:00
> Why would a stack frame want to move ownership to its callee, when by the nature of LIFO the callee stack will always be destroyed first, so there is no danger in hanging to it until callee returns.

It definitely takes some getting used to, but there's absolutely times when you could want something to move ownership into a called function, and extending it would be wrong.

An example would be if it represents something you can only do once, e.g. deleting a file. Once you've done it, you don't want to be able to do it again.
by yunusabd | 2025-05-14 11:33:30+00:00
I was curious if the sensor would pick up other things like trees or other cyclist, but it seems like they accounted for that:

> We then log a sensor events [sic] if the majority of cells in the sensor frame agree to the same value within a threshold parameter [...]. This ensures that sensor events are only logged when large objects like cars block the sensor’s field-of-view , i.e., one or more small objects like branches or distance pedestrians in the sensor’s field-of-view will not trigger this condition. While there is no guarantee that this approach strictly identifies cars, we empirically saw during testing that passing cyclists and pedestrians rarely satisfied this condition at the typical passing distance due to the wide field-of-view of the VL53L8.

Also interesting that it's quite cheap to build:

> The whole system can cost less than $25 [...]

From the paper https://dl.acm.org/doi/10.1145/3706598.3713325
by olivermuty | 2025-05-14 11:33:35+00:00
Hello, I have two projects in prod on ash!

First of all, its not "macro based", as that implies dark magic and sacrificed goats. The spark dsl underlying all this is just structs all the way down in a nested manner. Just like you would see if you look under the covers of a Absinthe Blueprint produced by that dsl.

The dsl is declarative and allows to express a lot of stuff with less code, but I would say that saying its "macro based" is a bit misleading, although "technically correct". You could achieve the same by just having functions returning structs.

I have replaced a biiiiig nestjs app that exposed graphql with an ash app exposing graphql, and the boilerplate ratio for resolvers etc is bordering on 1:999. Like literally, across a 90 table large application I have maybe 600 lines of "specifically graphql related code" (5-10 lines of code to expose select actions as mutations and queries per resource). As opposed to the nestjs codebase that was using an annotation driven approach and had a gazillion lines of glue code for resolvers and data loading.

Also the authorization logic through the policies is so extremely composable and easy to do when combined with matching on resources it is fantastic. Each resource "owns" its own authorization, so there is no song and dance about figuring out acl from the entry point and then downwards a tree. You just let the resolver resolve its way down the graphql tree or just feed a long ass loader path into Ash.load and each resource is responsible to implement its own policies and you don't have to worry about accidentally leaking data because you access the data from a new entry path that was not locked down because you added a new resolver.

I kept reimplementing the same boring boiler plate every damn time I started a new project and that pain is almost 100% gone.

It is a harsh learning curve for sure, because the one downside of Ash is that you have to do it the "ash way" for stuff to compose as beautifully as it does. Once you really get into the groove making "expression calculations" (basically projections that reach into other resources or columns to make some kind of computed data, but is done in the database layer since you expose it as an expression) that you can compose and make depend on eachother etc it becomes so incredibly fast to make new functionality.

You think about one and one thing and let the framework take care of how to compose the loading and usage of what you make. A much simpler model than "making it yourself" in ecto which I have been doing for 10 years prior.
by zelphirkalt | 2025-05-14 11:33:50+00:00
I still feel like the point is useless, because at the end of the day, if some normal person went ahead and did the same thing the tech giant did, they would long be moved to a less comfortable new home, that has high security against breaking in. At the end of the day, the situation now is, that some are more equal than others, and it is unacceptable, yet, due to the mountains of (also unethically acquired) cash they have, they can get away with something a normal person cannot. Even the law might be bent to their will, because if suing them fails, it creates precedence.

If we end up saying it is not illegal, then I demand, that it will not be illegal for everyone. No double standards please. Let us all launder copyrighted material this way, labeling it "AI".
by robertlagrant | 2025-05-14 11:34:10+00:00
I'm not saying it's a crime. I'm saying it's not your boss demanding you work only for them.

If you do have that arrangement, it's because you signed a contract to agree to those terms. The CEO that is the CEO of multiple companies (rare, but it definitely happens) signed a contract to agree to those terms, and is no doubt bound by other terms.
by int_19h | 2025-05-14 11:35:01+00:00
You wrote:

> socialism as a form of economy where all means of production are in the hand of the state

whereas even the quote says something quite different:

> individual possessions should become the common property of all, to be administered by the State or by municipal bodies

This latter part is a very big distinction. Anarchists are by definition anti-state, but not necessarily anti-governance.

Of course, the other point is that this is simply the parade of horribles intended to smear the ideology. Quite similar to how today in US whenever someone says "socialism", you can virtually guarantee that someone will respond with "... but gulags!", as if that naturally followed.

> In the last years I have seen more and more posters here, especially American, abuse the word "socialism" to describe anything implementing social institutions or worker's rights, even calling very capitalist countries like Sweden "socialist". For a person who has experienced first hand what actual socialism is like, this gets old very fast.

FWIW I was born in the USSR so I know full well what that kind of socialism means. I also know that it's not the only kind of socialism possible - indeed, it was kinda late to the party. It just happened to be the one that got into power somewhere first because it was the only one brutal enough to overcome the violent state suppression of all socialist thought, so the kind of society it resulted in shouldn't be surprising.

Sweden is, of course, not socialist in any meaningful sense. The classic, and still the most accurate, definition of socialism is the lack of private property on the means of production (i.e. capital) at scale. Note that it doesn't necessarily mean state ownership, or even common ownership - e.g. worker coops are socialist but any given coop is only owned by its member-workers, not by everyone in its area.
by borromakot | 2025-05-14 11:35:02+00:00
I appreciate the perspective. Honestly for us it was just something that our whole user base was mega excited about, and so we made a big deal about it. It seemed like a positive that there was a book available (especially given that young-ish frameworks benefit from some level of legitimacy, given that it's a Prag Prog book etc.). I never even considered that it would rub people the wrong way honestly.

I think I'll probably keep it front and center for now, given that the book will be launched out of beta in the near future, but I can see how it might give the wrong idea, and will reconsider its placement going forward
by incomingpain | 2025-05-14 11:35:03+00:00
In canada, aged 20-29, 46% were still living with their parents. If you live in a big city like toronto, the number is way higher.

Kids living at home aren't saying "I still live in my parent's basement"

"oh, lets have a baby!" this really is the depth of the issue. Confidence isn't going to have you change this answer.
by redeux | 2025-05-14 11:35:16+00:00
> Microsoft tested its various Start menu designs with more than 300 Windows 11 fans and even co-creation calls with select fans. “We watched eye-tracking heat maps swirl, counted scroll wheels, and listened for ’oh!‘s of delight to know where we were hitting the mark,” says the design team.

I’m sorry but there’s no way anyone was giving “oh’s of delight” at the windows 11 start menu. I built a gaming PC with my son that uses windows 11, and after using only Linux and MacOS for years it really was disappointing to see just how poorly Windows performs. The start menu isn’t the worst thing about the platform, but it certainly isn’t eliciting delight.
Ask HN: How do you use the knowledge gained in a day?
by mdoliwa | 2025-05-14 11:36:28+00:00
I'm paraphrasing yesterday's Ask HN post: https://news.ycombinator.com/item?id=43976045

Every time I see posts like this, I feel like I should take more notes. I do write some down, but I rarely use them afterward.

I'm curious, what do you actually do with your notes? How do they help you in real life?
by parisidau | 2025-05-14 11:36:37+00:00
I can answer in our case: as an Australian business that receives a lot of USD, precious few options for keeping that money in USD _and_ having it accessible via a debit card exist. This is one of them. Typically, we don't let much money sit in the Wise account, because as you rightly say, their terms are onerous as hell.
by robertlagrant | 2025-05-14 11:36:51+00:00
No one's worshipping anything in this scenario. The company is "worshipping" the document by paying you on time the amount agreed, and abiding by everything else it says, and the employee is "worshipping" the document by doing the same.

Living your life the way you want presumably doesn't include you wanting other people breaking their obligations to you. Why do you want to do it to them?
by tw04 | 2025-05-14 11:37:14+00:00
This is the thing that bummed me out the most about Microsoft exiting the phone market.

I know Windows isn’t super popular around here, but the idea of carrying one device that I can just dock to work on always intrigued me.

There’s just no way this is taking off with any significant market share in the business world anytime soon being android only, and Apple will never adopt it because they want you to buy 3 different devices. Such a great concept, and with the performance of mobile chips getting so good, very viable.
by sbuttgereit | 2025-05-14 11:37:28+00:00
I've got to be honest. The comment you're replying to is spot on.

The headline, "Model your domain, derive the rest" is fine by itself. But the paragraph underneath is just dismissible drivel; sure, I could click through the links to more detail, but you've not given me a reason to do so... you've not set the hook. Once I did click through the links, I'm either in the documentation, which is way too much, or at YouTube, etc. The opening paragraph doesn't give me enough reason to click through the links, and if I do I'm given what feels like a firehose.

I appreciate that's pretty harsh assessment of your landing page, but that's exactly how it strikes me and I think you need to hear it if your goal is really to capture audience. That landing page should give me the gist of what you do, several short paragraphs outlining the higher level features... I dunno, call them "selling points"... something that can give me cause to care enough to dig into some details. Once I care, then sure... I'll dive into the docs or watch a video.

As for the book ad other comments talk about: it's fine. I would expect that people that know what Ash Framework is also come to the page and having that out front isn't a problem and speaks to the existing community.

Personally, I already know what Ash Framework is, so I know you have some good selling points that could be summarized and that would be of interest to people. You just need to get them out front in as pithy a way as possible.
by cookiengineer | 2025-05-14 11:37:30+00:00
I think what interests me the most about this is what exactly is the cause of the liability here, assuming that the product name and company entity wasn't sold off to the current owner.

Is it the customer database?

Is it the IP / domain of the server?

Is it the website that promised it and hosted the contract?

Is it the ownership of the app code rights?

Because if you think more about it, there is some potential gap here in copyleft licenses which might need to be fixed to protect projects against companies abusing this methodology.

Should we tie liabilities to contracts therefore to customer data instead of apps and codes of apps? Is this a glitch in the democratic law that needs to be fixed by the legislatives?

In European law liabilities are tied to the legal entities, meaning that there is a transitioning phase of 5 years of the liquidation process until an entity can be sold off by the liquidator, and within that time frame customers must file their complaints/liabilities against the legal entity if e.g. they want their money back. That is unless a judicative / court decides otherwise and puts responsibility onto the owners if there is illegal ownership behavior (e.g. fraud) that was provable.
by pjmlp | 2025-05-14 11:37:46+00:00
Partially, it still has lots of issues that were never fixed.

https://chromeos.dev/en/linux

https://www.chromium.org/chromium-os/chrome-os-systems-suppo...

https://www.chromium.org/chromium-os/developer-library/guide...

Note specially the parts of WIP, missing features, to be yet done, and so on.
by bArray | 2025-05-14 11:38:02+00:00
We are talking about an MCU, not a CPU :)

I think once we start talking about GPU, MMU, USB, display, etc, we're getting towards a CPU of sorts.

Speaking of a low-end CPU, I want to test out the RV1103 Rockchip, those crazy little chips are running Linux apparently [1], and even able to run Python [2]. Depending on power draw, a Linux-based smart watch could be on the horizon.

[1] https://www.luckfox.com/EN-Luckfox-Pico

[2] https://wiki.luckfox.com/Luckfox-Pico/Luckfox-Pico-SDK
by jamalaramala | 2025-05-14 11:38:38+00:00
Blender had moderate success when it was closed source, but not enough to pay its development, so it was going to die.

After its creator raised €100,000 to release it under the GPL, Blender became the leading open-source 3D tool it is today.

And they make enough money from recurring donations, service subscriptions, merchandise, conferences and trainings.
by trealira | 2025-05-14 11:38:43+00:00
A lot of people are already being "programmed" to be Nazis via existing media. I doubt a hypothetical chatbot that does the opposite of this one could do any better than existing celebrities and influencers peddling such lies and propaganda. On the other hand, no one who's a Nazi is being deprogrammed of it by anyone, unless their media consumption is simply cut off for a long time. It's not a symmetric situation. If that's really your only concern, I wouldn't worry about it.
by wkat4242 | 2025-05-14 11:38:55+00:00
This is the problem. VR/AR can add value but you really have to tailor the experience to it. And it has to be a suitable usecase.

If you just lift over what you have in 2D it becomes only more painful. But this is what most people do. Also many platforms, like Microsoft Mesh. Yes, it's cool that you can join a teams meeting in VR. But until they add something that actually takes advantage of being in VR, all it does is add more friction. Roasting marshmallows and other cutesy minigames does not add any value whatsoever.
by lucozade | 2025-05-14 11:39:15+00:00
> _who_ is the owner. Is it a stack frame?

The owned memory may be on a stack frame or it may be heap memory. It could even be in the memory mapped binary.

> Why would a stack frame want to move ownership to its callee

Because it wants to hand full responsibility to some other part of the program. Let's say you have allocated some memory on the heap and handed a reference to a callee then the callee returned to you. Did they free the memory? Did they hand the reference to another thread? Did they hand the reference to a library where you have no access to the code? Because the answer to those questions will determine if you are safe to continue using the reference you have. Including, but not limited to, whether you are safe to free the memory.

If you hand ownership to the callee, you simply don't care about any of that because you can't use your reference to the object after the callee returns. And the compiler enforces that. Now the callee could, in theory give you back ownership of the same memory but, if it does, you know that it didn't destroy etc that data otherwise it couldn't give it you back. And, again, the compiler is enforcing all that.

> Why can mutable reference be only handed out once?

Let's say you have 2 references to arrays of some type T and you want to copy from one array to the other. Will it do what you expect? It probably will if they are distinct but what if they overlap? memcpy has this issue and "solves" it by making overlapped copies undefined. With a single mutable reference system, it's not possible to get that scenario because, if there were 2 overlapping references, you couldn't write to either of them. And if you could write to one, then the other has to be a reference (mutable or not) to some other object.

There are also optimisation opportunities if you know 2 objects are distinct. That's why C added the restrict keyword.

> If I'm only using a single thread

If you're just knocking up small scripts or whatever then a lot of this is overkill. But if you're writing libraries, large applications, multi-dev systems etc then you may be single threaded but who's confirming that for every piece of the system at all times? People are generally really rubbish at that sort of long range thinking. That's where these more automated approaches shine.

> hide information...Why, from whom?

The main reason is that you want to expose a specific contract to the rest of the system. It may be, for example, that you have to maintain invariants eg double entry book-keeping or that the sides of a square are the same length. Alternatively, you may want to specify a high level algorithm eg matrix inversion, but want it to work for lots of varieties of matrix implementation eg sparse, square. In these cases, you want your consumer to be able to use your objects, with a standard interface, without them knowing, or caring, about the detail. In other words you're hiding the implementation detail behind the interface.
by didgeoridoo | 2025-05-14 11:39:55+00:00
Confidently posting links without reading or understanding them is worst of all. Your source does not remotely contradict my point. This says that, while we harmlessly consume incidental fluorine from the environment all the time, there is no recommended or minimum intake. That’s because it is not an essential nutrient. Its only use mentioned here is the prevention of dental caries, and then only when applied topically.

There is no such thing as “enough” consumed fluorine. Consuming fluorine bypasses your teeth, the only place it does any good. Enamel is not generated with fluorine in it; it must be applied afterward for anticavity benefits.
by 0x000xca0xfe | 2025-05-14 11:40:39+00:00
C is elegant because as an extremely powerful programming language used to create an uncountable number of high-profile projects it's simple enough that I feel optimistic I could write a C compiler myself if it was really necessary.

It may be impractical for some tasks but the power:complexity rate is very impressive. Lua feels similar in that regard.