HNHacker News
TopNewBestAskShowJobs

spacechild1

3,562 karma · joined May 28, 2017

submissionscomments
spacechild1··on AI sticker shock hits corporate America
I think you missed the joke.
spacechild1··on I think Anthropic and OpenAI have found product-market fit
Please let's not dilute the meaning of 'AI psychosis'. It is a real phenomenon that involves actual psychosis.
spacechild1··on C constructs that still don't work in C++
> Because some warnings are just believed to be more serious, than others.

Yes, that is my entire point. For some reason you were arguing against it.

spacechild1··on C constructs that still don't work in C++
> That's because the default mode for compilers is to just shut up and compile this throw away code.

That's just not true. Compilers do issue certain warnings by default and they even treat some warnings as errors. See https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html

> ?? Uninitialized variables are also serious issues and also undefined behaviour.

Oh my, I meant to write "unused variables" facepalm. Uninitialized variables are of course a serious issue.

So back to my original point: you said that warnings in C are always a serious thing, but that's not really true. Warnings can range from more or less harmless to very serious. In fact, compilers recognize this issue by upgrading certain warnings to errors by default. See again my link to the GCC 14 post: https://gcc.gnu.org/gcc-14/porting_to.html.

spacechild1··on C constructs that still don't work in C++
Ok, but then compilers should really throw errors for these diagnostics by default. Why lump serious issues like incompatible pointer casts together with benign things like uninitialized variables?

(Another pet peeve of mine is that missing returns in functions is not considered a hard error. GCC 16 does not even issue a warning by default when compiling C code, which is just crazy. "-Werror=return-type" is the first thing I do in every new C or C++ project. I don't understand how this is still not the default...)

spacechild1··on Performance of Rust Language [pdf]
> You can do everything you can do with C++ static reflection.

Are you really sure about that?

I have a slight problem with such sweeping statements and also with your original claim that "Rust's metaprogramming capabilities are now on par with C++". I think you can only make such claims if you know both languages really, really well.

That being said, I acknowledge that Rust's metaprogramming capabilities have improved significantly in recent years.

> Both have been added and expanded.

In stable Rust?

spacechild1··on Performance of Rust Language [pdf]
> Rust's metaprogramming capabilities are now on par with C++ (they weren't always).

Is that really true, though? I haven't really written any Rust code, so I have no idea, but I don't think Rust has static reflection. Also, aren't const generics much more limited? I've also heard there is no template specialization and no "if constexpr". Or what about dynamic allocations in constexpr functions?

spacechild1··on C constructs that still don't work in C++
I see your point. It would be nice if a C-style cast behaved like a static_cast in C++, but that's not possible because of backwards compatibility. At least with GCC/Clang you can disable C-style casts altogether with '-Werror=old-style-cast'. (Maybe there is a similar option for MSVC.)
spacechild1··on C constructs that still don't work in C++
You are right that the C standard only talks about diagnostics, but this doesn't change the fact that implicit casts between unrelated pointer types are not treated as hard errors.
spacechild1··on C constructs that still don't work in C++
Thanks!
spacechild1··on C constructs that still don't work in C++
That's the comma operator. I didn't know you could overload it! That's pretty crazy. However, I have never seen anyone do that. Do you have any real world examples?
spacechild1··on C constructs that still don't work in C++
> but then most C++ seems to use a C-style cast

If C++ programmers do not use modern safety features, that's really their fault. C-style pointer casts should be flagged in code review.

> but that it becomes even less safe by adding a C-style cast.

At least in C++ there is a safer option. If you really want to be on the safe side, you can even to a dynamic_cast (assuming your code base allows RTTI).

> It is also not clear what is gained by forcing programmers to add a cast.

I think the point is to make it explicit and stand out.

spacechild1··on C constructs that still don't work in C++
I don't get your point at all. C++ has different casting operators (static_cast, const_cast, reinterpret_cast) that are strictly safer than C-style casts.

Also, let's not forget that implicit casts between unrelated pointer types is only a warning in C. Fortunately, modern C compilers started treating it as an error by default because it caused so much harm: https://gcc.gnu.org/gcc-14/porting_to.html. In C++ this was always a compiler error.

