Hacker Newsnew | past | comments | ask | show | jobs | submit | marshray's commentslogin

Or you could just, you know, "talk like a human".

I did plenty of experiments as a teenager, but I never attempted to chlorinate a freakin swimming pool.

It was an above ground pool so I'm not all snooty about it

> ... but I never attempted to chlorinate a freakin swimming pool.

Me neither, but that is probably attributable to the fact that I didnt have a swiming pool.


Think about all the applications that spawn a subprocess and enable you to override the executable by configuration or just the PATH.

Those are plugin systems too, unless your term 'plugin' requires dynamically loaded code libraries by definition.


I agree the claim of "memory safe" is not "strong" in the sense of formal verification.

But the goal was to bring verification techniques (type systems, ownership and lifetime tracking, etc) to a practical language that also supported efficient interop with existing C libraries and APIs. Hence the 'unsafe' keyword. At this, Rust has succeeded wildly.

I've been writing Rust for years and almost never need to use 'unsafe'.


What is the point of inventing some sort of existential conflict between Rust and C++?

Why must Rust have "a fully bootstraped reference implementation"?

This is weird, dude.


> in most administrations of the past, overlapping interests like this would constitute a scandal and would call for further investigation.

Imagine all the laywers in any administration, then imagine all the clients that their firms had ever represented.


They should have thought about the before representing their bug-ridden code as suitable for critical infrastructure.

I know this sounds harsh but it really would be better for the world if these "processing complex untrusted data structures in C" enthusiasts found another hobby.


> They should have thought about the before representing their bug-ridden code as suitable for critical infrastructure

Typically it's presented as-is and without any form of warranty, but in the hope it will be useful - not "suitable for critical infrastructure".

Perhaps those using it for "critical infrastructure" can write their own utilities, or chip in to support the developer whose hard work they apparently rely so heavily on, so bug fixes aren't done merely in the dev's unpaid time-off?


"Critical infrastructure" wasn't my phrase and I agree that the corporations who are using open source have a moral and pragmatic obligation to fund its maintenance.

But what does a developer (open source or not) who releases a container format parser and codec collection upon the world expect people to do with it if not run it on malicious data on personal devices?


> But what does a developer who releases [...] upon the world expect people to do with it

Sometimes you build things to explore how they work, or to test your assumptions about how something would work. To build your own knowledge about a format, language, or system. Hell, sometimes it's just the middle of a venn diagram between fun and practice.

And, because it's easy to throw something up on GitHub, you can say "Look at this cool thing I made", "Look, I actually can do what I claim on my resume", or "Anyone struggling in the same place as me can use this as an example workaround, or inspiration for a solution"

Nobody has to, or is even necessarily expected, to use it. Sometimes it's just the author sharing this cool thing they made.


> Sometimes it's just the author sharing this cool thing they made.

Certain OS kernel started out like this circa 1991. :)


The problem is that the attacker gets to choose the codec that your device runs.

From November 2 to Nov 22 2018 the "DrSheldon" account asks exactly one question per day. https://space.stackexchange.com/users/drsheldon?tab=question...

Like this one, most of the questions are worded to enable an easy answer from a primary source.

In one instance the account answers its own question within the same minute: https://space.stackexchange.com/questions/31279/how-was-the-...

In another instance, the account replies to a comment with "Nonetheless, this would be the question to document any examples."


Hi, former stack exchange moderator here.

This is normal and expected activity. We encouraged our users to write canonical answers, that could be run as community wikis (not everything got converted to a wiki, but many things did). One of the reasons was to take a spot in the top 3 on a search engine, in an attempt to displace some horrendous / ad riddled website that at best a bad user experience, and frequently was subtly wrong or incomplete.

Some examples: we settled on a canonical answer for “how to install packages in Ubuntu”, or when there was a particularly interesting question that was discussed in the chat rooms, someone might volunteer to consolidate that information and publish the Q&A as a wiki.

It’s just internet points. They’re not worth much.


Indeed. The user later gets permission and community participation for future series of questions and identifies them as such: https://space.meta.stackexchange.com/questions/1498/any-oppo... https://space.meta.stackexchange.com/questions/1746/60th-ann...

That’s pretty cool.

Answering one's own question is encouraged on stack exchange sites.

Activity simulators, they're called. A good way to make a web site feel alive even with no or few human visitors. 4chan does this. Reddit. X/Twitter. And others...

Remember the guy that was hyper active wrt C# questions maybe 10 years ago?

People were amazed he would answer every C# and WPF questions minutes after they were posted.

I am convinced to this day he did the same thing.



Yes! Was he really a super human or was he cheating?

Jon legitimately was (is) superhuman with answering questions.

Some people just want to watch the world learn.


That’s fascinating.

I remember back in the days my colleagues and I couldn’t believe how productive and smart he was.

He probably helped train 30% of the coding aspect of LLMs…


Does he still feel the motivation?

Yes, an analogy for inner experiences that could never fully be communicated to others.

Like seeing C-beams glittering off the Tannhauser Gate, or flying around the Bay Area in an F/A 18 Interceptor on an Amiga.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: