skysight-inc/HackerNews huggingface dataset:
you can't have more parallelism by simply increasing #threads. Parallelism is bound by CPU cores.

Threads need to scale with CPU cores, however simply increasing #threads doesn't help. You need to split tasks of your program such that more tasks can be executed in parallel while not adding more overhead than you gain by parallelism.

Then you can distribute those tasks on as many threads as possible (while still being bound by #cores).
How old were you in the 1990s? I’ve noticed that for a lot of people, the golden age of no strife just happens to be right before they became aware of how people actually behave in public.

I too looked fondly back on the 1990s, but I was also a child. Looking back as an adult I can tell that my recollection of the era was colored by my inexperience. To draw one example, I totally missed all the moral panics of the 1990s, and how many people that harmed just for liking D&D.
> One other thing that's new, in America, is the idea that speech is less important than people's feelings.

This is not new. People were shot and killed for pro-trade-union speech, for example.
Hmm. If the Soviets were so deeply afraid of nuclear annihilation, maybe the US and NATO should be threatening it offensively as a means to get concessions. Like Russia has been doing.
If a thread is waiting for I/O or a mutex, it will yield and let another thread use that CPU time to do something. This doesn't work if you don't have more threads than logical cores, because then there is no job that can take over.

We've had this type of cpu time sharing far longer than we've had multicore CPUs.
I’m trying to figure out if you were actually asking a question or if it was rhetorical and you were calling shots.
Reading these made me wonder: what was the best self-hosted language on the C64 (or Apple II or other early computers)?

Like if those computers had existed in a world like today with open source and easy communication, what could the development environment have looked like?

I had an Apple II as a kid and knowledge and tools were so _scarce_ ... there was a certain magic to the secret world of the computers, but mostly I was cut off by a lack of access. And I'm sure some of the languages in this list were denied the audience they deserved by that same lack of access. (COMAL for instance looks like it would have been a breath of fresh air for my younger self)
>Can not-dead process exist without a thread at all? I'd expect not.

Isn't this the case for some older cooperative threading OSes? It's possible in theory, anyway.
The LG counter part of this monitor does pretty well for driving both a Mac and a PC. With a simple usb switch you can even share mouse, keyboard, webcam and a 4th device via one cable attached to laptop or pc. For 3090 though, you need https://evedevices.com/pages/spectrum. I’m waiting for mine to ship.
> there's a natural "limit" on the happiness I can enjoy at any given moment

This is roughly my experience, although, you can choose between peaks & valleys vs emotional stability. Highs are generally followed by lows and vice versa. The classic rockstar chooses to swing wildly between drugs/sex/crowds/etc. and addiction/depression/death while the buddhist munk reaches nirvana by maintaining an even keel.

Keep in mind there are other life considerations besides 'happiness' of course:

1. retrospective life satisfaction
2. responsibility
3. morality
4. procreation
5. etc.

I don't generally trust psych research, but Jonathan Haidt's book The Happiness Hypothesis is a good read on the subject. He highlights things that do/don't marginally increase baseline happiness.
Your point is rooted in wrong facts. On-chip fabrics are much more efficient than separate computers over ethernet. More energy efficient and lower latency.

Not only that. On-chip gives you high precision synchronous time (all cores observe the same time) so you can use synchronous distributed algorithms that are unsuitable for ethernet networks.

This type of hardware allows for much better solutions to some problems.
"Common patterns" including, running more than one application on a system.

I've worked on several thread-per-core systems, including embedded systems in which each thread owns a core and does not make system calls or context switch. You can do that, and it's ideal performance-wise, but it does not apply to multi-process systems -- how else are they to coordinate workflows, than through kernel-visible concurrency constructs: i.e., threads?

In language implementations with built-in user-mode schedulers like Go and Erlang, you get closer to this ideal for, as they will spin up a thread per core for CPU-intensive workloads. But even there, blocking system calls are still the norm (at least with Linux, which is only very recently moving toward a generic async system call system, with io_uring), requiring many more threads per core to saturate I/O workloads. And that still doesn't address the multi-process coordination problem.
Pfizer used AI and big iron to design its Covid-19 vaccine
> I've never seen a notable public market investor who made the world a better place.

which isn't their goal.

Investors' goal is to earn the highest return possible on their capital they invest, and take the lowest risk possible they can get away with.

Making the world a better place is something a charity does. Making money is what a company does. If the company incidentally makes the world a better place, that's great, but why does anyone expect this to happen?
Did you ever look at the Strida? It was designed in response to the Brompton, with a simpler fold and the ability to wheel it around on its actual wheels while folded, rather than little casters. It doesn't fold quite as small as a Brompton (it's more golf-bag like), but the footprint is similar if there's something to lean it against.

