skysight-inc/HackerNews huggingface dataset:
Wages being included as a component in GDP calculation does not make wages equal to GDP.
I’m sure you meant something more along the lines of “strncpy is better than strcpy”.
> I would much rather have my computer run slower than have to continuously deal with security vulnerabilities. My time is much more valuable than CPU time.

To be devil’s advocate and take the other side of this argument: I would rather the CPU I paid for spend its cycles performing actual application logic. Every cycle spent executing all this “safety code” overhead feels like me having to pay for a developer’s sloppiness.

I feel end users pay a high cost for all this runtime checking and all these frameworks and levels of abstraction.
Yeah, and that they just give you DaVinci kinda stuns me. It wasn't that long ago that entire agencies existed as a business just to in effect rent productions access to that for color correction.
Fantastic thread. Love the simple explanation of the 6-page memo process and the Amazon writing rules.
The irony of cryptocurrencies destroying anonymity always makes me laugh, given the original claims of the opposite years ago.
Yes, I think we're actually all in agreement here. The common point is that TFA's argument that we need to keep C because it's faster is invalid. The GP's point is that it is not in fact faster because of all the things you need to do to produce code that can actually be deployed in today's world. My point is that even if C were faster (which it actually isn't) that would not matter because C is unsafe even with all the extra stuff that people stick onto it to try to make it safe. So the original claim is really a judgement call that speed matters more than safety, and this is not something about which there is any kind of consensus.
> a non-sanctioned non-American paying another non-sanctioned non-American for something with mixed crypto entirely off of US soil

Sure. You will be a fugitive from American law for the rest of your life. But plenty of people make a living in that category.
this pretty much summarises my opinion - one nitpick - i assume you meant "omit bounds and other checks", not "emit bounds and other checks" which seems to mean the opposite of what you're intending
Twitter crypto spam bots copy real tweets to appear real
Most of the diseases you’re describing are associated with ageing, if you can treat ageing their prevalence would likely be vastly reduced; not to mention that there wouldn’t really be a concept of “elderly” anymore, just people who’ve been alive longer.
memcpy is better than strncpy and strcpy ;)
So I'll bet that cash back was always a lower rate. Their terms are rather evasively written, but my reading is that they have two different redemption categories, both called "statement credit":

1) "eligible Rewards Partner transaction" statement credit

2) general "Cash Back Statement Credit"

From the link you provided, they tell you that 2) can be a lower rate, but they don't tell you what that lower rate is. But I did see the recent reddit discussion saying that it's 0.7 points.
Air conditioning remade politics. Now, it’s key to navigating climate change
They also say "There is no gene for success"
I use image thumbnails for my blog posts as well but they don't even show up in the article. Instead when the article is linked to on twitter or a message the thumbnail will show up. That's to say that this is pretty awesome and very valuable for a blog even if not used for cringy pop-gif stuff in the article.
Russia starts stripping jetliners for parts as sanctions bite
It doesn't make sense to put two limit here, it's essential a single select query with join table.

If you mean use sub-query. You may write something like below

select post [
id
title
user { nickname }
]
limit 5
where user_id in (
select user [ id ]
order by created_at desc
limit 2
)

Thanks for your interest, welcome more questions and ideas :)
Isn't this a design flaw, and such printers can be returned in (atleast most) EU countries? If there is a flaw, that existed when you bought the device, that prevents you doing the thing you bought the device for, you can return the device to the seller to get them to either fix it or to get a refund.

If every time some manufacturer decided to do stupid stuff like this, 80% of their customers returned the devices to get refunds, they would maybe actually stop with the shitty behaviour.
I have worked from home for 18 years now. Don’t ever see myself in an office other than for visits and specific meetings ever again. We still do in person events and I have many long standing friendships and relationships with prior colleagues. Though I did travel to my clients officers for a few years in there, it is different and would not support Gladwell’s argument anyhow because it was always different offices and people.
Yes, thank you! That's an embarrassing typo!

