Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?

Comment Re:Issue is more complicated (Score 1) 927

Both. Men need to learn to communicate _differently_ with women and consider their feelings. And women need to learn not to take everything so fucking personal.

Bzzzzzzt. Wrong answer! or You're being a fuckwad. Don't do this.

This is not a gender-based difference. It's bullshit gender-stereotyping to think women need thicker skins, or than men need to be softer when dealing with women. I know plenty of women that can dish out and receive much blunter criticism than average, and plenty of men who can't.

This is a matter of different communication styles and is irrespective of gender. Insular communities that have made bluntness (or worse, crudeness) an acceptable form of communication are inherently hostile to people that find that unacceptable. As a result, they will lose the support and contributions from people that value less toxic communication.

On the flip side, too much caveating and balancing of emotion can be stifling to those who do not value amicability in their communications. This also can have a negative impact on participation. This is basic human communication skills, and requires finding the right balance based on the personalities of the participants in determining what the collective group will value and respond best to.

It's very well known that the Linux kernel community weighs very heavily to one side of the spectrum, and honestly it's as the public face, Linus sets the tone (intentionally or not). This is a very good example of a well-respected person making it clear that they are self-limiting their contributions specifically because of how communications within the community are balanced.

Chalking this up to "men and women are different' is a disingenuous attempt to sidetrack the discussion with a red herring.

Comment Re:That's what Nokia, Moto, and Microsoft said (Score 1) 535

Exactly. People used WinCE devices because they had to (usually because of Exchange servers), not because they wanted to. Like so much else that MS does, they completely ignored the single most important aspect of a mobile OS - the user experience. Apple made that their #1 focus (remember how original iOS didn't support apps? or that they forced AT&T over a barrel to create visual voicemail?) and that's why they cleaned house. Android still hasn't caught up in a lot of areas which is why Samsung hasn't displaced Apple.

Comment Re:That's what Nokia, Moto, and Microsoft said (Score 1) 535

Umm... that's exactly what Microsoft did - there were even multiple versions of the Palm Treo running Windows CE aka Windows Mobile.

Microsoft's failure was in trying to chipping away at a desktop GUI until it was a PDA/Phone GUI and even Google made the same mistake with Android 1.0 (not sure if Android still uses "click" events instead of "tap" events, been a while since I looked at the SDK).

What Apple did brilliantly was take a fundamentally touchscreen phone-based GUI and extend it into a richer experience. No-one else other than Palm was ready to to move in the same direction, and they were hampered by massive management problems and their legacy platform.

Comment Re: Idiocy. (Score 1) 394

I'm the boss who determined and approved sublime as the text editor for the roles I oversee. A year later when my machine is wiped by a failure in the automatic deployment in the craptastic non-native, buggy, full disk encryption that IT forces in their standard, I requested the license to reinstall sublime (I have admin access). Answer? "We don't support that. Use the version of Text Wrangler that was put on the standard image for your role 3 years ago because we can't remember that we were supposed to update the standard image to sublime last year"

Comment Actually, RIAA isn't far off base (Score 3, Informative) 109

For once the RIAA actually gets it. They aren't claiming that BitTorrent (the protocol) is illegal or that it doesn't have legitimate uses.

Instead, they very specifically said that of the illegal file sharing happening over BItTorrent, the majority of it is coming from uTorrent, the client published by BItTorrent (the company).

They're clearly looking hoping the company will implement filtering to combat piracy (likely knowing full well that they'll kill the company in the process). This tactic has worked against other companies in the past who published software that was used more for piracy than legitimate uses (MetaMachine and eDonkey anyone?). Don't go after the technology - go after the company supporting the technology.

Comment Re:Safari was late in implementing some web APIs (Score 1) 311

App API support is totally different than in-browser support.

As a web developer, it's very difficult to determine which specific hardware my page is being rendered on. And the abstraction of the web implies that I *should not* be targeting specific hardware.

Hence OS level. Of course I shouldn't be targeting specific OS either, but that's a different story.

Comment Re:That's because... (Score 1) 311

Surely their native APIs are not so limited that they make you embed a whole browser in your application just to be able to do something.

Starting a sentence with "surely" to indicate disbelief is asking for confirmation of the statement contained therein.

But I wasn't the one playing grammar nazi with where question marks were being placed.

The API does provide a web view and I don't think there is really anything you can do in web app that you can't do in a native app. In fact for a long time it was the other way around, WebGL 3D graphics have only recently become available in Safari.

The HTML view originally did not allow any remote content loading. This is one of the limitations PhoneGap was originally created for. The "UIWebView" added later essentially embeds a Safari page in your app and prevents a very tidy container to limit how the contents can affect the container app.