I'm very happy with mine, and it has most of the advantages you list - luggage rack, real bike feel (my longest day is apparently 64km and top speed 64kph). The sensitive steering takes a bit of getting used to the first time but you adapt quite quickly. For me the simple fold (and, sure, lower price) feels like a big advantage compared to the Brompton, which is what several of my friends have.
They do it maybe for similar reasons some car manufacturers are involved in Formula 1: prestige, pushing their engineering competence, application of research that benefits their products, etc.
https://en.wikipedia.org/wiki/Apolipoprotein_E#Alzheimer's_d...

Alz is not entirely dictated by genetics, but certain genetic alleles can influence your likelihood of developing the disease.

I am watching my 81 year old mother go through this. She and I are both genetically predisposed. It's terrifying.
Depends on one's connotations of the word "inquisitive." You may be associating to "general inquiry", while the GP is thinking more "the Spanish Inquisition".
I really don’t think this is that different from how a lot of us learned to code though. I learned by writing html and PHP specifically to solve a problem of having a website. The only difference I see is that the average CS student has to write reliable and working code as their career, while quants and statisticians tend to think that code is just a means to the end. Both are right I’d say depending on the problem.
That's true, but it's not relevant here... we're talking about reliability.
Just ignore them. Doomers will exist your whole life, they have throughout mine. They used to be the evangelicals, but I guess the failures of Y2K and 2012 to come to fruition made them go... a different insane path.

Russia seems most interested in taking Ukrainian nuclear sites to give to Rosacom, establishing an oil/trade/military corridor through the black sea, and sealing up the holes in the natural physical barriers of defense that the USSR once controlled. Nuking Ukraine, or the world, or whatever, is counter to that goal. Putin miscalculated the sanctions the west would take in reaction to their invasion as most sanctions have been pretty tame in the past, so with the assumption that no or limited sanctions would be imposed, invasion might have made sense in a psychopath's world chess game. Obviously very little of this has gone to plan, but making things worse is not going to help him either.

Any real worry should go toward the primary real effects of the actual civilian casualties in Ukraine, including any real possibility of tactical nuclear warheads used (possible, but only semi-likely... still would be likely smaller than Hiroshima or Nagasaki if used) and the secondary effects of the wheat issues on the food supply in Africa and the Middle East in the coming years from low-yield of Ukrainian and Russian wheat crops. Oil/gas is going to be a clusterfuck but it'll adapt.
Couldn't boot, since (on my HP and Lenovo) it comes with encryption out of the box.
I had several paragraphs to try and explain how scary Trump was for the rest of the world. I've deleted them because I don't want to enter an endless debate.

Just know that, for dozens of reasons, in Europe, the Trump administration was seen as irrational and dangerous to his allies. These views were shared by both Progressives and Conservatives, throughout Europe, even to a large extent in the UK. In comparison, Putin was seen as more rational, hence a more measurable danger.

It is now clear that the latter assessment was wrong. Regarding the former, the jury is still out.
> He's very clearly saying that if you are doing that, it's always possible to avoid it and work within the intent of the spec instead.