(And thanks to the other person as well, who presumably deleted the same comment after seeing yours.)
It's basically a way in which already delusional people are further deluding themselves that writing a part of a sentence while interacting with a black box is engineering.
I never realized this until I first took a break, but regular coffee intake has severely blunted my sense of smell. After about three days of abstinence, everything has an attention-grabbing smell in a way I never realized I had been missing out on for years.
Oh that's interesting, I kept saying Apple is the only "big tech" company not using Rust. (Huawei should probably also be considered "big tech", but they are also using Rust.) But with Apple being as closed as they are, I guess it's not too surprising that one doesn't hear much about it...

Is there any public source for Apple using Rust?

And yeah those are exactly the domains Rust is designed for, and even if it doesn't mean huge codebases, that kind of usage at a whole bunch of huge companies hopefully means Rust is more likely to survive beyond the initial hype. :)
> It is difficult for me to explain because I very rarely deal with in absolutes and have found that most people want online discourse to be in absolute terms.

> Again, I believe those people are being earnest because I know extremists exist for every position.

Indeed. I hear a lot of this rhetoric from both crypto maximalists and crypto skeptics and both of them always argue in very absolute terms.

I can agree that regulators won't allow privacy coins like Monero and tools like Tornado.cash to succeed and are already de-listing, banning them from exchanges. It also doesn't mean that these cryptocurrency or projects will 'all die in a fire' or 'totally go away' entirely. The same is true for crypto maximalists who also believe that it will 'take over the whole financial system'.

I'm already convinced that (some) cryptocurrencies and (some) crypto projects are here to stay.
> January 6 wasn't enough?

And what exactly is his alleged crime or wrongdoing?

Here’s the full transcript from his speech that day: https://www.npr.org/2021/02/10/966396848/read-trumps-jan-6-s...

Here’s a sample (emphasis mine):

> I know that everyone here will soon be marching over to the Capitol building to peacefully and patriotically make your voices heard.
It's more about finding the logic of the argument
> (which the other's can't due to copyright issues)

Be sure to pass this along to Microsoft's GitHub Copilot.
Well, for one, it's getting increasingly hard to run arbitrary code on any kind of manufactured computing device.

Riding the current of valid security concerns, all platforms are moving towards all code being signed and attributable and most code operating only within abstract/virtual environments that only provide mediated access to the hardware or the host system.
Calvinism is still a thing among US Evangelicals btw, most famously George W Bush, which gives some pause for thought vs how hawkish his administration was.
Parent Sues Facebook Alleging It Affected Her Daughter's Mental Health
Not to mention that both C++ and Rust can specialise algorithms and containers for specific types, whereas in C most developers resort to void* and function pointers. It's not unusual to see C programs written in a "typical" C style become dramatically faster when rewritten in a more modern language.

For example, typical C programs also don't use hashtables even when this makes the most sense, causing weird performance cliffs due to O(n^2) algorithms all over the place. Why not hashtables? Because they're not generic, so they're a pain to use. Not impossible of course, it's just that C developers avoid them.

Similarly, "strongly typed" containers full of simple struct types enable compiler auto-vectorisation that's often unavailable in C for the same kind of reason.

Last but not least, you would have to be a masochist to write heavily multi-threaded code in C... so hardly anybody does. These days, that's throwing away over 90% of the computer power in a typical PC, let alone a server.
> If crypto mixers are outlawed, only outlaws will use crypto mixers.

This is only true in the tautological sense.

Crypto mixers are outlawed > All users of crypto mixers are therefore deemed outlaws > Only outlaws use crypto mixers.

An otherwise innocent person who has never heard about the sanctions may continue to "launder" their crypto unawares because they don't want everyone they transact with to know their total balance. I would not consider them an outlaw but they may be in for a nasty surprise now.
I’m sick of people explaining why people are wrong for preferring what they prefer.
Perhaps Krugman never had a BBS account.
This conversation is about general use of C vs alternatives such as Rust.

