Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
Trust the World's Fastest VPN with Your Internet Security & Freedom - A Lifetime Subscription of PureVPN at 88% off. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. ×

Comment Re:Arrest him and throw him into Gitmo (Score 2) 626

So now it's getting interesting. NASA forbids him to reveal the PIN code (and let's assume there's a law in place that underpins this).

With NASA being a government agency it's possible there is a law but it still seems unlikely. I'd rather expect it to be part of his employment contract or a related NDA (non-disclosure agreement). Then it's not two laws being at odds, it's a contract and a law. It seems like the law should prevail, but should it really?

Let's say a Boeing employee travels to France and a border officer there requires that he provides the password for his professional phone. Should he hand it over? Wouldn't every American accuse the French government of being in cahoots with Airbus and thus argue that the Boeing employee's NDA trumps (the hypothetical) French law?

I think what this shows is that we don't want border officers to have unlimited search powers.

Comment Re:Seven years. (Score 1) 69

It's been seven years since Tesla has gone public. And almost as long since it has shipped product.

No profit - except for the quarter of some accounting tricks. None.

Which only makes sense. Tesla needs to grow fast to profit from their first-mover advantage and achieve a scale that lets them compete with other car manufacturers on a more equal footing. That means taking risks (yes, they may still fail) and investing as much of their income as possible to fuel that growth, profits be damned. But that's okay because it's not like anyone would be dumb enough to invest in a fledgling manufacturing company in a field dominated by giants expecting it to play it safe and immediately serve fat dividends.

Ford - started by an actual brilliant engineer and entrepreneur was profitable in its FIRST QUARTER of doing business.

Yeah. Not only have times changed in a century, but Tesla's competitors have had 100 years to prepare and put up barriers against new entrants! Who could have guessed?

Musk is an incompetent CEO and must step aside for Tesla to survive.

So if you were Tesla's CEO you'd cripple its growth so as to give enough time for its competitors to catch up and then run Tesla into the ground through a price war? It's a good thing you're not in command then.

Comment Re:Wine (Score 1) 202

And even they did use #import, it's easy to fix since #import generates the source code for itself so just compile that instead.

That's just not workable. First it means you still need the Windows toolchain to generate the source that you will then have to transfer to Linux to compile. But then it means your Linux developers will not be able to modify the code they compile because it's auto-generated code and any change they make will be lost the next time around. So if they find a bug or need to make a change they will have to find the matching original source file, make the change there, use the Windows toolchain to regenerate the source code, transfer to the Linux build machine and rebuild. It's too cumbersome.

Comment Re:Wine (Score 1) 202

No it isn't. A Win32 application running over wine involves more context switching and memory contention due to wineserver and other libraries eating up resources.

It is the wineserver that handles all accesses to the registry. For that reason and many others, there is no way you're going to start a Wine or WineLib process without it. So it really makes no difference either way.

Once compiled there is no more difference between a WineLib process and a Wine one than between an a.out process and an elf one. Probably even less since in both cases you have all the PE structures (since some applications access them directly), only in the Windows executable file the PE-stuff is all alone, while in the WineLib case there's an extra ELF wrapper.

In theory a natively compiled Win32 exe might be more optimal if MSVC ran more efficiently than gcc / clang but these days that's unlikely.

Another point for just running the regular Windows executable.

So the rest of the Wine runtime is superfluous bloat. Compiling and linking against winelib saves space on disk because the code that is unused will not be linked into the executable.

WineLib is not something distinct from Wine. Rather it's just the source-level compatibility aspects of Wine: are the functions definitions in the right C header files, do they use the right types, can we produce PE executables, etc. WineLib does not have its own libraries: it uses the Wine dlls. So if you package your application with a self-contained Wine environment you can of course pick and choose which Wine dlls you want to package it with. That requires a non trivial amount of work though and it's not going to impact performance, just disk usage which nobody care much about these days. The latter is particularly true for games since they are typically multi-GB beasts these days while a full Wine is under 0.15GB.

It also means the game can ship only things that it needs to work and can tested to within an inch of its life against those things instead of some random Wine on someone's machine.

