skysight-inc/HackerNews huggingface dataset:
From the paper, here is the core of the research:

We use rock physics models and Bayesian inversion to identify combinations of lithology, liquid water saturation, porosity, and pore shape consistent with the constrained mid-crust (∼11.5 to 20 km depths) seismic velocities and gravity near the InSight lander. A mid-crust composed of fractured igneous rocks saturated with liquid water best explains the existing data.

https://www.pnas.org/doi/10.1073/pnas.2409983121
Locking Up Items to Deter Shoplifting Is Pushing Shoppers Online
Does Datadog have a good remote policy? Will be interesting to see if any acquirer keeps it long term.

edit: I guess they do https://careers.datadoghq.com/remote/
>> and there was absolutely no indication of what caused it

That's the Accordion Effect.

With enough cars on the road, one little tap of someone's brakes flashes their brake lights and it ripples upstream until the 80mph column of cars is forced to go to down to zero ASAP.
That's one answer. Although manager technical expertise has to also come with minimal ego, so you can defer to your people when they know more than you.

The alternative is developing an intuition for bullshit. It's rarer, but I've had a few non-technical PMs / managers who were excellent at their job because they could suss out whether someone wasn't being honest.
No IBM?
Didn't that get reallocated to other cellular phones? AMPS band became GSM 850 and later LTE band 5 / 5G band n5.

TV above channel 37 has been reallocated for even more cellular phone use in two more chunks since then.

Cellular phones get a lot of bandwidth, but it's highly utilized.
It has always both surprised and dismayed me that transparent video on the web is still so damn hard. It's nice to see someone managing to make it work and then sharing their solution.
Like Lucy in the chocolate factory.
Nvidia broadcast does a pretty good job of deepfaking your eyes to look cat the camera... then again thats not as fun
Time to invent the musical keyboard which plays a different sound every time one presses a key.
Comparing Apple's Latest App Store in the EU to Google's Play Store Guidelines
System 76 has some AMD desktop / laptop options
https://system76.com/desktops

Sounds like its a no go anyway, but just in case this is not the one you already found.
Shit hits the fans
Good fit considering they’ve both embraced remote, preventing potential value destruction by an acquirer. DataDog also going big into cloud security recently with product releases, so perhaps a more engineering/dev focused Wiz “grow and roll up” play. DataDog and Gitlab combined would be worth almost $45B.
I smell lawsuit. Apple should not force a company to change their ways outside the Apple ecosystem for a chance to publish an app. I bet the EU won’t like this one.
Is the US Getting 'All Aboard' with Electric Trains?
I mean, 0xDDDB00B5 is about as appropriate in a codebase as 0xB166D1C5 or 0x73571C23 would be. Which is to say, it isn’t.
Please no! I already have parasites in my head!
More or less! Before that we basically had two kinds of jobs: one where Docker provided the job's dependencies and one where Nix provided the job's dependencies. The former was, naturally, always containerized, but the latter ran on bare metal. (We also had some jobs that used Nix without a persistent /nix/store, but never mind that.) Given both options, choosing Nix over Docker is really nice in two ways: (1) you don't need to deal with any infrastructure (i.e., push an image somewhere) for your job; and (2) even so, the second run and later can be really, really fast. We also use Nix to provide dependencies on our local machines for some projects, so just reusing that same environment in CI is a natural fit, too.

But as we started to mature our own CI 'infrastructure' (the automation we use to set up our self-hosted runners), I wanted to containerize the Nix builds. Using 'shell executors' in GitLab just feels icky to me, like a step backwards into Jenkins hell. Those jobs do leave a little bit more behind on disk. More importantly, though, while all of my team's Nix jobs use Nix in an ephemeral way, it is possible to run `nix profile install ...` in one of these bare metal jobs. That could potentially affect other such jobs, plus it creates a 'garbage collector root' that will reduce how much `nix-collect-garbage` can clean up a little bit. Our jobs are ones we'd like other teams across the company to run, and so we also want to provide some really low-effort ways for them to do so, namely: via shared infrastructure we host, via any Docker-capable runners they might already have, and by leveraging the same IaC we use to stand up our own runners.

