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

 



Forgot your password?
typodupeerror
Slashdot Deals: Prep for the CompTIA A+ certification exam. Save 95% on the CompTIA IT Certification Bundle ×

Comment Re:Learning to program by Googling + Trial & E (Score 2) 293

Yes, anyone can code, just as anyone can build a house. Whether or not the house collapses immediately, whether it has any real value, or by any other measure still depends on the skill of the builder, just as in software.

If builders built buildings the way that programmers wrote programs, then the first woodpecker that came along would destroy civilization.

Comment Re:You keep using that word. I don't think it mean (Score 1) 307

But there'd be no reason to. Industrial power is different because you're paying for infrastructure built just for you, so you pay based on peak usage, not KWh. Water hookups just for outdoor use may have non-potable water, or more commonly, you pay normally for the water but you don't pay for sewer (which costs 3x in some places).

For data, the only difference is "upstream" vs "downstream", which is quite significant. Charging based on the of the data shouldn't fly (that should be the whole point of net neutrality regs, reality aside). Backhaul is all price-per-GB anyhow as I understand it.

Comment Re:Does Sony also provide... (Score 1) 100

The eye has higher effective resolution than Apple has led us to believe with their "retina" marketing. This article shows how human eye can see 530 ppi resolution in a 20 x 13.3-inch print viewed at 20 inches. http://clarkvision.com/imagede...

Which is hardly news in the print world. Most fonts are passable, but noticeably less than perfect at 600dpi. Some fonts still don't quite work right at 1200dpi. Of course, that's without anti-aliasing. Grayscale at 600 dpi can do a pretty good job of representing print if the anti-aliasing is well done.

Comment Re:Sans-Serif (Score 1) 119

Because more people access Google from their tiny telephone screens, where the serifs get lost anyhow.

Small screens still have lower resolution than print, to be sure, but with reasonable anti-aliasing any modern small display will never "lose the serifs". But serifs are an odd on a title/header font anyhow - they're a tool to make it less fatiguing to read large blocks of text, irrelevant to logos.

Comment Re:Poor example (Score 5, Insightful) 398

it will be always be a challenge to have these control systems anticipate what human drivers intend to do.

This is complicated by the fact that some human drivers do not even know themselves, what they intend to do. So how should a computer control system be able to anticipate what a human driver intends to do, when the human drivers don't even know themselves?

I really don't think it is that many . . . maybe only 1% of all human drivers. However, one clueless driver can confuse and tie up 99 drivers who know where they want to go, and can communicate it to other drivers.

It's like being on a escalator at the airport or train station. Two folks don't know where they are going. So they stop dead in their tracks at the end of the escalator, blocking the path for all the other folks on the escalator. An accordion affect ensues, with all the folks on the escalator getting squished together. The two people doing the blocking, are totally oblivious to this fact. Their field of vision ends at their own noses. They are entirely engulfed in themselves, and can't even conceive that there are other living beings around them.

This is what happens on the road, as well. The driver of the car parked halfway into the street, is just not capable of thinking, that other drivers might be confused by this. Is the car really parked? Or is the driver trying to park? Or maybe trying to drive away . . . ? At any rate, some drivers need to be taught that it is terribly important to anticipate how others might interpret their actions.

Comment Re:How is this legal? (Score 3, Interesting) 297

There have been cases where EULAs that were not presented before the product was purchased were declared grounds for returning the product for a full refund. There is also a huge body of case law on contracts in general. In common law countries, the requirement for a contract to be binding is that a 'meeting of minds' has occurred and it is up to the party wishing to enforce the contract to prove this. Signatures, for example, provide strong evidence (and the backing of case law that they count as evidence), but there is very little statute law defining what makes a contract binding (though some on what makes one non-binding, such as requiring one party to break a law).

Comment Re:No Apple (Score 1) 89

How do those numbers change if you look at revenue? Last numbers I saw showed that the iOS ecosystem made about as much money as the Android one for app developers. If you have a small market, but that market has the majority of people who have disposable income and are willing to spend it, then it's not such a good idea to ignore it.

Comment Re:It's no ARMv8 (Score 1) 52

It depends hugely on the workload and it also depends a lot on the core. The ARMv8 ecosystem is quite diverse. For example, you have some players like nVidia's Project Denver, which fuses some of their GPU ideas with designs inherited from Transmeta. The Denver core is VLIW, but with staggered pipelines, so that results from one instruction in a VLIW bundle can be fed into the next (without needing rename registers, which are one of the biggest power sinks on a modern OoO CPU). When you start a program running, there's a simple decoder that turns ARM instructions into fairly inefficient VLIW instructions, but after a little while hot loops are optimised by a JIT and get a lot faster.

At the other end of the design spectrum, Cavium's Thunder X has 48 ARMv8 cores (not hyperthreads) per die, and supports dual-socket configurations for up to 96 processors per board. Individually the cores are weaker than a Xeon, but on some workloads (network routing, some database serving), they're pretty impressive in aggregate. That many physical cores also makes it easier to load balance VMs in a hosted environment. This is especially good for the kind of workload where most clients are idle for a lot of the time, but when they're busy they're very busy.

Comment Re:the comparison is pointless (Score 2) 76

-Os frankly is of little interest to desktop developers. Heck, I spend quite a bit of my time on 8 bitters these days, and I think you're being pedantic.

You might want to tell Apple that, as they compile everything with -Os. It turns out that instruction cache pressure still matters, and matters a lot more if you're in the kind of environment where multiple applications are competing for space.

Comment Re:Willl any of this affect Swift performance? (Score 1) 76

Objective-C++ also works pretty well now (including in the open source implementation), to the point that I generally prefer C++ containers to Objective-C ones. std::unordered_map seems to be faster than NSMutableDictionary for most things, and has the added advantage that you can have primitive types as keys or values without resorting to boxing. The big problem for Swift is that the FFI to C is fine, but the FFI to C++ is basically nonexistent.

Comment Re:Yay for OSX (Score 1) 76

and I believe are its biggest contributors

I'm not 100% sure, but I think that Google passed Apple as the largest single contributor (incrementally, at least, not cumulatively) somewhere in the 3.5 to 3.7 time frame. A lot of the Apple compiler team has been busy with Swift.

Nature always sides with the hidden flaw.

Working...