skysight-inc/HackerNews huggingface dataset:
There's several solutions for comments, as documented here: https://darekkay.com/blog/static-site-comments/
Automation makes the happy path faster but almost always makes the unhappy paths much, much slower. So, if you wind up with too many unhappy path cases, your automation made things worse, not better.
I created a backend for a mobile game once. It was one of those typical mobile "get hooked" clones, with loot boxes, hard & soft currencies, the works. It was created to promote a sports club, one of the really big ones. I was mainly just programming other people's ideas (if I wanted to write a game it certainly wouldn't be something like that), but they needed help parameterizing loot chances and stuff like that, and I eagerly helped - I wrote mathematical formulas that fitted their descriptions & presented it to them and it was quite fun as opposed to the usual business software "data goes from A to B" boring crap.

At a certain point we had a tournament. The prize was surprisingly rich, the club gave something quite rare and unique. So people really played! We would watch on those fancy Grafana charts I programmed how people would play night and day. I wrote an SQL query that would track the habits of the top 3 players specifically and we would comment on the few breaks in their gaming spree: "food", "power nap", "ahah, toilet break!". For an entire week. They slept an hour here and an hour there, otherwise they played. I sure hope the poor bastard who won really got their memorabilia.

The game stopped soon after that, the club decided to ditch it (for whatever reason, my employer said it was club politics but who knows). I was a bit surprised at myself that I didn't feel any really strong emotions about it.. I mean sure, the worst of it was when they were going for a real prize, but anyhow I never had a true "Oh no what have I done" moment, even before I learned the app would be cancelled. Not an emotional one anyway, rationally I do realize that entire mechanics and the tournament you could win by staking all your free time is not great to say the least.
This blogpost is bitter and weird. Cloudflare is announcing an improvement in their platform, and Fastly is responding with a weird flex about losing their competitive advantage?

As a customer, I don't really care which vendor had the edge 10 years ago, I just want to compare features today. Does Fastly support WebSockets yet? This just highlights how little Fastly is doing recently.
Whether the assailant intended to cause death is unknowable.
I stayed in Budapest Hungary last year and a bunch of the buildings had warnings they were testing the water for lead contamination. So this is apparently an issue in Europe as well.
Car companies are sending data to insurance companies. Previously discussed: https://news.ycombinator.com/item?id=40169341
From the Ideas Page:

> The model has 4 (2²) possible symbols and 8 (2³) possible states, so in total 32 possible symbol-state combinations. Each instruction has 7 bits (3 for the state, 2 for the symbol, 1 for moving left/right and 1 for stopping)

And the tape is unlimited of course ;)
Discussing the right levels of abstraction is a huge thing in computational biology. At what level is 'the algorithm' of natural computation implemented?
Technical details here https://dontvacuum.me/talks/HITCON2024/HITCON-CMT-2024_Ecova...
Unions have their place, but I would argue that any heavy concentration of power (this obviously also applies to corporations) is bad. There absolutely no reason an entity should exist that can on a whim shut down the entire east coast/gulf shipping industry.
Start sinking the vessels intentionally and they'll stop coming. You might save lives in the long run.
https://tomlehrersongs.com/wernher-von-braun/ is perhaps a better link.
Before anyone else does this... make sure people actually use it enough to invest the time and money into it.

I mean for Apple / Android / Windows? app store reviews you often don't get much choice (not until EU laws are fully complied with anyway), as I've found out the hard way over the years developing apps.
I wonder if lack of competition is to blame for that.

