skysight-inc/HackerNews huggingface dataset:
The file API is mostly fine. Opening with that is the wrong approach to me; the comparison with Rust doesn't really illustrate any serious issues. All of the complaints could be addressed with better documentation.

The time API, on the other hand, is that bad, and worse. Besides the bizarre monotonic time implementation, there's also the bloated size of the time.Time struct, and the lack of actual "dates" (YYYY-MM-DD) and "times" (HH:MM:SS) that you can do arithmetic on. You can't really roll your own robustly either because time.Time isn't a great foundation to build on and //go:linkname is getting locked down.

Thankfully, build constraints are much better now, since they just use regular boolean operators, e.g.:

//go:build windows && (i386 || amd64)

I agree that there shouldn't be any _buildtag.go magic, and I think they ought to remove that "feature" entirely in a future version of Go (which can be done so that it doesn't affect older or unversioned code). It seems they added a "unix" build tag too.

Also, one of my personal gripes is that the standard library exposes no guaranteed way to access the system CSPRNG. Any code can replace (crypto/rand).Reader with another implementation and compromise cryptographic operations. It's a trivial supply-chain attack vector, and even in non-malicious scenarios, it can be done mistakenly and break things all over the place in a subtle but dangerous way. The language developers have so far refused to fix it too.

Then there's log/slog with no TRACE or FATAL levels built-in; yeah, you can roll your own levels, but why should you have to?
Apply to the Fellowship for Maintainers
Lego Ideas: Working Turing Machine
Good lord the work that went into this is humbling.
This is a great alternative to Pocket or other read it later type program.
Would be great if HackerNews had a save to Omnivore button next to each story.
The point on interpretability is scientific applications is in symbolic regression - MLPs cannot always spit out an equation for some data set: KANs can.
That's shifting the goalposts somewhat! Can Haskell be used for LOB software. Yes! In fact it's the one I am most effective in for that purpose. If I was starting a startup, it would be in Haskell, no question. "Let's suppose that you and I are non-technical founders of some medium-size software product ..." Well, that's something else entirely.
Syncing Basecamp Card Table and Google Sheets
When you're uber-rich I guess you want something no commoner can do.
The choices thing is interesting. I go both ways on this. Some of the story choices lead to places you don't want and didn't foresee. Part of me wants the story to go where I want it to go and thus I will wiki the conversational choices. Part of me loves that this is a story and stories can take your characters where the story takes them. In life we make all sorts of "conversational choices" where the ramifications long in the future are hard/impossible to foresee but profound.

Overall though I love the game. Nothing is perfect but this game is a blast and kudos to the developers more making something so deep, interesting, and fun.
Jane Street famously uses Ocaml, which is, granred, not F# but closee enough/
A slightly different take.

If everything is either an obvious sketch, or pixel perfect you can get decent feedback, but a design that is just a little off in jarring ways will distract people from the functionality or design intention.
After Shark Tank, Mark Cuban Just Wants to Break the Prescription Drug Industry
IIRC, performance was fantastic, but they were never able/willing to match the data density and data cost improvements in stacked-NAND flash, and without forcing themselves into the market at competitive rates, nobody wanted to write applications or design hardware suited to their unique strengths as low-latency caches.

There is still, to this day, a numerical niche for these drives, which is being served imperfectly by either normal TLC drives of very large size, SLC cache drives, or DRAM expansion cards connecting to the CPU through a PCIE bus. Just not at the prices they wanted to charge.
It specifically kills the pigment cells within the follicle, causing the hair to grow back white [1].

If this case study [2] is anything to go by, then it would seem it isn't that effective on humans.

[1]: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC1494747/