If you can't use Rust because of your specific circumstances that's ok - use C! But don't use "my current circumstances prevent me from using Rust" as an argument as an argument against Rust in general - which is what you're doing.
Are laser printers still a ‘thing’? I recall having one as a kid and it just wiped the floor against any InkJet printer I’d used - holy crap.

It was limited to black and white though.
> Please take a few days to review John Regehr’s excellent blog.

Haven't heard of him but will certainly give a read. Thanks for the heads up.

> Npm is the poster child for supply chain attacks.

The only reason C doesn't (often) have similar supply chain attacks is because pulling in dependencies is so hard that you aren't likely to end up with a 10k dependency project.

Hard to say that's really a plus.

Other ecosystems have their own problems and certainly aren't perfect. However, the toolchains are generally leaps and bounds ahead of what C currently has.
Recently bought an older Laserjet off CL. HL-4040CN.

The autofeed tray was broken, but the manual feed tray still worked.

A steal at $100 and cheaper, easier and more reliable even in the short run than trying to unclog the 2 inkjets my wife and I both brought to the marriage.

Marriage: Pick your battles.
You're assuming that safety features will prevent security bugs. I think that is...optimistic at best.

Yes, they can defeat a few classes of exploits, but generally not the ones that lead to really bad outcomes.
Watch the January 6th hearings if there is any doubt in your mind. The evidence is laid out quite clearly.
Effective altruism is great.

I don't follow its precepts.
> The status of C as the lingua franca of today's computing makes it worthwhile to write tools for it, so there are many tools being written.

The vast, vast majority of programmers aren’t doing their computing by writing C anymore. It’s been the better part of 20 years since you could plausibly call it the Lingua Franca of computing.
Lago: Open-Source Billing API for Product Led SaaS
> trying to write new code for IBM RPG servers

Hey, I know that! Challenge accep... Eeeeh, nevermind.
Valgrind's memcheck is great for exercising known paths in a program, and determining whether they're likely to contain memory errors. It doesn't help you discover those paths, which is what attackers are doing when they research and then exploit your program.

We've known for decades that compiler mitigations, fuzz testing, and dynamic instrumentation are excellent and necessary components of writing more secure C. But they don't secure C programs, because C itself is fundamentally unsafe.

> No, they're not static tools but being dynamic has a host of advantages too.

Advantages that any compiled binary can enjoy.
> It's been 45 minutes and I'm still waiting for my Bitcoin transaction to go through.

At this point, and given HN's POV on BTC, I can't take these statements serious unless you are willing to post the tx hash?

Most of these criticisms seem to be unfounded and only speculative, or you deliberately put a low priority mining fee and feel the need to blame the protocol for that.

The truth is a 30 cent mining fee was clearing all day in the next block, so I struggle to see how this is the fault of Bitcoin mainchain. With that said, as someone already mentioned, LN txs are instant and near free.
My first impression of him was that he was an intellectual con artist.
I’m not saying cars don’t have consumables, I’m saying a car doesn’t brick itself when it decides that you’ve driven sufficient miles to need to replace the relevant filters. That you can replace your filters yourself is a secondary (though related) issue.
Does this analysis account for the acceleration of scientific inquiry and the follow-on benefits?
Working from a corporate office is entirely someone holding me hostage. I hate it like I hate death.

It's my sincere hope that Malcolm continues his slide into irrelevancy.
I totally agree with you, but are we really expecting "a typical PC" to have 10+ threads?
From a quick scroll, that seems to be just C-style `select` with `if` guards?

What I was referring to is things like `match x { Some(y) => ..., None => ... }`, where there is data that is available only in some variants of the type (like `y`). Without a type, even naming these variants becomes an interesting problem. (Not unsolvable, mind you. But not obvious either, and you lose some of the benefits that algebraic data types have in typed languages.)
I agree with this comment. I think as we condition from profession to team to company culture - assuming there is anything causal with WFH - some may be more productive, while others less so.
Precisely. This is perhaps the strangest part of the original post: C++ has the same performance advantages as Rust! It has them not because it's more safe (although it is, in some regards), but because it allows programmers to express behaviors that the compiler can reason about statically.
C is used because it has to be used, i.e. low level environments etc. not because 'performance' most of the time.