When you look at Europe each sea faring nation has at least one modern port that can facilitate the largest container ships.
And Unions generally don't operate across borders so a strike can be broken by diverting traffic.
I remember my Dad raving about the good quality and cheap price of a Japanese dial micrometer he had bought in the 1970s when Japanese products had a poor reputation in general in the west rather like everything Temu sells has now.
I think a lot about how Super Mario 64 is one of, if not the most studied program out there. So many people have ripped that game apart down to assembly and studied every facet of it looking for glitches and speed running strategies. It's honestly super impressive
Sure, agreed. I’m just pointing out that the GP quibbles “what about microplastics” without comparing the known levels of lead (ie even extremely small amounts) that are unsafe. And it’s pretty obvious that high levels of lead lead to developmental issues. The same cannot currently be said of microplastics.
There shouldn’t be any issues with customs but as far as security you can bring it in your checked baggage if it is packaged properly and safely.
You ain't wrong.

Lots of ML is heavily influenced by fundamental research done by Physicists (eg. Boltzmann Machines), Linguists (eg. Optimality Theory / Paul Smolensky, Phylogenetic Trees/Stuart Russell+Tandy Warnow), Computational Biologists (eg. Phylogenetic Trees/Stuart Russell+Tandy Warnow), Electrical Engineers (eg. Claude Shannon), etc.

ML (and CS in general) is very interdisciplinary, and it annoys me that a lot of SWEs think they know more than other fields.
There is a great documentary on Netflix called "The Devil Next Door." It covers a similar story.
And Google heavily pushes them to, to the point of (when I last made an android app years ago) automatically adding its libraries to your project every time you open the project, then giving compiler warnings if you use the old ones.
What part flexes and rubs?
An exciting release with my favourite feature of cache reliability. The arrival of this feature motivated me to making AppBundler.jl, which can bundle GUI applications into familiar installers found on major desktop platforms [1]. I will also enjoy using public keyword when working with submodules to keep APIs more organized. This could also allow to show a tree view of the module functions from `public` and `export` statements.

The `[sources]` in Project.toml is useful feature when retrieving projects without a `Manifest.toml` file. A thing I found missing there, is the lack of integration with `Pkg.add` and `Pkg.dev`, where now I need to manually edit the file to keep those things persistent when `Manifest.toml` is not present. Hopefully, that can be improved with future releases.

I did not understand the ScopedValues example utility. The middleware could handle most of those permission controls by being more explicit with methods `handle_admin` and `handle_guest`. Perhaps someone has a better example where it is really useful.

[1]: https://github.com/PeaceFounder/AppBundler.jl
That's fair! The point about shared cross-cutting concerns still applies, but yeah, that's a fair point - thank you for pointing that out!
What you want is Money, currency is a _unit_ type of a Money quantity, just as meter is a unit type of Length.

Money cost = 25M USD;

cost += 12M EUR;

display(cost.to(EUR));
Because we want to plug into GCC, so that we can use the rest of the compiler chain to output to all of the architectures that GCC supports.
As always, I am super proud of the Australian Broadcasting Corporation and their consistent balanced (for the most part) good work.
Is the article a canvas or a document?
Speaking of cab companies/Lyft/Uber, etc now similar to striking unions, those companies have a vested interest to block public transit expansion because it's a direct competitor. It's always been like this; we have to balance things out and not give into regulatory capture.
"these days it's somewhat controversial and sometimes considered undesirable"

I respectfully disagree.

It it fundamentally related to your use-cases, execution times, and design paradigms.

If your team comes from a *nix background, than having dozens of processes interfacing over various pipes/network-sockets/fifo/mem-share is normal. In a cluster environment, having the ability to spin up processes on any host, yet remain functional over middle-ware can be very robust from a maintenance perspective.

A periodic self-restart trigger feature is only a small part of these feature sets.

Containerization on the other hand was necessitated out of poor OS design consistency, and rotten permission handling. It added overhead, complexity, and costs. However, it also solved a very real user requirement of keeping many things operational at the same time.

Daemons are almost certainly still required if you have software that must remain running for >6 months outside a users session. Also, periodic processes do not necessarily have to remain resident in all use cases if that was a concern.

Best of luck, =3
I have a ton of opinions on exceptions too, mostly because I love them.

