skysight-inc/HackerNews huggingface dataset:
I needed a computer to sit in a corner and run some application, performance irrelevant. I had a Mac Mini that Apple calls "obsolete" and doesn't support, but it's really a PC so I put Linux on it. An old iPhone would have used less power, but "vertical integration" means when the vendor stops supporting it neither can anyone else. Vertical integration is not the solution, it's the problem.

The hardware vendors are providing the firmware instead of a spec that allows you to write your own. Then you're stuck using their software to use their hardware, even if it's awful or they stop updating it.

It's perfectly fine to provide a reference implementation, but that's not a substitute for hardware documentation sufficient to let you make your own if you don't want the vertical integration.

Because the party with the economic incentive to make it better is the end user. Not all of them have the capacity to do that, but only one of them needs to and you have better code available to the whole world.
I don't get the problem. They are going to tune their search engine to return their version of these recordings? Who cares? They're not going to be able to do that with popular music. Only public domain stuff.
It would be. But like all other material science publications: paper is cheap and easy to manipulate, a lot can happen between the laboratory and the product shelf that impact those KPIs. The energy density is useless until factors such as packaging and thermal management are taken into account. Those can eat up any perceived advantage in hurry.

So I'm not going to get excited until there is an actual product which may well be many years away. So there is nothing to 'move over' just yet.
It's not perpetuating stereotypes, it's showing that these stereotypes exist in society. Similar to how a comedian might point out the absurdity of racism by writing and delivering a joke about race. Or how a child might ask why people of certain skin tones tend to have different hair styles as well. Neither the child nor the comedian are definitely racist, but they are making observations that may not be considered politically correct.
Congrats on a great idea well executed!

In my mind, the gold standard for engaging summaries is Seeking Alpha. As a random example, see https://seekingalpha.com/article/4633758-sell-amazon-before-...

If you could train the model to come up with well structured bullet points, the summaries would be amenable to scanning before committing to fully engage. This is just an idea, I am not sure what fraction of your readers would prefer bullet points.
It's just another salt I suppose, anything soluble ends up getting washed in there. The question is, "why is the water on land not salty?" answer: it all got washed into the sea. The water keeps going in a cycle, evaporating and raining, but the salt stays in the sea.
More discussion later over here: https://news.ycombinator.com/item?id=37435454
Green Shades – tensile structures covered in vegetation
Seems they both have similar plans: serverless hosting, continuous integration, etc. etc.

All valid ideas. But the involvement of VCs makes me wonder what kind of scale they're going to be expected to achieve and what will happen if they don't.
Code to calculate size of preallocated array is incorrect. Size ends up too small or underflows.

Buffer is reused across calls. Buffer is actually mapped across processes and thus page-aligned. Code to check how much space is needed checks number of pages versus actual number of bytes, and fails to clear leftover data correctly.

Code receives RGBA buffer but expects some other encoding. Accidentally reads out of bounds as a result.

You can definitely say “oh these are stupid and I wouldn’t screw this up” but people do and that’s what really matters.
> If there is a kind of “ethical ads” that’s as close as it gets.

A news paper ad? A builtin board? I think advertisements that hijack your attention are always unethical. You should have to look for ads to see them.
I highly recommend watching the Indian movie: The great Indian kitchen. It does really offer a different perspective to anyone who believes that a housewife's job is better than a corporate drone's :)
> But then rust also has channels. When you read about it, it talks about "messages", which to me means little objects. Like a few bytes little. This is the solution, pretty much everything I write now is just a few tasks that service some channels. They look at what's arrived and if there's something to output, they will put a message on the appropriate channel for another task to deal with. No sharing objects or anything. If there's a large object that more than one task needs, either you put it in a task that sends messages containing the relevant query result, or you let each task construct its own copy from the stream of messages.

The dream of Smalltalk and true OOP is still alive.
Virtual threads or green threads, etc., are all names for the same thing: stackful coroutines. I would say yes! If your language/platform/runtime supports them, that should definitely be your starting point.
https://www.youtube.com/results?search_query=procreate
> Which is weird since apple did that like three years ago? Just no one cared much since it was Safari.

Because Apple is not running competing ad network. Their only ad network is running on their own app store. Apple does not get any competitive benefits from 3p cookie deprecation for its ad networks.

> The linked document is about _replacing_ 3pc,not simply eliminating them, which seems a crucial distinction.

I don't know why you're getting the impression that the doc is only about replacing 3pc, but Google which tried to remove 3p cookies drew significant attentions from competing ad network and eventually antitrust regulatories. I know this since some of my work closely depends on this timeline.
> If both partners work then [...] more vehicles needed

I was thinking about the logistics of this the other day since one of our cars is down, I'm WFH with a SAHM and I hate the expense of having to maintain two cars. Maybe this is the time to downgrade to one (which will be followed by mandatory RTO, knowing my luck).

