skysight-inc/HackerNews huggingface dataset:
Sounds like a great library to use for automatically testing all the new models being released everyday and finding out if a new open source model significantly performs better on your custom dataset.

1. What's the largest model (number of parameters) that you've tested the library with?

2. Will MoE models work as well? They're known to have more unstable training and need some custom techniques to stabilize
It is easy to create bad tests. I have seen an over-reliance on mocking giving high code coverage but still quite useless tests.
I have a friend called Nick, but we call him Nikipedia, since he has a crazy amount of facts stored into his brain. When we go to quizzes, our group is most likely to win.

I can tell you this: LLM's know more than Nick and would beat these quizzes every single time.

You can use any definition of "intelligence" that makes you happy, no problem.
Related:

Tesla settles with family who said Autopilot caused his fatal crash

https://news.ycombinator.com/item?id=39974575
I use node, deno, bun, qjs, tjs at the same time
'Relative to' rather than 'faster than', as in the speed of light being 20x slower or human perception and reflexes being 20x faster, or some mix of the two. If people were thinking way faster then the lag would be unbearable, and there would be no way around it.
We'd still be using triple-DES to protect data, arguing that the NIST time to break it was still far out beyond. And hash functions would be like the CRC32 in TCP, not the modern stuff.

CISC computers which did more in parallel per instruction would be common because they existed for concrete reasons: the settling time for things in a discrete logic system was high, you needed to try and do as much as possible inside the time. (thats a stretch argument. they were what they were, but I do think the DEC 5 operand instruction model in part reflected "god, what can we do while we're here" attitudes) -We'd probably have a lot more Cray-1 like parallelism where a high frequency clock drove simple logic to do things in parallel over matrices, so I guess thats GPU cards.
Nice room for a new player to disrupt then
Women are also resentful of their partner's success and their egos can not take it.

The paragraph you quoted, Ely's husband sounds jealous of the attention she got and her control over the company. That can happen in any kind of partnership.

You're dragging up sexism, where it is not the primary problem. Why?
He'll censor anything on behalf of Saudi Arabia or India, but complains loudly when it's Brazil.

Why the double standard? He wants a pliable, aligned government in Brazil so he's using his megaphone to try to achieve that.
Sounds right to me. Without being able to rely on flashy visuals and low-latency so much, games would've had to be somewhat more strategic and intellectual to sell (although I imagine graphics would eventually catch up due to its fitness for parallel processing). Even if brain rotting visual spectacles were just pushed 7 years down the line, they still would probably have a more sophisticated flavor that might be cemented with time (e.g. this counterfactual TikTok might have given users much more direct control over their feed algorithm).
> because of all the tests you will have to rewrite

If you have to rewrite tests that means you've changed the user experience in ways that are not backwards compatible.

Which is sometimes valid, but not exactly what is being talked about here. The discussion here is more about changing the code in ways that makes the code better, but still delivers the same user experience – possibly with new features added, but not where anything is taken away.
I think you can merge multiple directories onto /usr/local using overlayfs.

That seems to be what Stow is simulating, using symlinks.

Symlinks have the advantage that they persist; you don't have to recreate them after every reboot.

Stow also has ignore lists, which isn't something overlayfs will do, or not nicely; it is oriented toward directories. In the package installation use case, you could just keep unwanted cruft out of the individual installation directories that are being combined.
Love Candle! I actually ported Karpathy's previous GPT tutorial to candle, including training [0]

[0] https://www.perceptivebits.com/building-gpt-from-scratch-in-...
Viewing the 2024 Solar Eclipse with Commodore 64's 1984 Sky Travel [video]
More C/C++ based business apps that run locally. Cloud would be less relevant. No large browser engines, which means a lot less JS and of-course no Electron :)
Feels like that would be noticed rather quickly given that you would be able to access someone else's funds on the network automatically, whereas in the SSH vulnerability case you have to proactively check if servers you want to access have one of the bad fingerprints.
Design, Implementation and Evaluation of the SeL4 Device Driver Framework [pdf]
thou, you are in a world of hurt if it takes a extra day
I've been using BART all my life, and while I'm not old enough to have been doing so since it first came into service, I did get to experience it during its glory days. It legitimately felt like getting on an airplane, and it was fascinating to young-me, as trains are to many kids.

