skysight-inc/HackerNews huggingface dataset:
Go is worse at _lightweight_ concurrency because each Goroutine is much costlier than each .NET task. Also Go has less pleasant concurrency semantics comparatively speaking because Goroutines cannot yield a value - you have to spawn a channel on top of spawning a Goroutine or you need to use a wait group or similar. .NET offers better experience for concurrency-centric code at a much lower overhead for code that has light of finely grained concurrent operations.

https://hez2010.github.io/async-runtimes-benchmarks-2024/tak...
This might be the best publicly available model for coding:

https://livebench.ai/#/?Coding=as
tptacek I don't want to waste your time, but do you have any good recommendations for material that bridges the gap between modern deployed cryptosystems and the current SOTA quantum computing world in enough detail that is useful for an engineer practitioner preparing for next 10 years?
Sure, if you never need to deal with actual low-level high-performance systems code. Just because this use case doesn’t apply to anything you do doesn’t mean it applies to nobody. This is the kind of attitude that undermines languages like Rust (which I use in my systems). A fair criticism of Rust as a “systems language” is that it simply excludes all the really difficult parts of being a systems language.

C++ deserves a lot of criticism. Many aspects of the language are quite fucked. But willfully ignoring that it solves real problems that other nominal systems languages are unwilling to address doesn’t mean those problems don’t exist.
IIRC C# investigated virtual/green threads, but decided to drop it because of poor interactions with reentrant code from async/await. The fact that C# went all in on async/await when it was the rage has prevented it from adopting a better solution. Java's conservative attitude fares better for such fundamental changes.
As a Taiwanese citizen, with only a Taiwanese passport, you can move pretty freely throughout the world.

If most countries didn't recognize Taiwan as a country, they wouldn't consider these passports valid, no?
This post is cringe. There's simply no other word to describe it.
Stop payments to his competitors?
My wife is a professional translator and both revises others' work and gets revised. Based on numerous anecdotes from her, I can promise you that "single correct translation" does not exist.
I've done a couple of projects in Rust, and I can appreciate this sentiment.

I don't think my code was pretty and I know it wasn't idiomatic. But I have some experience in writing concurrent code, so I have an understanding of the reasoning behind Rust's borrowing semantics, why lifetimes are important, and the difference between boxed values, rc, arc, and I additionally understand the semantics of semaphores, mutexes, spinlocks, and critical sections.

(As an aside, I don't know if I'm an N+1 programmer. My code works, long term, requires very little maintenance, and generally stays out the way. Just the way I like it.)

But- I see these recurring themes in posts from Rustaceans along the lines of "the compiler tells you what's wrong" and "if it compiles, it's correct!"

These kinds of statements worry me. Not necessarily because I think their code is going to blow something up, but because I think a sizeable portion of the community does not really understand the guarantees Rust provides, and under what contexts they are valid. I mean, sure, you might not have a data race, but you sure as hell can code yourself into race condition or a deadlock, and from what I understand from HNers, these situations are not all that uncommon in Rust crates. I'm also led to believe that the panic handling situation in some crates isn't ideal.

You shouldn't just haphazardly Arc<Mutex<T>> all the things just because that gives you the Send + Sync that you think you're looking for (or the compiler is looking for). You should understand what the hell you're doing, be able to tell if those things are necessary, and understand the ramifications of using those abstractions.

I think there's a lot of good going on in the Rust ecosystem, and I wish I had more work in that area, but there's a lot of blind advocacy there that assumes the Rust approach is the best, but the language does have serious ergonomic limitations in certain low level scenarios. My whole career I've had to focus on scope and objects that outlive their scope, but now every other word I seem to hear from the Rust community is "Lifetimes" and "Ownership", like these concepts were completely unfamiliar to developers before and now the Rust Way(tm) is not only THE WAY, but THE ONLY RIGHT WAY.

