Then you had a piss-poor release engineer who didn't understand how to construct config specs based on a stable baseline, label & promote stable builds regularly, and use clearmake properly, or manage dependencies and allow you to do a clean, fast local build.
Oh they had plenty of release engineers, and that sort of demonstrates what bullshit Clearcase was. It was so slow that every site needed its own set of engineers, own set of servers and own set of mirrors to replicate each repo. Something no sane source control system has ever required. Then they had to have scripts to periodically sync changes back and forth. Two teams at two sites had to sit around and wait for changes to appear, and of course view specs couldn't be shared, and occasionally syncs failed because of merge issues. And if we wanted branch us poor devs had to appear like supplicants in front of release engineers to beg for a view spec.
I'm also pretty sure the engineers had nothing to do with the speed issues or the bluescreens.
Dynamic views as you're talking about were not - and never were - intended for use across WANs, their Admin & Deploy guides specifically stated that it required a fast connection to a local server. If you wanted WAN connectivity, you either used RTC (Rational Team Client) to pull web views, or you used snapshot views, or you ponied up for MultiSite licenses and set up a sync scheme so that each site could have local copy on a VOB & View server they had a fast connection to.
And neither were static views. Trying to checkout updates could take hours over a WAN. I know because I'd work remotely from home and it was unusable. Clearcase was so slow that IBM create a kludge called Clearcase Remote which checked out a snapshot on the server and had a fat client to sync the local files to the server snapshot.
Clearcase sucks balls. It is a piece of shit by any objective measure.
I had to use Clearcase as my source control system for one company I worked for. The idea was you set up a view spec (a bit like a branch), mapped a drive letter to it and you never had to pull again because it would always reflect that branch. Your local changes went over the top and when it was time to commit you could merge up and commit. In practice what it meant was the source code was constantly changing under your feet, and binaries were constantly stale or in a mystery state because you didn't know what they were compiled against. And because this was IBM software it was unusably slow across WANs, memory hungry and enjoyed triggering random blue screens.
While a vfs sounds like a great idea, I think in theory it's only of use for very, very large repos. Even then I wonder if the exact same issues that made Clearcase suck would make it suck even with Git.
Trump spouts what he does because the oil and coal industry have learned to massage his ego. The solar industry should learn to do likewise. Be totally obsequious, pander to his narcissism and all of sudden he'll be parroting how amazing solar and renewables are.
Don't worry, the Nissan Leaf will be obsolete before that. It uses a CHAdeMO standard for charging the vehicle. The US is adopting type 1 CCS and Europe is adopting type 2 CCS. That leaves the Leaf and a handful of other models in the lurch. I expect you'll be lucky in 8 years to see any charging station support the format. If it works at all it'll be through some expensive active cable that converts the supply to CHAdeMO or through a refit program.
If you want to call them Nazis, then you are saying they are far left, not right. The Nazi movement was a socialist movement, and is on the left, along with communism and fascism. The far right is Anarchy.
Go and look up the origins of national socialism and how the name was co-opted please. And stop parroting this bullshit.
Alt right IS far right. Change a few words, dress up like hipsters, but otherwise behave, act and think like nazis. Punchy McPunchface, leading light of the nazi (oops alt right movement) was giving a nazi style salutes to Trump only a few months back. They're far right.
I expect someone has produced a distortion filter for digital audio which makes it sound like a record player. It's lossy of course but I wonder what the outcome of an A+B test would be for that.
Vinyl had its day. These days it's just a scam aimed at audiophiles.
Defender just gets on with its job with relatively little overhead or other intrusion. The same cannot be said of virtually any other AV suite. Even the "reputable" ones like McAfee, Norton etc seems to exist as a form of crapware these days and are so bloated and slow that any protection comes at a high price.
Yes it does. Google only reports human interventions when there is an imminent danger such as a system failure, risk of collision etc. And they've reported hundreds of such interventions. They don't bother to count the many thousands, tens of thousands of other times where the car undoubtedly did something really dumb, got stuck, or asked the human for help.
And that's even without counting ANY of the scenarios above. Just regular driving at 20mph on nice wide roads. Other self drive projects like Ubers are even worse running lights and other patently dangerous behaviour.
None of this should be a surprise to anyone. So stop drinking the kool aid. Yeah we'll probably see some limited self drive. But pretending it makes a car capable of learning more scenarios than humans (the point I was addressing) is ludicrous.
Well, even the best DAC available only can create a approximation from the original analog sound signal, while vinyl is an analog recording by nature.
That doesn't make any sense for a couple of reasons.
Virtually all music is mastered digitally so its already passed through various DACs any way. A vinyl record will be a reproduction of a digital master so any supposed benefits of being analogue are irrelevant.
Just because something is analogue doesn't mean it better either. A record master may be filtered and have a reduced dynamic range so the needle doesn't bounce around or skip. Records also wear out, particularly high frequency and attract dust and scratches so the sound degrades with each play. Then of course you have all the electro-mechanical distortion introduced by the equipment itself.
So no, vinyl isn't any better than digital. I expect what attracts most aficionados of the format has more to do with the ritual of the format and almost nothing to do with the sound quality. The sound quality isn't better.
You can train it for more scenarios than you can train a human for. And the knowledge is cumulative. If one car in one place records "unseen data" you can roll that out to all cars next software update.
That's doubtful and it supposes that the computer is even capable of recognizing the scenario in the first place. e.g. is the car ahead stopped because a) the driver has suffered a heart attack, b) it's broken down in the road, c) there is traffic ahead of that car, d) baby ducks are walking across the road, e) the road is flooded, f) the lane is closed and the car is a road maintenance vehicle, g) it's a carjacker waiting for the dumb smart car to stop behind it so it can be robbed.
It's virtually an intractable problem for a computer to solve. Even if a computer could reliably drive 99% of the time that means 1% of the time it fucks up and the chances are it will require an alert human to takeover to prevent the problem or extricate it. And self drive vehicles are nowhere close to that level of reliability.
LibreOffice is a great suite of tools, more than enough for a lot of purposes, but some of the tools like Impress still suck compared to Office.
An extremely trivial example of that is the placement of the button that creates a new slide. In Powerpoint there's a big button marked "New Slide", on the left hand side of the ribbon. On Impress it's buried in the toolbar somewhere on the right and not given any particular importance. One of the most basic actions is less usable in one tool over the other. A succession of little things like this compound the hassle of using the tool.
The suite really needs to keep hitting on usability as its #1 focus and it needs to figure out how people use the tools and fashion its UI around those actions.
Trump is what Russians would call a "useful idiot". Providing you can stroke his massive ego and indulge his narcissism, you can make him parrot anything you want.
The best thing Musk could do to stroke his ego is through a transparently obsequious act, e.g. offer to clad out Mar Del Lago or one of his other buildings with solar panels. Trump will suddenly start spouting how wonderful solar and renewables are for creating jobs.
The thing costs a fortune. And even if it didn't, there are some pretty obvious limitations to what you can do with AR especially when it requires wearing a dorky helmet.
Fine. Build an oil fired plant beside them. Let's see if they appreciate the fish kill offs and listening to fog horns from 100,000 tonne tankers passing by at 3am. People can be so fucking stupid and selfish sometimes.
Sensible people realise that a few windmills out in the sea is infinitely preferable to a coal / oil / gas plant with all the infrastructure that goes with it - railway lines, slag heaps, ash ponds, oil / gas holders, deep dredged docks, traffic, tanker / colliers sounding horns etc.
I still have a Nexus 4 as a backup phone and it's still a beautiful little phone. It might not have been the best feature phone in its day (nor was it meant to be), but it was comparatively affordable and did its job really well.
I really don't know what Google are going with the Pixel but it seems pretty self-defeating to price a device so high and offer so little in terms of features (except for some extra software) to justify that price. Honestly, the specs of the OnePlus 3T aren't far off the Pixel and it costs significantly less.
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.
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. 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.
In addition, games tend to be self contained and only touch certain APIs. 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. 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.
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. These changes might only amount 2% of the codebase allowing the rest to be preserved. I'd add that code is very unlikely to be using #import or MFC in a game. And even they did use #import, it's easy to fix since #import generates the source code for itself so just compile that instead.
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. It would be better for you and Linux if the game was ported and ran natively on the platform even if that were through winelib.
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.
Hoho, you get a double dose of it if you're flying between the USA and the UK. I flew Manchester to Orlando - 90 minutes in MCO. Flying back another 90 minutes. The USA had kiosks that people were supposed to use but most of them were roped off for another flight. They also had 16 desks to process people through but only 4 were manned for about 500 people.
And it's the biggest cluster fuck you can imagine. Only registered travellers over the age of 18 get to use it. Every one else gets to join an EVEN LONGER QUEUE because they can't be bothered to lay on sufficient staff to process people coming through. Entire families stuck in a fucking queue for over an hour thanks to electronic borders. Progress.
Slashdot Mirror
Then you had a piss-poor release engineer who didn't understand how to construct config specs based on a stable baseline, label & promote stable builds regularly, and use clearmake properly, or manage dependencies and allow you to do a clean, fast local build.
Oh they had plenty of release engineers, and that sort of demonstrates what bullshit Clearcase was. It was so slow that every site needed its own set of engineers, own set of servers and own set of mirrors to replicate each repo. Something no sane source control system has ever required. Then they had to have scripts to periodically sync changes back and forth. Two teams at two sites had to sit around and wait for changes to appear, and of course view specs couldn't be shared, and occasionally syncs failed because of merge issues. And if we wanted branch us poor devs had to appear like supplicants in front of release engineers to beg for a view spec.
I'm also pretty sure the engineers had nothing to do with the speed issues or the bluescreens.
Dynamic views as you're talking about were not - and never were - intended for use across WANs, their Admin & Deploy guides specifically stated that it required a fast connection to a local server. If you wanted WAN connectivity, you either used RTC (Rational Team Client) to pull web views, or you used snapshot views, or you ponied up for MultiSite licenses and set up a sync scheme so that each site could have local copy on a VOB & View server they had a fast connection to.
And neither were static views. Trying to checkout updates could take hours over a WAN. I know because I'd work remotely from home and it was unusable. Clearcase was so slow that IBM create a kludge called Clearcase Remote which checked out a snapshot on the server and had a fat client to sync the local files to the server snapshot.
Clearcase sucks balls. It is a piece of shit by any objective measure.
While a vfs sounds like a great idea, I think in theory it's only of use for very, very large repos. Even then I wonder if the exact same issues that made Clearcase suck would make it suck even with Git.
Trump spouts what he does because the oil and coal industry have learned to massage his ego. The solar industry should learn to do likewise. Be totally obsequious, pander to his narcissism and all of sudden he'll be parroting how amazing solar and renewables are.
Don't worry, the Nissan Leaf will be obsolete before that. It uses a CHAdeMO standard for charging the vehicle. The US is adopting type 1 CCS and Europe is adopting type 2 CCS. That leaves the Leaf and a handful of other models in the lurch. I expect you'll be lucky in 8 years to see any charging station support the format. If it works at all it'll be through some expensive active cable that converts the supply to CHAdeMO or through a refit program.
If you want to call them Nazis, then you are saying they are far left, not right. The Nazi movement was a socialist movement, and is on the left, along with communism and fascism. The far right is Anarchy.
Go and look up the origins of national socialism and how the name was co-opted please. And stop parroting this bullshit.
Alt right IS far right. Change a few words, dress up like hipsters, but otherwise behave, act and think like nazis. Punchy McPunchface, leading light of the nazi (oops alt right movement) was giving a nazi style salutes to Trump only a few months back. They're far right.
Vinyl had its day. These days it's just a scam aimed at audiophiles.
I don't know why you would make any such assumption. And even if it were (it isn't), it doesn't negate point 2.
If you can't trust a piracy forum to protect your online details then who can you trust?
That's great and every one can all do the same with absolutely no consideration at all of what they bought the computer for.
Defender just gets on with its job with relatively little overhead or other intrusion. The same cannot be said of virtually any other AV suite. Even the "reputable" ones like McAfee, Norton etc seems to exist as a form of crapware these days and are so bloated and slow that any protection comes at a high price.
You're so far off base of what is out there already it's funny. Tell me more about how these cars ".don't work"
Oh really? Cite examples of self drive vehicles that could take a guess for scenario a, b, c, d, e, f or g above. I expect you can't.
And that's even without counting ANY of the scenarios above. Just regular driving at 20mph on nice wide roads. Other self drive projects like Ubers are even worse running lights and other patently dangerous behaviour.
None of this should be a surprise to anyone. So stop drinking the kool aid. Yeah we'll probably see some limited self drive. But pretending it makes a car capable of learning more scenarios than humans (the point I was addressing) is ludicrous.
Well, even the best DAC available only can create a approximation from the original analog sound signal, while vinyl is an analog recording by nature.
That doesn't make any sense for a couple of reasons.
So no, vinyl isn't any better than digital. I expect what attracts most aficionados of the format has more to do with the ritual of the format and almost nothing to do with the sound quality. The sound quality isn't better.
You can train it for more scenarios than you can train a human for. And the knowledge is cumulative. If one car in one place records "unseen data" you can roll that out to all cars next software update.
That's doubtful and it supposes that the computer is even capable of recognizing the scenario in the first place. e.g. is the car ahead stopped because a) the driver has suffered a heart attack, b) it's broken down in the road, c) there is traffic ahead of that car, d) baby ducks are walking across the road, e) the road is flooded, f) the lane is closed and the car is a road maintenance vehicle, g) it's a carjacker waiting for the dumb smart car to stop behind it so it can be robbed.
It's virtually an intractable problem for a computer to solve. Even if a computer could reliably drive 99% of the time that means 1% of the time it fucks up and the chances are it will require an alert human to takeover to prevent the problem or extricate it. And self drive vehicles are nowhere close to that level of reliability.
An extremely trivial example of that is the placement of the button that creates a new slide. In Powerpoint there's a big button marked "New Slide", on the left hand side of the ribbon. On Impress it's buried in the toolbar somewhere on the right and not given any particular importance. One of the most basic actions is less usable in one tool over the other. A succession of little things like this compound the hassle of using the tool.
The suite really needs to keep hitting on usability as its #1 focus and it needs to figure out how people use the tools and fashion its UI around those actions.
The best thing Musk could do to stroke his ego is through a transparently obsequious act, e.g. offer to clad out Mar Del Lago or one of his other buildings with solar panels. Trump will suddenly start spouting how wonderful solar and renewables are for creating jobs.
The thing costs a fortune. And even if it didn't, there are some pretty obvious limitations to what you can do with AR especially when it requires wearing a dorky helmet.
Fine. Build an oil fired plant beside them. Let's see if they appreciate the fish kill offs and listening to fog horns from 100,000 tonne tankers passing by at 3am. People can be so fucking stupid and selfish sometimes.
Sensible people realise that a few windmills out in the sea is infinitely preferable to a coal / oil / gas plant with all the infrastructure that goes with it - railway lines, slag heaps, ash ponds, oil / gas holders, deep dredged docks, traffic, tanker / colliers sounding horns etc.
I really don't know what Google are going with the Pixel but it seems pretty self-defeating to price a device so high and offer so little in terms of features (except for some extra software) to justify that price. Honestly, the specs of the OnePlus 3T aren't far off the Pixel and it costs significantly less.
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.
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. 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.
In addition, games tend to be self contained and only touch certain APIs. 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. 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.
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. These changes might only amount 2% of the codebase allowing the rest to be preserved. I'd add that code is very unlikely to be using #import or MFC in a game. And even they did use #import, it's easy to fix since #import generates the source code for itself so just compile that instead.
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. It would be better for you and Linux if the game was ported and ran natively on the platform even if that were through winelib.
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.
Hoho, you get a double dose of it if you're flying between the USA and the UK. I flew Manchester to Orlando - 90 minutes in MCO. Flying back another 90 minutes. The USA had kiosks that people were supposed to use but most of them were roped off for another flight. They also had 16 desks to process people through but only 4 were manned for about 500 people.
And it's the biggest cluster fuck you can imagine. Only registered travellers over the age of 18 get to use it. Every one else gets to join an EVEN LONGER QUEUE because they can't be bothered to lay on sufficient staff to process people coming through. Entire families stuck in a fucking queue for over an hour thanks to electronic borders. Progress.