skysight-inc/HackerNews huggingface dataset:
> It's far from perfect of course, but it's not like legislation just consists of a bunch of random symbols that are later imbued with meaning by a court operating in a vacuum.

Isn't this exactly what happened? A court of computer laypeople reached for Merriam-Webster in order to disambiguate a sample of programmer argot that was written into law by another group of computer laypeople. The legal profession isn't just dirty, it seems doomed to defeat itself in even its most rigorous practice.
There will never be some permission model. Like in VBA there is after all this years nothing. VBA would be much less problematic if you could restrict VBA to just one Excel sheet or so
Show HN: Verity – A tiny and super fast open-source server for Altcha
it is very annoying the message that appears in VS Code linux, "We have uninstalled 'equinusocio..." please guys fix this. I have tried to uninstall the extension but magically it appears again, for today I have to use another IDE because of how annoying it is...
You benefit by living in a prosperous country that was in part built on the backs of people who were enslaved or egregiously mistreated.

Personally I have no direct connection to much of that because all my ancestors arrived in the US around 1900. My point is you can't extricate what the US is today from what was done to people in order to make it what it is today. I still indirectly benefit. I think my ancestors benefited from having white skin in the US as opposed to dark skin, when they arrived.

> Just being part white and alive today means your ancestors won lots of fights over thousands of years.

Being white has nothing to do with it. Everyone's ancestors probably did terrible things if you go back far enough. That's not the point. You're not guilty and you don't need to feel guilty. But you should at least be aware of how the modern context in which you live was derived. It was derived from the suffering of others. How far back do we need to go? I don't think it matters, really, but just as far as is substantially relevant to the present. So for the US today, I'd say it's worth considering at least as far back as the founding of the country because we can still draw direct lines from the way things are today to events that happened from then until now. I mean, it was only in 1967 that many people realistically gained the right to vote, unfettered from schemes like poll taxes and more which were used to disenfranchise them.

> How far back in history are you willing to go, to make everyone feel guilty?

The goal is not to make anyone feel guilty. And there's no benefit in delving through ancient history. Because many of the problems that still exist in this country today are persistent effects of what happening in what is really only very recent history.

Do Italians need to feel bad about the Romans keeping slaves? I don't think so, I think it would be a stretch to say that modern Italian society was built by the slaves of Romans, let alone the Romans themselves.

But if you look around the US today you can easily find buildings that are still in use, sometimes in their original capacity, that were built by enslaved people. So I think it's still relevant. Likewise you can find the direct ancestors of native people who were forcibly displaced and mistreated, and by direct ancestors I mean really only a handful of generations, still very much recent, by historical standards.
Again, a big misconception that you do Open Source for money and to get rich.

Also, the maintainers "burnt" listed in this blog post got pissed off because they can't control another project ("linux"), that doesn't belong to them or was created by them, to go in a specific direction that they would like.
Please don't give Skynet any ideas...
No https://arxiv.org/abs/2402.07443
Oh, these tools are written in languages which can be directly compiled to WebAssembly without any changes?
Yes, then it make sense, thank you for clarification.
This seems to be your first sincere comment in this thread, and I'll leave it at that for everyone else to see.

> Any more comments on how should I live my life?

I would also suggest you stop demanding empathy when you demonstrate none yourself. Regarding your anecdote - do you know if that woman was clear minded? Do you know if she hadn't lost a family member to COVID the day before? This highlights the fundamental problem with anecdotal evidence: we can talk in circles, and none of it establishes a meaningful point.

> Stop being like that, please... Engage in some empathy. Put yourself in someone else's shoes for once.

You're right about one thing: I struggle to show empathy for someone who complains about racism while exhibiting racist behavior themselves.
The solution is to treat versions as opaque identifiers and encode the information about compatibility between versions of software through a separate database rather than trying to infer it from semantic analysis of the version numbers which are known to not be able to express sufficient compatibility information.