If you could pay in performance a little bit, but have a clean, portable, beautiful debugger experience, nice libraries like 'Java' with a 'stable ABI' ... nobody would use C. We'd all use 'that new thing'. And we would just buy slightly faster hardware for the IoT whatever.

We use C++ smart pointers all over the place, and they come with a 'cost'. We mostly 'happily pay the price' because it's worth it most scenarios.

Engineers obsession with performance is a bit of a curse. Rarely do we really need that much. Kernel code, sure, IoT and remotely controlled toy cars, mostly not.
Okay, great. So I've learned something new. But I feel like this distinction didn't come from nowhere. Did the FSF not feel the same way at some point in the past?
Which podcast was that? A Rust podcast with the main Zig dev sounds very interesting!
It's mentioned in Barnes Wallis' biography, competing claims of accuracy
Weaviate 1.14 Release
Why not? I just opened htop on my desktop, and I have 789 threads running over 117 processes, with 12 logical cores.
Good eye. I might add: the blind praise of garbage collection, and the "symbol not found xyz" bit raised an eyebrow for me.

You can't trust HN comments. Most of them sound good to laymen. But to a trained eye, it's a comment tree of cards.
Google sued after pulling free Workspace tools for early adopters
Really?
How much money are you willing to put on the claim "LLMs are going to produce >80% of newly written production code in 5 years"? If it's less than your yearly salary, then even you don't believe your own assertion.
This is already a thing multiple vendors provide, e.g. https://www.idnow.io/products/idnow-videoident/ (used for use cases like banking and electronic contract signing)
First, not all language safety features have to manifest themselves as run-time checks. A properly designed language will allow many safety checks to be done at compile-time.

And second, would you really rather deal with security holes on an on-going basis?

The problem with C is not that you can write unsafe code in it, it is that the design of the language -- and pointer aliasing in particular -- makes it impossible to perform even basic sanity checks at compile time [EDIT: or even at run-time for that matter]. For example:

int x[10];

...

int y = x[11];

In any sane language, that would be a trivially-checkable compile-time error. But in C it is not because there are all kinds of things that could legally happen where the ellipses are that would make this code not violate any of C's safety constraints. That is the problem with C, and it is a fundamental problem with C's design, that it conflates pointers and arrays. C was designed for a totally different world, and it is broken beyond repair.
You don't seem to understand that those malicious programs have no way of running on someone's computer if they can't exploit some other program to get installed on the machine in the first place. If the system software on the target machine is written in a better language and has no exploits, then it doesn't matter what language the attacker uses for their software.
> 220V, 221V, whatever it takes.

Thanks, the Mr. Mom reference made me smile.
I don't have a good way to include the image anyway (or I am too lazy to figure out how to do that in Jekyll, I guess), so its appearance(s) on my blog will be text-only for now. Thus no image license trouble. ;)
Memorization only works well if your approach leads to chunking. They have done studies on chess players specifically, which supports what you are saying. Masters are no better than a beginner at memorizing a random chess board. This critical mass of memorization, when finally encoded into chunks is what I think a lot of people are describing as the “aha” of memorizing to conquer complex topics. So it isn’t really the blind memorization, but the process of learning and getting information and concepts into coherent and related chunks.
For a lot of people, I would say most people, working from home has short term benefits and is long-term career-limiting.