[2]: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8166665/
https://archive.is/juv2o
If we're looking at its emissions with all those downstream requirements involved too, the point of comparison would be all the emissions involved in everything that the average American relies on, which is certainly not just 16 tons.
I remember in the early days the idea of not having physical copies and trusting Steam to continue to provide access to your content was quite a hard pill to swallow for a lot of people. It's somewhat ironic that while they paved the way, they have kept a good reputation while others that followed have abused this trust.
True. It is not totally useless. There's a lot of utility.
It's called System Management Mode, it's in official Intel documentation for x86.
I was sorta dismissive of the Vision Pro when they came out.

But then I did a demo of them while waiting for a repair and it was so impressive it was almost like a religious experience.

It almost felt like a veil had been lifted and this was some glimpse into the future and for the next couple days my mind was racing with ideas about what sort of societal changes would come about from this kind of device.

With that said. I’m not about to drop 3500 bucks for one.
What they really needs is competition through the reduced cost of switching for users. Today, you lose your friends, follows, and history if you wanted to move to another social media app.

With Bluesky / ATProto, this is no longer the case. They have also made the algo and moderation pluggable, so you have choice before you feel the need to move. It's actually even better because all the apps store your content in your atproto database, each user has a dedicated sqlite
This reads more like how to get more bang from your content buck by upcycling social posts into a newsletter or blog, which in itself is a good idea. I like the process for turning in the moment comments into a more structured article.

That said, I am a little disappointed because I expected the article to be more about encouraging people to integrate social posts into a website and keeping old content available despite seo pressures to get rid of old stuff. As far as I'm concerned, I won't shut down old blogs and they still serve their niche purpose for new visitors 15 years later even if I don't add new content. I wouldn't put this much effort in a newsletter that no one new can access past sending... that seems like as much waste to me as a message in slack, except more effort was put in.
I can't imagine it's a standard thing.

On X86 we have ring 0 and 3, with 1 and 2 never used and removed in newer CPUs. ARM has 3 or 4 privilege layers, but they're named differently.

They probably just called it ring -2 because it's a couple layers below ring 0.
React, Angular, (Vue, and others) "failed" because they are too different and never gained universal adoption, yet they all solved the same problems. At my company I have seen the churn from JQuery, then AngularJS, then Angular, then to Vue, every few years. These were all major rewrites. That's the failure. You couldn't just do a simple upgrade with a few breaking changes. If hiring managers are looking for experienced React developers, but won't accept a Angular dev, (or vice-versa) that is a failure, too. You shouldn't have to "bet" on a technology stack and hope it continues to stay marketable, is the point.
the traditional NASA suits are also absolutely massive and would make fitting people into the crew capsule very difficult
> If you can't take criticism without the blame-game, you're not worth my time and effort.

QFT
It's not too dissimilar, that said, SQLite is much more performant than Jet (MS Access) for mostly read scenarios. Not to mention that computers and disk speed are much better today than decades ago, where Access use was larger. You can pretty easily hit tens of thousands of rps with SQLite and probably even Jet for mostly-read usage.

Most applications don't have even hundreds of thousands of simultaneous users, so SQLite can be a great fit. Where SQLite also shines in that it has clients in just about every platform/language you're likely to want to use.

Archival/backup/portability are also very nice use cases for SQLite. I've worked on projects where there are specific, time-boxed data input and had actively pushed for using SQLite per box and still feel it would have been better. Vs having a very complex schema with export/archive functionality as custom code. My idea would have allowed to simply copy a file as archive/backup and schema changes over time would not necessarily need to be accounted for as deeply.

YMMV, but it's definitely a decent solution for many problems. Much in that using PostgreSQL or another RDBMS is often a better solution over using a more scalable no-sql option for most applications. There has been a tendency to over-engineer things, and we're approaching a level of compute/io that is less and less likely to justify those efforts.
The (state-owned) power company owning the grid and much of the generation for the country has been pushing this change forward. The country has transitioned from almost pure hydro to wind and has an excess of this type of generation, especially at night when it would be the ideal charging time.