I don't want to go too far off the rails, because I find the ecosystem intriguing, and I see tremendous value there. Whether those approaches stand the test of time isn't a given (although let's face it, they probably will because they are sound and they are gaining developer mindshare, which is the most important factor).

I just worry about ergonomics. Coding is not supposed to be easy, so please don't misunderstand- but coding, especially for those that do it day in and day out for decades, should not be a chore. There are definitely some QOL improvements that could be realized in the near term, although I'm not sure what those would look like.
i see, thanks mate
The temperature itself was probably reason enough. It was the coldest inauguration since 1985 and the inauguration was held inside that year also.
It really needs to be taught in comp sci classes at this point. Have an entire project dedicated to why rolling your own crypto is at best a waste of time. Students will listen if they need to pass a test on it.
> at least for sqrt(), internally it's likely implemented as a heuristic guess

Square roots are implemented in hardware: https://www.felixcloutier.com/x86/sqrtsd

> In software, you'd normally iterate Newton's Method

Software normally computes trigonometric functions (and other complicated ones like exponents and std::erf) with a high-degree polynomial approximation.
Do you mean like my approach is bad or the whole business problem in particular cannot be solved effectively?
One company outright designated a segment of engineering headcount as exclusive to women and URM candidates. Managers were prohibited from fulfilling this headcount with Asian and white men. This was done despite having an overrepresentation of women in engineering roles relative to their representation in the field. Another allowed diverse candidates multiple attempts to pass technical interviews where white and Asian men got one chance. A third company set a quota of 40% women in engineering hires in OKRs (contrast this with ~20% of software developers and ~10% of electrical engineers that are women, those two fields made up almost all engineering roles at the company).
FWIW, that chat.deepseek.com link at least doesn't still work... did it ever (for people not logged into your account)?
>It doesn't address any points

Taking some time to point out the vulnerability is already charity work. Assuming that's also a commitment to a free lecture on how the attacks work, and another hour of free consultation to look into the codebase to see if an attack could be mounted, is a bit too much to ask.

Cryptography is a funny field in that cribs often lead to breaks. So even if the attack vector pointed out doesn't lead to complete break immediately, who's to know it won't eventually if code is being YOLOed in.

The fact the author is making such a novice mistake as unauthenticated CBC, shows they have not read a single book on the topic should not yet be writing cryptographic code for production use.
Nice! C# is also a secret systems programming language in a way that competing GC-based languages are not. It’s actually very nice for high load environments. With the caveat that, much like in Rust, you have to actively vet your dependencies and sometimes write your own optimal implementations, which C# enables incredibly well with precise control over memory management, first-class structs, zero-cost abstractions, SIMD and a compiler that is slowly closing the gap with LLVM.
The problem isn't "the server sends me a public key".

The problem is there's no way to know if the server is lying.
This is disappointing. But I have had similar questions for along time that the article touched on. We could have 4:1 or 8:1 or in not far future 16:1 Server Density. When Zen 6C arrives it would be 256 Core / 512 vCPU per Socket.

If we were to move all of our Cloud Native workload to 8:1 Server. What do we do with the 7 Racks Space left over? And yet we continue to build out New Datacenter. I know there are power density and cooling issues with older DC, but is retrofitting some of them more expensive then building out a new one?
Any Voice Agent Experts?
I’m building an AI-powered outbound calling agent using Twilio (for calling), OpenAI (for conversation logic), and Eleven Labs (for voice synthesis). The issue I’m facing is barge-in detection—when the AI is speaking, I want it to immediately stop and listen if the user interrupts, but currently, it finishes its sentence before processing the user’s input.

Leave me your discord if I can hire you to help crack it!
2018 wasn't a presidential race, which consistently have higher spending. 2020 and 2024 were each over $15B, and there is a steady upward trend in real dollars.

https://www.opensecrets.org/news/2024/10/total-2024-election...

The current supreme court also has a tendency to strike down campaign finance regulations. Everyone knows citizens United, but more recently e.g. AFP v Bonta (2021) struck down reporting requirements in California, which paves the way for unlimited anonymous spending, and Snyder (2022), which reclassifies anything except the most obvious bribes as "gratuities". We'll probably have more 5-4 or 6-3 decisions in the next four years that increase money in politics.
Nah, hell is being stuck writing Kubernetes configs.
I likes Peter Schiff's take on DOGE and Trump's meme coin. He said for all the finger pointing Trump did at Biden for corruption, the only thing DOGE has done is increase the efficiency with which anyone can bribe Trump. And private or state actor can pay him off publicly and immediately through his meme coin.
> How will Australia's under-16 social media ban work?

Ooh! Ooh! I know this one!

It won't.

There are a couple of ways I see it going.

1) Let's just say there are 300 days left before the ban takes effect. Option 1 is that in 298 days, after every tech person in the world telling them how stupid and ineffective the idea is, and when the dumb populace realises "wait now everybody is going to have to verify their id to use social media?", the law gets repealed. This will happen quietly and without any media circus, because Australia has no independent media, OR:

