skysight-inc/HackerNews huggingface dataset:
> (I agree some lead time / attempt at coordinated disclosure is preferable here.)

Then I think we are in agreement overall. I took your initial comment to mean that as soon as you discover a vulnerability, you should make it public. If we agree that the process should always be to disclose it to the project, wait some amount of time, and only then make it public - then I think we are actually on the exact same page.

Now, for the specific amount of time: ideally, you'd wait until the project has a patch available, if they are collaborating and prioritizing things appropriately. However, if they are dragging their feet and/or not even acknowledging that a fix is needed, then I also agree that you should set a fixed time as a last ditch attempt to get them to fix it (say, "2 weeks from today"), and then make it public as a 0-day.
It’s kind of like Java. It’s a way to feel like you’re doing work without actually doing anything
This is really disappointing. You'd expect the opposite (the platform becoming more capable and versatile) but I guess Apple's understanding of "better" is not the same.
It starts with being able to tell that the information was encoded correctly when I submitted it.

Tell me this: what is the advantage of a barcode, over a scantron-esque system where I can see which item I chose because a dot is filled in?

The scantron-esque system is still efficiently machine readable; we've had scantron since I was a kid. The difference is, I can verify with my own two eyes that the information is encoded correctly on the ballot I submitted if it's done scantron-style.

I cannot do that with barcodes.

It adds another layer of safety. Do we still have to be able to trust the rest of the system? Yup. But I cannot trust anything at all if I cannot even verify that my vote was submitted correctly in the first place.

JMHO.
Find and fund a hobby, something else that drives you. You'll need that job to pay for it.

But really though, just show up to the interviews, sometimes you're a shoo-in and don't know it.
For reasonable reasons in my view.

The actor model is imo a great way of doing concurrency in the absence of the data race guarantee that safe rust provides at compile time. If you know you have no data races, I don't think actors give you that much.

That said, some people just really like actors as a mental model and/or they want to interoperate with actor-based systems written in other languages or provide an actor substrate written in rust that will be embedded into another language perhaps? It's definitely a niche usage.
Depends on your age. In this study, in those under 40 with obstructive coronary artery disease, 58% had a CAC of zero. So it can be a dreadful risk marker in some scenarios: https://jamanetwork.com/journals/jamacardiology/fullarticle/...

Your Dr Davis just appears to be one person saying something is the case, without providing any evidence for it. I don’t see why we should believe his claims that serum cholesterol is irrelevant over the incredibly robust evidence I’ve brought to the table.

I agree that the two things don’t add up, but why wouldn’t we then just favour the higher quality evidence? Seems like Davis is a quack with historical form for just making things up without any evidence in order to sell a product: https://www.healthyeating.org/blog/detail/rdn-s-book-review-...
> What was the energy requirements to manufacture the solar panels? To clear the site? How much ecosystem was bulldozed to put that many panels in?

Funny how nobody asks that about coal plants, oil processing plants, oil well, fracked areas, etc
> But honestly, I think the whole idea of being able to prove how you voted being dangerous is overblown.

Well you’re wrong.
WebGL is like letting your browser use your GPU with a condom on, and WebGPU is doing the same without one. The indirection is useful for safety assuming people maintain the standard and think about it. Opening up capability in the browser needs to be a careful process. It has not been recently.
Why are we so crummy? Is it because our talent finds it generally easy to migrate to the states for better opportunities, because of no language barrier and the ‘coalition of the willing’ visa (iirc)?
They're communists but they're capitalisting better than the actual capitalists, and you're advocating for out-communisting the communists.

Protectionism doesn't work, because you can block them from selling in your country's market, but you can't block them from selling to every other country in the planet. Meanwhile, tarrifing their cars will be as effective in helping domestic industry drop prices as it was for Harley Davidson since the 1970s (who received "temporary" protectionism).