There's also initiatives to encourage permanent grid use by the cars since the batteries can provide capacitive load which locally counters the grid's natural inductive load which is beneficial if it can be leveraged.
You can figure it out, but likely with a lot of questions. Why did you do it this way vs that way? What were you thinking here? Why does it appear this was "hacked" in? Bring in a new developer that doesn't completely understand your thought process and the code just gets worse and worse over time. I think you're oversimplifying.

You should absolutely learn the language, but reinventing the wheel on every project is not the way. And if you're not reinventing the wheel, then all you've done is create your own framework that only you know the ins and outs of. Sounds more like you're looking out for your own job security than anything.
Opt-in is better than nothing, but in practice I assume this sees little use because it breaks compatibility with old code. Null safety (and type safety in general) has to be present in a programming language from the start; it can't realistically be added as a feature later.
I'm not really making a judgement about their competence, the results just didn't turn out well. I think these things are indeed very difficult. To hazard a guess about the competency behind this, they had some people filling double roles doing the fashion of the suit. That they essentially asked an engineer with a side gig as a designer to make it.
Do you literally paste a wall of text (source code of the filtered whole repo) into the prompt and ask the LLM to give you a diff patch as an answer to your question?

Example,

Here is my whole project, now implement user authentication with plain username/password?
Yes. The point being they don't have a orbital vehicle yet
> a cringey Klaus Schwab windows machine

Say what? haha
I learned touch typing on a good mechanical keyboard. It is good to not have to think about pressing the right buttons, and the time can be used for thinking, your fingers become extensions of your brain. It is a strange sentence fragment that makes sense if you know touch typing. I just avoid laptop keyboards, they are just terrible for productivity work, they're awful without exception.

Commit frequently, and pushing my work to Github. It allows private repos so not everything needs to be shown. It may not be useful now, it may be throw away, but I might be doing something else one day and realize I've got a snippet or some learnings in that other repo, so I can go reference it. On the other hand if I made a script or utility for myself, no harm in making it public. Even if there's nobody using or even looking at it. Doing this makes me conscientious about my repos and project structure.
No doubt that is true, but are there particular batteries you’re thinking of?
Google had a library like that, and one of the foot guns is that requests that are malformed or otherwise do 0 work have incredibly low cost, which results in them being prioritized above all other requests. Every user had to configure some obscure options to set cost multipliers based on return code to try and correct for this, which felt like a pretty fundamental bug that was being hacked around.

Edit: this was actually for cost-based load balancing, not load shedding. You obviously can't load shed based on return code.
Yes, this is a great idea. I grew up with a similar pattern where streets are mostly east-west and avenues are mostly north-south. But whenever I have explored new cities there always seems to be hidden patterns unique to that place, or at least new to me. And figuring out what they are sometimes takes more time than a short visit.

An example that bit me once, before smartphones and widespread gps, is that numbered streets and avenues in Phoenix both run north-south. The numbering gets higher in both directions as you move away from Central Ave, so the smaller numbered streets/aves are relatively close to one another. Very simple pattern indeed, but it was very surprising the first time I encountered it, didn't match my expectations I guess.
Yes, but how do you chain them?

map(func4, map(func3, map(func2, map(func1, iter))))

vs

iter.map(f1).map(f2).map(f3).map(f4)

I made up the syntax for the last one, but most functional languages have a nice syntax for it. Here's F#:

iter |> f1 |> f2 |> f3 |> f4

Or plain shell:

command | f1 | f2 | f3 | f4
...we're not talking about force-feeding someone a fifth of whiskey here.

A stable, thoughtful, trained scientist, in the company of supportive and emotionally intelligent colleagues, does not present a significant risk when fed a normal dose of LSD.
I would be _very_ interested in a "Hat" which would allow connecting such a display to a Raspberry Pi....
> Space tourism on the other hand is a different thing in my opinion.

