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


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Re:Rural has to be solved to go mainstream (Score 1) 381

I'm saying that the "rarely" is the problem. Until that is solved you have to:

a) Own a separate car that is rarely used just to go out for those rare events.
b) Rent a car to go out into the boonies. This may or may not be feasible to do on a whim.
c) Don't go.

"a" is a huge financial hurdle. "b" has limitations on spontaneity. "c" represents a freedom I'm not wiling to give up.

Comment Rural has to be solved to go mainstream (Score 0) 381

Everyone that keeps saying that the autonomous cars are just around the corner all live in big cities. To get to the point they work without a steering wheel (aka manual mode) these companies have to solve for rural driving. Until the cars can reliably drive up a back woods, rocky, single lane mountain road they are worthless.

Think of going camping. Are you going to be able to take your family camping in your autonomous minivan? What about going for a tour of scenic back roads in Montana, Alaska, Wyoming, the Dakotas.

Last, how are these cars going to navigate through a rural dirt road with 2 feet of fresh snow on it.

These are all problems the people in the big cities are going to have to live with. They may only live with it a very very small percentage of the time, but it's a major hurdle to overcome.

Comment Based on experience (Score 2) 274

Based on my experience at a fortune 100 company with a heavy interest in Java. Don't use Java. Use PHP or LUA as a cgi. Your sysadmins who have to keep your application up will thank you.

  • Do not use java. To make it work rigth you have to go against everything the community says you should do.
  • Do not use NFS
  • For file storage use something like MogileFS. It is not likely the best, but it's a proper example of what you will want
  • If you use a database you MUST understand and use the relational aspects of things. If you use the database as just a key:value store I will personally beat the ever living shit out of you.
  • Use loose coupling and sharding of your data. Multiple databases on multiple replicated servers is happy. Isolate each aspect of your product into separate databases.
  • On a related note it's likely that only accounts need to be replicated between databases. It's not hard and will allow you to scale very large
  • If you use memcached do not store individual bits of data. Store complete rendered data only
  • Use cgi. Mod_* and Java are a bitch to debug. Php and lua work well for this. If you have something that is multi-tenant multi-version this applies even more.
  • Do not use web session affinity.
  • Do not use full text search in a database
  • Do not use stored procedures
  • Do not use large frameworks. If you must use a framework use small ones dedicated to a small subset of functionality. No framework you use should use a database.

Comment Re:Not even /.ed yet! ;-) (Score 1) 150

Our interviews for sysadmins always ask what editor people use on their Linux boxes. People always think it's a funny joke due to the vi/emacs war, but it is actually a serious question and there is only two wrong answers: nano and pico. If you answer nano or pico you will not get hired.

It actually shows that you do not know the system as well as you are claiming. nano/pico will silently corrupt files on you.

Try it for yourself. Create a file with long lines in vi/emacs. Have a bunch of words on the long line. Now open that file in pico/nano and put a single space at the beginning of the long line and save the file.

If you go in with emacs/vi you will now notice an extra carriage return that you did not put in. If I ever catch a sysadmin using nano on a system file it is cause for termination.

Comment Re:'Kill shot' cameras (Score 5, Interesting) 263

Except for varmint shooters (I'm one). That's all for the kill. Gophers/Prairie dogs exploding in a ball of red mist is just amazing.

They make really heavy guns shooting small caliber bullets out of medium cartidges (.204 Ruger/.17 Fireball) for two things: Target (read paper) and Varmint (dead sploded things). The heavy guns let you see the target in scope as it blows up. Without the combination of lighter cartridge and heavy gun the recoil would not allow you to see the action.

The design of the varmint bullets is such that you have a bullet spinning at a couple hundred thousand RPMs that is highly frangible. This is what makes the things go *poof*. There is far more varmint type bullets from commercial manufacturers than there are target bullets in these calibers. That's what people want, and for good reason: it's fun.

Down south some of these critters actually get big enough to be a source of food. Where I live (up north) that's not the case. They are tiny little critters that just annoy ranchers and farmers. The annoyance is in the form of broken legs on cows/horses and crop damage. My fun actually helps things, but I do it for the fun, not out of helping a fellow human down the road.

Comment WTF.. Why do we let retards like this post... (Score 4, Insightful) 374

A 7"/10" tablet or a 4" phone screen will NEVER replace a gaming console. There are many many factors that make this an insane and retarded statement.

1) Game controller. Yes the kinect is interesting. Yes gyros can provide an intersting experience as well. But can you do a 16 hour gaming session waving your arms around like that (both kinect style or wii style with a large tablet). The standard game controller is a perfect interface for most games, and an OK stand in for others (FPS games should be with a mouse).

2) As mentioned above: Screen size.

3) Social gaming (in close physical proximity). A big screen is ideal for this. Tablets (or worse phones) are just too small to share.

4) Touch screens suck for the vast majority of stuff. Motion control is just behind it in usability. With touch screens a large number of games are not playable because your hand is blocking critical space on the screen.

There are more.. but there's beer in the NOC and I'm thirsty.

Comment Not exactly speeding bullet..... (Score 1) 405

Assuming I'm doing the math correctly 1050 MPH is only 1540 feet per second. That's half again as fast as a typical .22. The current crop of "speeding bullets" is pushing around 4200 f/s.

That's only about 1/6 the way through the speed range of a typical bullet. I'd say when you get to 5/6 of the higher end you can begin calling it "speeding".


The State of Ruby VMs — Ruby Renaissance 89

igrigorik writes "In the short span of just a couple of years, the Ruby VM space has evolved to more than just a handful of choices: MRI, JRuby, IronRuby, MacRuby, Rubinius, MagLev, REE and BlueRuby. Four of these VMs will hit 1.0 status in the upcoming year and will open up entirely new possibilities for the language — Mac apps via MacRuby, Ruby in the browser via Silverlight, object persistence via Smalltalk VM, and so forth. This article takes a detailed look at the past year, the progress of each project, and where the community is heading. It's an exciting time to be a Rubyist."

iPhone Owners Demand To See Apple Source Code 298

CWmike writes "iPhone owners charging Apple and AT&T with breaking antitrust laws asked a federal judge this week to force Apple to hand over the iPhone source code, court documents show. The lawsuit, which was filed in October 2007, accuses Apple and AT&T of violating antitrust laws, including the Sherman Act, by agreeing to a multi-year deal that locks US iPhone owners into using the mobile carrier. On Wednesday, the plaintiffs asked US District Court Judge James Ware to compel Apple to produce the source code for the iPhone 1.1.1 software, an update that Apple issued in September 2007. The update crippled iPhones that had been unlocked, or 'jailbroken,' so that they could be used with mobile providers other than AT&T. The iPhone 1.1.1 'bricked' those first-generation iPhones that had been hacked, rendering them useless and wiping all personal data from the device. The plaintiffs say that the source code is necessary to determine whether all iPhones were given the same 1.1.1 update, and whether it was designed to brick all or just some hacked iPhones."

Slashdot Top Deals

A list is only as strong as its weakest link. -- Don Knuth