This isn't a result of some evil communist plot, China just had their shit together 10-20 years ago and are reaping the rewards.
Hokusai’s prints do not belong on canvas, please don't do that, paper is fine.
And I'd bet that after you left, your system was ignored or fell apart while those "chaotic" employees with their spreadsheets just kept chugging along fine.
The best analogy is a toaster

Is it really that hard to grill bread? Nope, but you have to pay attention somewhat to stop it burning.

Once you hit a certain volume of usage, an automatic device makes a lot of sense.
How do you explain the fact that car manufacturers can and do build plants in Mexico and use cheap labour there, but still can’t compete with Chinese manufacturers?
Labour cost isn’t the problem, the problem is that US innovation has stagnated and now his to rely on protectionism to compete.
I’m quite sure that Babbage is the wrong person to use to illustrate the point I think you are trying to make.
New Horizons is slower than Voyager 1, and is also decelerating more. New Horizons will never pass the others. Voyager 1 is the fastest probe in an escape trajectory.

https://en.wikipedia.org/wiki/Voyager_1#Far_future
No, constant torque against nothing is infinite RPM. Imagine a space capsule with a stuck roll thruster.
I'm building something similar, with a focus on quality. There's a wait-list you can sign up for in the meantime: https://aiconstrux.com
Herb Sutter's Cppfront 0.8.0
I love the idea and drive behind your site, and the functionality, but I do have one suggestion that may help.

I suggest toning down the brutalist "look" just from 10 to 9. Two things you can do that will keep the soul of your site and make it more usable:
- add system-matched light and dark mode, that 100% white is very aggressive and bright, too much so and is putting me off using it.
- just bring the white and black in a tiny bit from 100% white and 100% black, make it a slightly softer grey and almost black. Again this is more about making it accessibile to eyeballs. Brutalist doesn't mean unpleasent afterall.
Ractor is cool, but I've been wondering why it uses the async `async_trait` rather than native async traits. Is it just because it came out before async traits were stabilized, and now code relies on it and it would be a breaking change to migrate?

For context, the `async_trait` crate makes futures from trait methods that are wrapped in `Pin<Box<dyn Future<...>>>`, which means that every async call to a trait method must make a heap allocation. This is currently a necessary thing to do if async trait methods were invoked with dynamic dispatch (through `dyn Actor`), but the `Actor` trait has associated methods, so that is already not generally possible.

I realize that methods on the `Actor` trait return futures that are `Send`, but specifically for an actor framework that feels like a very specific design choice that isn't universally good or necessary. Another design would give let the spawned task that executes the actor's messages exclusive access to the actor (so `handle()` could take `&mut self`).

I've ended up implementing a simple alternative design in my own project (it's not fundamentally very hard, but doesn't have all the features, like supervision) because the per-message heap allocations and internal locking became wasteful for my use case.
Hacker News Explorer
My point is: if you found a vulnerability and know that it is actively being exploited (say, you find out through contacts, or see it on your own systems, or whatever), then I would agree that it is ethical to publicize it immediately, maybe without even giving the creators prior notice: the vulnerability is already known by at least some bad actors, and users should be made aware immediately and take action.

However, if you don't know that it is being actively exploited, then the right course of action is to disclose it secretly to the creators, and work with them to coordinate on a timely patch before any public disclosure. Exactly how timely will depend on yours and their judgement of many factors. Even if the team is showing very bad judgement from your point of view, and acting dismissively; even if you have a history with them of doing this - you still owe it to the users of the code to at least try, and to at least give some unilateral but reasonable timeline in which you will disclose.

Even if you don't want to do this free work, the alternative is not to publicly disclose: it's to do nothing. In general, the users are still safer with an unknown vulnerability than they are with a known one that the developers aren't fixing. You don't have any responsibility to waste your own time to try to work with disagreeable people, but you also don't have the right to put users at risk just because you found an issue.
Which contains this gem:

> Conflict of interest statement