FWIW you can override the stack trace collecting behaviour of Java exceptions. Not collecting the stack trace makes exceptions really fast and thats actually how Scala is implementing their boundary/break feature. I do kind of wish that Java could backtrack and that the stack trace would only be filled in on RuntimeExceptions that are true panics.

I really feel like Java just needs investment on the language syntax to make checked exceptions good. Things like `try!` or `try?` from Swift would be nice and taking Scala's try { as an expression with case catch blocks would make it really fluent. I think most devs can agree that they want to know what errors can happen, but currently in Java its just a pain to deal with them. Brian Goetz originally had some ideas around evolving the switch construct for this [0] so at least we know making exceptions better is on his radar.

[0] https://openjdk.org/jeps/8323658
Thank you for your insights!

I think it makes sense that this feature would not be planned in your library - as I understand, its goal is to support developers to write better money-related logic, which is sometimes related but different from simulating as accurately as possible.

I just noticed a potential misuse of your API: Transitve relationships: "A" = 2.0000 "B", and "B" = 3.0000 "C", then implicitely, "A" = 6.0000 "C". Can the user now define "A" = 7.0000 "C"?

That would be wrong - but not trivial to prevent, and practically speaking, it is okay I think.

Thank you for your time and for this exchange, wish you good success and fun with kotlin money! :)
Not if the economy collapses before you can collect / spend your pension. I think such an event is inevitable even though it may be a long time away. Pending global conflicts could bring it forward. If you need a pension and don’t get it there isn’t really much you can do about it.
I'm not really sure if I follow your suggestion; what would be done with the camera? Authenticate that a picture is real? I'm not sure how that will be workable? For example, how would I (random internet person) verify a picture from you (also random internet person) is real?
Germans run Uber Long Term Support dialects
Perspectives on R in RAG
The problem with this is that pollster doesn't, by itself, provide a signalling mechanism by which bottom-level futures (such as OS-provided IO primitives) can signal the executor. It isn't a "light-weight replacement" for tokio, tokio does a lot of stuff that pollster simply can't because tokio is a reactor + a runtime, whereas pollster is just a runtime. [This page](https://rust-lang.github.io/async-book/08_ecosystem/00_chapt...) gives some nice details about the difference, and hopefully some sense of the sheer difficult that comes with trying to integrate a default reactor into `std` without it falling well short when it comes to extensibility.
The death threats angle is a complete red herring, considering that other social media absolutely does leave out such posts for even longer than parler did (and very rarely is held accountable for whatever their users are posting, even when it takes literal months to moderate).

But regarding your last paragraph. Sure let's agree that everything you said was right. So what? It still shows that AWS does cut off consumers based on politics. I'm not aware of any legal action against Parler so I don't think they were accused of anything illegal. The fact that you agree with the political reasoning behind the decision does not make it any less political.

Especially since the only time that they ever intervened for something like this was when it happened in the US. It didn't happen during the Arab Spring, or the 2014 Ukrainian revolution, or any other time where people used an AWS hosted platform to coordinate a coup.
Create and test a chatbot for your website without sign-up (up to 10 URLs)
People should stop treating the dom and browser abstraction as golden standard. It's just an abstration that happens to be standardized. Sometimes it makes sense to follow the standard, sometimes "the standard" is just too shitty to follow.
I think the GP was suggesting, and imo it's a good idea, that you should first ask them to update your birth date saying you entered it incorrectly. Then you can request deletion again and your ID should be accepted.
Can you show examples of developers successfully striking? It's not comparable. Even in unsuccessful strikes, wages haven't suffered in software.
Next up, check out our vector addition implementation of Hello+World. Spoiler alert, the result is Zalgo
English-speaking programmers still say "octet" for byte sometimes, for example when talking about IP addresses.
SpaceX's next Starship launch–and first catch–could happen this weekend
Ah, facebook then.
So you're describing a bunch of unnecessary things, and stating they make microservices more difficult to debug?