The things you care about for games are the X and OpenGL libraries, and graphics driver (including the Linux kernel part) and you cannot package those with your game. Also, as stated before there's no difference between Wine and WineLib there.

Thirdly, a game running on Linux might have to disable or modify its copy protection, change or remove certain texts and assets, interact with Linux in certain ways (e.g. disable screensaver, input devices), interact with other software such as Steam on Linux, or use different file paths.

True. The ISV would typically do that by modifying the source code and producing a Linux-specific Windows binary thus side-stepping all of the toolchain changes. He would then package the resulting Windows executable with Wine as stated before (or have someone like CodeWeavers package with CrossOver). In some extreme cases he may end up developing a Wine dll (i.e. a WineLib dll as all Wine dlls) to interface in some way with Linux and use the API provided by that dll in his game. That's pretty rare though.

Yes you could run a game on Linux through Wine and that's the fallback situation you'd still be running the Windows game. You wouldn't even register as a Linux user on some spreadsheet of the company that produced it.

You're mixing up buying the standard Windows game and running it through Wine with no involvement on the part of the game studio, and buying a Linux or Mac game that has been ported using Wine rather than WineLib. Of course in the first case the game studio is not going to know you're running their game in Linux or Mac since, as far as they know, it only runs on Windows. But if they made a port with Wine it's up to them to decide whether they track the Linux and Mac versions separately from the Windows one. If they have separate SKUs for each platform tracking is trivial. If they decide that when you buy the game you can run it on any platform then it means they'll need some code in the game to gather statistics.

Comment Re:Wine (Score 1) 202

Only if the libraries are as fast or as feature-rich as they are under Windows.

That's true when comparing Wine to Windows. But this thread is comparing Wine to WineLib and they both use the same libraries.

Comment Re:Wine (Score 1) 202

Wine is an emulator and it's not an emulator. You can run a Windows executable on the runtime or you can compile Windows source code and run it as a native executable. The latter would be more useful for things like porting games.

The performance of an application ported through WineLib is going to be identical to the performance of the Windows binary running through Wine. So WineLib is no more and no less useful for games than it is for any other application.

What WineLib does buy you however is lots of complications with the compilation toolchain as soon as your code depends on Microsoft-specific C++ features like the omnipresent #import directive, Visual C++ project files (even with winemaker), or the MFC, etc. Things get complex pretty quickly if you also have third-party libraries or use other languages like Visual Basic or even C#.

Comment Re:Wine (Score 3, Insightful) 202

I recall long ago (2003 maybe?) one of the Wine developers showed up on Tech TV and Leo Laporte asked him something like "if wine isn't an emulator, then what is it?" and the dude answers back "it's an emulator".

The dude in question was Alexandre Julliard, Wine's project leader. The goal of the show was to present Wine so there was a sort of rehearsal during which the journalist said he was going to say something like "so Wine is an emulator" to which Alexandre would object. But during the live interview the journalist actually said "so Wine is not an emulator" which caused Alexandre to take the opposite stance as per the rehearsal. I'd say he a better as a tech leader than as a PR guy and I certainly wouldn't want it any other way.

Even so he did not say that Wine would emulate CPUs which was the common understanding of the word 'emulator' at the time. It's still true that Wine will not deal with CPU emulators or virtual machines. Both of these aspects are best dealt with independently of Wine. So anyone who needs that should run Wine and their application inside their VM or CPU emulator. Except in pathological cases, if the VM / CPU emulator is fast enough to run the application it's still going to be fast enough if you add Wine to the mix.

Wine is a reimplementation of the Win32 and Win64 APIs on top of the Unix (and X, OpenGL, Cocoa) APIs. It's not all that different from Glib and GTK+ which provide their own system and graphics APIs on top of the underlying system APIs, be that Unix or Windows. Of course the Windows APIs were not meant for this so there are some extra complications and side effects (e.g. %fs register usage conflicts on some platforms), but not so much for the general case.

Comment Re:Set speeds will follow autonomous vehicles. (Score 1) 162

The car in the video is not a Tesla, it's an Uber self-driving car. These seem to not be driving very well as they are also known to drive on the bicycle lane. Uber is denying the red-light issue but says they are working on the bicycle lane one, thus acknowledging there are problems with their self-driving software.