> R. Shanmugam reports a patent for Specific inhibition of telomerase activity in colorectal cancer pending. J.-L. Low reports grants from National Research Foundation, Singapore, during the conduct of the study. I.B. Tan reports grants and personal fees from MSD and Roche, personal fees from BMS, AstraZeneca, and Merck Serano, and personal fees from Amgen outside the submitted work; in addition, I.B. Tan has a patent for related to current work pending. V. Tergaonkar reports grants from National Research Foundation (NRF) and National Medical Research Council (NMRC) during the conduct of the study. No disclosures were reported by the other authors.
Depends, it's not just about access time and GC pressure, it's also about sharing that cache with other processes on the node.
The whole voting process is fundamentally broken in this country. One side argues we need to fix this and is told it’s fine. I then see articles like this and can’t help but reaffirm they’re right.
> Pretty sure the "clean power" mathematics doesn't take much of that into consideration

What are you basing this conclusion on? Your own fantasies? All of this is taken into consideration, you're just not willing to read any of it.
> Scala

Note about Scala's string interpolation. They can be used as pattern match targets.

val s"${a} + ${b}" = "1 + 2";
println(a) // 1
println(b) // 2
If you think about other data structures, we don't feel the need for a specialised database for them either. You don't need a set, map, heap, stack, array, hash etc database. You can do all of those just using a relational database. It's really not obvious to me why people think graphs need their own database, and I speak as someone who has stored certainly hundreds of thousands and possibly millions of graphs in databases over the years and almost exclusively used either an RDBMS, something like parquet or a key/value store to do it (to great success). I absolutely love graphs in programming and use them all the time but I've never once thought to myself that I would like to have graph semantics in a database over and above the links between relations you get in an rdbms or the links between whatever you like that you get in a key-value store.

More concretely I'm pretty sure you could demonstrate using relational algebra that any graph can be formed pretty trivially using relations. So I think there is probably provably no use case that can't be done with a more traditional RDBMS. Likewise it seems obvious that any graph can be stored in a key/value store (bunch of nodes, bunch of edges, badda bing badda boom) and therefore there is similarly no graph db use case that can't be done using a k/v store if that's your thing.
Most of the time,

git clone URL
cd PROJECTNAME

gets you most of the way there.

For Rust,

cargo test

usually takes care of all the dependencies and building.

The old days of

./autoconf
make

are over, but there are modern replacements.

Python and Javascript have too many build and install systems and much worse versioning problems.
Or chef or carpenter or automobile builder or priest or...
MDN Plus. For some weird reason we can't get the offline version in Australia, but it is available in New Zealand.
Evolve: An incremental game about evolving a civilization
It's a marketing piece, they don't particularly want to emphasize the hacky early days for an audience of Serious Enterprise Customers.
ICE and hybrids are still essential. Toyota estimated that EVs were going to be unsuitable for 75% of the US market. They aren't idiots. The car companies are making what people actually need. We don't have charging or electric infrastructure to support everyone having an EV, and there are many fire safety issues yet to be resolved for that to work.
It would not remove it, everything would float relative to that point. If you don't define the reference point, things still move about the price of labour since that's the dominant variable, just the absolute baseline can float around too. Defining a single point allows any arbitrary market position for everything else.

Since money is a social construct with a social purpose (and indeed, is the reason people are unemployed) it's perfectly reasonable that we define it's value to provide a social purpose, which has the added benefit of providing price stability.

Moreover, it provides a buffer stock of employed that can easily transfer to and from the private sector.
> something no allocation strategy can fix

Well, yes, with a GC when your heap is full, you make space by getting rid of the garbage.

Also, with a good GC, allocating is most of the time just bumping a pointer, exactly like an arena, and the collection time is proportional to the number of live objects, which when triggered out of band is basically 0.