To that end, we really want to have just one type of job that requires just one type of execution environment, and we definitely want opt-in persistence instead of a mess where jobs can very easily influence one another by accident or malice. But we don't want to lose the speedup! The real action in these jobs is small, so by sharing a persistent Nix store between runs, they go down from 2-10 minutes to 2-10 seconds, which is the kind of UX we want for our internal customers.

The new Nix image is more suitable for all three target scenarios: it's less risky on runner hosts shared by multiple teams, it still works normally (downloading deps via Nix on every run) on 'naive' Docker/Podman setups, and our runner initialization script actually uses Nix to provide Docker and Podman (both rootless), so any team can use it on top of whatever VM images they're already using for their CI runners regardless of distro or version once they're ready to opt into that performance optimization.
> The person in question is Tim Peters.

> It’s weird to not name them, but not linking to the thread is appropriate.

It looks like they're applying the Met Police standard: even discussing it in specific terms is "an offence" because of the potential for attracting sympathy for the offender.
The request/response optimization discussed in the first half of this post has been explored quite a bit in the context of Object-Oriented Programming and Actors, where the desired feature is called "Promise Pipelining":

http://www.erights.org/elib/distrib/pipeline.html

Outside of the E programming language and in the realm of language-agnostic tooling, you can find promise pipelining in some RPC frameworks, such as Cap'n Proto:

https://capnproto.org/rpc.html

Generally, this work comes from the Object-Capabilities community.
Actually, I'm very glad that Thompson, Ritchie, and friends used these strange names for the commands they implemented (supposedly because they didn't like to type long words). This leaves longer, more meaningful names open for me to use in naming commands I write.

In any case, (a) UNIX (as it was spelled then) antedates C, so it's more that the UNIX spelling conventions influenced C's development; and (b) lots of earlier and later programming languages have had mystical abbreviations. For example, ALGOL68 replaced “integer” with “int”, for reasons I have never understood; Wirth's original CDC 6600 had a data type “alfa”, which was a 10-character string; William Wulf's Bliss language had library routines with names like “getnum” rather than “get_number”. In PL/I, you can write “proc” for procedure, and “dec” for “decimal”.

Me, I prefer to program in a language that has primitive procedure names like “call-with-current-continuation”.
There is no realization of higher profit margins, though, which means that restaurants operating under that model also have to reduce their income in order to "save" on wages.

So, while a fun distraction, we're right back to you thinking that money in someone else's hand is better than money in your own. What is your rational? Conventional wisdom says that there is leverage in increased cashflow. Why is the conventional wisdom wrong?
It also reduces the value of debt.
Printable Board Game Templates (100% Free) – PrintableTemplates
survival bias is the last refuge of the modern architect

Abandoned power stations found in the middle of rural California built by nameless workers simply using pattern books are more aesthetically significant buildings than most high end projects today
Most animals get tired running very quickly too. A cheetah, just like you, also can't sustain a run at their max speed for very long (about 30 seconds max). But when it comes to endurance, very few animals come close to us thanks to how efficient we are. A lot that comes from us being bipedal, a good amount of our muscles being slow twitch, our ability to breathe independent of our muscle usage while running, and having a very high density of sweat glands across our bodies (10 times the density of chimps) giving us an efficient and superb cooling capacity.
I found the cave-like, scarcely trafficked bare concrete stairwells of the tall buildings oddly comforting: cool on a hot afternoon, perfect when my exercise regimen included stair-running, and sprinkled with chalked graffiti not suited for publication in the school paper.

Sample:

Ronald Wilson Reagan
\ | /
6 6 6
You learn it like a language and it soon becomes second-nature to refer to chowning, chmodding, catting, and fscking. Much better than that stupid lowest-common-denominator horridly verbose tripe that gets peddled today.
> For example, in one run, it edited the code to perform a system call to run itself. This led to the script endlessly calling itself. In another case, its experiments took too long to complete, hitting our timeout limit. Instead of making its code run faster, it simply tried to modify its own code to extend the timeout period.

