Hiring might be up but that doesn't make it any cheaper to live there. Housing on average is nearly 5 times the cost of average US houses.
Check out this guy (Cameron Moll) -- he's a fantastic designer and passed up a job with Apple partially because of the cost of living (he's a family of 6). Even for a family of 2 or 4, it's hard to find an affordable place to live.
So, I think the 10 minute rule is great for hype, horrible in the real world. 10 minutes is what it takes to do a good demo, nothing more... and we all know what demos are worth. There are plenty of extremely powerful tools and frameworks out there in all disciplines (the web isn't the only thing people do, although you wouldn't know it from looking at slashdot) that take significantly more time to feel productive in than 10 minutes. But that up front learning curve pays off later.
You miss my point, I'm not talking about demos. I'm talking about 10 minutes of hands-on testing. In 10 minutes you should be able to build the source, run tests, read docs and read the APIs. Well documented code, good build scripts, simple & clean architecture are all signs that the developer of the framework has focused on quality. After 10 enjoyable minutes it's likely the framework will hold up to more inspection.
The first test is the 10 minute rule. Start by downloading the framework or project, compile it, get it to run and read the docs. If in 10 minutes you feel productive then you can move to the next steps.
An amazing framework will be easy to use, well documented, intuitive and will make you feel smart & productive all within 10 minutes.
No, that's not true that you only benefit if you're a shareholder. A company with more capital is able to hire more non-techinal people (product managers, biz dev, accountants) and put more $ into the economy in terms of capital expenditures (computers, notepads, etc).
Further, half your argument assumes foreign workers are exploited by the US corp - that's just not the case. Making $20/hr as a programmer in Russia is a good salary and it's a job they're eager to have (ie, it's not a sweatshop!).
Right, the cost savings over the long term might be nil, BUT the big thing for me is the environmental impact. My fiancee and I rented a Ford Escape for a day and LOVED it but would never buy one because of the horrible gas milage and effect that has on pollution (I should know, I live in Jersey). Anyway, Ford will be selling a hybrid next year and the thought of getting 40 mpg on an SUV is awesome - all the SUV with none of the enviromental guilt.
Awesome, can't wait to read it.
on
New Heinlein Novel
·
· Score: -1, Flamebait
Thank god, because I thought his last novel wasn't up to par. Will Jack Ryan be back this time? I heard this one focuses more on his son, Jack Ryan, Jr.
Interesting they decided to bundle that search engine - I'm surprised they didn't go with Lucene (http://jakarta.apache.org/lucene/). It's open source, 100% Java, fast, and fully featured.
Re:I'd like to take this oppertunity..
on
Head First Java
·
· Score: 0, Troll
Oh, for fuck's sake... Nothing like a little slashdot FUD.
Malocchio, people like you really need to invest some time into *learning* about Java before you just rehash the same old TIRED and incorrect comments about the language.
Do you feel you might be a target of litigation or any sort of legal action because you're the "point" person for this project? Stories like these prompted my question: http://slashdot.org/article.pl?sid=03/0 5/27/133822 3&mode=thread&tid=188&tid=97
It looks like the media companies are looking for someone to "drag over the coals.":)
One of the coolest new features of JDK 1.5 is the completely reworked concurrency stuff (JSR 166). I just listened to Doug Lea (spec lead) give a talk on this very subject and I'm pretty convince this will rocket Java performance way up for a lot of the collections stuff, concurrent programming, etc.
Bascially, the goal of JSR 166 is to do for concurrency programming what JDK 1.2 did for data structurs (Collections stuff). The gist is, you'll never need to use "new Thread()" or "synchronized" anymore, but rather you'll execute Runnables, use Locks and Semaphores, etc. Also, queues are *completely* reworked to be ultra scalable.
JSR 166 is based on Doug's concurrency package: http://gee.cs.oswego.edu/dl/classes/EDU/ oswego/cs/ dl/util/concurrent/intro.html
OH, and there will be classes like AtomicLong which guarantee atomic 'compare and set' options for primitives.:)
Yep, it works in Netscape 6, but not Mozilla. How *lame*.
In the 1950's, people argued that racism was bad for business against those businesses who didn't serve to African Amercians. Why do I feel like this is the same type of thing going on with MS's treatment of Mozilla users? Screw MS.. I'll just go to Netcape or Yahoo.
I'm one of the lead developers on the Open Source project Jive. Many of our contributors work on the project as part of their job duties at their place of employment. In light of that, we've been considering a mandatory Contributor Agreement for all code that is submitted to the project (excluding one-liners).
We want the agreement to accomplish three things:
Stipulate that the code is being released to the project under the project's license (for our project this is the Apache License).
Ensure that the contributor has permission to release the intellectual property to the project, including any necessary permission from their employer.
Make sure that the contributor does not apply for patents for the code that they're submitting.
My question is:
Do you see legal value in this sort of agreement?
Do you know of any boilerplate agreements that exist?
Shouldn't more Open Source projects be worried about IP issues that a contributor agreement seeks to prevent?
Slashdot Mirror
Hiring might be up but that doesn't make it any cheaper to live there. Housing on average is nearly 5 times the cost of average US houses.
Check out this guy (Cameron Moll) -- he's a fantastic designer and passed up a job with Apple partially because of the cost of living (he's a family of 6). Even for a family of 2 or 4, it's hard to find an affordable place to live.
It should be SWT vs Swing. There's hardly a reason to use the plain AWT when there's Swing (a much more powerful library built on top of AWT).
So, I think the 10 minute rule is great for hype, horrible in the real world. 10 minutes is what it takes to do a good demo, nothing more... and we all know what demos are worth. There are plenty of extremely powerful tools and frameworks out there in all disciplines (the web isn't the only thing people do, although you wouldn't know it from looking at slashdot) that take significantly more time to feel productive in than 10 minutes. But that up front learning curve pays off later. You miss my point, I'm not talking about demos. I'm talking about 10 minutes of hands-on testing. In 10 minutes you should be able to build the source, run tests, read docs and read the APIs. Well documented code, good build scripts, simple & clean architecture are all signs that the developer of the framework has focused on quality. After 10 enjoyable minutes it's likely the framework will hold up to more inspection.
The first test is the 10 minute rule. Start by downloading the framework or project, compile it, get it to run and read the docs. If in 10 minutes you feel productive then you can move to the next steps.
An amazing framework will be easy to use, well documented, intuitive and will make you feel smart & productive all within 10 minutes.
No, that's not true that you only benefit if you're a shareholder. A company with more capital is able to hire more non-techinal people (product managers, biz dev, accountants) and put more $ into the economy in terms of capital expenditures (computers, notepads, etc).
Further, half your argument assumes foreign workers are exploited by the US corp - that's just not the case. Making $20/hr as a programmer in Russia is a good salary and it's a job they're eager to have (ie, it's not a sweatshop!).
... that's what Microsoft or Oracle make in a week. I don't think the OS business model is quite there, yet. ;)
Right, the cost savings over the long term might be nil, BUT the big thing for me is the environmental impact. My fiancee and I rented a Ford Escape for a day and LOVED it but would never buy one because of the horrible gas milage and effect that has on pollution (I should know, I live in Jersey). Anyway, Ford will be selling a hybrid next year and the thought of getting 40 mpg on an SUV is awesome - all the SUV with none of the enviromental guilt.
Thank god, because I thought his last novel wasn't up to par. Will Jack Ryan be back this time? I heard this one focuses more on his son, Jack Ryan, Jr.
Boo to the writer - "Are reporting" ??
Interesting they decided to bundle that search engine - I'm surprised they didn't go with Lucene (http://jakarta.apache.org/lucene/). It's open source, 100% Java, fast, and fully featured.
Oh, for fuck's sake... Nothing like a little slashdot FUD.
Malocchio, people like you really need to invest some time into *learning* about Java before you just rehash the same old TIRED and incorrect comments about the language.
Bram,
0 5/27/133822 3&mode=thread&tid=188&tid=97
:)
Do you feel you might be a target of litigation or any sort of legal action because you're the "point" person for this project? Stories like these prompted my question:
http://slashdot.org/article.pl?sid=03/
It looks like the media companies are looking for someone to "drag over the coals."
Heh, that's not me, that's /.!
--Bill
One of the coolest new features of JDK 1.5 is the completely reworked concurrency stuff (JSR 166). I just listened to Doug Lea (spec lead) give a talk on this very subject and I'm pretty convince this will rocket Java performance way up for a lot of the collections stuff, concurrent programming, etc.
/ oswego/cs/ dl/util/concurrent/intro.html
:)
Bascially, the goal of JSR 166 is to do for concurrency programming what JDK 1.2 did for data structurs (Collections stuff). The gist is, you'll never need to use "new Thread()" or "synchronized" anymore, but rather you'll execute Runnables, use Locks and Semaphores, etc. Also, queues are *completely* reworked to be ultra scalable.
JSR 166 is based on Doug's concurrency package:
http://gee.cs.oswego.edu/dl/classes/EDU
OH, and there will be classes like AtomicLong which guarantee atomic 'compare and set' options for primitives.
Cheers!
I don't know if it's possible for the /. guys to make an *uglier* site. I mean seriously - I think they had to try to make this site this bad looking.
/. ever get a facelift? I'm not sure if this has been brought up before so maybe some of the /. vets can comment.
Will
I mean seriously. It's too bad I can't filter birthday notices out of my new articles.
:)
Someday I'm sure there will be a "Linus takes a crap" posting...
This is a lot like:1 25 9&mode=thread
http://slashdot.org/article.pl?sid=02/01/23/213
Slashdot looks the exact same it did 5 years ago!
WHEN is this site going to be updated? Forget the wayback machine, if I want ancient web history I visit slashdot.
--Dood
Can you guys spell anything? "debth"???
Arg.. all sites are *hosed*. Can anyone mirror this?
Yep, it works in Netscape 6, but not Mozilla. How *lame*.
In the 1950's, people argued that racism was bad for business against those businesses who didn't serve to African Amercians. Why do I feel like this is the same type of thing going on with MS's treatment of Mozilla users? Screw MS.. I'll just go to Netcape or Yahoo.
d00d
Hey, I understand about all the ads, but how about a look and feel update to /. ? I'd say it's well overdue.
Any plans?
What is the market share of Compuserve? One tenth of one percent?
Seriously this is a drop in a drop in the bucket compared to the suscriber base of AOL/MSN.
I think the only reason this might be interesting is because AOL is testing the water with this one incase they need to quicly drop IE in AOL.
--d00d
Uhh, we need more CS/CE majors, not less.
We want the agreement to accomplish three things:
- Stipulate that the code is being released to the project under the project's license (for our project this is the Apache License).
- Ensure that the contributor has permission to release the intellectual property to the project, including any necessary permission from their employer.
- Make sure that the contributor does not apply for patents for the code that they're submitting.
My question is:- Do you see legal value in this sort of agreement?
- Do you know of any boilerplate agreements that exist?
- Shouldn't more Open Source projects be worried about IP issues that a contributor agreement seeks to prevent?
Thanks!