2) The ban goes into effect. On the same day, teens abandon social media en-masse. Nobody knows where they've gone. Weirdly, these events correlate with a spike in VPN subscriptions encrypted traffic to decentralised services.

I'm hoping for the second one - a more security aware next-generation would be a good thing.
I'm sure they'll undersand
My mum gave me HSV, she currently has Alzheimer's and has forgotten who everyone, including me is. She is 64.
Wow, the smugness of that reply. Responding by calling someone naive and blowing them off despite there being real questions.

The “insecure crypto “ that they clearly link to (despite not wanting to put them on blast) was also a bit overdone.
I guess we all are stuck hiring this expert to review our crypto code(under NDA of course) and tell us we really should use AWS KMS.
LeaderKey – Efficient Nested Shortcut Launcher
The mba is definitely an amazingly refined laptop. I've purchased 2 over the years. That being said, I'd still be very interested in a linux powered snapdragon laptop.
I believe the ChromeOS -> Android move was because the CrOS model of having Google pay for the testing support of partner devices was not working out, and moving towards Android's model would cut costs while also cutting duplicate development costs.
There is reason async/await got so popular after it was adopted by C# based in the early Async work in F# :)

Stackful coroutines have their pros but they are not a better choice. Rust did not and will not adopt them nor any other serious systems programming language will.

You don’t have to follow noisy style you often see - tasks compose nicely and express deferred operations incredibly well in a way that will not blow up on you in a surprising way.

There is an ongoing Async2 project which will massively reduce task state machine overhead further by only ever paying for it in the code that actually suspends rather than the code that just forwards the calls or doesn’t. It will likely land as preview in .NET 10 and as full release in .NET 11.
It was prohibited to create such policies since 2019[1]. They've increased punishment for offenders. You might want to read on what exactly changed[2]

Besides Tennessee law prohibits creation of "sanctuary city" way before Trump came into power.

[1] https://wapp.capitol.tn.gov/apps/Billinfo/default.aspx?BillN...

[2] https://wapp.capitol.tn.gov/apps/BillInfo/Default.aspx?BillN...
I reay like the Asus TUF series in this regard. Except battery life and weight of course.
I agree with his comment and would like to add that the critic came across as rude and superior. Instead of answering the dev’s question in good faith, they linked to their own blog entry that has the same tone. Is it a cryptographic expert thing to act so rude?
Use Emacs to drive gdb (through the GUD mode) gives a much more ergonomic interface. It highlights the line of code being traced in the code window.
I'm not sure the way to get developers to stop writing their own crypto is to turn it into a delicious forbidden fruit edible only by the most virtuous. APIs sometimes have a "Veblen good" character to them: the more difficult, the more use they attract, because people come to see use of the hard API as a demonstration of skill.

The right way to stop people writing their own cryptography isn't to admonish them or talk up the fiendish difficulty of the field. The right way to make it boring, not worth the effort one would spend to reinvent it.
Did you read the section on the ear, or any of the entries under musculature? Try https://en.wikipedia.org/wiki/Darwin%27s_tubercle

> you don’t accept that organs not occurring in all humans are vestigial […] several organs that don’t appear in all humans are absolutely critical.

