Please create an account to participate in the Slashdot moderation system


Forgot your password?

Comment: Re:Rent seeking (Score 1) 570

by eth1 (#48869973) Attached to: Microsoft Reveals Windows 10 Will Be a Free Upgrade

indicating Windows would be software that users subscribe to, rather than buy outright

No thanks. Just like with Adobe CS, it looks like it's time to buy up some licenses before they disappear. I have no interest in renting my software.

Renting software, especially non-essential software, is one thing, but renting the OS, without which the system won't even function, is more akin to renting ransom-ware. (good move M$, he said sarcastically)

It doesn't really make sense for MS to use a subscription model for the OS, even from their perspective. I would actually be perfectly willing to pay $20-30/yr, but the problem is, what happens when I stop paying, or some kind of problem occurs with the system? If it totally locks you out, you'd have people lining up with pitchforks and torches. If it just stops getting updates, you have a bunch of insecure Windows boxen, that would make MS look bad. You could potentially turn it into nagware, but you'd still have people just ignore it. Same with doing nothing - people would pay for the first year, then stop. So, you charge several years' worth of "subscription" up front, and then provide updates until the EOL date.

Comment: Re:Cost? (Score 4, Interesting) 426

by eth1 (#48792885) Attached to: Chevrolet Unveils 200-Mile Bolt EV At Detroit Auto Show

Tesla would seemingly need the battery cost reductions from their "GigaFactory" to get the cost of their 200-mile electric car down to $35,000, and Chevy is going to sell a 200-mile EV for $30,000 without those cost reductions?

Something's gotta give to pull that off.

Well, no one said they were planning on making a profit selling it. Could be propped up by other sales, just to push competitors out. Or maybe to game the "fleet average" fuel economy numbers.

Comment: Re:Re usability (Score 2) 151

by eth1 (#48740659) Attached to: In Daring Plan, Tomorrow SpaceX To Land a Rocket On Floating Platform

I'm sure that customers with astronomically expensive or critical payloads will always have the option to specify a "new" booster if they're willing to pay more.

On the other hand, if you need to launch a constellation of 20 satellites, it might be much cheaper to budget for 22-24 cheaper "used" launches than 20 more expensive but more reliable new ones.

Comment: Re:Pullin' a Gates? (Score 1) 449

by eth1 (#48717231) Attached to: How We'll Program 1000 Cores - and Get Linus Ranting, Again

Your Linux gaming machine shouldn't be doing more than 3/4 cores of CPU and handing the heavy grunt work off to the GPU anyway. No need for a 64 core CPU for that one.

I beg to differ. Games that are trying to run hundreds/thousands of copies of a unit AI or pathfinding (Dwarf Fortress, RTSs, etc.), or are doing tons of physics (KSP, From the Depths, etc.) are what usually end up causing slide shows for me these days, not the graphics. More cores & threads, please. (Yes, I'm aware that a lot of times this due to the games not taking advantage of existing cores)

Comment: Re:Pullin' a Gates? (Score 1) 449

by eth1 (#48717137) Attached to: How We'll Program 1000 Cores - and Get Linus Ranting, Again

Point of Linus was, taking a 6 core CPU, and replacing 2 cores with more cache and more transistors per core should make almost anything on Desktop run faster.

The real problem is that some desktop tasks really need one thread to run as fast as possible, and others (path finding for 200 drunken Dwarf Fortress denizens, for example) would benefit from having 100 somewhat slower cores. When you buy a desktop CPU, all the cores are the same, and you end up having to compromise between number of cores, single-thread speed, heat, etc.

Maybe it's time we started designing systems with two separate chips - one dual core chip optimized for running single tasks as fast as possible, and another with 10-50 simpler cores optimized for parallel tasks. I think we're halfway there already, what with GPUs being used that way to some extent, but standardizing it would actually allow non-custom applications to make use of it.

Comment: Re:Oh how great is this! (Score 1) 158

by eth1 (#48691263) Attached to: Norse Security IDs 6, Including Ex-Employee, As Sony Hack Perpetrators

So you might be a 'suspect'. In the real word (as opposed the paranoid crazy version here) someone would politely sit down with you and discuss a few things. Then someone else might come over and discuss some more things.

If you're a 'suspect', and they want to talk to you, then at a minimum, you're forced to pay to retain counsel (unless you're stupid, and talk to them without one). So you're screwed no matter what at that point.

Comment: Re:Tree of liberty (Score 1) 360

by eth1 (#48670681) Attached to: UK Man Arrested Over "Offensive" Tweet

And from Salman Rushdie:
“Nobody has the right to not be offended. That right doesn't exist in any declaration I have ever read.

If you are offended it is your problem, and frankly lots of things offend lots of people.

My favorite way to deal with people that claim a right to not be offended is to point out that I find them taking offense at whatever stupid thing they're on about very offensive, so by their own logic, they must stop being offended because they're violating my rights. :P

Comment: Re:Learning through repetition (Score 1) 515

by eth1 (#48582825) Attached to: Once Again, Baltimore Police Arrest a Person For Recording Them

Best solution? Encourage everyone to record every interaction with the police. This will systematically education the police on the rights of citizens.

Just like the 2nd Amendment public carry folks with a big old riffle slung over their shoulder on the sidewalk - it educated the police & public at the same time, and nobody gets hurt. (The the latter case, jimmes get russeled by some liberals, but, meh)

What we really need is a purpose-built "CopCorder" device. Has a camera and mic that records to local storage, and streams via 3/4G to mitigate confiscation. It would have a panic button that can be configured to lock it into recording mode for a time period, until the battery dies, or it's destroyed (so it's physically impossible to comply with any order to turn it off). The storage to local media means that if THEY destroy it, they've destroyed evidence, and you probably have a recording streamed of them doing it. If they confiscate it, you continue to get the streamed recording of whatever they subsequently do/say. Bonus if it can support a hidden external bluetooth or whatever external camera or mic, so if they take it and put it in their car or something, you may still get a recording.

Comment: Re:Quit buying games on day one (Score 2) 474

For that matter, quit buying them the first month or two. Let someone else debug them and when the game is worth actually playing, get it. Heck by then 1/2 the time the game has dropped in price 10-25% anyway.

I have given up on buying games before the first major patch, for that matter the first few if I am really interested and the reviews are that bad.

Or quit buying AAA titles at all. There are enough good indie games around that I haven't even got around to looking at the big names for the last two years. Even the pre-alpha/alpha/beta versions seem to have fewer bugs (and they get fixed faster) than a major release of a AAA title.

Makes you wonder just what the budget split is in the big studios between bling/marketing/executive leeches and actual development.

Comment: Re:Competition (Score 1) 265

by eth1 (#48265145) Attached to: Apple Pay Competitor CurrentC Breached

CurrentC also tracks information about a user's purchase history for merchants. CurrentC users can select what information they want to share with retailers and can opt out of marketing communications, according to the MCX website.

And if you really trust a merchant created system to respect your wishes and not track you, you're hopelessly naive.

Yep... read that quote very carefully. "...can select what information they want to share with retailers..." They'll still hoard everything, they just won't (voluntarily) share it with retailers (but might with anyone else who's not a retailer?).

Comment: Re:No Carriers (Score 1) 149

by eth1 (#48142639) Attached to: ISPs Violating Net Neutrality To Block Encryption

I call bullshit without more evidence. From the article:

When it detects the STARTTLS command being sent from the client to the server, the mobile wireless provider modifies the command to âoeXXXXXXXX.â The server does not understand this command and therefore sends an error message to the client.

This smells like a transparent proxy for mail, in a similar manner is providers have been doing transparent proxying for a long time. This does not necessarily have anything to do with DPI and selectively modifying server's responses to client requests.

The whole article is written by folks who clearly have no idea about how the internet works.

Worse, TFA only gives ONE example, then goes on to say, "...monitoring the responses from the email server in issue."

This seems to imply that not all email servers have a problem. Given that the symptoms (*****-ing out the SMTP banner, and blocking STARTTLS) are the exact behavior of a default protocol inspection config on a Cisco ASA or PIX firewall, I'm guessing that it's a major overreaction to the way the firewall in front of the destination email server is configured, and nothing to do with the ISP at all.

Comment: Re:Cisco ASA (Score 4, Interesting) 149

by eth1 (#48142575) Attached to: ISPs Violating Net Neutrality To Block Encryption

Google "250-XXXXXXXA asa cisco starttls" and you'll find this is almost certainly an ASA preventing TLS as configured on the device. Since it doesn't want TLS traffic, the config is to just mangle the packets. Well known effect, been around for years (5+). The FW admin needs to correctly deploy fixup, allow TLS or simply not inspect esmtp. Simple fix, documented in Cisco doc 118550, among many other places.

You beat me to it. That's the first thing that popped into my head, too. This (for some inexplicable reason known only to Cisco) is the *default* behavior of ASA and PIX firewalls, so really it probably just means that someone that didn't know what they were doing threw a firewall in the mix somewhere. It's an easy fix, but requires messing with policy-maps, which inexperienced admins often find confusing.

"May the forces of evil become confused on the way to your house." -- George Carlin