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

 



Forgot your password?
typodupeerror
×

Comment Doesn't always work all that well... (Score 1) 274

I'm 35. I recently left a startup where most of the people there were about 10 years earlier. The difference is a bit more than age for me - I spent most of the 10 years I had on them working for a University, but the combination of age and differences in interests were very rough - I didn't feel that I fit in, I didn't hang out with them after work, I didn't want the same things out of life, and so on. It can be rough.

Comment Brain damaged project (Score -1) 134

I like how they place an emphasis on it being small, but they require you to link the whole damned thing into your app. And of c ourse that doesn't help you write correct software, because you won't figure out if you really need -lm unless you also test your app on a more correct libc.

Lightweight and correct indeed.

Comment Re:Native Targets? (Score 2) 166

My point is that with modern VMs and JITs and partial nativisation and other systems/PL technologies, you no longer should care whether something "runs native", and that that's a distinction that is so blurred anyhow that it barely makes sense to talk about it. It may have once been important and simple, but nowadays it is neither.

Comment Re:Native Targets? (Score 3, Insightful) 166

So what? Perl can compile to C too, by bundling the interpreter into your target binary. Windows apps can compile "to native" as well. Neither makes it exactly native, similarly to having your app interpreted by a native HTML5 engine is.

The most native way something can be for a platform is to be written directly for its platform, bound directly to its APIs. Anything but that gets very conceptually fuzzy. And if you're worried about this for performance reasons, you should look at the Quakelikes that have been ported to HTML5.

Communications

Killing Net Neutrality Could Be Good For You 361

Hugh Pickens DOT Com writes "Berin Szoka and Brent Skorup write that everyone assumes that cable companies have all the market power, and so of course a bigger cable company means disaster. But content owners may be the real heavyweights here: It was Netflix that withheld high-quality streaming from Time Warner Cable customers last year, not vice versa and it was ESPN that first proposed to subsidize its mobile viewers' data usage last year. 'We need to move away from the fear-mongering and exaggerations about threats to the Internet as well as simplistic assumptions about how Internet traffic moves. The real problems online are far more complex and less scary. And it's not about net neutrality, but about net capacity.' The debate is really about who pays for — and who profits from — the increasingly elaborate infrastructure required to make the Internet do something it was never designed to do in the first place: stream high-speed video. 'While many were quick to assume that broadband providers were throttling Netflix traffic, the explanation could be far simpler: The company simply lacked the capacity to handle the "Super HD" video quality it began offering last year.' A two-sided market means broadband providers would have an incentive to help because they would receive revenue from two major sources: content providers (through sponsorship or ads), and consumers (through subscription fees). 'Unfortunately, this kind of market innovation is viewed as controversial or even harmful to consumers by some policy and Internet advocates. But these concerns are premature, unfounded, and arise mostly from status quo bias: Carriers and providers haven't priced like this before, so of course change will create some kind of harm,' conclude Szoka and Skorup. 'Bottom line: The FCC should stop trying to ban prioritization outright and focus only on actual abuses of market power.'"

Slashdot Top Deals

Dynamically binding, you realize the magic. Statically binding, you see only the hierarchy.

Working...