No, he very plainly (almost literally) said that if the tool isn't used exclusively in the way that he imagined, then you don't understand what you're doing. It was a blatant attempt at belittling a community which has been forced to tirelessly work around CSS's terrible spec for decades.

> The "logistics" of you needing to get your work done has no bearing on what the designers of the tools you're using intended.

You have this completely backward, and you may think you're defending Pemberton, but you're actually making him look more elitist and foolish by highlighting why the real world is different from the spec.

Implementations of CSS have been an absolute disaster since day one, and that is largely because of early design mistakes that did not account for countless scenarios and necessary functionality, making interfaces extremely difficult to both build and test, and forcing browser developers to create their own solutions over decades. A lot of those have been "fixed" by adding completely new methods (flex, etc) to replace the broken concepts, but that doesn't automagically make the original bad spec any better, which to this day still makes everything in CSS more difficult than it needs to be.

If a designer is not factoring in those real-world elements, then they have completely failed at their task, because the real world is the part that actually matters -- everything else is an ideological theory.
Man assumed another identity for decades until getting a Covid shot outed him
Found the private equity ghoul
Concur, 5meo typtamines are extremely potent and quite dangerous. Witnessed overdoses and while they weren't lethal, they certainly had the risk. Just because the compound doesn't kill, doesn't mean you can't die from a secondary or tertiary effect.
Ford is turning its EVs into video conference rooms with help from Cisco
I actually did the exact same thing. Went with the ProArt B550 and didn’t consider that the LG 5k requires two video connections to the graphics card. This[0] eventually helped me realize my mistake. Currently running in 4k and it’s fine. At least camera, speakers, and hub work.

0: http://johnwilger.com/2019/01/27/lg-utlrafine-on-linux-gnome...
This is common in modern embedded devices. Sometimes they're called eFuses.

https://imxdev.gitlab.io/tutorial/Burning_eFuses_on_i.MX/
> then it's priced incorrectly

There's no such thing as a "correct price". There is a "highest price" that enough people will still pay such that all inventory is sold, but that's not the same thing as being "correct". It depends on what the seller is optimizing for.

The Raspberry Pi Foundation wants their hardware to be sold at particular price points, and they've worked hard to keep costs down so it can be sold at those price points. They've chosen to forego extra profit, with the goal of getting this hardware into as many hands as possible, especially the hands of people who want to learn and may not be able to afford a higher price.

Sure, this isn't consistent with our profit-at-all-costs capitalist culture, but that doesn't make it wrong. And retailers are free to do their best to ensure that these products get into the hands of actual end-users, rather than parasitic, speculative, profiteering scalpers who provide no added value.

In the case of Adafruit, they would much rather have a bunch of satisfied end customers who are able to buy their products and get use out of them, than a bunch of satisfied scalpers. That's their choice (and frankly, I think much better for their business), and it's their right to impose technical measures to try to deny bots from their platform. (They may not always succeed, but that's another matter.)

> If a gas station started selling gasoline at half price, it would be instantly overrun with everyone from Harry with his pickup truck full of jerry cans to empty tanker trucks.

Just like Adafruit is trying to do with bots, that gas station would be well within its rights to refuse to serve tanker trucks or pickup trucks full of gas cans, if their goal in slashing prices was to sell gasoline cheaply to end customers.
You’re right, but I’d would think in recent years most stats people would have python as their first language. It probably comes preinstalled on their OS at this point (not sure if this applies to windows outside of WSL yet.)
New Backdoor Targets French Entities with Unique Attack Chain
What was going on in Turkey last month? https://stats.kiwix.org/index.php?module=CoreHome&action=ind...
Couldn't agree more. Electric Unicycles are unbelievable, here are the benefits:

1. Size / Portable, about 7" x 17" x 24"

2. Agility, better maneuverability around cars and obstacles

3. Speed, can go >40mph, most of the time you only need 15~25mph

4. Hands free, can carry stuff

5. Wheel size is 16" and up (better than scooters with small wheels)

Downsides:

1. Weight, 40lbs and up (my current one is 65lbs)

2. Electric only

3. Safety - if it cuts out, your falling off (has yet to happen to me)

4. No exercise like a bike (I became much weaker after I stopped riding my bike)

5. Expensive (starts ~$1300 for basic, likely will want to spend $1800-$2400)
As the top post says, White would probably agree with you about the struggle session. But there is room for a wide gulf between a joke leading to a struggle session and "other people people saying mean things in response to your speech". The category potentially covered by "cancel culture" is too broad, and failure to dig into the details and trade offs is at best unserious. At worst, it's a dishonest way to use norms at one end of the spectrum (let's all take jokes in stride) to defend norm-breaking on the other side (Milo should get invited to university stages even though he uses them to bully individuals).
They don't mention how deep the lens is. A sales piece with no independent photos.
What led you to this bold prediction of the future?
Well, I drink coffee, so the game is up.

