As far as formatting goes, I believe in letting each developer do it however they like. Things like braces on the same line, or on the next line just don't matter that much in a world of automatic code formatting utilities.
I just wish there was a way to view code in your preferred style, but not actually modify it.
That's the whole point of today's announcement. They've removed the restrictions.
You can make swf-creation tools. You can make swf-playback tools (this was what wasn't allowed before) And you can make swf related stuff not even thought of yet.
Just like C/C++ it's completely possible to write an AIR application to performs malicious actions. Just like C/C++ is't possible to exploit an AIR app that someone else has written. Just like C/C++ apps you have to download and install an AIR app. Unlike a C/C++ app, the app must be signed, and you're warned on the installation dialog that the app can access your files.
For those of you who don't drink the Adobe kool-aid, a quick explanation.
AIR is a desktop runtime environment. You can run either Html/Javascript or Flash based applications inside it. AIR provides a few interesting features beyond HTML/Flash including:
1) File I/O 2) SQLLite Support 3) An integrated web browser (based on WebKit) that you can use inside applications. 4) A fairly good distribution mechanism 5) Desktop integration (OSX Dock icons, Win32 systray support, etc.)
It's a great technology if you're using Adobe products to make web applications and you want to branch into making desktop apps.
It's a great technology if you want to make a desktop app that may later become a web app and you want to share most of the code.
It's a horrible technology if you're a desktop developer who's looking for a different technology.
It's way more write-once run-anywhere than Java ever was.
It does not pick up the system's native UI widgets.
I didn't think there was a version of silverlight for mobile devices? Perhaps I just missed it.
And the deal is for FlashLite, which supports a crappy / old set of API's and is only of use to people developing specifically for it. Getting the real flash player on phones would be a whole lot more useful, but it ain't the best performing application in embedded systems.
I'm confused by the $1 per watt and "cheaper than coal"...
Please correct me if I'm wrong here, but I thought a watt was a measure of capacity whereas a watt-hour was what we actually paid for from our electric company as a measure of (what? power? energy?)... So a watt-hour is something like "continuously using one watt for one hour".
For solar, there's no fuel cost. So the $1 gets you a "perpetual" 1 watt. If it lasted forever (which it won't), that'd be an infinite amount of watt-hours.
But coal plants have a fuel cost. So $1 only gets them so much coal, and only so many watt-hours.
Or is that comparing the cost of building a coal plant to building solar panels? Or is it some kind of TCO figure?
I think the main problem is we can't really come up with an open source scheduling system that's compelely new and innovative because you need compatibility with people outside your organization.
If we're not coming up with something new and innovative we're stuck making outlook clones. People don't like writing software like that.
In general, the company I work for goes from end of development to GM in about a month, for boxed CD software that ain't bad. That assumes QA has been testing right through development. But it's going to vary widely based on the industry and size of the product.
Essentially it comes down to choosing a smart policy and sticking with it. If your company's policy is "Spend 2 weeks QA on every release." and you don't spend that two weeks, expect that release to suck.
It's the first console game my wife has ever actually enjoyed.
I think it's the combination of being pretty and the fact that it's a very easy & fun game to play. The death penalty is minor and it's fairly easy to kill the enemies.
Don't just give up without asking them to change it. Many times these things are boilerplate contracts that some lawyer in isolation from the real-world business constraints dreamed up. That lawyer put everything he could possible imagine in there to cover his ass.
If the company risks losing a valuable employee, they'll likely consider changing it for you.
Slashdot Mirror
Who cares about tabletop fusion?
I want my "Mr. Fusion" that I can slap into my car!
As far as formatting goes, I believe in letting each developer do it however they like. Things like braces on the same line, or on the next line just don't matter that much in a world of automatic code formatting utilities.
I just wish there was a way to view code in your preferred style, but not actually modify it.
And yet Obama & Clinton aren't for telcom immunity.
hmmm....
Last I knew, Gnash didn't have any AVM2 support, so nothing taking advantage of the latest API's would work.
That's the whole point of today's announcement. They've removed the restrictions.
You can make swf-creation tools.
You can make swf-playback tools (this was what wasn't allowed before)
And you can make swf related stuff not even thought of yet.
Just like C/C++ it's completely possible to write an AIR application to performs malicious actions.
Just like C/C++ is't possible to exploit an AIR app that someone else has written.
Just like C/C++ apps you have to download and install an AIR app.
Unlike a C/C++ app, the app must be signed, and you're warned on the installation dialog that the app can access your files.
What type of review would make you happy?
Free in cost, yes.
SDK, and runtime distribution both are free.
Some (not all) parts of the SDK are also Free as in Open Source.
For those of you who don't drink the Adobe kool-aid, a quick explanation.
AIR is a desktop runtime environment. You can run either Html/Javascript or Flash based applications inside it. AIR provides a few interesting features beyond HTML/Flash including:
1) File I/O
2) SQLLite Support
3) An integrated web browser (based on WebKit) that you can use inside applications.
4) A fairly good distribution mechanism
5) Desktop integration (OSX Dock icons, Win32 systray support, etc.)
It's a great technology if you're using Adobe products to make web applications and you want to branch into making desktop apps.
It's a great technology if you want to make a desktop app that may later become a web app and you want to share most of the code.
It's a horrible technology if you're a desktop developer who's looking for a different technology.
It's way more write-once run-anywhere than Java ever was.
It does not pick up the system's native UI widgets.
I've worked at two companies where hard drives were removed from computers before they were sent out for recycling.
Then the company would physically destroy the drives... the low-budget company was a lot more fun then having them professionally destroyed.
I've heard that the military calls this "Spiking" a drive as they drive a railroad spike through the platters. But who knows if that's true or not.
I didn't think there was a version of silverlight for mobile devices? Perhaps I just missed it.
And the deal is for FlashLite, which supports a crappy / old set of API's and is only of use to people developing specifically for it. Getting the real flash player on phones would be a whole lot more useful, but it ain't the best performing application in embedded systems.
It only did send them to Gmail :)
200KW = 200000 Watts = $200000
I'm confused by the $1 per watt and "cheaper than coal"...
Please correct me if I'm wrong here, but I thought a watt was a measure of capacity whereas a watt-hour was what we actually paid for from our electric company as a measure of (what? power? energy?)... So a watt-hour is something like "continuously using one watt for one hour".
For solar, there's no fuel cost. So the $1 gets you a "perpetual" 1 watt. If it lasted forever (which it won't), that'd be an infinite amount of watt-hours.
But coal plants have a fuel cost. So $1 only gets them so much coal, and only so many watt-hours.
Or is that comparing the cost of building a coal plant to building solar panels? Or is it some kind of TCO figure?
The poor principal is getting a $$$$ internet bill next month for posting that on his site.
I approve of the new story icon :)
Honestly, is any "XXXXX caught modifying wikipedia" article really newsworthy nowadays?
Wikipedia is editable by anyone.
It's human nature to want to modify bad news about yourself or your business.
yeah yeah, horrible thing nobody should do that.
But it's neat, how does it work?
Remember to write your congressmen.
Both in opposition to this bill and to state you general feelings that copyright law has become too broad and too far in favor of big media companies.
Do it now, email is good, paper is better.
I'll happily not scan your DNA for $999, please send check or money order to...
I think the main problem is we can't really come up with an open source scheduling system that's compelely new and innovative because you need compatibility with people outside your organization.
If we're not coming up with something new and innovative we're stuck making outlook clones. People don't like writing software like that.
Yeah, must be working. I got an article about male enhancement...
I think the biggest problem with Vista is there is no compelling reason to upgrade for business users.
It's prettier. But that's about it.
In general, the company I work for goes from end of development to GM in about a month, for boxed CD software that ain't bad. That assumes QA has been testing right through development. But it's going to vary widely based on the industry and size of the product.
I blogged about the opposite issue this morning.
http://www.rogue-development.com/blog/2007/11/i-love-my-job.html
Essentially it comes down to choosing a smart policy and sticking with it. If your company's policy is "Spend 2 weeks QA on every release." and you don't spend that two weeks, expect that release to suck.
It's the first console game my wife has ever actually enjoyed.
I think it's the combination of being pretty and the fact that it's a very easy & fun game to play. The death penalty is minor and it's fairly easy to kill the enemies.
Don't just give up without asking them to change it. Many times these things are boilerplate contracts that some lawyer in isolation from the real-world business constraints dreamed up. That lawyer put everything he could possible imagine in there to cover his ass.
If the company risks losing a valuable employee, they'll likely consider changing it for you.