porise · HackerTrans

3 か月前議論

Sorry for not answering your question, but asking how to not let something do your work for you not be so exhausting is like listening to a billionaire complain that they have to instruct their maids and chefs too often.

porise

3 か月前議論

Yeah I wouldn't like this in a code review. Add one more line of code so I don't have to investigate foo().

That's my fundamental gripe with C++

int i = 0;

function_0(i,...);

...

function_9(i,...);

which one changes i? It's not obvious in a code review due to default mutable references.

porise

3 か月前議論

Reading this makes me wonder if Easter eggs are ever appropriate for something as ubiquitous as man.

porise

3 か月前議論

And yet, none of them work with std::regex etc.

porise

3 か月前議論

I don't care until they stop pretending Unicode doesn't exist.

porise

3 か月前議論

It's not as bad as JIRA, although JIRA is marginally more useful than LinkedIn.

porise

4 か月前議論

I'm still waiting for C++ to support Unicode properly.

porise

4 か月前議論

Rusts tradeoff is awful. People organize struct members in the logical ways in which they will be accessed. Rust just decides to do things different so they can say they do things different and "better" than the old C. The featured article is an extreme case but other normal cases would have the same issue. Packing structs should be the exception.

porise

4 か月前議論

Why is rust allowed to reorder fields? If I know that fields are going to be generally accessed together, this prevents me from ordering them so they fit in cache lines.

porise

5 か月前議論

I heard they changed it to 5Rs.

Refuse, reduce, reuse, recyle, rot.

porise

5 か月前議論

Nope. If someone did that it should be reported if it's against the rules here.

porise

5 か月前議論

I've had two accounts. I changed because I don't like the history (maybe one other person has the same opinion I did?). Anyways it's pretty obvious why this is an issue. Microsoft has a historical issue with being brutal to competition. There is no oversight as to what they do with the private data on GitHub. It's absolutely an antitrust issue. Do you need more reasoning?

porise

5 か月前議論

Can they use Github to their advantage to maintain a monopoly if they are nefarious? Think about it.

porise

5 か月前議論

Companies used to be forced to sell parts of their business when antitrust was involved. The issue isn't the downtime, they should never have been allowed to own this in the first place.

There was just a recent case with Google to decide if they would have to sell Chrome. Of course the Judge ruled no. Nowadays you can have a monopoly in 20 adjacent industries and the courts will say it's fine.

porise

5 か月前議論

What antitrust issue does my open source software have?

porise

5 か月前議論

Take it away from Microsoft. Not sure how this isn't an antitrust issue anyway.

porise

5 か月前議論

Perl was written to write more complicated bash scripts. It's so seamless to call and handle shell commands and the first class regexes make it terse in a way that's appropriate for this use case.

porise

5 か月前議論

Just say Google. The need for keywords plastered everywhere (often hidden in the HTML) was their invention.

porise

5 か月前議論

I guess package managers win in the end. I got two emails from my IT department in the last year telling me to immediately update it.

porise

6 か月前議論

I wish the people who wrote this let us know what king of codebases they are working on. They seem mostly useless in a sufficiently large codebase especially when they are messy and interactions aren't always obvious. I don't know how much better Claude is than ChatGPT, but I can't get ChatGPT to do much useful with an existing large codebase.

コメント