>Most inventions are discovered simultaneously or nearly so, based on the natural progression of science and the technical arts.
False.
There is also a factor pertaining to the VOLUME of people involved. If the field in question has 7 people working in it, it is far less likely that any invention will be "discovered simultaneously" than if there are 1E6 people in the field. 1.00001^(population) as an example.
> Every investor wants you to maximize opportunities at your disposal
False.
Wall street wants to capitalize on your balance sheet. Ideas/Intellectual property seldom enters the equation. Witness Nikolai Tesla.
>More important to a company than inventions are their employees, who create those inventions
False.
As someone working at a startup in search of funding, patents help, but Angel/VC investing is about what the investors believe the risk vs. potential return is. A 1% return at huge risk will NEVER get funded. Yes, it is important for key employees to have a strong track record of delivering, but the big issue is risk/return.
In no particular order
- dealing with management not interested in product quality
- dealing with management who is biased towards their local site over product quality (Tel Aviv is full of ass-hats in this regard)
- dealing with management that interprets "Agile" as being 30-45 minute "standups" every day that are nothing more than "I worked on Bug X today" rehashes.
- dealing with management wherein the people hired by a particular manager are automatically given more credibility than people who are forcibly transferred in.
Yes, I refer to AMD from direct experience.
Yup. A Troll-bait comment subject.
But not every project is one where it can be afforded to "fix it" next month/next quarter. Device drivers. Compilers. Mainframe OS's.
I heard a figure recently (from in-person discussion with a Mainframe SW person) that downtime costs them upwards of US$10,000 PER SECOND of downtime. Agile focuses on fast responses to customer bugs, not on ensuring that the number of bugs experienced by the customer is virtually zero.
The point is that Mission Critical content has to have a correctness level which is an order of magnitude (or more) than a game or a less-than-wonderful UI.
A bad case scenario: Oh, I'm sorry, Miss/Mr. medical patient of Therac25 (http://en.wikipedia.org/wiki/Therac-25) - we'll fix that in two revisions by using our Agile process (its a tough bug to fix), and we're sorry that you will contract a horrible form of cancer in the meantime.
The problem isn't Windows per-se. It is Metro. Metro is just not usable unless you have a touch screen.
Enterprise PCs are not touch screen. Existing PCs are not touch screen.
Making it horribly difficult to use a "traditional" (non-touch-screen) interface is a fatal flaw. And not just for Windows.
Some of the newer linux distributions are equally unusable. I tried Fedora 17 for my web server. Truly worthless UI.
Fine if you are running a tablet, but completely unsuited for a server. Went back to CentOS on my web server.
And I've used RedHat/Centos on a regular basis since kernel 1.3.57.
Phalse.
Windows 3.x did NOT have "task scheduling" It was "pre-emptive multi-tasking". My college OS project was better at Multi-tasking (and context switching) than WinDoze 3.x. In that sense, Windows 3.x was actually "less" than an application on top of DOS - it constrained things to prevent actual multi-tasking.
Bzzzzt. Use of Qt presumes some sort of GUI. Not all applications need a GUI. Why would a loader need Qt?
For the puzzled, a loader is/lib/ld.so* and is the key bit of code which manages where your application sits in Virtual Memory, along with the statically bound dynamic libraries. For general application developers, It is something well beyond your capacity to understand, so stick with your burger-flipping.
How many people _actually_ shoot more than 10 frames/minute on a regular/continuous basis?
Really. Think about your personal usage.
The likelyhood is that the answer is Z-Eee-Arrr-Oooh. ZERO. or close to it. Those who do are serious about their video, and are much more picky about things than simple capture rates.
Too bad the AMD sacked the vast majority of their software people with any sort of Linux skills/background at the end of October.
They could have been relevant.
It is unfortunate that the Linux kernel still does not support a number of key features available in currently available hardware. Such as some features that Windows8 supports out-of-the box.
Here's one example: AMD's LWP feature set. It requires XSAVE/XRSTOR, but has been rejected by the Linux kernel developers.
No, I'm NOT an AMD employee. Yes I do own a couple of desktops based upon AMD cpus. Motivation: COST, COST, COST.
Writing anonymously as a former AMD-er: the performance has absolutely NOTHING to do with the underlying architecture. The root cause is a software development (if you can call it "development") culture which is completely incapable of moving at more than a snails pace. Thank you Ben Bar-Haim & associated Markham Bozos. I've met a lot of developers who are actually focused on quality at AMD, but they generally seem to be in the minority. Too many managers/directors of SW products at AMD seem to believe that the "look and feel" of the UI is much more important than actually being correct, let alone performant. I personally know for a fact that the shader compiler team is totally dedicated to correctness and high performance. But when they are [under] staffed at N, while the UI portion of the Catalyst driver is staffed at N^2 (or greater) the end result is inevitable. Goals are set on how "pretty" it is, rather than on performance and correctness.
I entered college at age 16, coming from a [private] college prep high school. Turns out I was in _waaaay_ over my head on the social aspects. And the age differential was from "skipping" 3rd grade, and had nothing to do with cruising through high-school. Moral of the story is for parents to be conscious of social issues when accelerating kids.
While fat binaries are one approach to run applications which are binary-only on Linux, a much better way is to use binary translation. A fat-binary approach would require application vendors to qualify both versions, which means approximately twice the cost. Translators can be developed by 3rd parties. There are a lot of commercial-grade binary translators and binary optimizers that have shipped over the years. Tandem, Digital, Transmeta, Transitive, etc.
The messy parts are getting the OS conversion semantics correct when the source and target OS's are not very similar. Instruction decode can be a bit tricky, but it is not the development bottleneck.
RTF License, not the FAQ. Explicitly:
An "Excluded License" is one that requires, as a condition of use, modification, or distribution, that (a) the code be disclosed or distributed in source code form; or (b) others have the right to modify it; or (xi) include the Redistributables in malicious, deceptive, or unlawful programs.
There are a couple of "iffy" items in the article.
First, how can an oil leak detector cause oil leaks (let alone spills)? That like saying having a faulty gas gauge on my car is going to either keep the tank completely empty or completely full all the time.
Secondly, a claim is made that "computer viruses have caused personnel injuries". This seems unlikely; without specific examples, it seems more likely to be a case of alarmist authorship or convenient excuse for another root cause.
It's just an Insel Intide thing. DAAMIT processors are more predictable. Or not. If you don't use numactl (1) to force socket (and memory) affinity, you get exactly what you ask for (randomly selected sockets, and unpredictable performance)
If you really think this is a problem, put your money into it. I did. So there is now an endowment for the math and sciences at my former high school. Don't whine, actually do something
This is drivel - it assumes that a static binary analysis can be used to predict the dynamic behavior of a non-trivial application, with zero false positives. Unless of course, "benign intent" equates to "trivial". As a concrete counter-example, witness the (rather old) Solaris telnet bug wherein a specific input string coupled with a particular environment variable could result in the skipping of requiring a password. A simple model based upon the CFG would indicate that this is a legitimate possibility.
My qualifications in this area: multiple product-grade binary translators and binary optimizers; former developer (Okena/Cisco) of a HIPS (Host Intrusion Prevention) system where we actually had to worry about this kind of problem.
Slashdot Mirror
Time to change "lifelong" party affiliations then.
>Most inventions are discovered simultaneously or nearly so, based on the natural progression of science and the technical arts. False. There is also a factor pertaining to the VOLUME of people involved. If the field in question has 7 people working in it, it is far less likely that any invention will be "discovered simultaneously" than if there are 1E6 people in the field. 1.00001^(population) as an example. > Every investor wants you to maximize opportunities at your disposal False. Wall street wants to capitalize on your balance sheet. Ideas/Intellectual property seldom enters the equation. Witness Nikolai Tesla. >More important to a company than inventions are their employees, who create those inventions False. As someone working at a startup in search of funding, patents help, but Angel/VC investing is about what the investors believe the risk vs. potential return is. A 1% return at huge risk will NEVER get funded. Yes, it is important for key employees to have a strong track record of delivering, but the big issue is risk/return.
Alternative definition of "NSA" == Network Storage Attachment
In no particular order - dealing with management not interested in product quality - dealing with management who is biased towards their local site over product quality (Tel Aviv is full of ass-hats in this regard) - dealing with management that interprets "Agile" as being 30-45 minute "standups" every day that are nothing more than "I worked on Bug X today" rehashes. - dealing with management wherein the people hired by a particular manager are automatically given more credibility than people who are forcibly transferred in. Yes, I refer to AMD from direct experience.
Larry Niven has gone into a great deal of theoretical depth on monopoles. Worth reading
Yup. A Troll-bait comment subject. But not every project is one where it can be afforded to "fix it" next month/next quarter. Device drivers. Compilers. Mainframe OS's. I heard a figure recently (from in-person discussion with a Mainframe SW person) that downtime costs them upwards of US$10,000 PER SECOND of downtime. Agile focuses on fast responses to customer bugs, not on ensuring that the number of bugs experienced by the customer is virtually zero. The point is that Mission Critical content has to have a correctness level which is an order of magnitude (or more) than a game or a less-than-wonderful UI. A bad case scenario: Oh, I'm sorry, Miss/Mr. medical patient of Therac25 (http://en.wikipedia.org/wiki/Therac-25) - we'll fix that in two revisions by using our Agile process (its a tough bug to fix), and we're sorry that you will contract a horrible form of cancer in the meantime.
Change the acronym, now relevant to OO-fans.
Wait - you forgot the 3 pages of required COBOL prologue to create a "hello world" style program.
The problem isn't Windows per-se. It is Metro. Metro is just not usable unless you have a touch screen. Enterprise PCs are not touch screen. Existing PCs are not touch screen. Making it horribly difficult to use a "traditional" (non-touch-screen) interface is a fatal flaw. And not just for Windows. Some of the newer linux distributions are equally unusable. I tried Fedora 17 for my web server. Truly worthless UI. Fine if you are running a tablet, but completely unsuited for a server. Went back to CentOS on my web server. And I've used RedHat/Centos on a regular basis since kernel 1.3.57.
Phalse. Windows 3.x did NOT have "task scheduling" It was "pre-emptive multi-tasking". My college OS project was better at Multi-tasking (and context switching) than WinDoze 3.x. In that sense, Windows 3.x was actually "less" than an application on top of DOS - it constrained things to prevent actual multi-tasking.
Bzzzzt. Use of Qt presumes some sort of GUI. Not all applications need a GUI. Why would a loader need Qt? For the puzzled, a loader is /lib/ld.so* and is the key bit of code which manages where your application sits in Virtual Memory, along with the statically bound dynamic libraries. For general application developers, It is something well beyond your capacity to understand, so stick with your burger-flipping.
How many people _actually_ shoot more than 10 frames/minute on a regular/continuous basis? Really. Think about your personal usage. The likelyhood is that the answer is Z-Eee-Arrr-Oooh. ZERO. or close to it. Those who do are serious about their video, and are much more picky about things than simple capture rates.
Liar and/or Troll.
Too bad the AMD sacked the vast majority of their software people with any sort of Linux skills/background at the end of October. They could have been relevant.
It is unfortunate that the Linux kernel still does not support a number of key features available in currently available hardware. Such as some features that Windows8 supports out-of-the box. Here's one example: AMD's LWP feature set. It requires XSAVE/XRSTOR, but has been rejected by the Linux kernel developers. No, I'm NOT an AMD employee. Yes I do own a couple of desktops based upon AMD cpus. Motivation: COST, COST, COST.
Writing anonymously as a former AMD-er: the performance has absolutely NOTHING to do with the underlying architecture. The root cause is a software development (if you can call it "development") culture which is completely incapable of moving at more than a snails pace. Thank you Ben Bar-Haim & associated Markham Bozos. I've met a lot of developers who are actually focused on quality at AMD, but they generally seem to be in the minority. Too many managers/directors of SW products at AMD seem to believe that the "look and feel" of the UI is much more important than actually being correct, let alone performant. I personally know for a fact that the shader compiler team is totally dedicated to correctness and high performance. But when they are [under] staffed at N, while the UI portion of the Catalyst driver is staffed at N^2 (or greater) the end result is inevitable. Goals are set on how "pretty" it is, rather than on performance and correctness.
I entered college at age 16, coming from a [private] college prep high school. Turns out I was in _waaaay_ over my head on the social aspects. And the age differential was from "skipping" 3rd grade, and had nothing to do with cruising through high-school. Moral of the story is for parents to be conscious of social issues when accelerating kids.
While fat binaries are one approach to run applications which are binary-only on Linux, a much better way is to use binary translation. A fat-binary approach would require application vendors to qualify both versions, which means approximately twice the cost. Translators can be developed by 3rd parties. There are a lot of commercial-grade binary translators and binary optimizers that have shipped over the years. Tandem, Digital, Transmeta, Transitive, etc. The messy parts are getting the OS conversion semantics correct when the source and target OS's are not very similar. Instruction decode can be a bit tricky, but it is not the development bottleneck.
RTF License, not the FAQ. Explicitly: An "Excluded License" is one that requires, as a condition of use, modification, or distribution, that (a) the code be disclosed or distributed in source code form; or (b) others have the right to modify it; or (xi) include the Redistributables in malicious, deceptive, or unlawful programs.
"You Lie!" They are NOT GPL-ed. The License is explicitly ANTI-GPL. Read it.
There are a couple of "iffy" items in the article. First, how can an oil leak detector cause oil leaks (let alone spills)? That like saying having a faulty gas gauge on my car is going to either keep the tank completely empty or completely full all the time. Secondly, a claim is made that "computer viruses have caused personnel injuries". This seems unlikely; without specific examples, it seems more likely to be a case of alarmist authorship or convenient excuse for another root cause.
It's just an Insel Intide thing. DAAMIT processors are more predictable. Or not. If you don't use numactl (1) to force socket (and memory) affinity, you get exactly what you ask for (randomly selected sockets, and unpredictable performance)
If you really think this is a problem, put your money into it. I did. So there is now an endowment for the math and sciences at my former high school. Don't whine, actually do something
This is drivel - it assumes that a static binary analysis can be used to predict the dynamic behavior of a non-trivial application, with zero false positives. Unless of course, "benign intent" equates to "trivial". As a concrete counter-example, witness the (rather old) Solaris telnet bug wherein a specific input string coupled with a particular environment variable could result in the skipping of requiring a password. A simple model based upon the CFG would indicate that this is a legitimate possibility. My qualifications in this area: multiple product-grade binary translators and binary optimizers; former developer (Okena/Cisco) of a HIPS (Host Intrusion Prevention) system where we actually had to worry about this kind of problem.