Slashdot is powered by your submissions, so send in your scoop


Forgot your password?
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. ×

Comment Re:Because consumer hype passes quickly. (Score 1, Interesting) 83

Unfortunately for Samsung, the problem may have crossed the threshold of marketing disaster. While the typical hype might be forgotten quickly, this problem turned into a federal offense to carry these phones on a US carrier.

The fact that air travelers must now suddenly be aware of their phone's make and model, and explicitly be aware of the Galaxy Note brand as "the banned one", is a PR disaster.

Most people don't know or care about these details which is why most of these events blow over after a few months. But this time, you are inconveniencing *all* air travelers to check their phones and become aware of the Samsung Galaxy Note brand in a bad way. So it's not just Samsung owners who have to pay attention to this. And the threat of breaking US federal law by not paying attention to this forces people to actually pay attention and inconvenience themselves, which helps drill in the bad brand connotation in a longer term way.

Then Samsung setting up recall kiosks at airports, while the right thing to do, is also a negative reinforcement of the brand image.

Samsung's saving grace is that they seemed to try to handle the problem in an honest way, without any coverup. (YouTube takedowns notwithstanding.) This helps keep the trust with their customers. If it later comes out that that Sansumg did something questionable, then they will have another PR disaster and I bet they will ditch the brand for sure.

Comment Re:Non-issue? (Score 2) 159

Most people aren't using a data cable any more. Remember when Apple finally allowed people to "cut the cable" and the rest of the world said, "about damn time"? Also, remember that the majority of people have Windows PCs, not Macs, and iTunes on Windows is a favorite past time for everybody to bash. Hence, the vast majority of people are using their iPhones in cordless mode, and presumably real world Wi-Fi on the iPhone is not enough to saturate the write limit.

And for those who do still transfer by cable, the vast majority of them are copying data back to their PC, not the other way around. The 32GB storage is too small. People are trying to offload pictures and videos they recorded on the go to free up space. So the write speed on the iPhone isn't significant for this case.

The most mainstream, intensive, data writing operation I can think of is video recording with the phone. As long as the iPhone's storage can keep up with how fast it can encode/dump bits, that is all that is needed. That was probably Apple's internal target spec, and paying any more for faster write performance is throwing money down the drain for both Apple and the customer they pass the cost on to.

Comment Re:But what is it used for? (Score 5, Informative) 252

Go was created by Rob Pike and Ken Thompson to solve real problems Google was having with its massive C++ code base.

The domain they work in is huge scalability, server backends.

You are right, it is a boring language, and that's just how they like it because Google is trying to solve their very specific problems without creating nightmares of new ones.