Nobody says you need http, sqs, grpc, and queue (message broker) all in the same system. Nor does anyone say you need to use 4 languages for these things, nor does anyone say you need to only enable observability when there's issues.

Bunch of handwavy "it's complicated" nonsense basically - demonstrating yet again most people don't really understand microservices.

A microservice can be as simple as studying it's inputs and outputs and nothing more. All of which can be observed via tracing, logging or whatever you prefer, either on a sampled-basis, only on errors, or all the time.

Microservices make you rethink almost all of your software engineering assumptions - and some people are just not in the right headspace to make the jump. The biggest change is viewing/treating your codebases like cattle more than pets. Automate everything, fail quickly, stop caring about crashes, keep services as small and focused as possible, stop worrying about multiple supported releases, etc.

It is very different, but that doesn't mean it needs to be complex.

That doesn't mean microservices are the solution to every problem. It does mean, however, it's a solution to more problems than some people are willing to admit and/or take the time to understand.
A deep dive into Solid Queue, a DB-backed queueing system
Trapped in the Matrix
inetd could pass the listening socket to the process. That was the `wait|nowait` field in /etc/inetd.conf. The typical config for TCP used with services like finger was `nowait`, which meant inetd would listen on a socket and spawn a new process for every incoming connection, without waiting for a previously spawned process to exit. But in `wait` mode it would spawn the process when it detected a connection, pass the listening socket (not connected socket) as fd 0, then wait for the server to exit before polling the listening socket again.

inetd was (remains?) a perfectly useful solution in this space. It just maybe needs some love to add some convenience features. Off the top of my head: 1) ability to split /etc/inetd.conf into, e.g., /etc/inetd.conf.d; 2) ability to trigger a restart of a specific service, rather than restarting the entirety of inetd.
Not OP, but IMO the real issue is pretending graphics is still about executing individual draw calls of meshes which map 1-to-1 to visible objects.

It's not true anymore, because you have all sorts of secondary rendering (e.g. shadow maps, or pre-passes), as well as temporal accumulation. These all need their own unique shaders. With meshlets and/or nanite, culling becomes a cross-object issue. With deferred rendering, separate materials require careful set up.

So now the idea that a dev can just bring their own shaders to plug into an existing pipeline kind of falls apart. You need a whole layer of infrastructure on top, be it node graphs, shader closures, etc. And dispatch glue to go along with it.

This is all true even with WebGPU where you don't have to deal with synchronization and mutexes. Just a shit show all around tbh. Rendering APIs have not kept up with rendering techniques. The driver devs just threw up their hands and said "look, it's a nightmare to keep up the facade of old-school GL, so why don't you do it instead".
Its their itch to scratch, and its good to have an independent implementation anyway
The main reason not to drink hot water is that it can be sitting around in a tank for a while, and it isn't held at a temperature which kills all bacteria.
HIPAA doesn't apply to 23&me.
Ask HN: What's the safest, most secure way to store sensitive images/videos
Images/videos that you don’t want anyone else to see beside you and the subject of the images
We're also able to do many kilowatts worth of digital inference equivalent processing, instantaneously, for a couple watts at most in cost.
Ask HN: What's your go to frontend stack for rapid MVP development?
Hey!

We’ve enjoyed building products from scratch for a good amount of time now and, in terms of web frontend, we’ve gone through the classical path from no-framework -> angular 1 -> react -> svelte with a bunch of component libraries (most recently Tailwind UI)

For max iteration speed; what frontend stack would you pick today to build an MVP which later can be iterated quickly on while searching for PMF?

To be clear: I understand accuracy is as crucial as speed. This question is about unlocking iteration speed.

Scenario:
- Building MVP, then iterating rapidly to PMF
- Mostly UI for CRUD
- Need standard UI components with some flexibility. A Tailwind based component lib is preferred.
- Fast iteration is crucial
- Okay with some tech debt if it significantly speeds up development