For those who didn't know, bart used to have:

- Generously padded cloth seats

- Carpet (!!!)

- Free parking

- Magnetic paper tickets, and the turnstile machines would stamp the remaining balance upon exit. They'd also get demagnetized all the time, or get stuck in the machine.

Yes, the cloth seats and carpet were terrible ideas, but before they got all disgusting, they looked and felt nice. Bart used to be really nice, it was clean, and people generally respected the system. I still think BART is fantastic, but I don't deny it has its problems.

Anyway, BART dropped a ton of merch when they were decommissioning their old stock, and I managed to snag an aluminum car ID plate and a real system map! https://imgur.com/a/rCvf93S
OGS is the closest thing I’ve found to lichess but it’s quite good! https://online-go.com/
It's pretty easy to check something kinda close to GitHub's source code to see, if you want.

Just buy a copy of GitHub Enterprise, deobfuscate the files (it's a fun challenge to deobfuscate them, and not all that hard), and look around to see.

It's unfortunately not open source, so we can't share and talk about the code, link to it on GitHub, or anything like that, but if GitHub Enterprise is still using such a patch, it's like the prod github is too.
Very awesome project
Unless your using database specific features. One of the biggest advantages for Postgres is how incredible the ecosystem is. It doesn't work for everything, but I have an OEM, multiple kinds of text search (vector, inverted indexes, trigrams), recursive and graph-like queries (though that's admittedly less of an issue if n+1 isn't a problem), row-level acls, locks, etc.

It's really nice to have all of that power available in one piece of infrastructure.
Unless you can hot-reload it?
I work in a place with 99% test coverage requirements and it's honestly still a super brittle system that everyone is afraid to make big changes to.

Obviously tests are going to break when you change the code's APIs and functionality. That's expected, and does nothing to boost your confidence in the part of the code you're working in. The point of tests is to improve your confidence that you're not doing things that have an unexpected impact somewhere else (hence the Bob Martin quote in the article about tests being useful even if you have good design).

Tests aren't an alternative to thinking. You still have to consider what changes you're making, and what tests should break as a result. That's just part of your code change. When tests that shouldn't have broken start failing that's when they show their value.
TFT? The first rule of TFT is...
Creating Seams in a Mainframe's Batch Pipelines
Eslint released in 2013, so sounds about right. Even Java has had more major releases than that.
Async_API_caller – simplifies asynchronous web API calling in Python
Alternative (the suckless way): don't require people to keep stupid 'configuration files', help them edit your program to suit their particular needs.
just encrypt it with symmetric cipher in ECB mode of operation.

For 128-bit GUID use AES-128 is perfect. You can still compare if the two GUIDs are the same without decrypting, but you need to decrypt to get the real GUID.
> Macros aren’t marked, so any unknown term might be a macro.

Yes, that's a problem.

There are two clues:

* Macros typically have naming conventions. For example anything beginning with DEF should be a defining macro, not a function. Anything with DO- will be a control structure. Anything with WITH- will be a scoping macro. And so on. Avoid active names like CREATE- and use DEFINE- instead. CREATE-CLASS would be a function, DEFINE-CLASS would be a macro.

* In source code the enclosed code typically has syntax and special indentation, when used with macros. Functions have certain uniform indentation rules.

(create-class 'container-ship
:superclasses '(ship)
:slots '((max-number-of-containers :type integer))
:documentation "our new container-ship class")

Above is a function and uses one of the typical formatting/indentation rules for functions. Line up the arguments. Start with the required argument and then the named argument pairs (name, arg).

The macro looks different. The first important things like name and superclasses are on the first line. The other parts of the class specification follow and are indented by two characters.

(define-class container-ship (ship)
((max-number-of-containers :type integer))
(:documentation "our new container-ship class"))

Developers who write macros should make it clear what a macro is, by using hints like these.
Some quotes:

>Measured performance shows a vast improvement over the CAmkES-based framework, as well as significantly better performance than Linux, despite the higher number of system calls and context-switches required. In particular we find that a highly componentised sDDF system easily distributes across cores, while each individual component being strictly sequential, reducing its complexity.

>The framework, running on the Microkit, clearly over-achieves our goal of “performance comparable to Linux”, outperforming Linux by a significant margin under all configurations evaluated. Performance is vastly better than that of the CAmkES system adapted to our transport layer (which is already a significant improvement over the performance of the previous CAmkES-based driver framework). The performance comparison to Linux is especially encouraging, given that the Linux IP stack is supposedly well optimised (especially for multicore use), while we are using the simple lwip [Dunkels, 2001]. We find that even on multicore (the scenario most favourable to Linux) our per-packet costs are significantly lower.
Huh? Isn't the entire point of GP's comments that they are /not/ gone?

Just because Chrome is a bit less terrible than IE6 in terms of user/dev experience (which, to me, is entirely a matter of more sophistication in software development and Internet stuff, and a keen and burning desire to sell ads) doesn't mean we're in a good position. A browser monoculture is good for nobody but Google.

This feels like the exact same bad old days to me, where if you're not using the modern-day IE6, the web is a pain in the ass. That was my takeaway from the article and (as a Firefox user that also reaches for Chrome far too often) one I sympathise with.
The only way I know for doing concurrent writes in sqlite is to open a transaction, accumulate a bunch of writes and then commit them. Otherwise it is dog slow. And it has to be a single process, or you get data corruption. Has this changed somehow?
It doesn't seem like anyone is working on JS tooling in C++. Some projects used Go but switched to Rust... I guess the object lifetimes are probably pretty simple so it's a no brainer.
Maybe top 1% of thinking they are ;)
https://news.ycombinator.com/item?id=6195493
No. In scenario 1, with TLS, an attacker gets access only to data corresponding to incoming requests. The same thing clientside Javascript cryptography code does to push secrets out to the client (either by deriving keys from memorable secrets or using local storage) works to store secrets serverside encryption can use; lots of encrypted cookie systems have been built to do this.

