skysight-inc/HackerNews huggingface dataset:
Most models are derived of Machine Learning principles that are a mix of classic probability theory, Frequentist and Bayesian statistics and lots of Computer Science fundamentals. But there have been advancements in Bayesian Inference and Bayesian Deep Learning, you should check the work of frameworks like Pyro (built on top of PyTorch)

Edit: corrected my sentence, but see 0xdde reply for better info.
Captain Beefheart music is the type of music you’re _supposed_ to like , but really doesn’t live up to its reputation.

Zappa music, otoh, reveals the genius behind it once you pay attention. Then again, half of his catalog is just self-indulgent wankery he himself admitted he funded through the juvenile songs.

Listen to “Inca Roads” or the whole “Zappa in NY” album and you’ll see Zappa’s greatness.
I think this is overly dismissive and pedantic. The person you're replying to is speaking more broadly, and presenting a hypothetical model where we would expect to see something that looks ostensibly like grade inflation, but isn't.

It's obvious that they understand this distinction, so I don't really believe your comment is all that constructive.

In the context of the subject article, it certainly appears that there was a sudden change based on a test-grading change and thus score inflation is indeed what happened. However, it's still possible that the former panel-of-experts system was inadvertently a more relative grading system which was slowly adapting to better pedagogical methods and better performing students. For what it's worth, I consider this unlikely, but it's an idea worth considering rather than dismissing entirely.
One person, IIRC, don't think anyone other than q3k was involved in CodiSec, and I think he left the company before proper development on Veles started (I think he was present when first talks about were happening and gave a lot of inspiration though, but isn't in credits for first open source version)
BitGrid is my hobby horse. It's a Cartesian grid of cells with 4 bit in, 4 bit out, LUTs (look up tables), latched in alternating phases to eliminate race conditions.

It's the response to the observation that most of the transistors in a computer are idle at any given instant.

There are a full rabbit hole worth of advantages to this architecture once you really dig into it.

Description https://esolangs.org/wiki/Bitgrid

Emulator
https://github.com/mikewarot/Bitgrid
I can attest that the frequentist view is still very much the mainstream here too and fills almost every college curriculum across the United States. You may get one or two Bayesian classes if you're a stats major, but generally it's hypothesis testing, point estimates, etc.

Regardless, the idea that frequentist stats requires a stronger background in mathematics is just flat out silly though, not even sure what you mean by that.
Curious, what's your profession? To me you do sound like a programmer.
There are people who live waaaaay out there and commute to their Silicon Valley job via a light airplane like a Cessna, quarterly, monthly, weekly, probably even daily. "Commutes, uh... find a way"
How do people even find the time to work on this stuff without being distracted by life, family, and everything else? I think this is why so many of these people are in Europe. America is too chaotic and full of obligations and distractions to do serious academic work.
It's interesting to see how different programming languages approach building software.

Languages like Lisp are all about planning out the whole program structure (the "Abstract Syntax Tree") upfront, kind of like a blueprint. But modern tools and visual programming often take a more piece-by-piece approach. You build smaller parts first and then connect them together, gradually building up the whole thing.

This bottom-up method feels more natural to how we solve problems in real life. Visual tools make it even easier because you can just drag and drop components instead of worrying about complex code structures.

I wonder if this kind of visual, incremental approach could make programming more accessible to everyone. It might help bridge the gap between our everyday thinking and the formal world of code.
Heckorator, a.k.a. why you should always check up on old unfinished projects
You're absolutely right, trying to walk a delicate tightrope that doesn't end up with me giving my unfiltered "you're wrong so lets end conversation" response.

Me 6 months ago would have written: "this comment is unhelpful and boring, but honestly, that's slightly unfair to you, as it just made me realize how little help the article is, and it set the tone. is this even a real argument with sides?"

For people who want to improve on this aspect of themselves, like I did for years:

- show, don't tell (ex. here, I made the oddities more explicit, enough that people could reply to me spelling out what I shouldn't.)

- Don't assert anything that wasn't said directly, ex. don't remark on the commenter, or subjective qualities you assess in the comment.
I fail to see any connection whatsoever between Maps and iMessage.

Regardless of what you think of iMessage, Maps is beta and it works on Windows in Edge and in Chrome.

So this is clearly not being restricted to Apple devices or to Apple browsers.
Animation solves this with onion skinning and I can visualize a number of ways you could use onion skinning and similar to diff two or more graphs.

https://en.wikipedia.org/wiki/Onion_skinning
> A world without marketing would still allow for products to be registered, reviewed, rated, and for people to talk about it. It would still allow you to have a website and a newsletter that people can opt into. The only restriction would be that you cannot pay for better visibility, reviews or references from influencers.