spacechild1··on C constructs that still don't work in C++
The one big and tragic exception being modules...
spacechild1··on C constructs that still don't work in C++
> They make sense but reduce type safety

Yes, downcasting can be unsafe and should be used carefully, but what's the alternative? At least in C++ you can't cast between unrelated types without an explicit reinterpret_cast (or C-style cast).

spacechild1··on C constructs that still don't work in C++
What's the "sequence point operator"?
spacechild1··on AI is just unauthorised plagiarism at a bigger scale
Oh, you're actually right! I did reply to the wrong comment... Mea culpa! Now I can't edit it anymore and look like an idiot. Well...
spacechild1··on College students drown out AI-praising commencement speeches with boos
Thanks for the tip! I will immediately try this line in my next professional e-mail. I am sure they will appreciate my courtesy.
spacechild1··on AI is just unauthorised plagiarism at a bigger scale
I don't think so.
spacechild1··on AI is just unauthorised plagiarism at a bigger scale
You don't seem to understand what FOSS is really about. The GPL has always been about the user. When a company license-washes a existing GPL software project and turns it into a proprietory product, the resulting code is not "free" anymore in the sense that the user has lost control. This is exactly what the author wanted to prevent in the first place by licensing their code under the GPL.
spacechild1··on AI is just unauthorised plagiarism at a bigger scale
> it’s a vibe against corporate use or control of software

The latter, i.e. corporate control of software, is exactly what copyleft licenses are trying to prevent. This is the very essence of the GPL.

The "license washing" of LLMs absolutely goes against the spirit of FOSS.

spacechild1··on AI is just unauthorised plagiarism at a bigger scale
It's actually costing them money/time! A friend of mine is a sysadmin at a university and he constantly has to deal with AI crawler DDoS-ing his servers. He said Anthropic is actually one of the worst offenders.

These AI companies are really just a gross example of the motto "Socialize the costs, privatise the profits". It's disgusting!

spacechild1··on College students drown out AI-praising commencement speeches with boos
> Just like this guy[1],

For the readers who are not aware: John Philip Sousa is, of course, not just some random guy, but the most famous composer of US-American marching music ("The Stars and Stripes Forever", "Washington Post March", etc.) I didn't know that he wrote essays for magazines.

This is really a fascinating document of a bygone era! Thanks for sharing!

spacechild1··on College students drown out AI-praising commencement speeches with boos
As long as it's for personal use you don't publish it on a streaming platform or try to make money off of it, there is no problem as far as I'm concerned.

The issue is really the people who fill the streaming platforms with slop to make a quick buck, drowning out the real artists and producers in the process. (As if the Spotify model wasn't already bad enough for artists...)

spacechild1··on College students drown out AI-praising commencement speeches with boos
For people who see art as human expression, AI generated music/literature/art is offensive. If they can't trust the artwork to be produced by a human being, they risk being betrayed.

Maybe it's a silly analogy, but you wouldn't buy unlabelled eggs in a supermarket if you are against cage farming because you don't want to accidentally support it.

spacechild1··on College students drown out AI-praising commencement speeches with boos
Do you really think the last sentence was necessary? It's a good answer otherwise.
spacechild1··on College students drown out AI-praising commencement speeches with boos
First, trickle-down economics is a modern neo-liberal concept.

Second, most people just do not earn enough to invest a significant amount of money in stocks. It's a system that largely benefits the rich. The more money you already have, the more you can invest.

spacechild1··on College students drown out AI-praising commencement speeches with boos
The parent comment was so sarcastic, it actually defeats Poe's law.
spacechild1··on Mercurial, 20 years and counting: how are we still alive and kicking? [video]
This sounds more complicated overall. Also, I would still need the staging area to only commit the debug statements.

As I said, I like to work on several things in parallel and I don't want to switch branches back and forth. That's just my workflow for my own projects and apparently I'm not alone.

spacechild1··on Mercurial, 20 years and counting: how are we still alive and kicking? [video]
Is there an equivalent to `git stash` in Mercurial?
← PreviousPage 6 of 34Next →