The version numbers should only express succession. That is the only thing that should be expected to apply to version number is the "Ordering Comparison Rules". One should not expect that 1.2 can replace 1.1 or that 2 can not replace 1. This compatibility should be expressed through a database in which people with reproducible builds and test frameworks prove that their software which works with 1 also works with 2 or that it does not. The build failures once also reproducible can prove incompatibility. Calculate this out and you get a testable matrix of software package version compatibility that does not depend on interpreting version numbers.

The CI systems can automatically fill in the columns of this matrix as new versions of packages are released or even follow the dependencies CI systems and run their own builds automatically once the package's CI system says that the software builds and passes its own tests. In such a design, version numbers become irrelevant and you can use commit ids instead.
It's 2025, regular english is machine readble
> Now after two years look at Cursor, aider, and all the llms powering them, what you can do with a few prompts and iterations.

I don't share this enthusiasm, things are better now because of better integrations and better UX, but the LLM improvements themselves have been incremental lately, with most of the gains from layers around them (e.g. you can easily improve code generation if you add an LSP in the loop / ensure the code actually compiles instead of trusting the output of the LLM blindly).
Can I ask some different questions then?

Do you parallelize your current tests? Why or why not? Do they work out well for you?
OK, I admit that the math flies way over my head and I barely understand the text around the math. Can someone please explain (in basic English) how this is equivalent to attention mechanism? What friquencies does it talk about? How does it encode positional relations between tokens?
Why are you saying it like it’s a veneer of legal or ethical grounds? Publishing something that was said off the record would be a violation of professional ethics, whether you personally agree with those ethics or not.
I agree. But here are other ways of accretion of code inconsistencies:

- Premature abstractions that are subsequently worked around around the edges.

- Automation built on top of wishful thinking instead of how people actually prefer to work.

- Inconsistent naming and file structure.

- Adopting many advanced or hyperspecific styles and techniques instead of leaning on more basic ones that already solve a problem.

I find it way easier, to go from more primitive, consistent, "inlined" code to more sophisticated abstractions that clearly solve emergent problems at a later point in time, than changing the direction of already factored, high level code.

To me it's a matter of mental capacity and friction as well. This stuff is hard, time consuming and requires deliberate effort. I rather accept that code goes through different phases of maturity and that using and maintaining the actual programs over time, gives me a much clearer path forward than applying patterns and principles in advance on an abstract level.

A caveat here is that many of these inconsistency factors come from adopting third party dependencies. In my experience this is the largest chunk of liability or tech debt.

---

However, a large factor that is often overlooked in these discussions, is also organizational scale. When you have to own and understand things from A-Z you can get away with different things than if you are one part of a much larger team and vice versa.

I'm firmly in the former category, so I have to optimize for being able to take a much larger slice of responsibility. But I can also get away with leaving code in a more raw state for longer. I assume this balance looks different the more people you add to a project or organization.

I think we need to take this into consideration in these public discussions. It's ultimately a trade off and programmers from different backgrounds will have different sensibilities.
This makes me wonder if math will ever reach a point where it’s “solved”. Like, a point where we know everything there is to know and every new field that you can think of can already be mapped to something else.
I love Scott, but I think OP's meaning is not about verifying discoveries, but rather having the tools necessary to create discoveries in the first place. You can't invent an electric motor without electricity. Alternatively, think about how Da Vinci has many notebooks full of ideas- but lacked the resources to create them.
>> ... mainstream database system ...

> SQLite, with far more installations than Postgres, isn't a "mainstream database"?

It's not a system, it's a monolith library, which is why it is used wherever you want a local database with local storage.

Postgres implementations are a client/server systems even if the connection is on localhost.

It's also MVCC and has RLS and other requirements that do not necessarily apply to a local database like SQLite.

It's not about the number of installations, it's the type of database.
I value research of people that spent their lives on it more than my personal illusions.

Reading someone's research has way less opportunities for lying to yourself than trying to form an opinion on this subject from your own experiences only.