These are all forms of marketing, but not specifically advertising. I think what OP meant to say is "a world without advertising."
Pretty good read. Particularly the part about avoiding enshittification. I've never really thought about it, but there are in fact a few very valuable lessons that many of the world's biggest tech companies could learn from this chinese gacha company, as ridiculous as it sounds, because their leadership is clearly well above average.

Also, next time I see someone asking why they don't release more skins, I'm going to link them to this article because it provides a pretty clear explanation for that, too.
> are disabled

I'm a low-vision US citizen, and our piss-poor public transit here is a massive problem for me.
> there's not a great story for adding a second machine if the first one can't handle the load

I mean this is basically your redis situation right? Just with a very specialized "redis".

You could scale this out, even after the pretty massive ability to scale up is exceeded. Have some front-end servers that act as a connection pooler to your datastore. Or shard the datastore, and have clients only request from the shards that they are currently looking at.
just hire some third party to do this for you, it shouldn't cost too much

just ideally find someone who has done this sort of work for people like you before

also, consider using ramp.com as your corp card if applicable, def best tracking/rewards of all of them
With all those Intel shenanigans, I wonder what are the barriers for China to disrupt the x86 market? It has more to do with patents, or just lithography? With their current equipment, if they were to release homemade x86 chips in the international market, would they be able to compete at least in the low-end?
Computer floop noises. Nice.
I would actually be less worried. The support at paddle is much better than what I've seen from both stripe and LS. LS had decent support a year ago, but has really dropped off. Moving to stripe makes me excited about their product, but more worried about the support.
Definitely not budget cuts. School budgets have surprisingly little to do with educational outcomes. See Abbott districts in New Jersey for one of the starkest examples of this: https://en.m.wikipedia.org/wiki/Abbott_district

Despite having better per-pupil funding than the wealthiest districts in the state (thanks to a court order mandating increased funding) student performance has stayed the same and even worsened in these districts.

The single biggest determiners of school performance seems to be the level of parental involvement and the average IQ of the students. Well those, plus selection effects to bump up numbers: https://freddiedeboer.substack.com/p/why-selection-bias-is-t...
Shiny Beast is a great album
The problem with Hypercard is that it used an extremely restricted subset of English constructions. Once you got used to the limitations, it was fine, but could be very frustrating for users learning what sorts of phrasing Hypercard expected.

Allowing too large a subset of English ends up allowing more ambiguous statements and more user surprise. Also, more complex grammar increases the chances of mistakes in implementation.

My current experience with LLM hallucination makes it clear that at present, we can't just throw an LLM at the parsing and semantic analysis side of programming language implementation.
Disagree with you 100%. This is why music is subjective.
On the one hand having passengers go by rail is not good for carbon. On the other hand replacing freight rail with trucks is also not good for carbon.

There are few rail networks that manage to serve both well.
> Components like exterior walls and roofs were designed to have as simple shapes as possible (no complex hips or wall jogs), and

This is a traditional and eminently sensible approach that has been lost in the "McMansion" era.

Simpler roof shapes are not only cheaper to build, but also are far easier to deal and insulate, and therefore more energy efficient.

Instead, simple energy efficient design is today mostly used in some high end custom homes while production homes are often overly complex and inefficient, relying on oversized mechanical equipment to make up for poor design choices.

> rooms were arranged so that plumbing lines could be placed near each other to simplify pipe routing.

There's a simple method to quantify this known as the "hot water rectangle". On the house's overhead view, draw the smallest rectangle that includes all the hot water faucets and the water heater.

The size of the rectangle affects build cost, efficiency, and hot water delivery performance. In many large houses there is no consideration for this at the design stage, so they end up using (wasteful) hot water recirculation pumps.

1. https://www.greenbuildingadvisor.com/article/the-hot-water-r...
Former machine technician. I used to repair machines in factories. I’ve been lurking on hacker news for over a decade because I find the work of programmers fascinating, but my brain just doesn’t cope well with code. I do however, understand machines and control logic, so for me visual programming is a sweet spot.
Likewise joints that are repairing need to be utilized just enough so that blood and lymph circulation can bring nutrients and repair materials while carrying away by-products of repair thereby not letting it concentrate through sedentariness.
If 100 is average IQ, isn’t it more likely that a higher percentage of population enrolling in college has caused the average college IQ to revert to the average population IQ?

You might say it’s a distinction without a difference, but surely it’s a healthy trend for more than 10% of the population to have access to a college education. (120 IQ is 90th percentile.)
[dupe]

More discussion on official post: https://news.ycombinator.com/item?id=41071585
Knee jerk low effort references are funny?
Hah, that's the first thing I thought about. I had no ideea it was after a real story!
"I just use an array" doesn't solve the problem "What if the array is full?".

