In some ways yes, in some ways no. Large history can be an issue, but to get to that point you pretty much need to be doing something pretty special for a fortune 500 company. The entirety of the Linux Kernel clocks in at under 2GiB, the only company I've ever heard make the claim that this is an issue was Facebook, who went with Mercurial instead.
The trick with branches is that each represents a different feature or bug fix. So long as they don't touch the same bits of code, git makes merging them painless. Local branches allow for trying out ideas, and swapping between tasks easy. Remote branches allow for greater control. A common paradigm is only one or two people have commit access to master. Everyone else asks them to merge their branch.
This branch and merge strategy, called 'pull requests', is the key to github's success. On sourceforge with svn, I would have to generate a patch file, then send it to the developers somehow, then wait for them to examine it, before finally deciding to add everything as one large commit. This can take a while, especially if several things have to be modified. Worse, the developers have to revert their local code copy to a clean slate before applying the patch. With git and github, you can easily view what's going to change, and merging is a simple click/command.
Git has what are known as hooks. Things that are run whenever you do something, like committing a file or trying to push to somewhere. It's how you get E-Mail notifications. These aren't anything new, so I think subversion offers something similar. The large difference is in what these let the maintainer do when it comes to integration.
Take a look at this page: https://github.com/OpenMW/open... Click on the green check marks or red 'X's. This is something github has integrated into their system, but there are other options as well. The advantage is that developers could add a new feature, or fix a bug without committing directly to the master branch. The primary maintainer can easily view if the patches compile cleanly, and if the patch is acceptable or not.
This is a consequence of how easy it is to branch and merge using git. I know subversion has branches, but they can be harder to deal with and it's hard to spin up a branch for every feature and patch. Combine that with git's local storage and swapping/reverting branches is a sna
Actually you can do that with git. Just set the right pre commit, or pre upload hooks and it'll do it all.
One project I contribute to on github preforms automatic coverity and travis-ci builds/tests every time someone asks to merge their code to the master branch.
Easy way to see if the thing even builds, without the maintainers having to do a thing.
I'm always going to recommend git as the version control system of choice. It scales well, and you can learn how it works without mucking with servers to start. Plus github.com has some good tutorials, and there are several web interfaces available. If you could convince your IT department to let you use a cloud based system, github would actually be perfect. Also, the speed. Don't underestimate how important that is.
Almost all of the requested features are possible with most version control systems, but, like back end infrastructure, require someone knowledgeable about that particular system to set things up. For instance, there are commit hooks to handle sending E-Mails and doing code checking, but that requires editing the right file.
Any processor, much less Xenons, in Epoxy is going to get hot. Like, the epoxy is going to melt hot. Even without the epoxy, that's a huge power profile in a small space. How exactly are they going to cool that?
Not quite so easy. Half the time these federal grants are tied to the individual, not the university. Heck, applying for a research position at my university is a waste of time unless you already have a grant. Side-note: Yep, they're having staffing problems.
The interesting thing is the computers. If they were on site, then it doesn't matter about root access. Pull the plug, and restore from backups or change to single user mode. If they're cloud servers paid for with federal grant money, then it becomes a tricky issue...
You should be able to take advantage of all of systemd's features whether the daemon is designed to be run from an init script or not, and even whether it is run from an init script or not. If not, there is either something deeply wrong with you (incompetence) or deeply wrong with systemd (poor design.)
Key features like dependency management, whether a service terminated with an error condition, and what to do when a service terminates are things that you CAN NOT DO if all you have is an init script.
It does seem a bit much, but the systemd transition is a slow one. Many packages are still using init.d startup scripts, which means we can't take advantage of systemd's features with them.
Systemd isn't really a startup management subsystem. It's a full blown service manager. It can be set, at the user's choice, to restart services when there's a problem. It can provide detailed logs from each service.
The best part is the service descriptor files follow a standard. If all people did at this conference was convert package init scripts to systemd I would be ecstatic.
Programs that require direct GPU access and as much of my system's RAM as possible are the top of my list of reasons for keeping a Windows partition around, personally. So, I've basically got one boot option to put my machine into gaming-console mode, and one to put it into everything-else mode. That set up will change when there's either a technical shift in what I can easily do on Linux or my interests change enough that I'm no longer interested in running that kind of program.
With newer machines having an IOMMU, that might be an option. There are several ways to let a guest OS now have full access to the GPU, and nothing else. http://www.firewing1.com/howto...
I've personally switched over to Linux full time, but that's because I don't mind the customization. I also realized the first thing I did on a new windows box was to install cygwin and windows equivalent of all the handy Linux utilities. Plus, package managers are a godsend when setting up a development environment.
While android itself may be open source, the Google APIs are not. There are some projects to replace them with open source alternatives, but Google keeps adding to/changing them and developers are addicted to the new and shiny. See the issues people with the Kindle Fire are dealing with.
The other big reason for the change is control. Android might be open source, but it's still Google that decides what direction it goes. Samsung want that kind of control over Tizen, or at least take advantage things being de-facto standards.
For instance Android has it's own compositor sitting on bare metal, and it's own 2d graphics library to talk to that compositor. You won't find either of those outside of android. Tizen uses a custom compositor with wayland or X11. Apps use whatever graphics library they like, and can just tell the OS to render it. That's standard practice for desktop developers today.
4K h.265 encoding at 2 frames per second on the fastest CPU. And I thought I had a memory channel bottleneck.
Video encoding is insanely slow! How do TV stations handle moving editing and encoding their video. It seems that the evening news wouldn't be feasible at these encoding rates.
High end hardware, professional software that takes advantage of the GPU and custom hardware encoders. Plus, the editing is normally done on uncompressed video. Not to mention things like animation/effects and encoding are often done on a render farm of dedicated servers.
Here in the US any library that deals with children must have mandatory filtering software installed. Given the typical puritanical attitude, quite a few public libraries also have filters.
Why should anyone care about the power level, as opposed to the pulse energy? ie why does it matter if the kilojoule is spread over one or ten picoseconds? Without this vital piece of information, it is hard to get excited (pardon the pun).
Well, given that a 9mm has about the same energy as two or three punches... Yeah, I'd say the time and method of energy transfer/release is extremely important.
Wireless and graphics are the two pieces of hardware Linux has occasional problems with, and that's become much more of a rarity in the past several years. Many wireless chips require a non-free firmware package to be installed, so if you run a "pure" os like Debian, you'll have to manually tell it to do that. Older and Intel graphics cards just work. The issue has always been getting good performance out of newer ATI and Nvidia cards.
Speaking as someone who uses Linux on my home machine, the most annoying part are peripherals like gaming mice and keyboards. Using all the buttons or changing settings is a pain in Linux. Companies like MadCatz and Razer just don't care. It will be interesting when people try to plug them into Steam machines and find they barely work
Honestly the freaking out thing isn't that bad, but the issue isn't Zirconium in general. For most applications, when they use Zirconium they don't bother to extract the Hafnium. It has most of the same properties, and it's expensive to remove. It just happens to be that one of the main applications that requires pure Zirconium involves the word nuclear. Which, is something no politician wants to touch with a ten foot pole.
Hafnium is about a dollar / gram. Nitrogen and carbon are plentiful and relatively cheap. Is this dramatically more expensive than current high temp materials?
442 stainless steel is US $1500.00 / Ton from Alibaba. Assuming metric, that works out to $1.5/kg, or $0.0015/g. Plus that $1/g is just for the raw Hafnium. Alloys like the one proposed here tend to be expensive, time consuming, and finicky to get right.
Then you get into the fact that producing Hafnium leaves pure Zirconium. Which is typically used as cladding for nuclear fuel rods. Something that a fair portion of the world would freak out about, because anything that's good for nuclear must be bad. Plus there's this gem: https://en.wikipedia.org/wiki/...
This hasn't been the case for years. Mainly because users value privacy, and don't like being annoyed. Perfect example: popup blockers. Every argument given for why browser makers should not stop annoying/malicious behavior has been made during that debate. For a while there, websites could even change window size and position. I know of at least one script that would forkbomb a computer with popups of itself while telling the user they were an idiot.
Use case 1 sounds like a problem, but one that should be fixed somewhere else. Use case 2 is like popups and the blink tag. The times when users actively want that feature is dwarfed by its abuse. Further, it's easy to work around. Worst case, I've used a cell phone camera because a program I had to use locked down the entire pc.
While it's true the site operators are at fault, I also blame the browser makers.
Many websites don't allow copy or paste, or even selecting/highlighting text. While I can understand the draw of websites, especially ones with games, being able to grab keyboard input, it's a potential security disaster waiting to happen.
Browser makers should treat these kind of keyboard/mouse hooks the same way they treat websites asking for location data. With a message asking the user if they want to allow the behavior or not. Furthermore, they should do it in such a way that operators can not force users to click allow.
You've hacked a bank and now you're a terrorist. Expect a visit from the FBI and a taxpayer funded trip to Cuba.
Vinegar Joe is, unfortunately, probably correct. The last time this happened the person was sent to jail and faced a hefty fine. http://appleinsider.com/articl...
Sorry mate, but reporting vulnerabilities puts you behind bars.
Under US Federal law it doesn't matter. If parent had any amount of drugs it's a felony, and in many areas comes with a mandatory minimum sentence. If parent has over an arbitrary amount of a drug then it's considered "possession with intent to distribute," which is a felony that can result in jail times longer than if parent had killed someone
Also, statistically, if someone arrested is not white then expect a harsher sentence in the US.
Actually that's a common justification for piracy. Ex: "I've already paid for it once, I'm not paying $XX just to get a Blue Ray version."
The thing to remember about phone apps is they tend to transfer within the same ecosystem. You buy an app for your old phone, and it'll pop up on your new phone as well.
PC software piracy is alive and well. Just look at any college where the students have to use proprietary software. Sure they could go to the labs, but they want it on their PCs and can't afford the $1000s per copy licence fee.
As I mentioned in another post, PILOTS use tablets now. It's a huge weight saver vs tons of paper maps. Sure they're supposed to turn the WiFi off on those things, but mistakes happen.
The funny part being that iPads and the MS Surfaces are rated for Cockpit use. Pilots are now using these all the time because it saves them from having to carry around 30lbs worth of paper charts. It's kind of a big deal if the pilot isn't allowed to double check where he or she is going because the plane might break. Oh, and when I say carry around I mean it. Things like charts are per pilot, not per aircraft.
Slashdot Mirror
In some ways yes, in some ways no. Large history can be an issue, but to get to that point you pretty much need to be doing something pretty special for a fortune 500 company. The entirety of the Linux Kernel clocks in at under 2GiB, the only company I've ever heard make the claim that this is an issue was Facebook, who went with Mercurial instead.
The trick with branches is that each represents a different feature or bug fix. So long as they don't touch the same bits of code, git makes merging them painless. Local branches allow for trying out ideas, and swapping between tasks easy. Remote branches allow for greater control. A common paradigm is only one or two people have commit access to master. Everyone else asks them to merge their branch.
This branch and merge strategy, called 'pull requests', is the key to github's success. On sourceforge with svn, I would have to generate a patch file, then send it to the developers somehow, then wait for them to examine it, before finally deciding to add everything as one large commit. This can take a while, especially if several things have to be modified. Worse, the developers have to revert their local code copy to a clean slate before applying the patch. With git and github, you can easily view what's going to change, and merging is a simple click/command.
Git has what are known as hooks. Things that are run whenever you do something, like committing a file or trying to push to somewhere. It's how you get E-Mail notifications. These aren't anything new, so I think subversion offers something similar. The large difference is in what these let the maintainer do when it comes to integration.
Take a look at this page: https://github.com/OpenMW/open...
Click on the green check marks or red 'X's. This is something github has integrated into their system, but there are other options as well. The advantage is that developers could add a new feature, or fix a bug without committing directly to the master branch. The primary maintainer can easily view if the patches compile cleanly, and if the patch is acceptable or not.
This is a consequence of how easy it is to branch and merge using git. I know subversion has branches, but they can be harder to deal with and it's hard to spin up a branch for every feature and patch. Combine that with git's local storage and swapping/reverting branches is a sna
Actually you can do that with git.
Just set the right pre commit, or pre upload hooks and it'll do it all.
One project I contribute to on github preforms automatic coverity and travis-ci builds/tests every time someone asks to merge their code to the master branch.
Easy way to see if the thing even builds, without the maintainers having to do a thing.
I'm always going to recommend git as the version control system of choice. It scales well, and you can learn how it works without mucking with servers to start. Plus github.com has some good tutorials, and there are several web interfaces available. If you could convince your IT department to let you use a cloud based system, github would actually be perfect. Also, the speed. Don't underestimate how important that is.
Here's a list of reasons to use it instead of SVN or CVS: http://www.gitguys.com/topics/...
Almost all of the requested features are possible with most version control systems, but, like back end infrastructure, require someone knowledgeable about that particular system to set things up. For instance, there are commit hooks to handle sending E-Mails and doing code checking, but that requires editing the right file.
Any processor, much less Xenons, in Epoxy is going to get hot. Like, the epoxy is going to melt hot.
Even without the epoxy, that's a huge power profile in a small space. How exactly are they going to cool that?
Not quite so easy. Half the time these federal grants are tied to the individual, not the university. Heck, applying for a research position at my university is a waste of time unless you already have a grant. Side-note: Yep, they're having staffing problems.
The interesting thing is the computers. If they were on site, then it doesn't matter about root access. Pull the plug, and restore from backups or change to single user mode. If they're cloud servers paid for with federal grant money, then it becomes a tricky issue...
You should be able to take advantage of all of systemd's features whether the daemon is designed to be run from an init script or not, and even whether it is run from an init script or not. If not, there is either something deeply wrong with you (incompetence) or deeply wrong with systemd (poor design.)
Yeah.... http://0pointer.de/blog/projec...
See the part where it's talking about forking vs non forking.
Key features like dependency management, whether a service terminated with an error condition, and what to do when a service terminates are things that you CAN NOT DO if all you have is an init script.
It does seem a bit much, but the systemd transition is a slow one. Many packages are still using init.d startup scripts, which means we can't take advantage of systemd's features with them.
Systemd isn't really a startup management subsystem. It's a full blown service manager. It can be set, at the user's choice, to restart services when there's a problem. It can provide detailed logs from each service.
The best part is the service descriptor files follow a standard. If all people did at this conference was convert package init scripts to systemd I would be ecstatic.
Programs that require direct GPU access and as much of my system's RAM as possible are the top of my list of reasons for keeping a Windows partition around, personally. So, I've basically got one boot option to put my machine into gaming-console mode, and one to put it into everything-else mode. That set up will change when there's either a technical shift in what I can easily do on Linux or my interests change enough that I'm no longer interested in running that kind of program.
With newer machines having an IOMMU, that might be an option.
There are several ways to let a guest OS now have full access to the GPU, and nothing else.
http://www.firewing1.com/howto...
I've personally switched over to Linux full time, but that's because I don't mind the customization.
I also realized the first thing I did on a new windows box was to install cygwin and windows equivalent of all the handy Linux utilities.
Plus, package managers are a godsend when setting up a development environment.
While android itself may be open source, the Google APIs are not.
There are some projects to replace them with open source alternatives, but Google keeps adding to/changing them and developers are addicted to the new and shiny.
See the issues people with the Kindle Fire are dealing with.
The other big reason for the change is control. Android might be open source, but it's still Google that decides what direction it goes. Samsung want that kind of control over Tizen, or at least take advantage things being de-facto standards.
For instance Android has it's own compositor sitting on bare metal, and it's own 2d graphics library to talk to that compositor. You won't find either of those outside of android.
Tizen uses a custom compositor with wayland or X11. Apps use whatever graphics library they like, and can just tell the OS to render it. That's standard practice for desktop developers today.
4K h.265 encoding at 2 frames per second on the fastest CPU. And I thought I had a memory channel bottleneck.
Video encoding is insanely slow! How do TV stations handle moving editing and encoding their video. It seems that the evening news wouldn't be feasible at these encoding rates.
High end hardware, professional software that takes advantage of the GPU and custom hardware encoders. Plus, the editing is normally done on uncompressed video.
Not to mention things like animation/effects and encoding are often done on a render farm of dedicated servers.
Here in the US any library that deals with children must have mandatory filtering software installed. Given the typical puritanical attitude, quite a few public libraries also have filters.
https://en.wikipedia.org/wiki/...
Why should anyone care about the power level, as opposed to the pulse energy?
ie why does it matter if the kilojoule is spread over one or ten picoseconds? Without this vital piece of information, it is hard to get excited (pardon the pun).
Well, given that a 9mm has about the same energy as two or three punches... Yeah, I'd say the time and method of energy transfer/release is extremely important.
Sources:
https://en.wikipedia.org/wiki/...
http://www.science.ca/askascie...
Wireless and graphics are the two pieces of hardware Linux has occasional problems with, and that's become much more of a rarity in the past several years.
Many wireless chips require a non-free firmware package to be installed, so if you run a "pure" os like Debian, you'll have to manually tell it to do that.
Older and Intel graphics cards just work. The issue has always been getting good performance out of newer ATI and Nvidia cards.
Speaking as someone who uses Linux on my home machine, the most annoying part are peripherals like gaming mice and keyboards. Using all the buttons or changing settings is a pain in Linux. Companies like MadCatz and Razer just don't care. It will be interesting when people try to plug them into Steam machines and find they barely work
Honestly the freaking out thing isn't that bad, but the issue isn't Zirconium in general. For most applications, when they use Zirconium they don't bother to extract the Hafnium. It has most of the same properties, and it's expensive to remove. It just happens to be that one of the main applications that requires pure Zirconium involves the word nuclear. Which, is something no politician wants to touch with a ten foot pole.
Hafnium is about a dollar / gram. Nitrogen and carbon are plentiful and relatively cheap. Is this dramatically more expensive than current high temp materials?
442 stainless steel is US $1500.00 / Ton from Alibaba. Assuming metric, that works out to $1.5/kg, or $0.0015/g.
Plus that $1/g is just for the raw Hafnium. Alloys like the one proposed here tend to be expensive, time consuming, and finicky to get right.
Then you get into the fact that producing Hafnium leaves pure Zirconium. Which is typically used as cladding for nuclear fuel rods. Something that a fair portion of the world would freak out about, because anything that's good for nuclear must be bad. Plus there's this gem: https://en.wikipedia.org/wiki/...
This hasn't been the case for years. Mainly because users value privacy, and don't like being annoyed.
Perfect example: popup blockers. Every argument given for why browser makers should not stop annoying/malicious behavior has been made during that debate.
For a while there, websites could even change window size and position. I know of at least one script that would forkbomb a computer with popups of itself while telling the user they were an idiot.
While not said in the best way, AC is correct.
Use case 1 sounds like a problem, but one that should be fixed somewhere else.
Use case 2 is like popups and the blink tag. The times when users actively want that feature is dwarfed by its abuse. Further, it's easy to work around. Worst case, I've used a cell phone camera because a program I had to use locked down the entire pc.
While it's true the site operators are at fault, I also blame the browser makers.
Many websites don't allow copy or paste, or even selecting/highlighting text.
While I can understand the draw of websites, especially ones with games, being able to grab keyboard input, it's a potential security disaster waiting to happen.
Browser makers should treat these kind of keyboard/mouse hooks the same way they treat websites asking for location data. With a message asking the user if they want to allow the behavior or not. Furthermore, they should do it in such a way that operators can not force users to click allow.
You've hacked a bank and now you're a terrorist. Expect a visit from the FBI and a taxpayer funded trip to Cuba.
Vinegar Joe is, unfortunately, probably correct. The last time this happened the person was sent to jail and faced a hefty fine. http://appleinsider.com/articl...
Sorry mate, but reporting vulnerabilities puts you behind bars.
Post to undo bad mod.
Ugh, really with they had an undo button.
Under US Federal law it doesn't matter. If parent had any amount of drugs it's a felony, and in many areas comes with a mandatory minimum sentence. If parent has over an arbitrary amount of a drug then it's considered "possession with intent to distribute," which is a felony that can result in jail times longer than if parent had killed someone
Also, statistically, if someone arrested is not white then expect a harsher sentence in the US.
Actually that's a common justification for piracy. Ex: "I've already paid for it once, I'm not paying $XX just to get a Blue Ray version."
The thing to remember about phone apps is they tend to transfer within the same ecosystem. You buy an app for your old phone, and it'll pop up on your new phone as well.
PC software piracy is alive and well. Just look at any college where the students have to use proprietary software. Sure they could go to the labs, but they want it on their PCs and can't afford the $1000s per copy licence fee.
As I mentioned in another post, PILOTS use tablets now. It's a huge weight saver vs tons of paper maps. Sure they're supposed to turn the WiFi off on those things, but mistakes happen.
The funny part being that iPads and the MS Surfaces are rated for Cockpit use. Pilots are now using these all the time because it saves them from having to carry around 30lbs worth of paper charts. It's kind of a big deal if the pilot isn't allowed to double check where he or she is going because the plane might break. Oh, and when I say carry around I mean it. Things like charts are per pilot, not per aircraft.