Go is designed to address many of the scale complexity problems they faced with C++, in both human terms and machine terms. In human terms, C++ is a very complex language. In machine terms, the joke was that Go was invented while waiting for a C++ compile job. (Google's build times are frequently measured in hours.)

Go also addressed scaling problems for other languages. Java, C#, Python, Ruby, NodeJS, etc. consume a lot more resources to spin up their virtual machines. At Google scale, this adds up to needing a lot more hardware, and a lot more power to run the data center, and a lot more cooling needed.

And since most of Google's server requests have no dependencies with each other, they could build directly into the language mechanisms to support concurrency. (And they make it a point to distinguish between concurrency and parallelism in computer science terms.)

In the end, Go is a fairly simple language that people from scripting languages can pick up reasonably, while getting pretty decent native performance, and also getting concurrency features which are optimized for their domain.

Comment Re: But what is it used for? (Score 1) 252

Be aware that coroutines are not the same as threads. They are much lighter and you can have a lot more.

Also remember, concurrency is not the same as parallelism. The Go literature tries very hard to remind people of this computer science fundamental.

Go's primary domain is server backends. The workload is basically handling many thousands of requests per second that are completely independent of each other (embarrassingly parallel). You are absolutely correct that you don't want zillions of threads. Coroutines can be very effective here.

Comment Re: But what is it used for? (Score 1) 252

> Go billed itself as a systems programming language.

They backed off on this claim a while ago. It's popularity and main use case has been as a server backend language.

Because the language compiles to native code and is closer to the hardware, everybody lumped it in with "systems" programming languages.

As a server language, it meets its objectives well. The native aspects give it an advantage over languages like Ruby (Rails), JavaScript (NodeJS), Python with smaller memory footprints and ability to take advantage of multiple cores/processors.

The built in design for coroutines makes it easier to do concurrency easier than other native languages which only have threads, and coroutines are much lighter weight than threads. (Please note, concurrency is not the same as parallelism. The Go literature tries very hard to remind people of this computer science fundamental.)

Comment Re: Surprised? (Score 1) 140

Dude, don't get me started on first world problems. We're about to get either Hillary Clinton or Donald Trump as President. Cut me some slack.

"Desperately needed" in the sense that Metroid 2 is the hardest game to play *legally* now and the longest in tooth technology-wise. Most people aren't going to casually go to eBay and pick up a working GameBoy.

The original Metroid got remade as Zero Mission. Super Metroid can be played on Wii U Virtual Console, and at least that game has color. Metroid 2 can be played on 3DS, but the low resolution monochrome graphics are a hard sell in today's modern world of retina displays and GPU in your pocket that are more powerful than the supercomputers of that era.

Comment Re:Surprised? (Score 0) 140

We just went through this a week and a half ago with the fan Metroid 2 remake AM2R. Nintendo shut that down in 2 days.

It is a brilliant remake, which was desperately needed because Nintendo seems to constantly ignore Metroid. If Nintendo shuts down something like this, Pokemon doesn't have a prayer.

Comment Focusing on the wrong systems (Score 1) 145

"But they have avoided the steep cost of rebuilding their reservations systems from the ground up,"

As somebody who had family affected by the Southwest outage 3 weeks ago, the reservation system was one of systems that remained up the longest. Southwest still could happily take your money even if nobody was going anywhere. (I suspect they manually took it down later it became clear the day was lost.)

Focusing on the reservation system sounds like a contractor lobbying to sell something...


Comment Re:Which version of C would you use? (Score 1) 315

I'm about to start a project for fun using C and I was wondering what the best version would be C89? C99? C11? It seems that nothing in C99/C11 is all that compelling and I'd like to have solid multi-threaded support (POSIX threads). Any reason to use anything other than C89 features?

C99 has some really convenient features:
- inline functions (note: these work slightly differently than C++ because they fix the problem of guaranteeing symbol generation for linkage concerns)
- long long
- _Bool and
- (uint32_t, int8_t, ...)
- // comments
- not requiring all variables to be declared at the top of the scope
- local scoping for for-loop variables: for(size_t i=0; ival; i++)
- variadic macros
- snprintf
- designated initializers
- restrict (for the hardcore performance sensitive folks)

Microsoft dragging its feet on updating Visual Studio's C compliance to C99 and beyond has been the major reason for people sticking to C89. But the rest of the world has moved on. Microsoft finally started waking up and realized not being able to compile massively cross-platform open source projects like Git was a problem. Also, Microsoft's iOS compatibility bridge requires a good C compiler as Obj-C is a superset of C and Obj-C devs take for granted a lot of the above listed features. Visual Studio 2015 has *finally* started adding a bunch of the more popular C99 features so it can finally compile Git, though it is still missing things, with __STDC_VERSION__ still not up to date as a telltale sign.

Comment Re:CGI was dumbed-down intentionally (Score 1) 125

Though what's interesting about the Return of the Jedi holographic Death Star briefing is also the point my prof was making. Despite the cool hologram, the rendered graphics in the hologram get intentionally dumbed down. You can see color filled translucent polygons and smooth curves (making the green and red colors of the moon and Death Star) in some parts showing the technology was actually there, but the major focus parts of the briefing are the Death Star and the tunnels to the reactor which are all wireframes, and the forest moon shield visualization is done with individual pixels.

Slashdot Top Deals

Enzymes are things invented by biologists that explain things which otherwise require harder thinking. -- Jerome Lettvin