I think the reason why Prius owners are defecting to the Model 3 has nothing to do with EV vs. hybrid, but rather the status associated with the Model 3. The original Prius was a plain boxy car, but the sales really took off when they decided to make it completely odd looking (ugly). When this happened, hybrid owners could drive around displaying how "earth friendly" they are, and everyone would notice them.
Nowadays every other Prius is a taxi/Uber/Lyft, and they're fairly common. Why would someone want to drive around making everyone think you're an Uber driver? The Model 3 got so much press due its delays, and now there's a sort of mystique surrounding it. People will pay attention to you again, and you can claim that you bought the car because you want to save the environment, but in reality, you care about the status symbol more than anything else.
Isn't each new USB standard backwards compatible with the old one? If my next computer only has USB4 ports, I'm pretty sure my keyboard and mouse will still work with it. USB improvements aren't like switching from Betamax to VHS.
Yes, constant Java updates would be nice, but backwards incompatible updates do creep in. This tends to affect popular frameworks, in part due to using deprecated and backdoor features. Eventually the frameworks get fixed, but forcing a new version of Java all the time would cause more harm than good.
As for your work with.NET, are you writing GUI apps? For that, I can see how forcing new updates really helps users in the long run. Java is a complete failure for developing GUIs, mostly because Sun/Oracle decided to implement that capability themselves, even though they really had no clue how.
Is it truly always MongoDB or do you tend to observe these case more often? My selection bias always tends to observe cases of unprotected S3 data being leaked. Another thing to consider in this particular case is that it might not be a "piss-poor" admin, but rather an admin that wanted to easily export the data and sell it after they got fired. This raises another question: how many people approved of this configuration, and will they all be held accountable?
Most people don't have seven dogs. If she planned properly, then she would have considered the possibility that something might happen in the future which would prevent her from taking care of so many dogs. Anticipating a rent increase is just one possibility. Other possibilities are loss of employment, health issues, etc.
In order to compare selling phones to selling cars, you need to determine if peak innovation has been reached. It looks like this is happening with phones, but cars are still changing radically. Think about safety features, self driving, efficiency, alternative energy sources, etc. You can also sell cars by making styling and comfort changes, which are mostly cosmetic. There's not much you can do to a simple rectangular phone to make it look more stylish. Wrapping it in a new case is simpler and cheaper.
The only thing wrong with Java checked exceptions is that the mechanism is provided by the exception type definition instead of the usage of the exception. Declaring that an exception can be thrown from a method is an indication from the API designer that this is something important and should be considered by the caller. The caller should simply receive a warning from the compiler, which can be suppressed, or the caller should be able to throw the exception out as unchecked. The latter is possible today, using various utilities that take advantage of Java generics and type erasure. This is what I do nowadays, and I like that the compiler informed me that an important exception is possible and that I need to consider it. Considered and rethrown is perfectly fine sometimes.
The point of the article was about the current state of macs for "pro" users, not web surfers. The pros need something that doesn't go into throttled mode when running a big task, and the era of thick laptops appears to be over. Windows and Linux users have more options available, but Apple users are stuck with what they've got. If Apple doesn't address the needs of the pros, then they'll leave the platform. Maybe Apple doesn't care about them and sees more profit by catering only to the web surfing masses.
The cheapest thing is almost certainly also the greenest.
It's pretty trivial to come up with counter arguments. It's cheaper for me to dump the engine oil from my car down the storm drain than it is to collect it and transport it to a proper waste oil processing center.
I'm pretty sure that this is real news. That is, there exists a team of treasure hunters that have found a ship that they think has a big treasure. This just doesn't seem to be all that newsworthy because the treasure hunter's claims are a bit too far fetched.
If the ship was actually carrying that much gold, it would have been discovered years ago. I'm pretty sure Russia would like to have it back and would have started searching in 1905. And from TFA: 'Although the Shinil Group claims it saw what it thinks was a “treasure box” among the wreckage, there appears to be no confirmation the Donskoi really was carrying the reported treasure'
How did you arrive at the 80% decrease in bird population? Do you have some data that shows that the birds living in this area depend exclusively on a diet of mosquitos? If this is the case, then it would seem that the population of the other mosquitos will go down as well. Keep in mind that an 80% reduction of disease caring mosquitos doesn't imply an 80% decrease in all mosquitos.
The Github that sold for $7.5B wasn't the same Github that was created in three months. Hundreds of people, working for ten years made Github worth $7.5B. That initial version wasn't worth any more than the time spent developing it.
Not necessary. If you want to find what are the popular FOSS projects, just scrape all the hosting sites. Count the number of downloads, followers, committers, etc.
I'm concerned that someone might hear "object serialization is bad, but JSON is good" and make the same mistakes that were made with Java object serialization. Java object serialization is bad for the following reasons:
1. No validation. You might have a nicely designed object, well tested, and has all sorts of validation checks to ensure that the internal state is never broken. Java object serialization bypasses all validation, permitting an attacker to construct a malformed object. Exactly how that would cause a problem requires a bit more work on the attacker's part, by studying how the application reacts to the malformed object. Adding validation is supported with Java serialization, but its not used by default. The designers favored simplicity over safety. Does switching to JSON magically fix the validation problem? Nope.
2. Loading of classes that you didn't expect to load. If I expect to receive a serialized list of strings, there's nothing to prevent an attacker to providing a list of any kind of object instead, due to type erasure. The application might fail to process the list because of a ClassCastException, but the potential damage is done. Java serialization/does/ support filtering out classes that aren't expected, but this is off by default. You need to define the blacklist yourself. Why is loading other classes a problem? See the next reasons:
3. Custom code during deserialization, which is actually necessary for performing your own validation. You can define your own code which runs when the object is deserialized, and the code can do pretty much anything. An attacker might be able to trick the code (using malformed input) into doing something harmful.
4. Additional classes on the classpath. Even if all of your code is well behaved, and has proper validation checks, and proper custom code, you're still vulnerable because additional classes exist that you're not aware of. You had no idea that there's this class 'Q' which has broken custom code, because Q was sucked in as a dependency of something else. That popular open source library you're using might be exposing your application to attack, and you didn't even know it.
For anyone designing an object serialization mechanism, always consider the tradeoffs when trying to make the system easier to use. Always use whitelists for trusted code instead of blacklists. Always construct objects using the object's public API. Favor the use of standard representations (maps, lists, tuples) instead of supporting full-blown customization. A little bit of friction can be a good thing.
Back in the days that Amazon was burning cash and not posting any profits they were still mostly known as being an e-commerce book company. And today there's no company that competes with them on selection, prices, delivery speed, and customer service. When you want to go buy something online, where do you go first most of the time? The only real competition they face right now is in streaming media and cloud services.
...except Amazon has had little competition. There's a quite a few other companies producing successful electric and hybrid models, and they have been for many years. Is Tesla a failure? Only if they try to compete in the mass market. As a luxury brand they should do fine, but they decided to play with the big boys and it's not going to work out well. Especially considering that the Model 3 is a terrible design from a usability standpoint. If I could buy a Model 3 today, it's the last choice I'd make, electric or gasoline.
We live in a world of extreme surplus, but we're still stuck to the notion that you must work to live. For those humans that can't get a job, do we feed them or treat them as useless? If useless, do we exterminate them? If so, how far do you go? Until there's one last human and everything is automated for him/her?
I like the idea of Universal Basic Income, but I fear that human instinct will cause it to fail. Remember, work hard! Millions on welfare depend on you! I have a difficult time letting go of this notion.
My understanding is that a practical device for achieving simulated gravity with spinning would need to be very very large. Otherwise, any people moving around would feel terribly sick. I believe this is known as the Coriolis effect.
In what world is missing predicted goals by 50% okay? Given that Tesla has been in business for nearly 10 years, and they've been mass-producing cars for 5 years, they should have figured things out by now. For some reason Tesla is treated as a start-up, even though they've been around a very long time now. Investors should be worried.
I have two Firefox tabs open to Slashdot and the total memory consumed by the three Firefox processes I see is about 250MB (private working set). How many extensions do you have installed? Any ad blocking? Script blocking? I tend to block as much stuff as possible.
Slashdot Mirror
I think the reason why Prius owners are defecting to the Model 3 has nothing to do with EV vs. hybrid, but rather the status associated with the Model 3. The original Prius was a plain boxy car, but the sales really took off when they decided to make it completely odd looking (ugly). When this happened, hybrid owners could drive around displaying how "earth friendly" they are, and everyone would notice them.
Nowadays every other Prius is a taxi/Uber/Lyft, and they're fairly common. Why would someone want to drive around making everyone think you're an Uber driver? The Model 3 got so much press due its delays, and now there's a sort of mystique surrounding it. People will pay attention to you again, and you can claim that you bought the car because you want to save the environment, but in reality, you care about the status symbol more than anything else.
Isn't each new USB standard backwards compatible with the old one? If my next computer only has USB4 ports, I'm pretty sure my keyboard and mouse will still work with it. USB improvements aren't like switching from Betamax to VHS.
As for your work with .NET, are you writing GUI apps? For that, I can see how forcing new updates really helps users in the long run. Java is a complete failure for developing GUIs, mostly because Sun/Oracle decided to implement that capability themselves, even though they really had no clue how.
Is it truly always MongoDB or do you tend to observe these case more often? My selection bias always tends to observe cases of unprotected S3 data being leaked. Another thing to consider in this particular case is that it might not be a "piss-poor" admin, but rather an admin that wanted to easily export the data and sell it after they got fired. This raises another question: how many people approved of this configuration, and will they all be held accountable?
Most people don't have seven dogs. If she planned properly, then she would have considered the possibility that something might happen in the future which would prevent her from taking care of so many dogs. Anticipating a rent increase is just one possibility. Other possibilities are loss of employment, health issues, etc.
In order to compare selling phones to selling cars, you need to determine if peak innovation has been reached. It looks like this is happening with phones, but cars are still changing radically. Think about safety features, self driving, efficiency, alternative energy sources, etc. You can also sell cars by making styling and comfort changes, which are mostly cosmetic. There's not much you can do to a simple rectangular phone to make it look more stylish. Wrapping it in a new case is simpler and cheaper.
The only thing wrong with Java checked exceptions is that the mechanism is provided by the exception type definition instead of the usage of the exception. Declaring that an exception can be thrown from a method is an indication from the API designer that this is something important and should be considered by the caller. The caller should simply receive a warning from the compiler, which can be suppressed, or the caller should be able to throw the exception out as unchecked. The latter is possible today, using various utilities that take advantage of Java generics and type erasure. This is what I do nowadays, and I like that the compiler informed me that an important exception is possible and that I need to consider it. Considered and rethrown is perfectly fine sometimes.
The point of the article was about the current state of macs for "pro" users, not web surfers. The pros need something that doesn't go into throttled mode when running a big task, and the era of thick laptops appears to be over. Windows and Linux users have more options available, but Apple users are stuck with what they've got. If Apple doesn't address the needs of the pros, then they'll leave the platform. Maybe Apple doesn't care about them and sees more profit by catering only to the web surfing masses.
The cheapest thing is almost certainly also the greenest.
It's pretty trivial to come up with counter arguments. It's cheaper for me to dump the engine oil from my car down the storm drain than it is to collect it and transport it to a proper waste oil processing center.
I'm pretty sure that this is real news. That is, there exists a team of treasure hunters that have found a ship that they think has a big treasure. This just doesn't seem to be all that newsworthy because the treasure hunter's claims are a bit too far fetched.
If the ship was actually carrying that much gold, it would have been discovered years ago. I'm pretty sure Russia would like to have it back and would have started searching in 1905. And from TFA: 'Although the Shinil Group claims it saw what it thinks was a “treasure box” among the wreckage, there appears to be no confirmation the Donskoi really was carrying the reported treasure'
How did you arrive at the 80% decrease in bird population? Do you have some data that shows that the birds living in this area depend exclusively on a diet of mosquitos? If this is the case, then it would seem that the population of the other mosquitos will go down as well. Keep in mind that an 80% reduction of disease caring mosquitos doesn't imply an 80% decrease in all mosquitos.
The Github that sold for $7.5B wasn't the same Github that was created in three months. Hundreds of people, working for ten years made Github worth $7.5B. That initial version wasn't worth any more than the time spent developing it.
Citation needed? I've not found anything that says 3D XPoint doesn't work as you describe.
Not necessary. If you want to find what are the popular FOSS projects, just scrape all the hosting sites. Count the number of downloads, followers, committers, etc.
1. No validation. You might have a nicely designed object, well tested, and has all sorts of validation checks to ensure that the internal state is never broken. Java object serialization bypasses all validation, permitting an attacker to construct a malformed object. Exactly how that would cause a problem requires a bit more work on the attacker's part, by studying how the application reacts to the malformed object. Adding validation is supported with Java serialization, but its not used by default. The designers favored simplicity over safety. Does switching to JSON magically fix the validation problem? Nope.
2. Loading of classes that you didn't expect to load. If I expect to receive a serialized list of strings, there's nothing to prevent an attacker to providing a list of any kind of object instead, due to type erasure. The application might fail to process the list because of a ClassCastException, but the potential damage is done. Java serialization /does/ support filtering out classes that aren't expected, but this is off by default. You need to define the blacklist yourself. Why is loading other classes a problem? See the next reasons:
3. Custom code during deserialization, which is actually necessary for performing your own validation. You can define your own code which runs when the object is deserialized, and the code can do pretty much anything. An attacker might be able to trick the code (using malformed input) into doing something harmful.
4. Additional classes on the classpath. Even if all of your code is well behaved, and has proper validation checks, and proper custom code, you're still vulnerable because additional classes exist that you're not aware of. You had no idea that there's this class 'Q' which has broken custom code, because Q was sucked in as a dependency of something else. That popular open source library you're using might be exposing your application to attack, and you didn't even know it.
For anyone designing an object serialization mechanism, always consider the tradeoffs when trying to make the system easier to use. Always use whitelists for trusted code instead of blacklists. Always construct objects using the object's public API. Favor the use of standard representations (maps, lists, tuples) instead of supporting full-blown customization. A little bit of friction can be a good thing.
Back in the days that Amazon was burning cash and not posting any profits they were still mostly known as being an e-commerce book company. And today there's no company that competes with them on selection, prices, delivery speed, and customer service. When you want to go buy something online, where do you go first most of the time? The only real competition they face right now is in streaming media and cloud services.
...except Amazon has had little competition. There's a quite a few other companies producing successful electric and hybrid models, and they have been for many years. Is Tesla a failure? Only if they try to compete in the mass market. As a luxury brand they should do fine, but they decided to play with the big boys and it's not going to work out well. Especially considering that the Model 3 is a terrible design from a usability standpoint. If I could buy a Model 3 today, it's the last choice I'd make, electric or gasoline.
We live in a world of extreme surplus, but we're still stuck to the notion that you must work to live. For those humans that can't get a job, do we feed them or treat them as useless? If useless, do we exterminate them? If so, how far do you go? Until there's one last human and everything is automated for him/her?
I like the idea of Universal Basic Income, but I fear that human instinct will cause it to fail. Remember, work hard! Millions on welfare depend on you! I have a difficult time letting go of this notion.
...except OLED displays aren't very good for monitors. Although the displays do have countermeasures, static images can still cause burn-in artifacts.
Where are Pike's rants on Go? I tried a simple search but didn't find anything interesting.
My understanding is that a practical device for achieving simulated gravity with spinning would need to be very very large. Otherwise, any people moving around would feel terribly sick. I believe this is known as the Coriolis effect.
In what world is missing predicted goals by 50% okay? Given that Tesla has been in business for nearly 10 years, and they've been mass-producing cars for 5 years, they should have figured things out by now. For some reason Tesla is treated as a start-up, even though they've been around a very long time now. Investors should be worried.
I have two Firefox tabs open to Slashdot and the total memory consumed by the three Firefox processes I see is about 250MB (private working set). How many extensions do you have installed? Any ad blocking? Script blocking? I tend to block as much stuff as possible.
Where did the 12 come from? The 21k liters is the yearly consumption, not the monthly consumption.