MurphyA/hacker-news huggingface dataset:
by mrkeen | 2025-10-16 15:46:35+00:00
All of this!

"Pure functional" isn't a style choice. The judges won't hold up big placards with 10 on them because you executed your business logic in style.

It's a contract that your code will give the same output given the same input. The contract goes both ways: your ability to supply a caller with functional code is made easier by your callees supplying you with functional code.

Someone decides that that's draconian and says "what's the worse that can happen?" and starts mutating in a library dependency. Well now your backtracking parser may or may not be able to backtrack. Your transactional code may or may not be able to be rolled back. Your multi-threaded code may or may not be free of races. `true || f()` no longer means the same thing as `true`. You might need to start scaffolding all your unit tests with @Before and @After to setup and teardown state, and give up running them in parallel.

Maybe you really, really, really need to fire the missiles at the bottom of the call chain. Fine, just mark that method as 'red' so I get a compiler error when I try to serve up 'blue' code to my callers.

As long as you're showing off the syntax (matter of taste) on blog posts you might as well get some mileage out of the semantics (guarantees).
by conductr | 2025-10-16 15:46:38+00:00
So maybe it's not BT, that was only an example theory. It also doesn't need to be always running, so could be harder to track. What if it turns out it's just some high pitch inaudible sound using morse code... I could go on but I'm not trying to crack the case - my point is that things like this that you assert don't exist, often do to turn out to exist on a long enough timescale. I remember reading a lot of tin foil hat theories on various things that some people asserted were illegal or simply impossible; then a decade later Snowden proved the theories right. It seems like these things happen regularly these days.
by Yizahi | 2025-10-16 15:46:44+00:00
The only people who can afford daily taxi, twice a day, are already rich. Those are the people who can afford any private car parking price near the office, or most likely will have a spot reserved included in their high paying job.

I do agree that this fleet will slightly alleviate parking issue for people sporadically taking cars, not regularly. But at the cost of more congestion on the roads, especially in the already congested city centers, since that will be overwhelming majority of trip start or end points.
by cultofmetatron | 2025-10-16 15:46:52+00:00
> Oban is great, but for most cases you don't need it.

7 years in on an elixir startup that has well over a thousand active paid accounts using our system every day to run critical businesses. I have to politely disagree.

USE OBAN from day one for any kind of background jobs. do not trust genservers. they lose their state if a pod goes. There's no retry logic built in.

> Start there and only use Oban if there's some form of consistency/resumability guarantee that you need.

oban is easy enough to integrate. it takes like 10 min of your time and you get a LOT out of the box. use genservers if you're running ephemeral servers but if you are creating background tasks, absolutely use oban for anything you plan to put on production.

Oban is such an easy value proposition to justify. consider it as important to learn as core phoenix
by jraph | 2025-10-16 15:46:54+00:00
> So do you also see what I meant about both permissive and copyleft licenses giving up some freedoms? You can't have it all.

Not a fan of the framing but I get your point (of view).

> For ongoing freedom, If I was choosing between plain MIT and a GPL clone that bans competiting companies but reverts to pure GPL after a couple years, I would pick the latter.

Reasonable. I would find the 2 years delay unbearable and pick MIT, but I wouldn't enjoy doing so. It's fortunate I don't have to pick :-)
by pron | 2025-10-16 15:46:55+00:00
> It means that it does the same JIT optimization tricks that Hotspot performs, escape analysis, devirtualization, inlining method calls, removing marshaling layers when calling into native code, PGO feedback,....

It has rather recently started using most (or perhaps all) of the same techniques; it does not actually perform all the same optimisations. C2 is still significantly more advanced. Of course, some optimisations are more difficult in C#, as its "low level" features expose more implementation details, giving the compiler less freedom.

> It is kind of interesting how after all these years, the solution is going to be similar in spirit to what Eiffel expanded types were already offering in 1986.