Questions:
1. Fastest framework to get from zero to PMF? (React/Vue/Svelte/other?)
2. Component library for quick development and iteration?
3. Clever shortcuts you took that didn't hurt too much when scaling? Vercel?
4. Speed traps you'd warn others about?
Do you argue against layered security in your day job? I'm making a case for reducing blast radius in the event of a breach.

Of course rodent issues are related to PEX: now if a rodent ever does get in, the damage is multiplied when they eat your delicious PEX water pipes and you get a flood in addition to all the other horrors. Not so with metal piping.

It would be nice if all homes on earth could be completely 100% rodent proof forever. And it would be nice if attackers never breached computer systems. But some of us have to live in a world where such things happen.
“Game engine” is supposed to simply mean, the parts of the game code that aren't the main game logic—the stuff that handles asset loading, entity management, input detection, rendering, sound playback—that sort of thing. It could be used to refer to Unreal Engine… or it could just mean the simple, minimal homemade tech stack that you built your game upon. Or anything in-between.

But you hit the nail on the head—it's definitely one of those terms that has been warped and downright mythologized in recent years, with the rise of free-to-download general-purpose GUI-editor “game engines”, and their ensuing popularity.
Yes. Also: that's common knowledge now, but probably wasn't in 1959 (certainly the distinction wasn't apparent in newspaper articles of the time). I don't think it was crazy for OPRF to assume, regardless of any documentation Kulle provided when he was hired, that he'd been vetted at immigration, and wasn't a war criminal. Of course, it was crazy for administrators to come to his defense in 1983 when the details were flushed out! But the village as a whole appears to have wanted him gone.
You forgot the evils of pinball and comic books.
Check it out here: https://www.youtube.com/watch?v=tJETffg0kFc&t=2s
Yes, though there's no "just" about it in many cases. If you kick the client out at an early enough stage in processing that the shed requests are only 1% as costly, then 3x retries aren't going to be able to cause a significant CPU spike. I would have liked to see how the simulation behaved, though, because I don't have empirical evidence for exactly what the traffic would look like.

You can also configure your client to stop retrying if it sees a load shedding error. That won't protect you against traffic that overwhelms the load shedder, but it's pretty effective against an innocently misbehaving client.
Footnote in the article provides the following explanation:
"The standard imposes this limitation because the implementation may need to add default function parameters, template default parameters, or overloads in order to accomplish the various requirements of the standard."
I wonder if we'll reach the physical nanostructure wall of silicon long before that, and then all progress will have to be algorithmic efficiency gains. The era of Metal Muscle will end and we will return to the era of smart people pondering in coffee shops.
Thank you for the interview link.
At the risk of repeating myself: wanting to improve your chances at making a decent living (i.e. being hired, having a place to live, etc.) is not the same as striving to become part of the power apparatus, despite the fact that both benefit from networking.
Extreme Weather Gives Video Games a Powerful Adversary
To be fair, Blue Scuti also used a modified Tetris ROM to set his record.
These all look reasonable to me.

I especially go back and forth on attribute inheritance (it can be disabled via the htmx.config.disableInheritance option)

Three of the criticisms boil down to the fact that client-side state doesn't always play well w/htmx swaps (especially the simple ones) which is absolutely true.

And events can get crazy. They are powerful, but crazy and at times hard to debug. Such is event-driven life.

The one thing I don't agree with is the default queuing mode: it is not to cancel an existing request and replace it. Instead it is to keep the current request in flight and queue one and only one additional request. I'd need to sit down w/them to see if they were misinterpreting something, using the hx-sync attribute to implement the behavior they mention, or if there is a bug.

I would also like to take this opportunity to market our mug for people who don't like htmx:

https://swag.htmx.org/products/htmx-sucks-mug
https://www.nytimes.com/2024/10/04/arts/extreme-weather-stor...
I suspect we'll only find out when WP Engine makes them explain it all out in court.

WP Engine, the hero we didn't even know we needed. /s