Being a housewife is Work. It's a full-time unpaid job that frequently involves bringing things to the home from outside of it. She's not my dog; if I took our only car to work, my wife doesn't just sit around awaiting my return or stop needing to go places. The kids still need to be brought to/from school (in California, this is at irregular times on irregular days for maximum exclusion). Sometimes they need to go to the doctor. Sometimes she needs to go to the doctor. Groceries need procurement.

She could take the bus, maybe. Then it's a discussion of which partner's role is critical enough to necessitate exclusive use of the car. Both sides are valid. Being a trailblazer doesn't mean shit if nobody's maintaining your path.

In past instances, I've left the car to her and just taken Uber to ad-hoc onsite work, but this is very unreliable (and expensive for short hops).

If you live in an American suburb, you need multiple vehicles regardless of employment status.
Anyone have a good resource on monorepo design and workflow? I find myself keeping supporting projects up to date in their own branch and then cherrypicking commits from random other projects' dev branches, where random commits happen to improve a non-focused branch. But the commit history in my main dev branch gets muddied with these random merge commits (merging changes that have improved the secondary projects).

In other words, merge commits aren't necessarily indicative of critical chronological moments. But they muddy up a nice chronology of development commits.

I could use some ideas on the architecture of monorepos...
This is the same woman who probably taught your SO not to take candy from strangers. I don't think you need to be engaged in social media from a young age to tune your BS detector.

On this specific video, which demonizes democrats as scary satanists, do keep in mind that conservatives have learned to focus on fear based messaging: https://slate.com/technology/2015/10/conservative-politician...

Also on that note, I do think education (especially humanities and social science) plays a role in being able to tell the difference between something being discussed in good faith and complete hokum, so it shouldn't come as a surprise that conservatives are trying to lower the quality of education Americans get as well: https://newrepublic.com/article/167375/republican-plan-devas...

This is part of a cycle that keeps Americans undereducated to make it easier to scare them into voting R.
I have found myself using it less and less because the fun of using it for goofy stuff has worn off and it still hallucinates far too much to be used for anything serious.
There’s the concept of ensuring a family wage, rather than an individual’s own living wage.
Yep, that’s what I said.
> Yes, async is effectively a much harder version of Rust, and it's regrettable how it's been shoved down the throats of everyone, while only 1% of projects using it really need it.

Yes. I just noticed that Tokio was pulled into my program as a dependency. Again. It's not being used, but I'm using a crate which has a function I'm not using which imports reqwest, which imports h2, which imports tokio.
See Smart TVs.
> Burnout's root cause is a mutually-reinforcing school/work/personal environment known as "total work

Personally, I would think the solution to this type of millennial burnout is having the economic stability and workplace protections to _not_ have to always be worrying about school and work.

Also, it’s baffling to me that this is treated like a choice everyone is making? Like, what if you need multiple incomes to afford rent, or what if you’re single???
Isn't pretty similar information available from Levels.FYI or eg Glassdoor? This is really bad coverage...
What's the target ICP - mid/late stage enterprises or startups/tinkerers?
Intution is just another way of saying "I like my anecdota and pretend it's statistically significantly better than guessing"
> Billboards still require tracking.

