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


Forgot your password?

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:Question still remains (Score 2) 110

by RabidReindeer (#49499461) Attached to: Google Adds Handwriting Input To Android

And now we have the tablet market.

I've been using the Google handwriting recognition installable "keyboard" for 2-3 days now.

Unlike the Newton, which was famous for its inability to accurately recognize what you input, the Google handwriting actually works pretty well. Although it's occasionally slow. I think it's doing a lot of its magic by talking back to a Google server.

Unfortunately, I've gotten into the habit of writing Grafitti-style, so using "real" letters and writing them across the input area instead of within a limited box doesn't come naturally to me any more. I could do Grafitti faster than I can type.

Also, the "forward-space gesture" just enters a dash. There's an actual "space bar" at the bottom of the input area that you have to tap.

Comment: Re:Lets use correct terminology. (Score 3, Insightful) 170

by RabidReindeer (#49496625) Attached to: MakerBot Lays Off 20 Percent of Its Employees

That smells too much of the zero-tolerance, total-fear climate that typifies the USA these days.

If you have enough unstable employees that you need to be that worried, you were doing something major wrong long before "firing" time.

In any event, laid-off people aren't known for running amok in the parking lots. They come back later, heavily-armed and lay waste to the remaining employees (and customers).

Comment: Re:It is unclear... (Score 1) 294

You don't need a massive conspiracy. You don't even really need a conspiracy.

All that's needed is for people - politicians and the populace - to accept just a little more incursion every time the investigation and enforcement people claim that their job is being made "too hard".

Inch by inch, until one day, it's no longer "We're free to do travel about and do things", but "Your papers, please!"

Comment: Re:Can we be sure there are no exploits? (Score 2) 207

by RabidReindeer (#49470005) Attached to: Linux Getting Extensive x86 Assembly Code Refresh

Because, among other things, compilers (such as C) can automatically generate pipeline-friendly machine language. All that extra bookkeeping is trivial for an automated process.

And a compiler can re-optimize the entire module every time they compile.

Hand-optimized assembly lost it when IBM introduced Pascal/VS. I COULD optimize code as good or better than it did, but considering that it was doing large-scale register reassignments, the equivalent amount of hand optimization for just one minor source change/recompile would have taken me a full day or more.

And my boss wouldn't have tolerated that.

Comment: Re:Can we be sure there are no exploits? (Score 1) 207

by RabidReindeer (#49468849) Attached to: Linux Getting Extensive x86 Assembly Code Refresh

Yeah, yeah, All You Have To Do, yada yada.

Unlike the old dinosaur mainframes, modern microprocessors run internal pipe lines and what instructions follow what other instructions can make a big different.

Aside from that, one reason that raw assembly is no longer the cult favorite it used to be is that the average C statement is probably going to produce 5-10 machine-language instructions. More instructions means more work to create or replace them, more places for potential bugs, and less flexibility to make high-level architectural changes.

Comment: Re:Or a simple solution. (Score 1) 95

by RabidReindeer (#49447819) Attached to: Microsoft Creates a Docker-Like Container For Windows

You have the same issues with Docker containers you know. You still have to set up DB connections, install data, etc, etc. Config files and static data can be put anywhere in both situations, so Docker really doesn't solve much more in the case you supplied. All you're doing is sticking it into a docker image rather than a directory structure.

Not entirely. In many apps, there are internal objects and external objects. When the app is installed as a native OS app, the difference is not apparent, so you have a fairly untidy collection of stuff all over the place.

When I package for docker, I leave most of the app's characteristics internal, and the docker run specs clearly document the external characteristics. At most that's usually config, data, and log volumes and one or 2 ports.

The difference between a container and just trying to grab everything in a tarball is that A) invariably something important doesn't make it into the tarball and B) the target system may have conflicts with what's in the tarball. For internal resources, all that's tidily collected within the Docker image and hidden by container virtualization. For external resources, I can, if necessary simply remap locations, since I'm not in the habit of making containers use shared external resources. Plus, thanks to container linking, I can often inject certain characteristics from container to container and not even have to worry about their external aspects.

It's true. No such thing as a Silver Bullet. And any sufficiently-advanced technology can be turned into a screaming nightmare when placed in the hands of incompetents. Done judiciously, however, I find Docker makes for a tidier system, and one that's a lot easier to assure business continuity on.

Comment: Re: And it's not even an election year (Score 3, Insightful) 407

Why does it not work? Even the Irish and Chinese railroad workers were made citizens. We brought in temp workers, and kept them. Africa first, others later. All were made citizens (and yes, slaves were citizens, just not free ones). We've always had a love-hate relationship with workers, but, until recently, were happy to make them citizens.

That's the point, though. All the asians I know of who are citizens didn't become citizens via H1-B, they did it on our own.

Yes, my state - and probably yours - is full of towns whose names and history reflect the fact that someone brought over people en-masse from some other town, village or country primarily to serve as cheap - and frequently semi-captive labor. That's not even touching the importation of slaves from Africa.

And those people often brought financial hurt to established citizens because they were easier to control and to keep under low wages.

But they were nevertheless brought in as permanent residents with citizenship rights - even the slaves, allowing for differences in who got what "citizenship rights".

The H1-B program was specifically designed to bring in temporary immigrants, not people who'd eventually grow to become a permanent part of the tax-paying populace and even to demand competitive wages instead of exploitative ones.

"Oh what wouldn't I give to be spat at in the face..." -- a prisoner in "Life of Brian"