it depends on whether you take into account relativity...
The argument goes both ways -- I've spent hundred hours of my life learning POSIX, and if my boss wants me to run a POSIX program in Windows, I'm pretty much doomed. (I know a bit of Win32 API if that helps...)
"Open" does not mean "supported on all major platforms". It only means "can be supported by other vendors if they choose to". And if you choose a language or technology that is out of fashion, it doesn't really matter whether it is open or not.
And yes, I know Microsoft Windows is POSIX compliant.
Which industry are you talking about? Because almost all your points are true for all industries to some extent. If that's your explanation why women are reluctant to study CS, you haven't proved your case.
clean-room reimplementation is legal
Clean room reimplementation is legal as long as the specification used by the implementors is free of copyright (and other I.P.) issues.
I definitely agree that some of the prior cases of clean-room implementation is at odds with the notion that APIs are copyrightable. To be honest, copyright law has never been logically consistent to me -- which is why I don't even pretend to have knowledge of it unless I'm arguing about legal topics on slashdot
The "wrong decision" referred to the GP isn't about the trivial range check, but rather the notion that APIs are not copyrightable.
It would be really shitty if APIs were copyrightable, but, as the GP said, that has been the conventional understanding of copyright law for a long time.
It would be interesting to see how the story unfolds, but really, there's nothing funny about the notion of APIs being copyrightable.
Furthermore, because of deallocation cascades, a release message in such schemes can have a very high latency
Right. When gc happens, good garbage collectors don't freeze the whole application for hundreds of milliseconds to scan through the allocated memory looking for objects to free.
It is legal paranoia. Just like how IT-types have network security paranoia and ban a bunch of software/tools that *could* *potentially* introduce security issues to the company network...
I mean, sure, if you spend time looking at an individual license it could be OK. But why spend the time to investigate? Just blanket deny, and if somebody thinks it's worth fighting the bureaucracy to use a damn piece of software, *then* it might be worth looking into making an exception...
they have not discovered any form of language beyond what they already knew about mRNA
Duh. Have you discovered any language beyond what you already knew about sound waves and ink? I thought not.
Most critical production systems have alerts to pagers and phones. Nobody exclusively relies on email for this kind of stuff.
What makes you think that the Java API is "public"? At least Sun/Oracle never said that anyone can use those APIs. Which is why there was this compatibility certification crap.
I read somewhere that Oracle wasn't interested in buying Sun until they learnt about Android's use of Java APIs. If they were successful in suing Google for this, the damages could make up the purchase price anyway.
I agree with your list, except this one:
- one day I will rewrite this to be better
Welcome to the real world, where there are deadlines and sometimes it's a necessary evil to write crap to fix later.
What you say is true, but "not being the most brilliant people I know" is not necessarily "failure", and definitely not "the floor".
I know a bunch of really brilliant CS people as well. Almost all of them graduated with CS degrees and doing quite well. There are different kinds of "smart". The person who becomes a competent sysadmin at 16 is different from the one who drops out of college to found a successful startup, and is different from the one who gets a CS PhD and then a researcher job at Princeton.
The 16-year-old sysadmin probably can't do my job, at least not as well as I (software engineering), and I probably can't do her job well either.
There are different paths to "success", although I must agree that the value of getting a degree is diminishing every day, it's not necessarily a bad thing to do. It really depends on the circumstances of each case.
If you can't write self-documenting code, you cannot write self-documenting documentation.
In my jurisdiction (non-US) there's stuff like these: http://en.wikipedia.org/wiki/D...
Not sure whether there are such laws in Massachusetts..