Space tourism is funding part of the R&D required through for new space to be able to do exploration.
Seems like it's pretty high-priced for a product aimed at beginners...
> Treat your overreaction to social cues as irrational, and deal with it accordingly.

This is so smart.

Even broader, take your overreactions to most things as irrational. I am using this recently to rewire myself on all sorts of things and it's quite transformative.
> Talking about "technological and political issues" without mentioning any

I don't know why you think none were mentioned - to name one, they link a GitHub issue created against the systemd repository by a Googler complaining that systemd is inappropriately using Google's NTP servers, which at the time were not a public service, and kindly asking for systemd to stop using them.

This request was refused and the issue was closed and locked.

Behaviour like this from the systemd maintainers can only appear bizarre, childish, and unreasonable to any unprejudiced observer, putting their character and integrity into question and casting doubt on whether they should be trusted with the maintenance of software so integral to at least a reasonably large minority of modern Linux systems.
I am curious if Diamond has ever done an apology for his incorrect Easter Island theory in Collapse.

As I understand it, at the time it was a reasonable conclusion (though even back then it was still highly controversial and lots of scientists disagreed), but in the decades since, it's become obvious this "ecoside" theory is wrong, and this latest study puts the nail in the coffin.

So has Diamond ever said "There is new evidence, and I was wrong"? Or is he doing that weird thing that humans often do where they double down on a now obviously incorrect theory because admitting fault is somehow too painful?
Video for those who can’t get past the paywall

https://youtu.be/DPYT8IH-R18?si=5tcQ3NJltxROJDUq
The claim of "extremely thin evidence" for the transmission of Kerala mathematics to Europe by Jesuits is far from accurate. In fact, there's a wealth of circumstantial evidence supporting this possibility. Jesuits were present in Kerala from 1540-1670, with many, like Matteo Ricci, being highly trained mathematicians tasked with studying Indian sciences.
We have clear documentation of their interest in local mathematics, astronomy, and timekeeping, even incorporating subjects like jyotisa into their curricula. Numerous examples show Jesuits actively gathering and transmitting knowledge, from Ricci's inquiries about Indian calendars to Schreck's astronomical observations sent to Kepler.
Their close relationships with the Court of Cochin provided access to valuable mathematical manuscripts, and there's evidence of collaboration with Brahmins in translating Sanskrit works.

The Jesuits were strongly motivated by practical needs in navigation and calendar reform. Moreover, Marin Mersenne's extensive correspondence network demonstrates that awareness of Indian mathematical knowledge was circulating in Europe. Intriguingly, there are methodological similarities between Kerala mathematics and later European developments, such as parallels between methods used by Wallis and those in the Yuktibhasa.

I believe it's crucial to consider the historical context of knowledge transmission between cultures, which often involved clandestine methods. A prime example is the case of Robert Fortune, a Scottish botanist, who in 1848 undertook a covert mission for the British East India Company. Fortune, disguised as a Chinese merchant from a distant province, infiltrated China's heavily guarded tea-growing regions. His objective was to acquire tea plants and seeds, along with the closely guarded secrets of tea production. Fortune's mission was successful; he managed to remove thousands of tea plants and seeds from China, effectively ending the Chinese monopoly on tea production.
This act of industrial espionage had far-reaching consequences, leading to the establishment of vast tea plantations in India and Ceylon (now Sri Lanka), and fundamentally altering the global tea trade. While this example pertains to botany rather than mathematics, it illustrates the lengths to which nations went extract knowledge.

(Source: Joseph, G. G. (2011). The Crest of the Peacock: Non-European Roots of Mathematics (Third Edition). Princeton University Press.)
It's weird everything after the slash seems to be ignored. You can type anything and it still goes to the home page. funky.
Of course it did, it was less than 14 kB.

But in all seriousness, this sort of site is what I wish more sites were like. No ridiculous JS rendering engine, or 11 billion AJAX requests to 3rd party servers, just simple HTML and CSS.
That monkey god game (Wukong something) also just came out this month and it's become one of Steam's most played games ever.