Huh? Are you suggesting that female reproductive organs should be considered vestigial because males don’t have them? That’s not what vestigial means. The vestigial organs that serve no known purpose and are missing in some humans demonstrates the lack of criticality and functionality, it demonstrates there’s no human dependency on them and that they actually don’t have any purpose. But not the other way around; a critical organ like a reproductive organ missing in some humans does not imply it’s vestigial… obviously. Is that confusing or hard to grasp?

It feels like you’re trying to construct some sort of semantic or logical trap to prove a point, but it seems like you misunderstood me somewhere. Using reproductive organs as your example is a pretty bad idea - in humans, males aren’t missing female organs, nor vice versa. We start with the same organs, and they grow slightly differently. They aren’t missing.

What I’m saying, plain and simple, is that your claim that “Evolutionary pressure is pretty brutal to things that actually aren't used” is false. (According to evolutionary biology, not according to me.) There is no pressure to evolve unless things affect survival (mortality or reproduction). Some organs evolved in the past and we still have genes for them, but they no longer serve their evolved purpose and also don’t affect mortality or mating in any significant way, and so there is no force to get rid of them. We call those organs vestigial. Some of them might be evolving away very slowly, which not occurring in all humans might suggest, and some might not - because whatever use they have is not affecting survival rates enough to matter.
its the same thing as:

gpt-3.5 -> gpt-4 (gpt-4-32k premium)

"omni" announced (multimodal fusion, initial promise of gpt-4o, but cost effectively distilled down with additional multimodal aspects)

gpt-4o-mini -> gpt-4o (multimodal, realtime)

gpt-4o + "reasoning" exposed via tools in ChatGPT (you can see it in export formats) -> "o" series

o1 -> o1 premium / o1-mini (equivalent of gpt-4 "god model" becoming basis for lots of other stuff)

o1-pro-mode, o1-premium, o1-mini, somewhere in that is the "o1-2024-12-17" model with not streaming, function calling, and structured outputs and vision

now, distilled o1-pro-mode probably is o3-mini and o3-mini-high-mode (the naming is becoming just as bad as android)

its the repeat, take model, scale it up, run evals, detect innefficiencies, retrain, scale, distill, see what's not working. when you find a good little zone in the efficiency frontier, release it with a cool name
rants about how immigrants are flooding the cities. When shown data and statistics and pointing out Trumps blatant lying

What? You are more misinformed than your father if you don't know that illegal aliens are flooding into the country. Trying to choose a neutral source for you.

https://www.bbc.com/news/articles/c0jp4xqx2z3o

Since January 2021, when Joe Biden came to office, there have been more than 10 million encounters - about 8 million came over the southwest land border with Mexico.

Under the Trump administration, there were 2.4 million encounters on this border.
Obama had a super majority and could've done single payer, but he let the insurance companies write the ACA while letting Citibank choose his cabinet. Such is life when you give Democrats the power they need to make change.

They'll fight back against the power structures by ceding control to them, and taking massive bribes. Every time.

Even Bernie Sanders is a Big Pharma lackey, accepting millions.
Just use Kagi
Have we ever not been in political purgatory? Some fundamental political issues such as federalism have been fought over since the founding of the republic. And that's not necessarily a bad thing.
Google, maybe. P&D, no.
You can see all the styles that are applied to a specific node and their provenance. I believe learning how to properly debug is way more valuable than hoping that an LLM will get it right. And there's no global, and import order is kinda the wrong way to think about it.
It's a genre. It's neither dogmatic, modern, nor unique to programming.
What does "don't build your own crypto" even mean any more?

I originally thought it meant "don't implement AES/RSA/etc algorithms yourself"

But now it seems to mean "pay auth0 for your sign in solution or else you'll definitely mess something up"