In fact it makes that problem acute. A linked list structure will degrade gradually as we shove more entries with the same hash into it, every look-up incurs a pointer chase down the entire list, slower is eventually unacceptable but we do get signs first -- but with arrays we're just screwed, in C it's pretty likely we end up with an illegal dereference or we lose data once there's no room.
I really appreciate blogs/articles like this. It really helps me get beyond the surface on things and I always learn something. Thanks for taking the time to share.
Champagne sales down worldwide in 2024, industry executives cite lack of 'cheer'
In other news the French rail systems suffered a major outage today, the opening day of the Olympics, as train infrastructure was firebombed by unknown parties.
Most quantile sketches (and t-digest in particular) do not assume stationarity.

Note also that there are other bounds of importance and each has trade-offs.

T-digest gives you a strict bound on memory use and no dynamic allocation. But it does not have guaranteed accuracy bounds. It gives very good accuracy in practice and is very good at relative errors (i.e. 99.999th percentile estimate is between the 99.9985%-ile and 99.9995%-ile)

KL-sketch gives you a strict bound on memory use, but is limited to absolute quantile error. (i.e. 99.99%-ile is between 99.9%-ile and 100%-ile. This is useless for extrema, but fine for medians)

Cormode's extension to KL-sketch gives you strict bound on relative accuracy, but n log n memory use.

Exponential histograms give you strict bounds on memory use, no allocation and strict bounds on relative error in measurement space (i.e. 99.99%-ile ± % error). See the log-histogram[1] for some simple code and hdrHistogram[2] for a widely used version. Variants of this are used in Prometheus.

The exponential histogram is, by far, the best choice in most practical situations since an answer that says 3.1 ± 0.2 seconds is just so much more understandable for humans than a bound on quantile error. I say this as the author of the t-digest.

[1] https://github.com/tdunning/t-digest/blob/main/core/src/main...

[2] https://hdrhistogram.org/
London's system is very old so basically it's loud because it's built with much tighter curves than a modern system would be built with today, plus there are few platform doors isolating noise away from people on the oldest lines.
While scrolling, I misread that as - "What it's like to dissect a cab driver" - and was like, huh?

I guess it's time to renew the prescription for my reading glasses.
I understand the war between bayesians and frequentists. Frequentist methods have been misused for over a century now to justify all sorts of pseudoscience and hoaxes (as well as created a fair share of honest mistakes), so it is understandable that people would come forward and claim there must be a better way.

What I don’t understand is the war between naive bayes and pragmatic bayes. If it is real, it seems like the extension of philosophers vs. engineers. Scientists should see value in both. Naive Bayes is important to the philosophy of science, without which there would be a lot of junk science which would go unscrutinized for far to long, and engineers should be able to see the value of philosophers saving them works by debunking wrong science before they start to implement theories which simply will not work in practice.
> mountaineering oriented

One would think hip designs be integrated to lighten backpack load.

From article:

>We heard a lot from people who felt self-conscious, who didn’t want a brace or walking stick but loved hiking poles and things that looked like [outdoor] gear

Rule of cool. It does look very cool though.
I believe you've just restated GP's point regarding the fall in IQ.
> Edit: It also strikes me that we have something even better today - pre-fab or "mobile" homes that can be delivered by truck to a suitable plot of land.

This author did a series about that as well: https://www.construction-physics.com/p/the-rise-and-fall-of-...
> If several things are at risk you can see which ones have more critical time constraints and allocate resources effectively

Hum... Have you used them that way? And have you needed a project design to actually discover risks and estimate that you need to act on them?

Or better, have you found any unexpected risk on a project design, and seen it materialize on practice?

> If something slips you know how to update your estimates for everything downstream.

And then your renewed estimates will be wrong again. No idea if more or less wrong than before your revision though. It can go either way.
That ship has sailed. C and C++ have macros so that line may do actually anything.
"So Lisp, even with macros, is not that bad."

Agreed in the general sense, which is why I chose Python for my example, for clearer contrast.

I would say there's still a qualitative difference between languages where there is some well-defined, concrete procedure where you can take a line of source code and resolve exactly what it is doing, and a language where said resolution of what it is doing involves arbitrary code execution between the source code and what the code is actually doing. Python is frankly insane in some ways, but you really only need one place where arbitrary code is being invoked, and I mean this in the nicest of ways but Lisp programmers are fully capable of driving a truck through even that one particular hole.
It's memory bound and single threaded?
This reminds me of the article discussed here a few weeks ago that Wine Sales are down in California:

https://news.ycombinator.com/item?id=40947332

I think consumers are turning to other beverages - spritzers, seltzers, mixed drinks, etc vs wine and champagne.
But Triton is just abstraction over CUDA for Python (same like cupy, numba etc.).
If you need low lvl access you still will use CUDA if you want high level you can use Triton or numba even higer you'll just use wrappers like pytorch/jax.
Why'd you disable right clicking and highlighting?

