Not on the news in every part of the world. And it took a while from submission to presentation where the editor obfuscated the content as well, original submission here: https://slashdot.org/submissio...
The fact that someone screwed up is one thing, but it's good to also get some information on what the screwup was and the consequences of it - that it wasn't entirely safe from a health point of view. At least it didn't create mustard gas.
The military application is there if the quantum technology is protecting secret communication to a level that makes it impossible for anyone external to view it.
I wonder if they have been able to also implement a way to detect if someone listens to the signal using entanglement. It would be quite the deal if it was possible to detect that on a wireless signal.
In some solutions it's a lot better that the applications continues to run than that it fails on an exception and the application has to be restarted. Especially when you work with systems where downtime is a big problem then you better catch problems and log them but then continue execution.
A horrible practice in C# is that exceptions aren't declared by the methods that throws them, so never know when to expect them without reading the documentation. You can of course do a general catch-all catch statement in strategic places but it don't really make for a good application.
If you use Exceptions for the normal flow it's not a good idea but if you use them only for actual faults then it's not a problem. An Exception shall be an exceptional event.
The problem is that most cars are compromises for users. When I'm commuting to work I could use a pretty small vehicle, but when I'm out and about for other activities then a large vehicle suits me better. Living in an apartment restricts my options too, as well as road tax issues.
So either I have a commuting vehicle or I have a vehicle that also fulfills my other needs, having both is not really an option.
I also used it before Mosaic became the big thing on the net.
A reason why Gopher died was as I understand it that there were some licensing issues surrounding it. And the search engine Veronica went in hand with Gopher if I remember right.
As an user I wouldn't store my data with any kind of encryption that the provider offers, I would turn to only store it in Veracrypt archives or similar.
Slashdot Mirror
Not anymore, now we have suddenly created a peak in the search for that technology.
Here they only lower the speed limit, but they rarely enforce it so people drive as they see fit.
The few that follows the speed limit causes some "interesting" driving.
Yup - the engine is still there.
I agree - and when I get a security warning for my own stuff signed with a self-signed certificate I also happily skip it.
The problem with security warnings is that they are too clunky.
The next generation gaming will be in the cloud, requiring gigabit connection.
Interesting that Eliza have that capability considering that it was written so many years ago.
“Certainly the game is rigged. Don't let that stop you; if you don't bet you can't win.”
Robert A. Heinlein, Time Enough for Love
Read the RCN series of books starting with With the Lightnings.
Not on the news in every part of the world. And it took a while from submission to presentation where the editor obfuscated the content as well, original submission here: https://slashdot.org/submissio...
The fact that someone screwed up is one thing, but it's good to also get some information on what the screwup was and the consequences of it - that it wasn't entirely safe from a health point of view. At least it didn't create mustard gas.
The military application is there if the quantum technology is protecting secret communication to a level that makes it impossible for anyone external to view it.
I wonder if they have been able to also implement a way to detect if someone listens to the signal using entanglement. It would be quite the deal if it was possible to detect that on a wireless signal.
You can often add your own sort condition to the sort routine that takes care of how to decide the order of the elements.
There are rare cases where the library-provided sort routines aren't good enough, but they are usually from performance perspective.
Most cases where OOP is used and failed is caused by not understanding the complete solution and a correct break-down of the "problem".
It usually is a bad idea, but it depends on the case.
In this case I don't see the need to break down on separate lines. But otherwise I agree that breaking down to separate lines is good.
switch ( something )
{
case 1: { a=4; break; }
case 2: { a=5; break; }
case 3: { a=0; break; }
default: { a=1; break; }
}
Add a comment and it isn't empty.
In some solutions it's a lot better that the applications continues to run than that it fails on an exception and the application has to be restarted. Especially when you work with systems where downtime is a big problem then you better catch problems and log them but then continue execution.
A horrible practice in C# is that exceptions aren't declared by the methods that throws them, so never know when to expect them without reading the documentation. You can of course do a general catch-all catch statement in strategic places but it don't really make for a good application.
Fortran 77 has some good sides too, but it's from an age where a lot of the paradigms we follow today weren't invented yet.
What's worse than Matlab - Simulink.
Not only VB6, any VB.
But you forgot Delphi these days - the company behind it is falling apart since lead developers on the compiler have dropped off.
Was it Finnish?
If you use Exceptions for the normal flow it's not a good idea but if you use them only for actual faults then it's not a problem. An Exception shall be an exceptional event.
The problem is that most cars are compromises for users. When I'm commuting to work I could use a pretty small vehicle, but when I'm out and about for other activities then a large vehicle suits me better. Living in an apartment restricts my options too, as well as road tax issues.
So either I have a commuting vehicle or I have a vehicle that also fulfills my other needs, having both is not really an option.
Which is why Windows 10 was pushed so hard.
Usually just called smiley.
I also used it before Mosaic became the big thing on the net.
A reason why Gopher died was as I understand it that there were some licensing issues surrounding it. And the search engine Veronica went in hand with Gopher if I remember right.
As an user I wouldn't store my data with any kind of encryption that the provider offers, I would turn to only store it in Veracrypt archives or similar.
If you go over to EFF you will get a good list of alternatives to Skype and how secure they are to use. Skype is ranking at the bottom.
Skype for Business, which is formerly named Lync and doesn't have much to do with Skype for private users.