Letting all the people with all the knowledge go is indeed not so smart. You better have a development team with both employees and freelancers. So knowledge about the software keeps inside the company. Working with employees only has the danger of getting tunnel vision: "This is what we always did and it works for us". Working with (experienced) freelancers has the benefit of bringing in new knowledge and new insights.
Of course you also need to have some code standards, but there's no difference between employees and freelancers in this respect.
In the web development world a stack is the combination of webserver, database and programming language, so you have the well known LAMP stack (Linux, Apache, MySQL and PHP) and the Java stack (Tomcat [for example], Oracle [for example] and Java) and the Microsoft stack (Windows, IIS, SQL Server and C#). Now you also have the JavaScript stack (Node.js [with build in webserver] and MongoDB).
The problem is not JavaScript, but programmers who think "it's just a scripting language, how hard can this be". And they hit a brick wall again and again because JavaScript is a language with its own features, features that has to be learnt.
And JavaScript is unmaintanable? It's just a programming language. It's up to the programmer to structure your code. How is that different from other languages? Of course it's possible to write maintainable large projects in JavaScript.
I agree best practices and frameworks are still being developed and improved, but is JavaScript a horrible language? No, it isn't.
The first ten reactions are about how slow Java is. Wake up! It's 2007, NOT 1997. The world has changed. Don't you keep your knowledge up to date? Are you amateurs? And no, a benchmark from 2001 doesn't count too.
Until now, you are only allowed to distribute the JRE with Java software. This has always been an problem for creators of Linux distributions who like to include Java in their distribution.
I seems Sun is gonna change their license at this point so every Linux distribution can distribute the JRE and support Java out of the box.
This is probably the most important part of the license change and I hear nobody about it.
"Applications run on PlanetLab are decentralized, with pieces running on many machines spread across the global Internet. They can also self-organize to form their own networks, and include some form of application processing inside the network (instead of at the edges), adding new intelligence and capabilities to the Internet."
"It would provide a platform on which Web services can run and a way to connect grid computing sites and utility data centers. It sits above the new physical infrastructure supplied by Internet 2 and above the networking layer where IPv6 functions, adding a new stratum of higher-level functionality to the Internet."
Why it has to replace the current TCP/IP-infrastructure is still unclear (apart from selling more hardware).
The Outlook interface was bad anyway. I can understand making an UNIX-version of Outlook to make it easier for Windows-users to migrate to UNIX, but from an usability standpoint, it's unbelievable.
Even Microsoft has come to understand this: the upcoming Outlook will be quite different.
Slashdot Mirror
Letting all the people with all the knowledge go is indeed not so smart. You better have a development team with both employees and freelancers. So knowledge about the software keeps inside the company. Working with employees only has the danger of getting tunnel vision: "This is what we always did and it works for us". Working with (experienced) freelancers has the benefit of bringing in new knowledge and new insights.
Of course you also need to have some code standards, but there's no difference between employees and freelancers in this respect.
In the web development world a stack is the combination of webserver, database and programming language, so you have the well known LAMP stack (Linux, Apache, MySQL and PHP) and the Java stack (Tomcat [for example], Oracle [for example] and Java) and the Microsoft stack (Windows, IIS, SQL Server and C#). Now you also have the JavaScript stack (Node.js [with build in webserver] and MongoDB).
Román Cortés has written a nice, detailed explanation of how he made his Furbee demo:
http://www.romancortes.com/blog/furbee-my-js1k-spring-13-entry/
Very interesting read.
The problem is not JavaScript, but programmers who think "it's just a scripting language, how hard can this be". And they hit a brick wall again and again because JavaScript is a language with its own features, features that has to be learnt.
And JavaScript is unmaintanable? It's just a programming language. It's up to the programmer to structure your code. How is that different from other languages? Of course it's possible to write maintainable large projects in JavaScript.
I agree best practices and frameworks are still being developed and improved, but is JavaScript a horrible language? No, it isn't.
System Operator arrested for leaving the computer system of the company he worked for vulnerable for attacks by kids. Oh wait...
Wow, so you found a bug in beta software? You know what beta means, do you? Apparently, not.
The first ten reactions are about how slow Java is. Wake up! It's 2007, NOT 1997. The world has changed. Don't you keep your knowledge up to date? Are you amateurs? And no, a benchmark from 2001 doesn't count too.
Just checking "leave mail on server" will probably do it.
Turn on pipelining and use more connections per host with this Firefox-Add-on
Tweak Network Settings:
http://www.bitstorm.org/extensions/tweak/
Very easy to use: just use the "Power profile".
I can't wait 'till we have enough photo's to make an animation of two colliding galaxies.
Have you ever tried to change Debian and release it as Debian?
No?
I thought so.
Debian also has restrictions if you want to use the official logo:
http://www.debian.org/logos/
And who made the decision and is he/she already been punished? :-/
Well, in Dutch 'lol' *is* a word, meaning fun. (Look it up in the dictionary if you don't believe me).
It's spoken with a short o, not like the English long Boooowl.
I don't know, but you can start here: http://www.speakdutch.nl/html/lesson1.htm
Until now, you are only allowed to distribute the JRE with Java software. This has always been an problem for creators of Linux distributions who like to include Java in their distribution.
I seems Sun is gonna change their license at this point so every Linux distribution can distribute the JRE and support Java out of the box.
This is probably the most important part of the license change and I hear nobody about it.
Here you can see some pictures:
http://www.lets-direct.jp/fsp/fsp3.htm (Mostly pictures of flowers in a vase).
I wonder if the last vase is really seven times more expensive than the first one.
Intel's press release about the same speech has a little bit more information, although nothing technical.
0 040909corp.htm
http://www.intel.com/pressroom/archive/releases/2
Also interesting: a link to the open platform website:
http://www.planet-lab.org/
Interesting quotes:
"Applications run on PlanetLab are decentralized, with pieces running on many machines spread across the global Internet. They can also self-organize to form their own networks, and include some form of application processing inside the network (instead of at the edges), adding new intelligence and capabilities to the Internet."
"It would provide a platform on which Web services can run and a way to connect grid computing sites and utility data centers. It sits above the new physical infrastructure supplied by Internet 2 and above the networking layer where IPv6 functions, adding a new stratum of higher-level functionality to the Internet."
Why it has to replace the current TCP/IP-infrastructure is still unclear (apart from selling more hardware).
First we hear is't a huge disadvantage when a programmer doesn't know the business-side of software development. And now it's the other way around.
I'm confused.
I wonder when Debian will support 2.6. Since the default kernel of het current stable Debian release is still version 2.2!
Maybe 2006?
Okay, you can run "testing", but I think a lot of the sysadmins only wants to run "stable" on their company machines.
This is a must read, I haven't seen on Slashdot before.
The Viola webbrowser featured plug-ins in 1993. The Eolas patens was filed in November 1994.
Two facts:
This stinks. Eolas will probably lose in the next round.
Read it all here:
You're right. This is strange.
You shouldn't call the method to write the plug-in on the page itself. Only from within the external script.
So put your externalWriteFlash() and externalWriteJava() inside externalwriter.js.
The patent is about programs embedded in hypertext documents. X is not an hypertext document, so it's (unfortunately) not prior art.
The W3C "standardized" it, and then both Netscape and Microsoft went about with their own proprietary versions.
The W3C has not much to do with JavaScript.
ECMA is the organization who made JavaScript into an independent standard (ECMAScript).
The Outlook interface was bad anyway. I can understand making an UNIX-version of Outlook to make it easier for Windows-users to migrate to UNIX, but from an usability standpoint, it's unbelievable.
Even Microsoft has come to understand this: the upcoming Outlook will be quite different.