Your scenario 2 analysis works by suggesting that attackers can't easily subvert the Javascript contexts of clients (it mentions for instance "resource integrity"). But every request for any resource that alters the DOM or loads code allows an attacker to pull this off; it's the premise of the attack. This is an even weaker case for browser JS crypto.

I think the big premise mismatch we have is that you're assuming I'm saying "just use TLS and store keys on the serverside".

I feel like discussions about WebCrypto always fall apart in arguments over abstractions, like software update versus HTTP requests. But I'm saying, it seems like you can literally just skip all the clientside cryptography, stuff keys in cookies (or whatever), and do all the encryption serverside, and end up with the same threat model, which to me is telling.

I don't think people are crazy for pushing back on this. People smarter than me disagree about it. I wonder if David Adrian wants to take a swipe at this argument.
> economically feasible

Luckily it's a University project. And economic feasibility does not apply.

Or should not. Unfortunately some universities do take this into consideration, rather than just scientific value.
> It is quite surprising to me that the app store gatekeepers don't force all app changes through their vetting process!

It's be because they can't anyways, what about web pages, feature flags & server side rendered views? The review process is mostly there to not circumvent their payment process.
if you allow multiple sequential memory lookups, this is true for any instruction set
also https://blog.1inch.io/a-vulnerability-disclosed-in-profanity...
See above; I addressed the same claim in your sibling comment.
They usually hide under bridges.
Distance from the body I have defined as distance from its center.