I don't have time to compare the details (and I don't work on Valhalla), but it doesn't seem to me to be the same thing. In Eiffel, the class says whether or not it's expanded. In Java, the compiler decides, as an optimisation, whether to inline or box different object instances (on a per-object, not per-class basis). It's just that classes with certain characteristics give the compiler more freedom to inline in more cases.

Think about it this way: In Java 8, Integer and int are two different types with very different behaviours, albeit with an autoboxing relationship. You can't synchronize on an int instance or assign null to an int variable; equality comparisons on Integer compare object identity, not numeric value. We'll gradually turn Integer and int into effectively the same type (with two names, for historical reasons), and turn the decision of whether a particular instance is inlined or not up to the compiler, as an optimisation decision. It's not that autoboxing will expand to user defined types, but rather it will become nonexistent.

But generally, almost anything we do in Java is something that's been done (more or less) somewhere else a while ago, because we like to avoid ideas that have not been tested. Basically, for X to be considered for Java, there must exist some language that tried X in 1986. It's just that it's not always the same language.
by brokegrammer | 2025-10-16 15:47:04+00:00
> TO be fair there are lots of other things that require a response from an API before responding to the request and therefore async reduces resource usage over threads or multi-process.

Agreed. However, these are rare and many people have been abusing asynchronous views instead of delegating the task to a background worker when multiple external requests are required. Showing a spinner while polling a synchronous view is dead simple to implement and more resilient against unexpected outages.
by just6979 | 2025-10-16 15:47:17+00:00
That's just because they're using a different scheme to fund development. SQLite has its paid support and consortium, while Turso is leaning on cloud hosting and the paid support that comes with that. Both can still be used standalone and unsupported, completely for free.

Turso is arguably positioned slightly better as a standalone product seeing as it's using a more traditional open source "bazaar" model, as opposed to SQLite's source available "cathedral" model.
by adastra22 | 2025-10-16 15:47:30+00:00
Yes, I can perceive that latency, if I am actively looking for it. No, it has absolutely no effect whatsoever on my ability to work. The latency is far, far below what could possibly affect neural feedback loops, even on the slowest editors. And it doesn’t bother me in the slightest.

Low-dpi font rendering also isn’t an issue for me, unless it is so bad as to be illegible (which no modern system is).

We really do perceive things differently.
by pjc50 | 2025-10-16 15:47:40+00:00
Leaving aside the question of automation (does HAL 9000 get to push the button?), there really isn't any alternative. The mission as a whole is fighting the Poisson distribution of encountering random objects in space. The probability of hitting one is very low but not zero. Unless the system is magnetic-ramjet powered, the fuel is finite. Ultimately the choice is between stopping at your predetermined destination or waiting until a rock turns your entire world into a sparse cloud of floating debris. It's like the "what do we do if Earth gets hit by a meteor" question but much, much more acute.
by nnwright | 2025-10-16 15:48:15+00:00
Having used Whatsapp for the majority of my messaging the last decade or so, every time I'm forced to use iMessage for communicating with family I can't help but think it's absolutely a garbage interface. Buggy, slow, difficult to really get anything done effectively. Threaded messages is a nightmare. I really can't wrap my head around how anyone prefers using this over literally anything else.
by FeepingCreature | 2025-10-16 15:48:16+00:00
If usability tickets are closed because the company doesn't want to bother, then maybe these gears deserve to have sand put in them.

I generally approve of subversive actions which are naturally damaging if and exactly if the accusation they are based on is true.

That is, the logic is something like "well, either it gets fixed, in which case it's a victory for good, or they're hypocrites who don't really care, in which case 1. it wastes their time and 2. they deserve to have their time wasted."
by mau | 2025-10-16 15:48:27+00:00
> Your coworkers and QA will thank you for learning LINQ and ditching the imperative methods that plague your Python brain.

This is a very unfortunate joke: Python has list (and generator) comprehension expression for a long time (2.3?) which are similar to LINQ. At some point in the history many languages stole useful expressions from other paradigms.

