Forgot your password?
typodupeerror

Comment Re:Is this really what people will pay for? (Score 0) 111

Our previous conversation was "closed".
So some answer to your CPC misconception ... which is off topic here.

a) 100 million of a bit more than a billion party members is a lot. It is around 10%.
b) in Germany not even 1 out of 80 is a member of a party. That is roughly 1%
c) in the US: parties have no real members
d) membership in the CPC is not "invite only" - you have to apply and do party work, like preparation of elections and counting of votes or other stuff, to be finally accepted

No idea where you get your information from.

I suggest to start reading the wikipedia articles ....

Comment Re:Is this really what people will pay for? (Score 2) 111

There was a player in EVE Online, who bulled his "guild mates" into helping him to get stuff he needed to build a super carrier. I think he got actually the first one of that type in game - not sure about that.

He sunk several 10k USD into it, in in-game currency to get what he wanted. As he was a general dickhead, when he made one of his first flights, perhaps even the first flight, he got "kicked from guild".

The whole universe was invited to kill him. I think the server crashed when 10k players where in the same system and nuked his nice new toy.

Comment Re:Why US and China won't go to war anytime soon (Score 1) 504

Last time, I looked the "don't mind a reunion" was 45 %.

China will get its ass handed to it if it ever tries with vast majorities of its forces being wrecked long before ever reaching Taiwan.
That is an extremely uninformed attitude. China is tech leader in nearly every military category. And the farking strait between mainland and Taiwan is short

Luckily for mainland China, an invasion is out of the question, so no one has to fear anything.

Comment Re: Renewable+storage = reliable (Score 1) 197

Yes, because you quoted me there.
And gave a stupid answer which had nothing to do with your quote.

Temperature "overload" - is not what the term "overload" in a grid means.

Overload means the voltage spiked. Not temperature.

Get a clue. No idea why you jumped into this discussion if you even do not remember what the topic was I talked about with my previous parent.

Comment Re: Summer vs Winter (Score 1) 197

Year, something like this, I would wear, too.
According to the weather app, it was 17C in the morning, with the note: "feels like 15C".
I had a long sleaved - relatively thick - long sleaved cotton shirt over my t-shirt, and: it was uncomfortably cold.
However, I had only slept 4h during the night.

Comment Re:Trust? (Score 1) 81

Safety does not need to be absolute to be present.

It is just your idiotic definition of your perceived idea of "safety". A safety belt is a safety belt. Nevertheless your car can be hit by a fuel truck, spilled all over and catch fire.

for instance not misusing NULL, but do you trust them, or, do you write code to check them?
Nope, if a language is null safe, like Dart, I do not check for null.

That would be idiotic.

The compiler would optimize away the null check, as it perfectly well knows: it can not be null.

And as soon as you change the code at a different place and introduce a null error: the compiler perfectly well knows that at the specific point a null can pop up, and a null check is needed (again).

Stupid question: are you actively setting variables to null, to help the garbage collector ... ???

I can take a C program, lint it with multiple linters, compile it with multiple compiles, a smart check to do when its critical code, and be sure the code is safe.
Nope, you will never be sure. As "unsafe" is not a flaw of the language or coding, it is a feature of the language.


int* ptr = 0xFFeF;
*ptr = 0; // or any other value

There is no farking way to know if that is safe or not: unless YOU know it. Hint: in Apple ][ it is either: ROM and what ever you write never happens, or it is the "language card", and you might destroy the Integer Basic interpreter or the Pascal P-Code interpreter, or what ever you have loaded there.

Or: You actually place a value there, that you really want to have there. No compiler or linter can know anything about that.

And that above: can in Rust only be placed inside of an unsafe block. In C you can do it anywhere, and no one - and especially no linter - can know if the code is correct and does what intended, or not.

Slashdot Top Deals

Aren't you glad you're not getting all the government you pay for now?

Working...