And of course Tencent also owns part of Path of Exile, Epic Games, Discord, Roblox, etc.

China used to own AMC Theaters too, and still owns some Hollywood studios like Legendary (Batman, The Hangover, Pacific Rim, Interstellar, etc.) through the Wanda conglomerate.

While we're talking about pop culture, China is just quietly buying up America piece by piece...
The speakers for the Open Source Observability Day on Oct 24 have been announced
Everyone here is talking about the life of either drives or and media.

The key point ought to be that data must be regenerated within a specified period to avoid bit rot (through loss of remanence).

No matter how many backups you have if they're all made at the same time then they should all be regenerated at the same time (and within the storage safety margin period).
Not just HN, Cardano's smart contract language, Plutus, is based on Haskell.
There isn't really a need for a competitor to Starliner or even Crew Dragon, because they were both designed for LEO re-entry.

Crew Dragon in particular was overbuilt for LEO so that it can be used multiple times. While lunar re-entry is indeed possible, the vehicle wasn't designed for more than a one off mission.

The missing link is a low cost reusable crew vehicle designed for carrying people between LEO and NRHO/LLO. Basically a competitor to Orion.

While it is true in theory that a Starship could carry people to the moon and land them directly on the surface, the return trip isn't that easy and basically boils down to a second starship picking up astronauts from NRHO.
No, not necessarily.

Trivially, in a monopoly, raising prices infinitely for a product does not maximize profit.

SpaceX has effectively had a monopoly on commercial space launch since it was first able to actually use reusable rockets. Because the innovation of reusing rockets has brought the marginal cost of launching so far down prices will continue to go down.

Right now SpaceX is supply constrained, not demand constrained. All of their launches are booked. As SpaceX's supply increases they will be able to bring launch costs down even further until they hit an equilibrium of monopoly pricing that does maximize profit.
For reference (in case it's helpful), my website (where this essay is hosted) is written in Haskell and is basically a fairly simple webserver.

For the "hello world" webserver, this might be a bit instructive: https://github.com/gfarrell/gtf.io/blob/main/src/GTF/Router....
I was excited to order that until I saw:

>32"-diagonal reflective TFT LCD
>1920 x 1080 resolution
Fediverse Discovery Providers
I've found that with a traditional RDBMS that schema and query structure often count for as much or more over specific tweaks. I have pushed for using a single-node CockroachDB configuration for local/development instances and then using hosted (cloud provided) PostgreSQL for production. The use of CDB is to allow for the potential of future scaling as needed, where PG is more widely available in an externally supported means from the start with CockroackLabs (cloud) as an optional step as well as self-managed.

Just my own $.02, you can definitely tweak an RDBMS, but it's definitely going to vary by use case and more work can definitely be needed (indexing in particular is a bit of a dark art).
If you receive free software funding, does this then make you liable for 15 million euro fines for the CRA if you become non-compliant on a security issue ?
I'm not sure if this applies to smaller parts like this, but traditional aerospace suppliers are allergic to iteration. Everything must work the first time. You can see this in how many rockets SpaceX has blown up vs. how many ULA has blown up.

I imagine it's similar to what we see in software, where we see mega-waterfall projects delivered for the government cost way too much and still fail, and where tech companies & literal hobbyists can deliver higher quality software more quickly by avoiding an overbearing planning process.
Yes, that seems worthwhile to do - I was just replying to the notion that the direct emissions of the rocket during launch is the limit of emissions. SpaceX is also highly integrated, so I do think the construction and ground operations cost (for everything SpaceX did that would not have happened had this mission not launched) are worthwhile including.

My feeling is that the scale of rocketry isn't large enough that 28k tons of emissions makes a difference vs, say, the much greater number of private helicopter & jet flights (or single-use plastics, or growing & watering crops in a desert, or any of the crazier things we do as a species)