They go on to say that the solution is sandboxing, but still, this feels like burying the lede.
If they can't trust their own build cache, they really have problems.
It's YC-aside, anyway. Just from a general founder perspective: there comes a point where repeatability far outpaces any growth hacks you put in place perviously. In that vain, I think it shows exceedingly good sportsmanship towards founders to switch someone who has long established repeatable business to someone who has just found it. If you give someone a chance right as they hit escape velocity PMF, I suspect you provide a considerable tailwind, certainly a very kind thing to do for any founder if you're able.
>> As a rider, Waymo generally feels safer than a human driver.

This was my experience too.

Way more smooth and smart about its SF driving than for instance, my elderly parents. It manages to be assertive without being aggressive.
You can definitely find an ebook, they're around. There are also some "worm scrapers" out there (search github), which are just scripts which scrape the site and compile the book.

I read it on my Kindle, it's way too long to read in any manner you don't find comfortable imo.
They got a good deal on EV Jags that weren't selling.
Show HN: Demo App for PLaMo-100B – A New Japan's 100B Parameter Language Model
> but zero value?

Value is the net worth of something. I judge it as negative because IMO if it didn’t exist we’d be better off which isn’t to say it has zero positives just that the negatives outweigh the positives.

Your free to disagree, but I think it’s a reasonable argument.
I don’t know if it’s my setup or just Windows quirks but even Alacritty feels slower than Windows Terminal.

You can also use Is It Snappy? from the App Store to test typing latency. It was made by Chad Austin who had problems similar to us.

https://chadaustin.me/2017/04/announcing-is-it-snappy/
Article title that I see is "Transport triggered architecture". Why the editorializing?
mutexes, in general, are considered to protect data. one associates a mutex with a piece of data. any number of bits of code might access that data, not just a single synchronized function.
Everything has to come with minimal ego. I don't see how that has anything to do with managers having technical knowledge.

And it's great if a handful of people can smell out bs in a field they're not familiar with, but you can't write policy on the back of a few unicorns like that. (Yes, managing ego is hard too, but I believe it's more common to start with and more trainable.)
Same, but s/Go/Scheme/g. For over 20 years now.
Auto-Generated Transcript of Musk-Trump Twitter Space
Most engineers aren't precise with throughput vs latency. Ideally you should report both figures (and anything else salient in performance-sensitive spaces), but it's less a lie and more an extremely commonplace mode of thinking and speaking.

Moreover, I think that mode of thought comes from the fact that most programming problems don't have hard latency bounds, so throughput dominates the conversation. If I'm spending 10us on average while handling a 10ms soft deadline, every single component can easily be occasionally 100x more expensive (latency) without me caring, and if it buys me another 1us on average (throughput) then I'll save gobs of money in compute.
IBM runs much of US banking and insurance.

Their hardware is actually fairly remarkable. If you have a certain kind of mission, it really makes sense to build a bunker around some mainframes.
You make a good point: if we’re always able to scale out the consumer, then we never need flow control to slow down the producer.
but death isn't a system or organism...
What about animated PNG?

https://apng.onevcat.com/demo/

Or animated webp?

https://mathiasbynens.be/demo/animated-webp

https://cobalt.googlesource.com/cobalt/+/refs/tags/trunk.unn...
There's a search feature?
with the money and power that's floating around the general US political sphere one would think they'd spend a few bucks more to distance themselves from one of the largest sociopolitical scandals of all modern history.
People doing all the work of dependency fetches, code builds, and test execution inside ephemeral environments never designed for building software within.
M&A w/ Bitbucket could also be interesting.