Edit: If you're not the author of the post, feel free to ignore :)
A few things I wish I knew when took Statistics courses at university some 25 or so years ago:

- Statistical significance testing and hypothesis testing are two completely different approaches with different philosophies behind them developed by different groups of people that kinda do the same thing but not quite and textbooks tend to completely blur this distinction out.

- The above approaches were developed in the early 1900s in the context of farms and breweries where 3 things were true - 1) data was extremely limited, often there were only 5 or 6 data points available, 2) there were no electronic computers, so computation was limited to pen and paper and slide rules, and 3) the cost in terms of time and money of running experiments (e.g., planting a crop differently and waiting for harvest) were enormous.

- The majority of classical statistics was focused on two simple questions - 1) what can I reliably say about a population based on a sample taken from it and 2) what can I reliably about the differences between two populations based on the samples taken from each? That's it. An enormous mathematical apparatus was built around answering those two questions in the context of the limitations in point #2.
The state of the art has moved well beyond these algorithms. See these

https://github.com/tdunning/t-digest
https://www.sciencedirect.com/science/article/pii/S266596382...
https://arxiv.org/pdf/2102.09299

And, as I mentioned else-thread, exponential histograms are the best choice in almost all practical situations.
You're not really making a lot of argumentation to back up your claims. C#'s TPL is ok, but it comes with a massive overhead compared to Goroutines where you can have millions of concurrent threads running at the same time, which is just immensely useful when you're dealing with lots and lots of data. Like gathering solar plant data from millions of inverters. On top of that Go comes with build in channels to ensure safe synchronization between your Goroutines. It's not that you cannot write concurrent code in C#, but to do so will involve a higher level of complexity as well as a much higher cost in memory usage and the risk of encountering deadlocks.

For us the major advantage is that it's much more efficient to spread out the computation on multiple CPU's rather than relying on OS or thread pool threads while also lowering the risk of someone writing a bottleneck when they are coding on a thursday afternoon after a day of horrible meetings.

> GitHub statistics

I think Github statistics are meaningless. My github repository is 100% rust. I very rarely use Rust professionally. In fact, I've done precisely one proof of concept before we decided it was too much trouble to adopt it instead of our C++. This may change in the future if the Rust "community" matures. In any case I mostly look at job "statistics" for my area of the world and while Go has been adopted at some of the places I might want to work, it's still a drop in the ocean of java/c#/php/python.
Also wondering this. I was planning on making the jump to LS soon but if Stripe will be offering MoR services then I'd rather stay within Stripe's stack.

I suspect (hope) Stripe Tax will soon offer a MoR service. I imagine this acquisition is mostly for their tax expertise & perhaps internal tools that do all the hard work behind the scenes.
> is there a specific reason you're not using plain-vanilla filesystems which _are_ stable?

my personal reasons are raid + compression
The same can be applied to a stock market. I am a big fan of looking into historical data, and I was using WealthLab for quite a while.

One of the funniest things is when you find "strategy" that performs best over one year by making from 50 to 100 deals. But don't get fooled, it's just a random parameters, and when applied to the next year or years, you won't get these results, of course.

So you're getting reliable results only when you can reproduce your success (no matter what it is) consistently.
When I was self diagnosing, my Google queries were simplistic.

E.g.

resistant hypertension many medications

Which led me to a couple of research articles about pheochromocytomas and a Washington Post article about someone with high blood pressure on a "bucketload of medications".

e.g. https://www.washingtonpost.com/health/2022/04/23/high-blood-...

If the LLM can provide a sample Google-like analysis, data points that my 7 specialty doctors missed, that's an improvement.
This might be a good reason to support trigraphs again! https://en.wikipedia.org/wiki/Digraphs_and_trigraphs_(progra...

edit: fixed link, copy paste fail dropped the ++
Right, and then the question is "is my specialized datastore gonna be faster than Redis" right? And it seems totally reasonable that you could make something faster eventually - but I think it's not a reasonable goal within the timeframe of the go rewrite (one Sunday afternoon and evening). Especially if you want to extend that system such that other services could talk to it!

The entire timeframe of this project was 2 weeks, and the critical period (most activity / new eyes) was a couple of days.
There is a lot of overhead when it comes to building out a factory supply chain for scalable parts, because factories are large sunk capex costs, particularly for large items. And manufactured housing often does not make sense because if you manufacture whole rooms, unless you get special vehicles and delivery permits you are limited to the dimensions of a container, and there's a nonzero chance you show up to the site and you have to do some fiddling anyways to get it to actually fit. Plus people are not actually looking for identical room sizes.

Probably the closest we'll ever get is to standardization of parts like the 2x4 or some of the insulation panels that exist nowadays, since you can flatpack those into a truck and make adjustments on the fly.