What billboard is tracking individuals?
Yes it is RAM intensive but depends on usage. When my instance is not being used much, it is consuming 1GB. I haven't seen high usage and RAM spikes as I have not published my instance to the world to use.
> (But if you're only firing up a few tasks, why not just use threads? To get a nice wrapper around an I/O event loop?)

To get easier timers, to make cancellation at all possible (how to cancel a sync I/O operation?), and to write composable code.

There are patterns that become simpler in async code and much more complicated in sync code.
> The RS-25 is related to the J-2

How so? Other than sharing a fuel type, and thus surely things learned during J-2 development and operation influenced the RS-25 development and operation, so far as I know the two engines are completely different. Different cycles, different power packs (e.g. turbopump), wildly different packaging, different head pressure, different chamber pressure, throat, etc etc etc. I'm pretty sure that the J-2 did not cool the bell with the fuel, though I could be mistaken. Are the combustion chambers similar? What makes the two engines related, other than the fuel type and of course manufacturer?
Relatedly, I authored a feature request to GitHub about access controls: https://github.com/orgs/community/discussions/66147
I don't think I've ever seen an NTSB report that looked like it would come close to revealing non-public design information or things that would violate ITAR.
Most of the time, that growth is good for us, so we continue to keep that economic system around.
Body of Netflix Engineer Found
:(

Who killed him ?
Same. It's one of the full ultra hyped things I've seen in my life that actually lives up to the hype.
> Why did they not include other companies

AFAIK: the initial stages of the project involved Vercel and Shopify [edit: and Gatsby]. these companies maintain frameworks and hosting solutions for them, which makes them good partners to work on full-stack features like this. notably, the convention ("use client") came about based on early feedback from Shopify.

the reason to work with framework authors first is that RSC requires a high degree of coordination/wiring across client code, server code, and the bundler. React itself only implements a couple of low-level primitives that need to be wired together by something like a framework to actually do anything useful

> expecting all third-party packages, React-related or not, to buy into the "use client" directive

AFAIK: non-react code has no reason to care about this directive. and on the react side, couldn't you make the same complaint about most breaking changes?
Parse.dev open source chat with your database
Hi,
My name is Elie and I built parse.dev (mostly for some projects I was launching) and I decided to opensource the application that I built.
With parse.dev you can simply talk to any database or any API using Swagger.
Hope you like it!
Some earlier posts and discussion:

https://news.ycombinator.com/item?id=37434066

https://news.ycombinator.com/item?id=37435158
The state already tracks users across cars. Not sure what data you think you're protecting.
Django does this too
I really can't even begin to empathize with the author. I find async/await to be significantly more ergonomic then the alternative in almost every use case.

The arguments about Arc fall flat because how else would you safely manage shared references, even in other lower level languages. And so called "modern GCs" still do come with a significant hit in performance; it's not just some "bizarre psyop".

Really the only problem I've run into with Rust's async/await is the fact that there is not much support for composing async tasks in a structured way (i.e. structured programming) and the author doesn't even touch on this issue.

Ultimately the goals and criticism of the author are just downright confusing because at the end he admits that he doesn't actually care for the fact that Rust is design constrained by being a low level language and instead advocates for using Haskell or Go for any application that requires significant concurrency. So to reformulate his argument: we should never use or design into low level languages an ergonomically integrated concurrency runtime because it may have a handful of engineering challenges. When put concisely, their thesis is really quite ridiculous.
I bought a top-of-the-line Samsung tablet a couple years ago to give it a chance. They are not at all comparable to iPads. Android tablets are terrible.
I've been running pgBouncer in large production systems for years (~10k connections to pgbouncer per DB, and 200-500 active connections to postgres). We have so many connections because microservices breed like rabbits in spring once developers make the first one, but I could rant about that in a different post.

We use transaction level sharing. Practically, this means we occasionally see problems when some per-connection state "leaks" from one client to another when someone issues a SQL statement that affects global connection state, and it affects the query of a subsequent client inheriting that state. It's annoying to track down, but given the understanding of behavior, developers generally know how to limit their queries at this point. Some queries aren't appropriate for going through pgbouncer, like cursor based queries, so we just connect directly to the DB for the rare cases where this is needed.

Why so many connections? Say you make a Go based service, which launches one goroutine per request, and your API handlers talk to the DB - the way the sql.dB connection pooling works in Go is that it'll grow its own pool to be large enough to satisfy the working parallelism, and it doesn't yield them for a while. Similar things happen in Java, Scala, etc, and with dozens of services replicated across multiple failure domains, you get a lot of connections.

It's a great tool. It allows you to provision smaller databases and save cost, at the cost of some complexity.
Where are you living that it is that hard? I am the sole breadwinner for our family, have been our whole marriage, and we have 4 little kids and live a fairly comfortable middle class lifestyle.

Although if food keeps going this way we may need to cut back on some things.
It's not the internals that make Git special, it's the fact that GitHub uses it, and all the other developers know it.

I always say people should learn VCS at the same time as their first programming language, it's that important. And GitHub is as close to "the standard" VCS as it gets.

Git cola makes most tasks easy, and the stuff it can't do, can be googled.
> You can also use the TPM + PIN as a sort of Yubikey

That's not zero. In my mind that's the main thing a TPM is really useful for. It's a secure enclave for a private key used for U2F/WebAuthn style attestation. I agree that the threat model not being explicitly discussed is a huge miss. But to that point, a TPM is still useful because it prevents someone who has hacked into my computer from commanding the TPM's authentication factor.

The other useful application is to prevent block device data extraction without knowing the passkey. And the author's argument there hinges on the notion that Microsoft won't patch OS security vulnerabilities that enable key extraction from memory. Which, OK, third-party drivers suck, but Microsoft's effort to patch is also not zero, and the most common (OS+browser/sandbox) threat model requires a chain of vulnerabilities that are hard to come by.
Java GC has a non trivial overhead. I’ve moved workloads from Java to rust and gotten a 30x improvement from lack of GC. Likewise I’ve gotten 10x improvement in Java by preallocating objects and reusing then to avoid GC. (Fucking google and the cult of immutable objects). Guess what, lots of things that “make it harder to introduce bugs” make your shit run a lot slower too.
"Modern Disney" is neat, I wasn't aware of that. Just so you know, The Mouse is much more fierce about protecting their classic properties like Mickey Mouse or Donald Duck, so this doesn't quite demonstrate my point yet.
What is this false dichotomy? Both can be bad, even if one is less bad than the other. It doesn't make either "benign."
A lot of that pain could have been avoided if the language had better primitives for async in the std or in the futures crate. Like a trait that executor must implement and a "default" blocking executor to execute async code from sync.

Right now even building a library that support multiple async runtimes is a PITA, I have done it a couple times. So you end up supporting either just tokio and maybe async-std.
WOW I love
Came to say something similar... Was worried it was SFW to click. "Procreate" as in to reproduce....
When did this site start having ads?
It could be named nodejs-api then.
For reducing workload - robot vacuums/mops, a decent dishwasher that cleans things up the first time, eating out a few times a week, and not having/coddling a pet if you can't handle it are all options to reduce the housework load. Most stores offer really good order pickup. Target is a star, you can just sit in your car and they load it for you.

One of the things I find annoying in American life is how so many bureaucratic things are only open 9-5ish. DMV, Doctor, Banks, Dry Cleaners, any government office etc. Having to shove these things into a lunch break or take time off really adds to stress levels. We did a great job 15-20 years of getting things moved online and out of "business hours" then we seemed to stall into whatever we're at now.
Thanks so much :)

I'll share it as soon as I have access! I'll also post a transcript on my site (charlieholtz.com) soon.
True but those average users might be using chatbots and other services with nice UIs they can understand that are making those API calls behind the scenes. So the average users are indeed using the API, just indirectly.

With so many AI products being launched these days, it could be that the user traffic is still rapidly increasing but just being spread out amongst all the interfaces becoming available.
On the one usage scenario that benefits a PC user, the TPM makes for a really bad yubikey. You can't carry it between computers, you can't back it up, and you are certain to lose it at some point when the computer breaks of gets outdated.

That means it either requires a second protocol for authentication, or that you will lose your accounts with all kinds of services all the time.
Congrats on the launch! I have been following Bun’s journey since the beginning. Excited to make the transition once it’s got more compatibility with our Node tooling (prisma specifically).
The attitude of "I've never heard of this before" has been a common internet troll for at least 25 years. At some point it's not on me to educate you about things that are widely common knowledge, and there's an art to asking for citations without sounding like you're being dismissive, or shifting all of the effort onto the other person.

The top level comment did not achieve this art, but I've seen worse.
Isn't it wild that the only meat-producing industry that hasn't been completely vertically monopolized by the likes of Tyson or Smithfield gets 100% of the online wrath for its greenhouse gas emissions?
Is there a quick summary of the problem somewhere? I haven't worked on frontend stuff in nearly a decade.
It would still be interesting to do that excersice but with more recent movies. I do think the formula works quite well.

As for the Joker I wasn't agreeing with the critics just describing the consensus based on reviews I've heard. To me personally it did feel like it took a bit too much inspiration from the movies it was trying to pay tribute to. When does a homage becomes a copy?

The political angle is irrelevant and I agree with you on that.
Well for one- creating abstractions always comes with a tradeoff, so it's good to have some basic skepticism around them. But Rust embraces them, for better and worse. It equips you to write extremely safe and scalable abstractions, but it's also designed in a way that assumes you're going to use those capabilities (mainly, being really low-level and explicit by default), and so you're going to have a harder time if you avoid them

Another thing, for me, was that I came from mostly writing TypeScript, which is the opposite: the base language is breezy without abstractions, and the type system equips you to strongly-type plain data and language features, so you'll have a great time if you stick to those

But yeah, it's been interesting to see how different the answers to these questions can be in different languages!
Exactly, because something somewhere needs to make one http call, and it's would be impossible if it wasn't done with scalable async executor. /i
Alerts on unauthorised access to Kubernetes secrets
Secrets in Kubernetes as are only encoded, not encrypted by default. Due to this, there is always a concern around unauthorised access to secrets.

This posts explains a step by step guide to receive alerts in case of any unauthorised access to a secret.
Sure, but that requires legislation or executive action.

Apple doing it unilaterally on their platform might invite anti-trust concerns.
on my currently crappy internet on ubuntu 22 i get ~2.65 seconds for bun and ~5.6 seconds for npm for a clean install without caching. so approx 2x as fast as npm.
Hopefully this is an appropriate place to ask this question: I don't know what to do about threads/CPU for a game server project I want to write.

I really want to use TypeScript, as I like the language and I want to use this as a way to learn it better. I'm not expecting to have some super successful game, but the programmer part of my mind is upset at not utilizing all the cores of the machine. So, what do people do? Split up the server into multiple independent running components, or is my choice really to just use another language?
Pi availability has been improving steadily since the beginning of the year.