As an example, we have a signing server. Upload a binary blob, get a signed blob back. Some blobs were huge (multiple GB), so the "upload" step was taking forever for some people. I wrote a new signing server that just requires you to pass a hash digest to the server, and you get the signature block back which you can append to the blob. The end result is identical (i.e. if you signed the same blob with both services the result would indistinguishable). I used openssl for basically everything. Did I roll my own crypto? What should I have done instead?
Insurance companies are part of the problem but not the foremost problem. Their profit margins are less than 10%, even if they operated as a charity, healthcare costs wouldn't go down much.

https://www.noahpinion.blog/p/insurance-companies-arent-the-...
I don't want to sound like I am bashing the original designer of the $200 monkey mascot, but I think the author has some misunderstanding here.

The market value of that was very unlikely $200. Before AI, there were so many people offering similar services on Fiverr. And from my experience they're mostly not scammers (just novices). Of course they might not live in the US, at least not in big cities.

The price range for that was $20~$50.

Edit: the article says 2013. I don't know if Fiverr was popular back then. I'm talking about more like 2019. At that point Fiverr and similar platforms had upended this kind of $200 market.
It's been making the rounds on Blue Sky: https://bsky.app/profile/myrnadash.bsky.social/post/3lh33szm...
On the one hand I would argue that you’re not supposed to visualize your lake as a bunch of rectangles. Visualize your lake as the shape the lake actually is.

On the other hand, for many people it’s easier to visualize than you might imagine. As you may know, virtually the entire US was surveyed and divided up into one mile × one mile sections. A square mile is exactly 640 acres. At one time a homesteader could buy that square mile and move west. Over time the minimum size of a homestead was halved and halved again until it was 160 acres, or one quarter of a square mile, around the time of the Civil War. These were often quartered again into 40 acre fields. A farmer and his family could expect to work two or three of those fields every year, rotating which one was fallow if they were smart. They are ¼ of a mile on a side.

You can zoom in on almost any random part of the US and find those squares everywhere. Farmland is all gridded with roads along the 1 mile section boundaries, and cities are a jumble. But in between the suburbs are made up of the smaller divisions. It is very common for a 40–acre field to be divided up into 13 lots of ~3 acres each. It is super common to find whole areas of 10–acre lots made by quartering those fields. And it is also not surprising to find a 10–acre lot that has been divided up into 1 acre lots that are all 66ft×660ft.

Here, as an example I [zoomed into a randomly–chosen point in the midwest](https://www.google.com/maps/@39.6540747,-86.0094355,1456m/da...). If you measure E McGregor Rd along the northern edge of the map you’ll find that it’s 1 mile long until it hits that jog. You can immediately see that this section was subdivided into four 160–acre farms, and some of those were subdivided into 40–acre fields. Knapp Rd runs north–south and divides the section in half. To the east is an older area of mostly 2, 3, and 5–acre lots. On the western side a developer has bought up 90 acres (two 40–acre fields connected by a 10–acre lot) and turned it into a very modern subdivision of houses each built on (approximately) half–acre lots. For many Americans, visualizing an acre is easy; it’s half the size of the land their house was built on, or their lot plus their neighbor’s lot, or some other similar amount.
I disagree with this logic and morality. There is a moral obligation to intervene when failing to intervene results in more harm. Naturally the type of intervention needs to be reasonable for the circumstances. But standing by and letting Assad and Putin drop barrel bombs on the population of Syria is clearly not the moral path.

By your logic if Japan hadn't attacked the US then the US should have just stood aside and let the Germans take Europe in WW-II.
for larger scripts,just use python or lua.
otherwise,bash is perfect
That's not the worst I saw this week. I saw a floating dialog box that cannot be closed, that was on the right hand side obscuring the form that it was hassling you to complete. You had to only scroll down a third of a page at a time in order to complete the form.
They've got classic innovator's dilemma
BTW.

I was recently asking very innocuous questions and as I was reading an answer being "typed", it just went away and replaced with some generic clap trap about wanting only to talk about science of something.

I asked it what happened and it had no idea of the answer nor question I was talking about.

It lacked complete introspection.

As anyone else seen anything like this.

PS: It bullshits way less than the other models but still creates authoritative sources from places like nature.com that simply do not exist.