Despite everyone on the Internet warning me about how everything is dangerous, I have done all these things without even coming close to risking anything.

I've also noticed that people on the Internet think that a child riding their bicycle on the sidewalk is dangerous to other people on the sidewalk. So that leaves me with the natural conclusion: the threshold people pick for unacceptable risk to life and limb is on a wide distribution, so P(I_will_think_x_is_dangerous|someone_told_me) is very low.

And in the end, I've written a lot of code for a lot of people and have led successful organizations, so I know I'm not unproductive and I know I'm still not unproductive. So maybe I'm rolling the dice each time, but you know what? The fact that I've done shrooms tens of times, and alcohol hundreds of times, and LSD some ten times, and I'm able to do all of this and still be okay by society's standards has got to set a lower bound on your posterior probability after reading this comment surely.

There's a lot of nutty mysticism surrounding so many completely normal things. It's like in middle school, when we kids were discussing what condoms make you do. Some theories from the time:

- condoms make you want to kiss someone

- some kid heard about another kid's friend who wore a condom and they got a baby as a result

- another kid heard that condoms are a kind of powder

That's the state of the comments here
I think some are configured in such a way the devil itself is perplexed by its sheer chaos.
Switching between threads is expensive, so ideally the threads are never waiting unless the system is literally idle as that would imply a context switch. For software that has a lot of fine-grained multi-thread coordination, like database engines, a substantial percentage of all CPU time is spent coordinating and context-switching between threads, not actual workload. The more cores you have, the worse this issue becomes.

This is why thread-per-core software architectures are idiomatic for anything requiring maximum performance, especially on systems with lots of cores. Similarly, there is no requirement to spawn separate threads for task concurrency. The non-blocking coroutine-style concurrency common in high-performance server software supports much higher concurrency and with context switching costs that are much lower.

The thread-per-core coroutine-style is easier to write and maintain too -- the logic is almost entirely single-threaded. No deadlocks, races, etc to worry about because lock graph concurrency is complicated.
Tell that to Detroit.
Ask HN: Why are some soundtracks of movies so powerful?
Everytime I hear the soundtrack of Ben Hur from Miklós Rózsa I'm already thrilled. Same for soundtracks of Ennio Morricone. I wonder if these soundtracks only work if you saw the movies or if it's also special if you never saw the movies. On the other hand the movies for sure wouldn't be so emotionally intriguing without exceptional soundtracks. What are your thoughts?
For it to not be nonsense, you need to explain:

a) How it's possible, even hypothetically for citizens to simultaneously have both "the right to speak their minds and voice their opinions in public" and "without fear of being shamed or shunned". The two are contradictory.