I don't dislike Github but prefer Bitbucket, I feel they're a bit underappreciated, in part due to the massive market share that Github has. This could help turn things around.
There are a few tragedies in the Docker story, but at least two are specifically tied to naming things. First, Swarm (mode) because by the time they released Swarm (mode) the world had already taken a collective dump on Swarm (the proof-of-concept). Even in 2024 most of the time people talk about Swarm and start dumping on it they're actually talking about the proof-of-concept architecture. Second, they should never have called the subcommand "build." It isn't building anything. In this case "build" is performing a packaging step with very raw tools. But the minute they called it build people started literally building software INSIDE intermediate container layers on the way to assembling a packaged container. Dockerfile is about as weak of a build tool as you could possibly ask for. Zero useful features with respect to building software. But Docker named it "build" and now we've got Dockerfile calling compilation steps, test commands, and dependency retrieval steps.
Only some of the market is end users. The rest is businesses looking to replace headcount and they don't care what users think.
So life as a system benefits from the randomness — but inevitableness — of death, is how I interpret that. Benefits as in, key to its continual perpetuation.
Solar PV with Battery Storage Cheaper Than Conventional Power Plants
The comm command is my favorite lesser know coreutils command https://blog.robertelder.org/intro-to-comm-command/
> Nothing stops me from self-signing apps or using websites only.

That is clearly not the same thing. Why don't you do the exact same thing? I mean, other than the monopolistic efforts holding you back.

