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

 



Forgot your password?
typodupeerror
×

Comment Re:Be careful what you wish for... (Score 1) 594

If they had gone with the embedded length option we'd be sitting around bitching about how short-sighted it was to use just two bytes for the length. Including how Dennis Ritchie supposedly said "64K strings should be enough for anybody".

One extra byte was clearly for that time, now days you would probably use 7 extra bytes (depending on memory model). This would of course not be hard coded.

Comment Re:To unclear (Score 1) 556

Apple should have said what this really is about: Your iDevice can't determine its position by using the MAC addresses of nearby WiFi points unless Apple knows the locations of those WiFi points. And Apple's servers can't tell your iDevice where it is right now, unless the iDevice gives them the information that Apple's servers need to determine the location of your iDevice.

To unclear? I do not understand anything you write, and wonder if you do???

I wonder if all those people who helped OpenStreetMap are aware that OpenStreetMap knows the exact location where they were when they collected the data.

I wonder who thinks that OpenStreetMap does not know where you have been when you collected the data, but for someone it must have been news as you where moderated insightful. Frightening.

On the other hand, there is a website know where you can enter the MAC address of a router, and it will give you the location of that router, based on data on Google's servers. I hope Apple doesn't allow the same thing. I would hope even more that Google would put a stop to this. According to what Apple says, this is a black box: Only when the location software in the iPhone OS asks for the information about routers that are physically nearby will it receive location information. And in that case, anyone with a working GPS could have the same information anyway, so this is no privacy breach.

Are you stupid? Seriously?

Comment Re:False (Score 1) 132

If you want predictable names from hardware, and you want to be able to add and remove devices the only solution would be to allocate enormous holes if you want to keep the current ethx naming scheme. i.e.

eth0 - eth999 on board
eth1000 + slot * 1000 + port for cards
etc

Comment Re:Is C++ ever the right tool for the job? (Score 1) 509

Most applications should not be written in C or C++., they should be written in a more high level language, where certain kinds of mistakes can not be made.
Some time critical stuff can be written (as you suggest) in small parts in C to make it perform well. For some stuff you can not mix the C language with languages like Python, Java or C# because latency is a factor, and you want real time behaviour (that is, no garbage collection). Then C++ is a great choice.

Slashdot Top Deals

Work is the crab grass in the lawn of life. -- Schulz

Working...