b) How that superposition is "a fundamental right as citizens of a free country", which Americans once had but are losing.
They can have my old ones
Your 12" m3 MacBook is likely at least twice as fast as a Raspberry Pi 4. The BCM2835 isn't a remotely powerful chip.
It sounds like you failed for many reasons, lean being the least of them. "Lean Startup" doesn't mean you should wait to raise, it means that you can get more "at bats" with the money you do have. Just because "lean" made it possible to not raising more money right away, that doesn't mean it's part of lean - that was a bad idea by the founder. And think about it this way, let's say you decided to "go big" and not raise right away - how much faster would you have gone bankrupt? The issue here is the lack of fundraising, not lean.

It feels like you took a bootstrapper approach to building your company, but within a YC incubator talking to VC investors.

No matter what methodology you use, that team sounds very small. I really hope the "1 founder" was a developer and an amazing design was crucial for your companies success.... :)
Does it make sense to ask for a system wide scheduler that manages tasks (tasks in terms of the state machine behind async await) instead of threads?

Currently every app that uses tasks has it's own executor with a corresponding thread pool, which may be more efficiently used if it was shared by using a single async executor across all processes.

of course, it requires to agree on one executor which doesn't sound realistic, but would it make sense in general?
Blaming the engineers rather than the businesses seems.. odd. It isn't like the people writing that code had control over what the company set as priorities. If anything, what you experienced seems to be a reflection of corporate short termism.
This seems like an American-centric view. I've heard in some other countries, patients have full control over their medical records, they take the records with them from doctor to doctor.
For the US, I highly recommend the Nuclear Posture Review, which is compiled by and details the current administration's policy as it relates to its nuclear stockpile and strategic purpose.

The last one, 2018: https://media.defense.gov/2018/Feb/02/2001872886/-1/-1/1/201...

https://en.wikipedia.org/wiki/Nuclear_Posture_Review
Are you using nvidia's driver or nouveau?
What's your point then? That someone might use cultural artifacts from another culture in a respectful non-offensive way, and that is bad?
All perfectly valid but I think you're letting perfect be the enemy of good here. Even if your app can be preempted, green threading is still useful.
the mobile version looks too narrow on my android chrome, but PC version looks good.
1700 Euro not counting tax doesn't look like affordable TBH...I'm thinking something around 500 bucks at most.
> it would require somebody to define a "security policy" for every module to whitelist permissions.

That doesn't seem particularly onerous. The writers of a piece of software should know if it requires network or filesystem or shell or eval access, and adding those permission requests to a package should require just a couple of keywords added to a config file.

If the permissions are too strict, then someone running the code in an enforcing runtime will get errors and presumably add an override, then submit a one-line patch upstream. On the other hand, if the permissions aren't strict enough, people should think "Hey, why does this arithmetic library need filesystem access?" and submit one-line patches to remove that permission request.

The hardest part will be encouraging writers of popular packages to split them along permission lines, so that people can install just the subset of functionality that solves their use case without granting unnecessary permissions.
In practice product requirements can get in the way of technically ideal solutions. One example of this is that analytics products allow users to pass in and analyze arbitrary number of user properties to do analysis on - more than even a columnar database can handle. The current solution of storing JSON as a column indeed has a very significant performance trade-off, but it's also needed to power queries users need to run. This is also why we're really excited about the new Object data type that landed in 22.3 as it handles these cases gracefully by creating dynamic subcolumns.

On JOINs - again, requirements bite us in different ways. Product analytics tool data ingestion pipelines can get quite complicated due to needing to handle merging anonymous and signed in users and user properties changing over time. Handling that via JOINs is as a go-to-market helps avoid that upfront cost by centralising the logic in SQL, but indeed does come with a significant cost in scalability. Delaying in turn allows you to be building tools users need. That said every loan needs to be paid at some point and we're currently knee deep in re-architecting everything to avoid these joins.

Also note that JOINs don't work the way you described from our experience - rather the right hand side of the join gets loaded into memory. The bottleneck there is memory pressure rather than I/O with a good ORDER BY on the table.

All that said, what a great summary of all the different things to keep an eye on. Thanks for reading and sharing your thoughts!