Hence why I think a well tuned GC really isn't that far off.
In ruby, the sequel database toolkit is vastly superior to activerecord, and that is a subject of discussion here and there. The difference is that rails is what most rubyists use at work, unlike in python, where choices are more diverse.
Unfortunately some humans are just violent in nature. Or perhaps most. When robots become as intelligent as humans, some people might enjoy abusing them like they once enjoyed abusing people of different skin color.
Cities have vast water and trash treatment facilities, at least in developed countries. Those facilities are at most decades old. Even if the sewer system itself may be centuries old, it is maintained as failing sewers are health risks. Also, cities make less use of disposable items.

I can be contrarian at times, but that's just plain wrong.
This story (different source) was posted already (https://news.ycombinator.com/item?id=42020398).

I didn't read it before, but now I have and it's interesting.

Quoting their medical director:

> "Our request of the board is that we would be able to carry and offer those
> (vaccines), recognizing that we always have these discussions of risks and
> benefits," Dr. Perry Jansen said at the meeting. "This is not a blind,
> everybody-gets-a-shot approach. This is a thoughtful approach."

On the face of it, that argument makes the about restriction nonsensical.

Yet it is not correct in the way that one would want it to be understood — the 'discussions' have been between PH and government agencies. Even now, only the boldest doctor would feel safe to have a wide-ranging conversation about COVID. The 'safe and effective' line is truly the safest line for a doctor concerned to continue their career.

Their board director is reported as having said:

> [...] the board had overstepped the relationship between patients and
> their doctors [...].

The irony is of course that (for COVID shots at least), there never was any relationship between patients and their doctors.

In their arguments, both Dr. Perry and Dir. Aberasturi are both fundamentally misunderstanding what patient-centred care looks like, which frankly says lot.

The consequence is that COVID shots are effectively band in these counties, which is not so smart. But as a kick towards a 'reset', hopefully ending with doctors interacting more directly with patients would be no bad outcome in my view.
Washington State Vote-by-Mail Fact Sheet [pdf]
That's an external dependency. You don't install anything here. It's no different than making any other module you reuse in multiple places.
The disconnect is that in most of the world we only vote for one or two candidates on a ballot. In America you vote for everything from the president to the dog catcher on one ballot.

While I think of it, the USA and UK should both stop holding votes on working days. That is nuts! Do what Australia does and vote on a Saturday and make it compulsory.
I went down this rabbit hole a few times as well. It's great fun.

https://github.com/toolslive/NFJE

You used to be able to run it in a browser until they kicked Java out.
My understanding is that insulin resistance leads to increase DNL in the liver, so you end up with a greater production rate of LDL particles, but each one contains less cholesterol. I’m not woke on the mechanisms, but there’s a review paper here if you’re interested: https://www.sciencedirect.com/science/article/abs/pii/S10501...

Re: the twitter conversation: the diet heart hypothesis is specifically about replacing saturated fat with polyunsaturated fat. If you just reduce overall fat, you may even be making that P:S ratio worse. In the case of the WHI it means that the study is essentially null by default on that issue.

Dietary cholesterol is an interesting one - basically there is a significant effect of dietary cholesterol on serum cholesterol, but only when you go from very low to low levels. After that, the effect tails off dramatically. So in the general population you might not expect a 30% reduction to make a significant difference.

Additionally, you have to consider the overall picture. Maybe the reduction in dietary cholesterol did have a small beneficial effect, but the fact that the intervention group ended up with lower PUFA consumption than the control group meant this reduction was overshadowed by that effect.

There’s no evidence that oxidised fats in unsaturated fats are a cause for concern for health. Aside from that I don’t think stringing together a bunch of mechanisms and speculating about them is a particularly useful way to carry out science.

What we care about is actual outcomes from actual interventions. So yes, I agree that in those with metabolic disease and insulin resistance, we should address this issue. The evidence seems to suggest this is best done by losing weight. If there’s a certain dietary pattern that helps someone do that, great. If it’s a GLP-1 agonist, go for it. Whatever works.

But we also know that fat quality affects CVD risk too, and by a decent amount. So within whatever dietary pattern one settles on, replacing SFA with PUFA would also be a good idea. We can do both!
After it purchased the device, Remington made several adjustments—including switching the period and "R" keys, so that salesmen could impress customers by typing "TYPEWRITER" using the keys in the top row—which created a keyboard with what is essentially the modern QWERTY layout.

https://en.wikipedia.org/wiki/Sholes_and_Glidden_typewriter#...
I absolutely love what Pony brings to the table. Unfortunately, while true, this video does nothing to sell the language.

In the video, and even on the website, it says essentially - if you don't have a hard concurrency problem, don't use Pony. Which is an absolute shame, because it's syntactically really nice, and has a lot of language features you'd desire in 202X, a really nice type system, the most sane OOP you're likely to see, a decent C FFI (WIP but usable).

Instead of scaring people away because of the learning curve of reference capabilities, they should either make the API more intuitive, or make them optional. Then you get a really nice language that can optionally benefit from the actor/model instead of a really nice language that has to carry it around like a ball and chain.

Syntactically, actors look just like classes except they have async "behaviors" instead of synchronous methods/functions. If you're not using any actors in your program, there's no reason you should have to even mess with all the reference caps because it would be essentially synchronous.

I get that that's currently it's whole identity, but it's also the biggest learning curve/burden to getting started.

EDIT: formatting
Lots of conversation on HN recently about how voting actually works. Here’s a nice high-level view from my home state.
Absolutely more than other cities. These things literally run on crude oil and dump shit (literall, and worse) unfiltered into the ocean.

Plus, as someone living a few hundred meters from a harbor that hosts these abominations, I can tell you that the kind of tourism they foster is super toxic to local politics. And, as someone engaged in local air quality measurements here, I can also tell you that they're toxic, in the literal sense, to the people living downwind from the harbor.

At this point, the only way forward I see is to outright ban these things.

/rant
When not using the format specifiers or alignment it will indeed compile to just string.Concat (which is also what the + operator for strings compiles to). Similar to C compilers choosing to call pits instead of printf if there is nothing to be formatted.
> nonzero number of illegal immigrants do vote

This hypothesis has been tested. Lots of people have spent a lot of time and money on it. We have zero examples. The only voter fraud we have found is right wing idiots who don’t understand the electoral college.

Believing in voter fraud is not quite flat Earth stupid. But it’s close.

> As for descendants, they vote mostly for democrats

Racial depolarisation is the term you’re looking for. Young single men vote Trump. Also, whose donors do you think hire illegal workers? Who pushes back on strict liability for employers?
> this is only relevant if you want to highlight the multiplication operator differently from the dereferencing operator

Can you mention one editor which does that?
It been a couple years since I was testing, but as a game developer I can tell you the performance difference is significant (altho I wonder if it’s due to driver quality or middleware being less optimised for android hardware).

I believe it was around 2021-22 when I was thoroughly testing but at the time even a 5 year old iPhone was faster than a brand new mid-range android (one of the Chinese brands that had good specs on paper).

And by faster I mean an integer multiple higher FPS, not just a little faster.

My guess would be that popular software like Unity and Unreal is much better optimised for iOS GPUs.
> Has anyone done a ground up exercise of rethinking the process and the involved technologies from a cybersecurity standpoint?

Chesterton’s fence.
Hmm, how to do a statistical hypothesis of nearest neighbor data? Distribution free?
Plant CO2 uptake rises by nearly one third in new global estimates
We're actually hoping to get mmtK included in Ruby to be able to use more advanced GCs. Medium term we hope to use Immix: https://bugs.ruby-lang.org/issues/20860

And yes, we're aware of ZGC &co https://www.eightbitraptor.com/presentations/RubyKaigi2023-m...
Presumably it needs to be run by someone who already has access to the computer and gives them (or a program executed by them) root/escalated privileges. Although that might include running code from a webpage etc.