Sure, my perceptions of reading someone's research are burdened with errors just like everything else I perceive in life. But since the knowledge is distilled and condensed then there's less opportunities to mess it up, compared to the alternative of "doing my own research".

I don't see how that's controversial for you. That's how science works. You read what other people wrote first. Then you try to make some contribution if you are so inclined.
Or Bose for that matter
this is not the point

Scanning a multi-page whole menu with a camera does not make it machine readable. And frankly, the menu is not in the qr-code, it is a link to the menu. What sounds appropriate here is to write also the content of the qr-code with plain letters, so one can type it, alongside the qr-code, for those who do not have a camera or whatever.

Now, the problem of requiring a mobile device to see the menu is a problem on its own, and while this is faciliated by having a qr-code vs having customers manually copy links on their phone (either writing them or with OCR), it is 2 separate issues for discussion. Moreover, OCR-A is not needed for any of that anywhere in the 2020s that we live.

The problems with QR code is that sometimes people have older smartphones or camera do not recognise them or, frankly, it being a means of obfuscating sth from humans. I have been in many situations with queues of people struggling for indeterminate reasons to scan a qr code to go fill up sth. If there was a simple link in plain text people could have even shared it between each other. Blindly trusting technology that can easily fail and is unnecessary for what one does and without redundancies is unwarranted imo.
> If I upgrade to the new LR and I get, let's say, 480km in the cold and at highway speeds, that would give me 2 hours and 24 minutes between stops.

480 km in the cold at highway speeds is 140 km more than your previously stated 340 km, which is an hour more at 140 km/h.

If you are driving between highway charge stops, it's a bit over 3.5 hours between stops.

> Longer range consistently tops consumer requirements

It is tied with "availability of chargers equal gas stations" in that report, suggesting that the range concern is not about roadtrips but daily convenience for households without own chargers.

Also, answers to a questionaire for "EV skeptical" people about why they haven't purchased an EV isn't representative of actual needs. People when asked about range answer that way because they're comparing to what they already have and have to make up an answer to justify their decisions, not because of need.

> You must just accept that others value different things.

And you must accept that your values does not equal the actual needs of the general population, which can be quite easily assessed based on normal worklife patterns.

I'm sure we can agree that any vehicle is objectively best if it is optimized for your actual needs, and that the more often it fit your need the better. This makes it quite simple: Does your daily driving equal roadtrips, yes or no?

If not, you will get an objectively better experience (better handling, less noise, less energy/fuel cost, less tire wear, faster charging to full) while simultaneously saving your bank account and the environment. And no, a dialy driver doesn't mean "renault zoe", it just means "smaller and lighter battery".

If you drive 1 roadtrip per year or less, it makes sense to rent the car for roadtrip to get the best of both worlds: the best roadtrip machine and the best daily driver, which are mutually exclusive requirements. The roadtrip vehicle might be a large, comfortable ICE car with below average fuel economy and plenty of space - maybe even pulling a camping wagon depending on what you want to do on roadtrips.

If you drive 2+ roadtrips per year, maybe it starts to make sense to buy a roadtrip-specific secondary vehicle. If you drive much more than that (e.g., every weekend, or daily work involves multi-hour driving), then it starts to make sense financially to compromise and use a roadtrip vehicle for daily driving.
>For everyone else, open source becomes a one-way relationship: all giving, little receiving

For me, open source is like making a painting and hanging it on a wall where others can see it. I will never lose a single second of sleep over whether someone else likes it or not.

I would never take money for an open source project unless I was prepared to work on it full time. It would give me a sense of responsibility which I don't want.

Normalize maintaining your own fork if upstream doesn't agree with you. It takes me 5 minutes per year to rebase some projects where I wanted them to work differently than the maintainers had envisioned.
> I agree that "vestibular" refers to a more particular concept.