Let’s joke on BASIC, it always works.
by akarshc | 2025-10-16 15:48:41+00:00
latency is minimal because liveview sends only dom diffs, not full page updates. most interactions feel instant. each connection runs as a lightweight beam process, so managing per-user state scales efficiently. for very high-frequency ui updates, some client-side js may still be needed, but for forms, lists, modals, and live updates, liveview is smooth and responsive.
by dfxm12 | 2025-10-16 15:49:21+00:00
They're cheap, easy to find and easy to prepare.

With grocery prices going up, what little progress has been made might get reversed, unfortunately. Making America healthy again means making non-ultraprocessed groceries available to everyone & cheaper, and ensuring that working families have time to cook. Pressuring Coke to create a new product with sugar is not going to move the needle.
by nop_slide | 2025-10-16 15:50:11+00:00
https://github.com/pallets-eco/flask-pydantic

https://luolingchun.github.io/flask-openapi3/v4.x/

> dependency injection

While nice I never found this to be a critical deciding factor of using a technology.

> real async

If you really want it there is Quart which is real async

https://github.com/pallets/quart

I'm not a huge async fan in python anymore so not it's not a huge issue for me. But there are definitely options for Flask if you want to use async.
by pjc50 | 2025-10-16 15:50:43+00:00
Remember that we're talking about a generation ship - after a very short fraction of the mission time, everyone will have been born on the ship.