(I recognize that you are trying to bring your own monopolistic definition to the table, and while I'm sure it has merit as a better definition, I fail to understand what value you think there is in trying to change the subject? Why not just stick to the topic in progress like everyone else, even if you don't love everything about it? The rest of us probably don't love it either, but that's not a good reason to toss the ball to the side in an effort to disrupt play because it isn't the brand of ball you have a preference for.)
I feel this, and not even in a situation that had complex transparency needs. I went down a path that needed the surrounding background perfectly matched to the video background, and it ended up being easier to render the video to a canvas, get the rendered pixel value, and update the surrounding background. Still necessary even knowing what the video background color should be given browser differences in rendering the video’s color. Prompted a fun conversation internally, though[1].

[1] https://www.mux.com/blog/your-browser-and-my-browser-see-dif...
Study: https://www.ise.fraunhofer.de/en/publications/studies/cost-o...
That's why Typescript is my hammer, unless I need a jack hammer, which is Rust.

With Deno and Typescript I get an even more versatile toolbox than with Go. And what's even more important to me, Typescript is safer and more ergonomic than Go, but slightly slower. Rust is safer, more ergonomic and faster than Go, but much harder to learn.

Especially strict (which is a must) Typescript is underrated. Compared to Go, we get:

- null safety

- widely supported generics

- discriminated unions with either manually (some lines of code) or es-lint exhaustiveness checks

- much safer concurrency, as all Typescript code runs single-threaded. You need web workers, which are not as safe as Rust for concurrency, but much safer than Go.

- collection / iterator methods

So far, I see only few downside. I'd be happy if people could provide more. Currently I'm scratching my head why I didn't fall in love with Typescript (for backend and CLI) earlier. Maybe I haven't seen the dark sides yet. So, some points where Go is stronger than Typescript:

- Go is much more efficient in terms of size and memory usage

- Go's GC is better than V8s

- Go is faster on CPU bound tasks

- Go has a greater std lib, however, Deno's std lib is pretty nice as well.

- The ecosystem is smaller, but has not as much trash as NPM. The dependency trees with NPM are usually large. By the way, Rust has this problem as well, less than Typescript but more than Go. Still, many mainstream NPM packages are safe and rock solid.

What else could we say against Typescript (and preferably Deno or Bun)? I'm really eager to hear people having ditched it an why.
Lol. He chartered it. He doesn't even own it. It doesn't reflect poorly on him at all. Do you check the history of every taxi you hire to make sure nobody evil ever used it?
Why can so few medium sized software companies succeed in the long term anymore? Why does everything need to consolidate to just a few companies.
> It will take 3-5 years for tools like this to mature. But it will happen, and hard fought skill sets like SQL database design, query design, and maybe even ORMs will become obsolete.

Until a query becomes a bottleneck and no one knows why because no one knows how databases work anymore.
Every key stroke has a unique sound signature. You just need to record it with a microphone that isn't terrible. For this reason a bugged room can be a bug in every keyboard in that room if the attacker is assumed to be sophisticated. There have been some projects which attempted this[1].

It may be hard to do a non-terrible DIY laser microphone that would allow to achieve this while targeting a non-laptop surface.

After you have the recording the biggest challenge is a problem solving one, you need to isolate the waveform for every keystroke, convert it to something that can be compared with other waveforms (and cluster them) and then solve the resultant substitution cipher (waveform -> key identity). If the keyboard was used for any length of time, you can assume the entry of common words and phrases occurred at some point and the solution to the cipher is trivial.

If you have the resources to collect the data, it should be possible to train a transformer model to convert an audio recording to the output of sound signatures belonging to key strokes of a keyboard or multiple keyboards. The trick would be to not try to train it to do the entire problem which will almost certainly fail or not generalize.

[1] <https://github.com/shoyo/acoustic-keylogger>
Feels like the next generation of models could truly start replacing lower level ML and software engineers
Well it is in a journal called "complexity." But I agree, that sentence is awful, I'm surprised they decided to lead with it, and nobody proof reading the paper objected.
Whenever I see this discussion come up my question is always: Why do you want to manually sort a giant list? I have never needed this. For smaller lists at the human scale (<1000 items), just use an integer. For larger lists no human should have to manually sort those anyway. Find some computational way of presenting the data to the human.
Because that’s the TAM without enterprise cross sell, which you only get once sucked up into the spaceship. Teams, GitHub, with Microsoft, Slack with Salesforce, Hashicorp with IBM, and so on.

You either grind and love the grind, and make peace with your slice of the industry (Automattic [$7.5B value], for example) or you sell out and up when you get bored or tired.
Comma has given up on self-driving cars and they're downplaying it now.
The switch from the Dualshock to the Logitech, as a system designed by students, demonstrates negligence that led to the catastrophe. Had the system not been designed by students, it would not use a wireless game controller. You could argue it in your head but in reality, which is part of the claim, no such system exists in any submarine.
They are starting to care about it after catching on to out how overstated the real world capabilities of AI are to actually replace headcount.
If they take VC money there are only two possible end goals. Go public or get bought. VC investment needs to be payed back.
But OpenAI said LLMs can't innovate until human-level reasoning and long-term agenthood is solved. [1] Referring to their precious 5 stages to classify AI before it reaches the scary "beyond" levels of intelligence... presumably at that point they get the feds involved to reg cap the field, so genuine is the fear of the pace they've set.

It's clear OpenAI is a hype company knocking over glass bottle stacks at its own wonderful carnival stall. Obviously if you can reason you can reason about what is innovative and we don't need OpenAI to set up fake scary progress markers like an Automated Scientific Organization.

Lets see if scientists even want this style of tech progress, it'd be sad to see each multitudes of AI papers having to be rebuilt from scratch and flushed down the toilet because associating with it is taboo.

[1]: https://arstechnica.com/information-technology/2024/07/opena...
Because I feel like most people have heard of CBT, but don’t realize that a “major version upgrade” to it is available.
No thanks. I want self-driving cars to obey traffic laws. It's bad enough people are incompetent.
Back in the 1970s, it was extremely common to buy a US-made brand-new car and have all kinds of major defects. It didn't matter that they were made in factories under "controlled conditions": the factories were poorly run, and the products that came out were junk. Dealers had large lots of cars that had just arrived from the factory and needed repairs before they could sell them. It wasn't until Japanese cars were imported in huge numbers, and had consistently high quality, that expectations changed.

The problem isn't factory vs. non-factory, the problem is culture. Many parts of American society have a culture of lying and cheating and making junk products and then lying to try to cover it up. Just look at Boeing.
Now I wonder what a machine learning model with risk seeking behaviour would look like.
update todos set pos = pos+1 where pos >= 3 ORDER BY pos DESC

Am I missing something?
White House Report Highlights Persistent Challenges and Urgent Needs in Open