Comment Re:Safari was late in implementing some web APIs (Score 1) 311

Firefox already does this with its WebGL driver blacklist. It does not support WebGL on pre-OpenGL 2.0 GPUs, such as the integrated GMA 3100 in the Atom N450 processor in my laptop.

Only because Firefox cannot control the hardware and the software layers. What's the point in saying your software supports feature X if all the hardware it runs on can't support X? Apple controls both sides within their products so they can choose what "support" means. They chose to make iOS8 the point where hardware-accelerated 3D was supported inside the browser because that's the release where all their supported hardware could handle the feature and do so without performance degradation.

Again, as a developer or product manager, "works in iOS8" is a lot easier to worry about than "works in iOS8, but only on iPhone 4s and later (not iPhone 4), iPad 3 and later (but not the first iPad mini) and only on the last version of the iPod Touch". Limits on hardware fragmentation is considered one of the benefits of iOS and OSX development.

Comment Re:Enterprise (Score 1) 311

Standards - They've supported tons of standards, and all their enterprise/business support tool chains are built up from *NIX libraries. Yes, they layer their own customizations on top (just like everyone else) and yes, these often change between releases without warning (but that's the point about secretive roadmaps).

It's pretty hard to claim that Safari always sucked. Webkit was a fork of KHTML and from day one it was better than any KHTML browser (Konquerer was horrendous!). By limiting the browser to just the standards they quickly got other browser makers to improve their standards support (hey, there's "standards" again!). The only "enterprise-friendly" browser has always been IE, and that's only if you define "enterprise" as "dependent on IE-specific behaviors".

Of all of these, secretive product roadmaps is the only one really at fault for lack of enterprise adoption. Speaking of enterprise adoption, which enterprise companies don't support iOS devices in this day and age?

Comment Re:That's because... (Score 1) 311

With the question mark it is an implied continuation of the previous question.

"You realize ... there are a lot of limitations in the iOS APIs because they'd prefer you do certain things in browsers where it can follow standards instead of being some developer's hack-up of poor security or poor performance?"

Speaking of which, Mr. Grammar Nazi, you forgot your own question mark:

Surely their native APIs are not so limited that they make you embed a whole browser in your application just to be able to do something.

For an example, try loading a publicly hosted URL directly in an HTML view with an app. Oh right, it used to be blocked because its a huge security risk on the level of stupidity that PDF is known for, and it directly duplicates what the browser should be doing. Instead you can use platform APIs to request content for your your view, or use the platform-provided wrapper to display remote content safely - which by necessity require you to build in a more responsible and secure way.

Comment Re:Safari was late in implementing some web APIs (Score 2) 311

For instance, please explain why it took until iOS 6 for HTML/JS apps to access the user's photo and video libraries through an controls

Because exposing a user's files to any in-page behavior is a security risk and needs to be handled in clean managed ways with limited APIs? The hooks they established to do this went far beyond just browsers and also affect how content is provided to apps and 3rd party API calls.

and until iOS 8 for HTML/JS apps to put the most basic 3D view on screen (WebGL).

Because 3D in browser has gone through a lot of iterations over the years? Read up on VRML for example. WebGL is a relatively recent fad extended from OpenGL and so relies on device drivers for hardware acceleration. Rather than have pages that would perform poorly or be inconsistently incompatible, Apple didn't guarantee provide the feature until OS-supported devices could support it. It's bad enough to run into situations where "it works on latest release, but not previous ones". Imagine how bad it would be if "it works on the latest release, but only on these specific models". That's a non-starter when it comes to the world of HTML/JS/CSS development.

Comment Re:That's because... (Score 1) 311

LOL - you realize the the original iPhone allowed *only* HTML/JS apps? And there are a lot of limitations in the iOS APIs because they'd prefer you do certain things in browsers where it can follow standards instead of being some developer's hack-up of poor security or poor performance?

Comment Re:jQuery is crapware (Score 1) 126

You bitch about devs lazily abusing repeated DOM lookups instead of variables, but that is exactly what prompted the Javascript speed war that even resulted in massive improvements on IE. So even if you think it's bad practice, it helped everyone.

Comment Re:Define controversy... (Score 2) 126


If you're browser-side JS developer (as opposed to something server-side like Node.JS) and you haven't worked with JQuery, then you're not really a browser-side JS developer. It's just far too widely used to pretend that it doesn't or shouldn't exist. And most of the consistency across other frameworks (like using the $ shortcut or css selectors to target elements in the DOM) comes from the popularity of JQuery to begin with.

You've been Berkeley'ed!