Not just that. A more surprising (i.e. less likely) result carries more information. In the informational theory sense. A word with broad scope will be more used, thus be more frequent in text, and thus, carry less information.

> To my understanding, you suggested using the term "THE text format on Linux" as a replacement for "machine-readable" (as it is currently used). My objection was that those concepts are not the same and, in fact, binary files tend to be machine-readable moreso than text files.

Ok, you have a point there.

But I don't think the author ever compared binary machine only readable formats, either. All the machine-readable formats that he looked into admin were human-readable too.

> Many things (including, say, an 8-bit image) can be rendered as bytes.

Sorry, I meant to say UTF8/UTF16/ASCII etc. Probably was messing around with UTF8 -> bytes conversion around that time.
Apologies, I was unclear.

I was referring to a journo signing up for say the training program in the article, and then divulging something that’s legally confidential in a story. That would be killed.

I just used “off the record” as an example of why in journalism, respecting agreements is critically important.
I downloaded it to take a look, all the js is obfuscated via https://github.com/javascript-obfuscator/javascript-obfuscat...
It's not a big. It works as intended.
Steve Wozniak: 'Founding Apple would be much harder today than in the 1970s'
While I understand these are mostly jokes, I do not like the racist and sexist one.
Writing React in F#
It would also be harder in 1939.
I think in the minds of not-particularly-literate online writers, "strange" = "bad" and "unique" = "good".
Evaluating LLM Systems with Production Data at Scale (Steal This Idea)
WebGPU Fluid Simulations: High Performance and Real-Time Rendering
I’d recommend to first see if you can use a full-Gleam solution (like wisp/lustre) if it’s a greenfield project – interop is of course possible but can sometimes be a bit unpleasant due to the difference in data structures (Elixir structs va Gleam records) and inability to use Elixir macros directly from Gleam, which are heavily used by projects like Phoenix and Ecto.
At Distrust we freely license every line of code we legally can right down to our website and infra repo. We also exclusively do our work with local and self hosted FOSS as well.

Our code and docs are always free but they happen on our terms by default. If you want to accelerate development of features that benefit your org, or if you want hands on support, or security advice, or you want your code reviewed quickly, etc, we offer retainer contracts.

Able to support 3 employees full time, knock on wood.
Gödel says no

https://en.wikipedia.org/wiki/G%C3%B6del%27s_incompleteness_...
You have misread your sources. The 32% is for doctors, the 19% is for all staff.

You wrote "But it must be a much broader category than immigrant, because only 19% [of UK doctors] are foreign nationals, and only 14% are from outside the EU [1]"

Your [1] says "Overall, 18.7% of staff report a nationality other than British. For doctors this figure is 35.0%, and for nurses it is 27.2%."

Your The Sun uses the same number: "Official figures reveal more than a third of the 113,000 doctors working in hospitals in England now come from abroad."

Instead of spending time to post 8 or so different links, it took me about a minute to find the OECD study at https://www.oecd.org/en/publications/recent-trends-in-intern... which defines foreign-trained as people who received their first medical or nursing in another country, noting that "a certain number of foreign-trained doctors or nurses may be people who were born in a country and decided to pursue their studies in another country before returning to their home country".

How is a summary of the 36 FTP inquiries in Ireland in 2010 at all relevant? It comes across like you've spread a wide net to bring up any anti-foreigner sources, while likely omitting all pro-foreigner sources.
Hard to parse when read as text. Heavier. Cannot read it through SSH. Need something else than your terminal.

As someone who live in terminal emulators (yes, even home), markdown is more WYSIWYG than most other formats (I still think org-mode is better though)
Yes, this is exactly where Telescope can be useful (and actually, the way Grafana displays logs was my motivation for writing my own viewer)

Telescope can work with any table in ClickHouse. Of course, not every single ClickHouse type has been tested, but there shouldn’t be any issues with the most common ones

If you want, you can check how it works with the OTEL schema in the live demo here: https://telescope.humanuser.net/sources/otel-demo/explore
Thanks!