(Does the ship have a class system? Is the ship structured as a commune? Do people "own" bits of it, or is it more of a feudal tenure system? Can you maintain a multigenerational society on a military command structure when there is no external enemy other than the vastness of space? Would you want to?)
by sodapopcan | 2025-10-16 15:51:02+00:00
Oh also wanted to point out that while there has been an ongoing effort for LiveView Native, it is not there yet (I actually haven't heard anyone talking about it in quite a while). I'm not too in the Rails world so I don't know how good Hotwire Native is, but I assume it's much further along than LV Native, so that's a big thing if you need that. No idea about LiveWire as I've never even been in the Laravel world.
by giraffe_lady | 2025-10-16 15:51:10+00:00
Didn't pino palladino tour with him on that one? He's had an amazing career and is probably better known for other things but the hip hop/r&b studio work he did in the late 90s is some of the most influential by a single musician I think. It was basically him and questlove figuring out right there how to play j dilla's approach to rhythm programming with live instrumentation.

The recorded music from the sessions went on albums for erykah badu, common, and d'angelo but it ended up being basically the blueprint for an approach to studio & live rhythm for pop, hip hop, r&b, and also even jazz & gospel. Always fun to get to let old The Who heads know that palladino is also the best living hip hop bass player.
by hunvreus | 2025-10-16 15:51:20+00:00
Some interesting concepts:

- Components: https://hyperflask.dev/guides/components/ - Bundling view and controller in the same file: https://hyperflask.dev/guides/interactive-apps/

I think these may be footguns though. Components for example are just a regular macros under the hood. Why not use macros then?

I'm also curious about the choice of Flask. I started with a similar approach for /dev/push [1], but ended up moving to FastAPI + Jinja2 + Alpine.js + HTMX once I figured out FastAPI wasn't just for APIs. I wanted proper async support. I love Flask, but don't you find it limiting?

[1]: https://github.com/hunvreus/devpush
by trinsic2 | 2025-10-16 15:51:39+00:00
Normally I would agree that security measures are needed in many, but not all cases, but only if they are in complete control of the user and cannot by altered by any one organization. For-profit companies cannot be in control of these mechanisms. We have seen how they can be abused with the latest decision by Google to limit side-loading to people who identify themselves. So your take is really a misdirection from how these tools are being used against our property.
by ryandrake | 2025-10-16 15:52:19+00:00
> "EA is not a struggling company," the statement reads. "With annual revenues reaching $7.5 billion and $1 billion in profit each year, EA is one of the largest video game developers and publishers in the world."

Seems to be a common theme in 2025: Actually-healthy companies cosplaying as struggling companies, as an excuse to justify layoffs and other activities that transfer wealth and power from employees to management and shareholders. Like, does anyone think any of these BigTech (and MediumTech) companies who are all doing layoffs are really "struggling" and "vulnerable"? It's always just an unbelievable excuse.
by umanwizard | 2025-10-16 15:52:21+00:00
> What does rust have to do with thread safety and race conditions? Is rust going to synchronize shared memory access for me?

Well, pretty close to that, actually! Rust will statically prevent you from accessing the same data from different threads concurrently without using a lock or atomic.

> what's preventing me from using C++ atomics to achieve the same thing

You might forget?
by parthdesai | 2025-10-16 15:52:25+00:00
With GenServers, what happens if you pod/machine crashes? You lose all the unprocessed jobs. Oban gives you safe retries, and guarantees consistency. If you're using a relational DB, I would infact suggest to start with Oban, and then take a look at the jobs and see if you are okay with losing jobs and move to GenServers.
by qwertox | 2025-10-16 15:52:27+00:00
I think this was either a `number of TBW (terabytes written)` or `% of space used` issue, since both got removed by the OS within 9 hours delta and the same usage (couple of months, ~500GB), because they were in a mirror since the beginning. If it were a sensor issue, SMART data should have shown this. Not saying that a sensor issue does not exist, but I doubt that this was my problem (mine don't have a preinstalled heatsink, I prefer to use my own).

I now use a 3-way mirror and am mixing brands.

One very nice thing: the Samsung Pro 990 4TB has the exact same space (down to the byte) as the WD_BLACK SN850X 4TB, so they can be replaced without any issues. This rarely was the case with SSDs and HDDs and probably other NVMes. Looks like they learned.
by Groxx | 2025-10-16 15:52:30+00:00
>Our estimates of the total surface partitioning capacity are much larger than if the reservoirs are taken to be thin organic films on smooth, impermeable surfaces.

... so is "smooth, impermeable surfaces" the current begrudgingly-accepted model or something? because there's no way any person who has ever been in a house would think that's a reasonable model. permeable surfaces are all over the place, literally most of the place because it includes essentially all walls and therefore wall interiors. managing that for e.g. humidity is a significant part of building design because it's completely inescapable... and that's before even touching stuff like fabric where your average couch probably has more surface area than all structural surfaces combined.
by macNchz | 2025-10-16 15:52:32+00:00
The great majority of development in American cities over the last 75 years has been single-use, with neighborhoods of exclusively single-family houses separated from nearby commercial strips with big parking lots along wide roads.

The downtown/center of older cities may still have mixed use, and there have been changes happening in recent years to allow/build more apartments and mixed use areas, but, generally outside of the densest parts of the largest cities commercial and residential areas are required to be separate, with personal cars as the primary/only way to get between them.

This has been a bit of a self-reinforcing phenomenon, IMO, as car-first infrastructure puts people at the mercy of traffic congestion, and means that any apartment building or business in their vicinity will result in more cars passing through, more congestion, more competition for parking, as well as the presence of the large parking lots that cities mandate for any new construction, which themselves make it unpleasant to get around in any other way.
by golol | 2025-10-16 15:52:41+00:00
This is pretty cool. I have several points to make. 1. We all know that Cellular automata or more generally any dynamical system of sufficient complexity (and maybe not too much complexity) will be Turing complete, will have complicated "uncomputable" behavior, will have perhaps pattern formation, or gliders, solitons etc. So what is a valuable addition to this these computational investigations? I think when studying emergent computational behavior we really care about dynamics complexity / rules complexity. It's not impressive to get complicated dynamics out of a complicated system but the simplicity of game of life made it really impressive. I think in that regard LACE is pretty nice: the rule still feels very simple/natural and you can get much more structured/complex behavior with fewer cells.

2. Nevertheless in the end this blog shows mostly pretty pictures of computational, complex, emergent, chaotic behavior, which we've all seen before. And the key features that make the difference go something I would call physics-like are still missing. And I guess that would be complex stable patterns that can have complex stable interactions. Who knows maybe there are 10^16-celled patterns that have this but we don't know.

3. If I were you I would cut the whole preamble. It will make people take you less seriously than they should. You don't want to look like a crank.
by isolli | 2025-10-16 15:52:50+00:00
For the sake of completeness, I would also mention:

- Suunto (20 to 30 days in smartwatch mode for the Verticals, optional solar charging, flashlight on the Vertical 2)

- Coros (2 to 3 weeks depending on the model), no flashlight

- Withings (30 days, looks like a regular watch)

Coros is good for how long they support their watches, and the fact that they don't restrict features in lesser models. Suunto is great for route planning. Polar is renowned for its training metrics (sleep, recovery etc.) but only fetches a week in smartwatch mode.
by agos | 2025-10-16 15:52:58+00:00
the sentiment around NextJS is terrible, I have rarely seen something go from "oh this might be cool" to "stop pushing this badly engineering crap on me" so quickly. Yes, it's widely used and that's to be expected given the amount of money spent in promoting it, but it's not loved by any mean and I see this as a fatal flaw that they'll have to reckon with sooner or later. It's so bad that it worsened React's reputation by association - React already had some issues to care about, but they went in Next's direction, and people have noticed
by k310 | 2025-10-16 15:53:14+00:00
No slight on the work you've done, but isn't there a way to rename pdf's without AI?

Almost always, I can just rename one with its Title, and that's usually the first line.

A summary (usually the abstract) could accompany the file, too long for a tag.

Think email. I'll often send a pdf with its title as the subject and the abstract as the message body above the attachment. Richer than the finder (and let's not gripe on that monster)

I'm also interested in a non-AI, application/image descriptor for my countless anonymous image files, though even a tag would be better than staring at endless screens of titles, or even thumbnail icons.

Again, no slight. I am just interested in something not reliant on AI.
by dominicrose | 2025-10-16 15:53:38+00:00
PHP (Laravel) + JQuery still works for me in 2025, but I would never use Livewire.

Using Node.js would hurt productivity but it's more powerful if needed. It may be needed because it has async/await and it has socket.io. It's also possible to use Typescript.

Next.js can be useful if you need everything (good SEO + highly interactive) but let's be honest how many websites need good SEO and websockets? LinkedIn maybe.
by dmoy | 2025-10-16 15:53:39+00:00
> whose employer uses a broker that doesn't do cost basis correctly for RSUs, I was very surprised TurboTax was able to import the supplement and adjust it correctly for me.

Approximately zero brokers do this, because RSU are still noncovered shares.

> Even without RSUs, I usually have hundreds of transactions across multiple brokers.

As a corollary, "hundreds of transactions" of covered shares collapsed into one summary line.

RSU is a pain though to enter. Technically you can enter a summary line and send in a 1099 to the IRS (last year was the first year that could be done electronically, so, fingers crossed it actually works correctly).
by FirmwareBurner | 2025-10-16 15:53:53+00:00
>...yes, you should!

Why? They're actively hostile to me as a user and nor catering to my needs and desires.

>Google does much worse things and is effectively a monopolist

Monopolies are the government's job to tackle so talk to your representative about Google, but leave suers alone to use what they like. When cars polluted we had the government force them to lower emission, not shamed users for buying cars.

>Bitch at Mozilla, sure, but don't stop using it.

How is bitching more effective tool than not using a product I dislike? Not using their product is my only way of protest as that shows in their statistics and analytics while they can and do ignore bitching.

Mozilla is a major corporation not a 15 year old with cancer sewing Knick-Knacks for donations in his bedroom, so it will only improve if the user base goes elsewhere, otherwise if people keep using it out of spite, they have no reason to ever improve.
by FeepingCreature | 2025-10-16 15:53:53+00:00
Why would he file tickets with browsers he does not use?

And my whole point is that a strategy can have multiple effects. As I understand it:

- Firefox care about usability => the issues get fixed or at least considered.

- Firefox don't care about usability => sand in the gears.

So it's a hybrid strategy whose purpose depends on the situation.