Erm, he did a start up in the 90's and literally crushed his competitors. The company was eventually sold to Yahoo! for approx $25 million. How much more in touch with the business environment can you get?
His trick was rapid development and the ability to debug and add features while he was still on the phone with customers. All of this using CLISP (byte-code compiler for lisp) in the mid-90's.
He generally rags on Java the most not because it's interpreted or slow or anything of that nature. It's because it's slow to write, has no REPL, and lacks good abstractions/is too verbose.
Ugh, this is just ignorant. There are plenty of programs that don't work at all out of the box on Solaris x86 (specifically OSS lisp implementations) which hopefully this will cover.
If they can get CMUCL to work on Solaris x86, I'll move my old fileserver over in a heartbeat.
When you have a so few resources you might want to look into implementing a small forth kernel (usually comes out to be 5-10k) and developing using forth. It's designed for soft real time applications and extremely compact program size.
When you have a method of knocking that complex, wouldn't it just be easier to have a static port (something in the userspace range) that you send a one time password to?
Ever tried an ML derivative? They are statically typed, yet typed-inferred so you save quite a lot of time and any change cascades itself down. Saves a whole lot of time, especially nice since the type system is flexible enough to do symbolic computing.
"""I feel one major pitfall of X is the inability to change the resolution of the X-Server without shutting it down."""
Commercial X servers have been doing this for a long time. It's an XFree issue not an X issue (See metrolink, or X implementations on commercial Unices).
Converting from one lossy format to another is a bad idea, you'll lose quality. However, if you really want to (for whatever reason) there is a utility that does such here.
Sun's thin clients don't run X (or an OS for that matter, thus no need for Linux on the client side) According to newsforge it's more along the lines of a grid/clustering offering (on Sun brand hardware).
To paraphrase (as I stated earlier) and contrary to what you said, you must distribute the source with the executables, or offer to give ANY third party the source.
Actually, you are only required to distribute it to any third party with the written offer. This allows the company to distribute along with their software something like a coupon which entitles the bearer to have a copy. The phrase 'any 3rd party' is used as to not preclude the resale of the software.
That's to prevent people from doing stupid stuff like modifying critical stuff [sh/csh/kernel] .
chflags [schg|noschg] sets/unsets this.
EXT2FS has this as well, (via chattr -i) and has had such since at least 1.3.7 (and before then I imagine). It's been a part of most modern OS's for the last 20+ years and definitely isn't a superior feature of *BSD.
Some clarifications from a random cs major at 'Tech.
The first class cs1311 is a scheme course which is required by every student (as far as I can tell). The second class cs1312 [Java] is required by CompSci, CompEng, and several other engineering majors (Industrial, Electrical, etc). Since all the departments pressure the CS dept. to dumb these classes down there really isn't a reason to copy code except laziness.
The surprise really isn't that they caught people cheating (it's usually around 5%), but that it was around 1 out of every 8 students that did so.
As a side note most of the assignments given aren't copy algorithms out of the book assignments. More so, according to the honor code you are required to cite any book from which you obtained an algorithm to use.
Slashdot Mirror
In the US, case law supports GP's argument: http://en.wikipedia.org/wiki/Feist_v._Rural
The key bit, is if it's published and a fact or collection of facts it can be reused.
It's more likely a Tu-143 with a larger wingspan and upgraded guts. So more like 70s or early 80s technology.
Something simple like a basic Webserver (GET/PUT/HEAD) or a FTP server.
You get:
a) simple string parsing/processing/manipulation
b) File I/O and filesystem manipulation
c) Network I/O
Optionally or language dependent:
d) Threading
e) Packaging
If a dynamic language (e.g. lisp):
f) Write something like JSP on top of it: dynamic dispatch to handling method/function
Optimizations are easy as well. Caching will give you a good overview of data structure speed.
According to the article betting is only open for 2 weeks.
Erm, he did a start up in the 90's and literally crushed his competitors. The company was eventually sold to Yahoo! for approx $25 million. How much more in touch with the business environment can you get?
His trick was rapid development and the ability to debug and add features while he was still on the phone with customers. All of this using CLISP (byte-code compiler for lisp) in the mid-90's.
He generally rags on Java the most not because it's interpreted or slow or anything of that nature. It's because it's slow to write, has no REPL, and lacks good abstractions/is too verbose.
Ugh, this is just ignorant.
There are plenty of programs that don't work at all out of the box on Solaris x86 (specifically OSS lisp implementations) which hopefully this will cover.
If they can get CMUCL to work on Solaris x86, I'll move my old fileserver over in a heartbeat.
It depends, but usually it's auctioned off and the money is given to any creditors.
When you have a so few resources you might want to look into implementing a small forth kernel (usually comes out to be 5-10k) and developing using forth. It's designed for soft real time applications and extremely compact program size.
When you have a method of knocking that complex, wouldn't it just be easier to have a static port (something in the userspace range) that you send a one time password to?
And just as fast, the contract they have with Real will say they can only link directly to Real's website/player.
That's what DNS is for. If it's not the main server or the MX record throw it away.
Ummm... XFree86 version 4 was a complete rewrite of XFree from scratch.
Ever tried an ML derivative?
They are statically typed, yet typed-inferred so you save quite a lot of time and any change cascades itself down. Saves a whole lot of time, especially nice since the type system is flexible enough to do symbolic computing.
"""I feel one major pitfall of X is the inability to change the resolution of the X-Server without shutting it down."""
Commercial X servers have been doing this for a long time. It's an XFree issue not an X issue (See metrolink, or X implementations on commercial Unices).
Converting from one lossy format to another is a bad idea, you'll lose quality. However, if you really want to (for whatever reason) there is a utility that does such here.
Sun's thin clients don't run X (or an OS for that matter, thus no need for Linux on the client side) According to newsforge it's more along the lines of a grid/clustering offering (on Sun brand hardware).
Actually, you are only required to distribute it to any third party with the written offer. This allows the company to distribute along with their software something like a coupon which entitles the bearer to have a copy. The phrase 'any 3rd party' is used as to not preclude the resale of the software.
That's to prevent people from doing stupid stuff like modifying critical stuff [sh/csh/kernel] . chflags [schg|noschg] sets/unsets this. EXT2FS has this as well, (via chattr -i) and has had such since at least 1.3.7 (and before then I imagine). It's been a part of most modern OS's for the last 20+ years and definitely isn't a superior feature of *BSD.
Some clarifications from a random cs major at 'Tech.
The first class cs1311 is a scheme course which is required by every student (as far as I can tell). The second class cs1312 [Java] is required by CompSci, CompEng, and several other engineering majors (Industrial, Electrical, etc). Since all the departments pressure the CS dept. to dumb these classes down there really isn't a reason to copy code except laziness.
The surprise really isn't that they caught people cheating (it's usually around 5%), but that it was around 1 out of every 8 students that did so.
As a side note most of the assignments given aren't copy algorithms out of the book assignments. More so, according to the honor code you are required to cite any book from which you obtained an algorithm to use.