Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: Re:There is no such thing as equal work (Score 1) 349

That problem is solved by providing paternity leave.

Solved is a pretty strong word to use to describe a benefit that lasts for, what, a few weeks? Maybe two months? Three?

Paternity leave is great and I'm all for it. But what happens afterward? Daycare, grandparents, or one of mom or dad stays home. And you can probably guess pretty well who it's going to be.

Comment: Re:Open source code is open for everyone (Score 1) 211

by ghettoimp (#48920433) Attached to: Serious Network Function Vulnerability Found In Glibc

To be fair, derision toward the likes of Microsoft has historically been pretty well warranted. Windows has, historically, obviously, been plagued by viruses, malware, crapware, etc., to a degree far surpassing any other operating system.

That's not to say this necessarily has anything to do with proprietary versus open-source. Obviously Windows has always been far more popular than any alternative, making it a much more tempting target for attackers. High profile bugs like shellshock have certainly pointed out that open source isn't a magical elixir that wards off security problems.

Nobody does security very well, yet. (Well, maybe excepting folks like the CompCert people and Sel4 people.) The underlying causes, I'm sure, is that it's not what your average (or even above average) consumer can evaluate and value, and it's not what your average programmer can deliver.

Comment: How about a web browser (Score 2) 264

by ghettoimp (#48805183) Attached to: Ask Slashdot: Linux Database GUI Application Development?
Web applications are portable, easy for users to install (they don't have to do anything), easy for users to update (they don't have to do anything), and accessible from just about anywhere on just about any device. HTML/CSS/JavaScript have matured a lot. It is very easy to prototype your application's UI, and easy to develop very slick looking applications with rich fonts, colors, fancy tables, etc. Unless there's some fundamental reason you absolutely must have a native UI, I would never choose a toolkit over the web.

Comment: Re:Not all that surprising... (Score 2) 131

by ghettoimp (#47659349) Attached to: Errata Prompts Intel To Disable TSX In Haswell, Early Broadwell CPUs
The FDIV bug was actually relatively limited in scope. Quoting Wikipedia, "Though rarely encountered by average users (Byte magazine estimated that 1 in 9 billion floating point divides with random parameters would produce inaccurate results),[3] both the flaw and Intel's initial handling of the matter were heavily criticized. Intel ultimately recalled the defective processors."

Comment: Re:It's open source (Score 1) 430

Eeh. I agree that, as a user, it's frustrating when software doesn't have proper documentation.

On the other hand, if someone donates his time to develop a program and makes it free software, it seems hardly fair to fault him for not writing documentation to go along with it.

Someone who really cares could, of course, do it themselves, or offer to pay the developer to do it. If most people don't care enough to do that, then maybe that's the problem to focus on.

If someone comes along and gives you a free hamburger, you don't complain that they didn't bring fries and a drink.

Comment: Re:CPU cycle != 1 second (Score 1) 189

by ghettoimp (#47026313) Attached to: Understanding an AI's Timescale

Not really.

A single "calculation" such as moving data between registers ("mov ax, cx") actually takes many clock cycles. The instruction has to be fetched and decoded, which may itself take several cycles. Then the instruction has to be scheduled, the operands have to be fetched from the register file, and eventually the result of the operation gets written back into the register file.

Thanks to pipelining, branch prediction, result forwarding, and so on, much of this latency can be hidden and, under ideal conditions, your processor might achieve an average throughput of many instructions per cycle because it is decoding and executing many instructions simultaneously. But, if you track any particular instruction from start to finish, it takes several cycles.

And of course, in practice there are much harder instructions than register moves. Division can take dozens of clock cycles. Waiting for data from main memory can take hundreds of core clocks. Mispredicting a branch stalls you out while you figure out where to start decoding from again...

Comment: The problem with this poll... (Score 1) 224

by ghettoimp (#46837545) Attached to: How much use would you get from a 1 gigabit internet connection?

By analogy: how much use would you get out of being able to drive your car at 1000 miles per hour?

My family lives almost exactly 1000 miles away, so once every few years I drive a thousand miles to visit them. So I suppose I'd get some use out of this, but of course I'm very reluctant to drive 1000 miles.

But the only reason I'm reluctant is because it (currently) sucks! It takes all day long and I have to plan it out. If I could make that drive in an hour, it would be so easy that I could just visit anytime, maybe every weekend.

It's silly to predict how much you'd use a connection like this based on what you're doing today, because your habits and the very marketplace of websites and services that you have to choose from is so very heavily influenced by the speeds that we currently have to put up with.

It's about how much you're not doing today that you could be doing, if you had a much, much faster connection.

Today's internet would be unusable if we had it ten years ago on dialup. Hopefully tomorrow's internet will be equally unusable on our current equipment.

Always try to do things in chronological order; it's less confusing that way.

Working...