I don't know about migrating my current project, but I'll definitely try Gel for a future project.

>Total TypeSafety enforced at all levels, built-in migrations engine, best in class access control (we'll be blogging about our access control vs RLS soon.)

Very very cool.

If I just dump my Supabase project's Postgres DB can I load the SQL into Gel and have everything work. Or would I need to setup the schema.

Ultimately I'm just looking for an open source alternative to firebase-> while amazing, I can't exactly claim to have an open source project that requires a closed source service.

Last question, Supabase heavily pushes the use of Captchas if you use any anonymous authentication. Does Gel also suggest this. Notably Firebase doesn't care, which makes it much easier on end users.

Imagine having to solve a captcha to browse Amazon and add products to your cart, you'd probably just use something else.

Ok, just one more question! How is your SDK support. JavaScript is a given, but Godot support would be nice.
The script works just fine on real Linux, it creates 2048 files and ls command lists them all with different names.

ls -l win32/
total 0
-rw-r--r-- 1 dawid dawid 0 Feb 26 12:13 ''$'\355\277\237''.exe'
-rw-r--r-- 1 dawid dawid 0 Feb 26 12:13 ''$'\355\267\213''.exe'
-rw-r--r-- 1 dawid dawid 0 Feb 26 12:13 ''$'\355\240\220''.exe'
-rw-r--r-- 1 dawid dawid 0 Feb 26 12:13 ''$'\355\274\273''.exe'
-rw-r--r-- 1 dawid dawid 0 Feb 26 12:13 ''$'\355\251\205''.exe'
-rw-r--r-- 1 dawid dawid 0 Feb 26 12:13 ''$'\355\255\223''.exe'
-rw-r--r-- 1 dawid dawid 0 Feb 26 12:13 ''$'\355\272\257''.exe'
-rw-r--r-- 1 dawid dawid 0 Feb 26 12:13 ''$'\355\264\207''.exe'
-rw-r--r-- 1 dawid dawid 0 Feb 26 12:13 ''$'\355\261\246''.exe'
-rw-r--r-- 1 dawid dawid 0 Feb 26 12:13 ''$'\355\254\266''.exe'
...
To be honest, I was more inspired by DataDog :)
Oh, great. Can you also share the locale? I'll write another Postscriptum section then.
Tesla 'Full Self-Driving' Isn't Called That in China
The actual mechanism at least is quite simple. Essentially it takes the FFT of the input embeddings, multiplies it elementwise with weights that are gotten from the input embeddings using an MLP (plus a constant (but learnable) bias) and then runs it through an activation function and finally takes the inverse FFT.

The "frequencies" are probably something quite abstract. FFT is often used in ways where there aren't really clear frequency interpretation. The use is due to convenient mathematical properties (e.g. the convolution theorem).

Rather amazing if this really works well. Very elegant.
I have two border collies at the moment. The older one is definitely food motivated but also ball-motivated. If presented with both, she goes back and forth, undecided as to what she wants first. The younger one is "meh" on food and would easily ignore it entirely if given the chance to run flat-out in a wide-open space. Her nickname is "Speed" (though my Apple watch thinks it should be "Loud Environment").
> The person who would want this product is the opposite of the person who would want their other products.

That's me! I'm that person! \o/
If it were enough that government data were available via discovery then we wouldn't need FOIA laws in the first place.

Patents aren't relevant here since they are disclosed upon granting and cover the design rather than the implementation, for trade secrets the situation is more complicated ( https://www.americanbar.org/groups/litigation/resources/news... ).
Basically leverages convolution theorem[0]: expensive convolutions in direct space becomes simple multiplications in reciprocal space, and vice versa.

Whereever you have a convolution operation on your data, transform them to the conjugate domain to turn it into multiplication.

In other words, work in the domain that is natural to your data.

[0] https://en.wikipedia.org/wiki/Convolution_theorem