People who are deep into their careers with built-out networks and contacts have no problem with the transition. But for others, it will play out over the next 5 years when they find that they are falling behind. The pendulum will swing the other way and having an office will be seen as a beneficial perk and career booster.
I strongly believe there is probable cause to be found that Trump committed crimes, but I can't help but ask if these hunts against former presidents are positive for the future peace and prosperity of America.
In fairness, graph theory/combinatorics is the poster child for clever problem solving techniques as far as areas of math go.
This is where I think many people talk past each other in the great wfh debate. If your commute is an easy 20 minutes where you listen to a podcast or an audiobook, and you find collaboration easier in-person rather than via Teams, it's a completely different equation to an introvert with a 1 hour commute through gridlock. Personally my commute isn't too bad & I'm far more productive at the office, though I do appreciate the opportunity to work from home 1-2 days per week.
I agree, it worked well for pot, now what about the human trafficking?
Or you know, we live on the other side of the country and we don't want to have to pay 5x for a comparable home in commuting distance...
I have some questions, if you don’t mind answering them! Everyone is welcome to respond, of course.

1. Did you learn Clojure at work or on your own?

2. Did you first ship production Clojure code at a job that already used it?

3. If not, did you/someone on your team push to first give it a try, or did you get hired as a Clojure dev by a shop that was already using it?

I’m asking because I know that I want my next job to be working with Clojure/script, but I found and learned and loved it on my own in 2018. So I’ve not yet worked on a team that uses it, and I’m wondering how hard it is to break into the Clojure scene. I’m a senior dev, been working mostly in front-end for the past decade, and not attached to staying there.
I think if your coin uses more energy to settle one transaction than a typical South American uses in a year it's the "shitcoin"

Crypto being filled with scams is a feature, not a bug.
Deconstruction of discourse: the vast majority of humans out of the decision loop.

All the main online sources are moving to subscription models with higher subscriptions for the real information. Only those with money will have access to information that informs decisions. At the low end, information is bundled only for its entertainment or propaganda value.

At the same time, decisions are increasingly automated as vast data streams are digested by automated processes.

20 or 100 years ago, people could stop work or stop buying or protest in the street. 20-100 years from now, there will be nothing the vast bulk of people can do to change their fate.

The resulting lack of citizen governance will at best be a world broken into geographic silos headed by corporate keiretsu.

So the next big technical thing will be domain-specific semantic models to drill down past what AI can do with probabilistic models -- just as the economy has moved well past bulk goods to bespoke services, e.g., the Nature article today providing a model for immune system cell-surface-protein interactions: https://www.nature.com/articles/s41586-022-05028-x
What kind of team is Malcolm Gladwell part of? A solitary writer is one thing, a team of 40 people where some are fresh grads who need hands on mentoring and some need quick emotional feedback on their ideas is another. Malcolm is not automatically a hypocrite by suggesting most people work in different circumstances from himself.
My (entirely uninformed… though I am a “doctor” har har) theory is that some sort of compression occurs in the brain. I also wrote out the answers to my flash cards by hand. I feel like these actions accelerate the compression process.

If it walks like a duck and quacks like a duck…
My Ryzen 5 3600X (a years-old mid-range CPU) has 6 cores and 12 threads, I wouldn't say that's atypical.
To be fair you'd have to compare people who had the same circumstances and desires, not simply both being rich.
> Watch the January 6th hearings if there is any doubt in your mind. The evidence is laid out quite clearly.

If you can’t even summarize a crime in one sentence then it’s anything but “quite clear”.
>You have to remember to close it after firing

You actually don't (https://www.youtube.com/watch?v=YAneTFiz5WU&t=110s).

The trick is that the bolt carrier itself seals the action so mud doesn't get into it; most other modern rifles eschew the dust cover entirely and just rely on this. It seems to work pretty well since they keep doing it.
And since then, development has continued on mrustc - it can now bootstrap Rust 1.54 directly (about 10 versions old as of now).
> The Chromium project finds that around 70% of our serious security bugs are memory safety problems.

> ~70% of the vulnerabilities Microsoft assigns a CVE each year continue to be memory safety issues

Memory safety is a leading source of serious bugs in a big group of operating systems, browsers, image and file parsers, and more.

It does seem likely we can stop this, and it doesn’t seem likely to me we can fix it in C. We have tried and failed for years at that.
Build react hello world and you’ve got gigabyte docker.