Comment Re:But... (Score 1) 239

People aren't generally crammed together in their homes or workplaces. Things can still spread, but not easily.

Are you saying that couples don't sleep together and never kiss their children? I think you should check up on this family concept. Even at work people shake hands or even kiss (yeah, certainly not in the US for the latter, though Americans are known to hug sometimes which from a contagion point of view is probably not so different). At least in public transports you don't kiss or shake hands with everyone you come across ;-)

Comment Re:But... (Score 2) 239

Flu shots are based on a guess each year of which flu strains to guard against. They've gotten the guess wrong some years, and people ended up with the flu whether they got the shot or not. If you have a weakened immune system, this is a big problem.

The GP seems to think taking the car is a valid alternative to taking a flu shot. That's just crazy. It's not public transportation you must avoid: it's everyone, starting with your kids if they go to school!

Comment Re:Fake! (Score 1) 239

Furthermore in the pictures you would not have seen any trace of a wood fire because you would just not find any wood to burn in Paris.

I was in Paris this summer, when was the last time you were there?

Well, yesterday. And last Monday. And last week. And the week before that. But sure, as someone who has been there for a couple of days six months ago you must have some deep insight lacking to people who live here.

Never mind the wide abundance of trees everywhere, and in the winter so much dead foliage

Yeah, foliage that's been collected a couple of months ago. You know we have those pesky leaf blowers too.

you could keep a campfire going all night every night simply by burning trash people leave along the river pathways every evening. I imagine that's reduced in the winter but there are still a ton of trashcans everywhere you could raid for flammable material.

You should try that next time you're there. The police will be happy to help you save on hotel and food. Good riddance.

Comment Re:But... (Score 1) 239

Many people drive a car in order not to use public transportation...

This seems like a very American sentiment (i.e. it always seems to be the first thing people say on Slashdot, and only on Slashdot). I don't know any one like that though I guess some of the very rich who would never mix with the plebes think that way. Most people they use their car because, for their particular case, it's the faster means of transport, just as for many others it's the public transport that's the faster and less irritating means of transport.

And people having a car don't really care about saving a couple of euros to travel within Paris/suburbs.

That's certainly true but it makes it less of a hassle for people who are forced to switch means of transportation for a couple of days in the year. Also it removes a reason for them to complain.

Comment Re:But... (Score 1) 239

When I worked in Paris, I lived in the suburbs surrounding Paris and worked in another one.

Great. Since you're not entering Paris you can take your car as usual. See not a problem for you. Now just stop ranting.

In my car, it was a solid 20 minutes, and I never caught the flu.

There's also flu shots for that. They cost a mere 10€ and 65% of that is reimbursed. By the way, what's the point of going to an office where you are all alone? What? You were not alone at the office? How did your car help you to not catch the flu from your crazy public-transport-using colleagues?

Comment Re:Great System (Score 1) 239

The administrative burden of JUST ABOUT ANYTHING ELSE is far too high and would actually cost you more.

And yet next year it's supposed to get replaced with which is an environmental badge that one will have to have on the windshield to get into Paris on days such as these. Cars will get a different color badge based on the environmental standards they implement. The color coding will make it easy for the police to spot cars that are not allowed and to stop + fine them.

Comment Re:Fake! (Score 2) 239

Pretty sure Reuters is one of those fake-news sites the liberals have been hyperventilating about recently, after all it disputes "fact" that he knows.

Well if you had read the article you would have noticed the migrants got evacuated to the countryside a month ago. Furthermore in the pictures you would not have seen any trace of a wood fire because you would just not find any wood to burn in Paris. So no, migrants are not responsible for the wood fires that are in part responsible for the current pollution.

Plus, wood fires have been blamed for pollution for many years and almost got banned two years ago. Are you going to blame the migrants for that too? Now like then the wood fires the article talks about are just lit by people in the chimney of their residential house just because it's nice to sit by the fire when it's cold. But of course don't let a mundane explanation get in the way of your paranoia.

Slashdot Top Deals

You might have mail.

Working...