Black hole does not have a surface. At least not that we know of. Event horizon is a surface, but it is not the surface of the BH in conventional sense. If you were falling into BH nothing special would happen as you crossed event horizon.

And neither does the Sun. Just like Earth's atmosphere, we can only talk about some arbitrary altitudes or pressures, but reality is that the atmosphere of the Sun or Earth does not have any firm beginning or end. And Sun is all atmosphere.
You need mostly integration tests, not unit tests.

Unit tests which dependency-inject mocks of other parts of your codebase are 99% worthless.

Source: Spent many years writing the latter and they caught close to 0 bugs. Moved to Elixir ecosystem where integration tests are the norm, and they catch bugs on a regular basis.
How do they distribute github enterprise? Like a VM or image?
> And that’s about to change - thanks EU

Lol, the EU law is there to protect you from a monopoly, not to force one. The mental gymnastics are in the circus territory for this one.
In gravel won't work, as the structure of the ground has a high impact on the shape of roots.

As I can confirm, trying to grow carrots in heavy clay ground for example.
As with all tools the goal is to be able to use the tool without fear.

Remember the first weeks of coding C? It took me 4 years to not get cold sweat just thinking about using it when the compiler didn't inform you about a typo and you have to rollback the code all the time to fix problems and learn assembly (in X86, ARM and now Risc-V).

And that was without deadlines or any delivery pressure.

Today I realize C is for mad people, but I learned to respect the thing while no longer being afraid to use it in a real scenario.
I see your point, but if the USA didn't encourage the company to set up fab shops domestically, then it wouldn't be receiving those taxes either - but in that scenario it also wouldn't be receiving the indirect benefits of having that company operating locally.

Your personal taxes are a different matter - the nation state is not trying to court you into operating within its borders with some tempting on-paper discounts.
I run stable Firefox and have only ever done so and have had the same problems, especially with anything video related. To the point where I don't bother using Firefox for things like Google Meet almost all the time - I don't want to be That Guy turning up to a client meeting with the wacky config that can't get sound/video working.

Edit: I haven't tried for a couple months at least so maybe it's improved lately, but certainly it's failed often enough in the past to make me reluctant to try it. I'll give it another go.

(I also get that this is probably not a Firefox problem at least some of the time, but devs not testing properly or using Chrome-only features. Maybe it's improving now but it certainly feels like Mozilla could do more advocacy here?)
> semiaccurate's track record is... "checkered", and afaik reports were this doesn't seem to have shipped in the final product

Sunlight is a good disinfectant.

We need more tech journalists to shine light on pre-production supply chains, early enough to improve GA hardware.
Ask HN: Getting recommendation letters for grad school after 10 years in tech
Most leaders I have worked with are too far in the past or will not be interested in me leaving my current organization. How to get recommendation letters then?
Hermeneutical testing reference card [pdf]
> you're having people modify files that you will also change

How is this different from the ever changing nginx configuration files?

I think the underlying problem is that various programs use different ways of shipping things. Some include configuration in source code, others require one to read a book to setup a configuration file, others have a database with configuration settings.

If it weren't for us humans creating these things, we would probably have settled on a single interface.
Ah - you might be right that there are some crossed wires here as I was imagining a "just use TLS and store keys on the server" scenario.

Could you correct me please so we're on the same discussion ground? Where does encryption happen and what mechanisms are used to ensure the security of keys?
Exactly my point, and they get hit by a video streaming bug == instant showstopper, world is crumbling, critical bug. Well it is not, just because it affects YOU.
List of Open Source Mentors with LinkedIn and GitHub Links
Hi, HN!

This is a curated list of awesome open source mentors who are happy to help newcomers with their first pull requests, inspired by [the great experiment initiated by Lena in 2018](https://github.com/lenadroid/awesome-oss-mentors). The original version did not include LinkedIn and GitHub links. I hope my efforts in adding those links will make it easier for you to explore and discover open source mentors.

Awesome List of OSS Mentors: https://github.com/novooss/Awesome-list-of-OSS-mentors

I would love to hear your thoughts, feedback, and suggestions as I continue to improve this Awesome List.

Contact: teamnova@myyahoo.com
Reading this I was wondering how far are video compression (with transformers), turns out decoding is still too expensive in practice (under 10 FPS for 1080p video).

https://arxiv.org/abs/2206.07307
https://arxiv.org/abs/2210.13827
or just dont use their programs, or write your own!
Not how that works....
nobody adds the decimal digit to integers, though

1180 can be 4 significant digits if the count is precise
I don't think people should be using videos without permission. But that said, I think we should err on the side of leniency, because if we allow openai to use the data, we will allow their competitors to as well.

If push comes to shove, openai can acquire all the data they need with microsoft money.

But the little guys can't. So if we let them get away with it, we are really making sure the little guys can compete!
What a surprise that is.
A bit off topic, but this is why I started using KDE over gnome. I liked to use middle mouse button for drag-move/resize but in gnome it required editing the source code and recompiling.
Oh My Git: An open source game about learning Git
The GNU Stow documentation has a curious blind spot; it doesn't mention the DESTDIR convention for installing in a separate directory:

$ ./configure --prefix=/usr/local
$ make
$ make install DESTDIR=/usr/local/stow/whatever

Using "make prefix=..." is not the main mechanism for overriding the install location; DESTDIR is. DESTDIR is widely supported, and documented in the GNU Coding Standards, in the Makefile Conventions section of the Release Process chapter:

https://www.gnu.org/prep/standards/html_node/DESTDIR.html
But you describe that you do perceive a latency difference.

My reaction is to someone who says you're unlikely to perceive latency difference when it gets better (lower).

Would you switch if ctrl-c wasn't reacting perceivably different?
New advancement of media compression seems always focusing on low bitrate, be it audio, video or image.

Which is totally fair given their applications, but I always wonder how much improvement they bring in high bitrate scenario. For example, are there codecs that have much better (perceptible) quality than Apple AAC 256kbps (or achieving similar quality at, say, 160kbps?) How much better are AV1 at 10Mbps compared to H265/264 (the improvement of H265 compared to H264 in "transparent" encoding was pretty disappointing IMHO).
"I do not guide my posts by what is financially beneficial but by what I believe is interesting or important or entertaining to the public,” said the owner of X.
Show HN: I made a discrete logic network card
Note the "mostly" and "typically". There are some amazing artists who really know what they're doing.

The chances of an artist having a PhD in machine learning and a masters at Goldsmiths are statistically speaking very low.
Apple extensively describes how "Find My" works:

https://support.apple.com/guide/security/find-my-security-se...
Thanks a lot for the kind words! It is always great and motivating to hear positive feedback from people. We are really glad our work is helping.
The argument is actually broader than what I expected from the title. It's not a matter of having to edit C code or Makefiles, it's a matter of having to edit any file (even a configuration file) that is shipped by the author of the program (or the package) and that can change. Then you are basically expected to maintain a fork.

I can't agree more with this.

Please make me edit completely empty files to override defaults.

Also related, it's painful when APT asks you what to do with an upgraded configuration file, just to notice that upstream edits are just mistake fixes in comments (hello Matrix / Synapse a while ago), or that self-closing XML tags have became totally equivalent but more verbose full, empty tags (WHY?!? Hello Collabora Online).

The moves to:

- let us expand the configuration in config.d folders

- ship default configuration files in system folders, outside /etc, config that you can overrides in /etc

are welcome. With the later, you can provide a fully documented default config file, and then I can override it, even commenting why I changed a value and these comments are not mixed with upstream documentation.
Nobody in their right mind expects truth from sales person. You deal with them to negotiate about price, not to inform yourself about a topic.

Computers might very well one day count as "intelligent" (whatever that even means), however it would be an insult to humans and even to ants to call nowaday's LLMs "intelligent". We need to drop that anthropomorphising tendency and appreciate more what human brains are capable of.