What type of applications are you intending on writing?
For something like 3d games, you'll have to decide on a platform. If you're doing something that can be rendered in a browser but still requires hardware access, you might want to take a look at the opensource PhoneGap project. That way you can write in a somewhat cross platform way and target both android and iphone devices.
I've also more often than not seen the exact opposite: Some crappy security consultants decide to do a security audit on software and network infrastructure and comes up with incorrect data or lies. I've seen auditors tell people that they have insecure access points when the access points belong to a nearby building. I've seen auditors call md5 hashes in a database clear text passwords.
Software developers have a right to be somewhat skeptical of security auditors in general. But they should also be grateful when a exploit is found so they can patch it before someone else uses it.
Asking for support is not the same as conversing with a developers about lacking features or design decisions. A good chunk of the questions I see on freenode are things addressed clearly on the the project's FAQ of their website or in documentation.
You can't expect instantaneous free support on a free project.
Engage in constructive criticism and hang around long enough to get a response. Some people are way too uptight and impatient.
Are you implying that most of developers can't handle being criticized?
Who are the ones that can't? I spend a bit of time of freenode with other developers of many different open source projects. If I go into a channel and ask why some feature works a certain way or why something is missing or broken, I generally get a response that they could use help in fixing the issue.
Another example is all the movies lately being filmed by some hack with a camcorder. The shaky video is more "gritty" and "edgy" and "dark"...riiiiiiiiight.
Because in IE 6 and below XMLHttprequest is an activeX object, while in other browsers like firefox and safari it's a javascript object. Javascript objects become part of the DOM.
This is not a Javascript problem, it's a DOM incompatibility problem. Changing the language does nothing to solve this.
And it's the reason that things like dojo and other javascript toolkits are picking up so much steam. They hide the DOM, event, and rendering differences under consistent APIs. No reason to code for browser differences when simple API calls can do it for you.
RHEL was around a couple of years before the redhat desktop and fedora split. The redhat desktop had a faster release schedule than RHEL since RHEL's inception.
Half an hour? You're exaggerating. Freshrpms, atrpms, and livna all have had an rpm on their site you could add to yum by simply clicking on the rpm link for several versions now.
And how exactly is synaptic better than yumex (yum extender) ?
Yeah, but I payed over 50 bucks because we were told there would be a Linux client.
There's a port actually done but we can't have it for some reason.
So I have an expensive box with a year of dust on it sitting on my shelf. Maybe it's not a great game, but I'd like to be the judge of that myself. I really enjoyed UT 99 and UT 2004 on Linux.
This isn't javascript connecting to a remote database. This is javascript talking to the local database built into HTML5 for local storage. No worse than making elaborate cookies unless the database for some reason is capable or executing things outside of its sandbox.
It was not clear at all. It looked like they logged in to paymo and started messing with javascript on the page. Anyone could do that with firebug and hose their own account if they wanted.
Where was code being executed from another site to cause problems with someone else's account?
Did the article have a problem with loading potentially harmful javascript code from google's server?
That's not entirely correct. Loki's business model was different.
Loki would pay game companies to license each copy of the game and then port and sell the linux versions. They made bad business decisions like buying way too many licenses of certain games.
Loki would probably be in trouble still even if Linux was as popular then as it is now.
Slashdot Mirror
Not the same thing at all. That site requires java. These sierra games are done using javascript and layered PNG images.
That's my point.
The original poster asked it IBM would continue to contribute.
Like I said, it has no choice.
It has no choice. It has vast amounts of code dependent on java.
Think they'll just rely on Oracle putting a JVM on AIX for websphere to run on?
"No one is interested in whether the software is open source"
Of course not, but people do like free things. I'm hoping that the more Android devices come out, the bigger the market of free apps will get.
What type of applications are you intending on writing?
For something like 3d games, you'll have to decide on a platform. If you're doing something that can be rendered in a browser but still requires hardware access, you might want to take a look at the opensource PhoneGap project. That way you can write in a somewhat cross platform way and target both android and iphone devices.
Yes, it is a good idea.
This would be nicer than a laptop for reading in bed.
I really enjoy having a g1 phone, but I only put up with a 3 inch screen when I'm not near a full sized computer.
I've seen this and it's usually pretty funny.
I've also more often than not seen the exact opposite:
Some crappy security consultants decide to do a security audit on software and network infrastructure and comes up with incorrect data or lies.
I've seen auditors tell people that they have insecure access points when the access points belong to a nearby building. I've seen auditors call md5 hashes in a database clear text passwords.
Software developers have a right to be somewhat skeptical of security auditors in general. But they should also be grateful when a exploit is found so they can patch it before someone else uses it.
Asking for support is not the same as conversing with a developers about lacking features or design decisions.
A good chunk of the questions I see on freenode are things addressed clearly on the the project's FAQ of their website or in documentation.
You can't expect instantaneous free support on a free project.
Engage in constructive criticism and hang around long enough to get a response.
Some people are way too uptight and impatient.
How many times did they have to state publicly that it lacked the features of 3.x? There's no history of ignoring user feedback.
KDE 4.0 was a huge architecture change for a better base product. They've been adding back functionality each point release.
Are you implying that most of developers can't handle being criticized?
Who are the ones that can't? I spend a bit of time of freenode with other developers of many different open source projects. If I go into a channel and ask why some feature works a certain way or why something is missing or broken, I generally get a response that they could use help in fixing the issue.
IBM still has a competing JVM, though it is only at the 1.5 spec. It is what webshpere 6.1 runs on.
Great post. As true as it gets.
Another example is all the movies lately being filmed by some hack with a camcorder. The shaky video is more "gritty" and "edgy" and "dark"...riiiiiiiiight.
Because in IE 6 and below XMLHttprequest is an activeX object, while in other browsers like firefox and safari it's a javascript object.
Javascript objects become part of the DOM.
This is not a Javascript problem, it's a DOM incompatibility problem. Changing the language does nothing to solve this.
Exactly.
And it's the reason that things like dojo and other javascript toolkits are picking up so much steam. They hide the DOM, event, and rendering differences under consistent APIs. No reason to code for browser differences when simple API calls can do it for you.
Chrome and Android's browser both use webkit for rendering, but they are different browsers.
For example, Android's browser is not able to render SVGs.
sorta.
RHEL was around a couple of years before the redhat desktop and fedora split. The redhat desktop had a faster release schedule than RHEL since RHEL's inception.
Half an hour? You're exaggerating. Freshrpms, atrpms, and livna all have had an rpm on their site you could add to yum by simply clicking on the rpm link for several versions now.
And how exactly is synaptic better than yumex (yum extender) ?
Yeah, but I payed over 50 bucks because we were told there would be a Linux client.
There's a port actually done but we can't have it for some reason.
So I have an expensive box with a year of dust on it sitting on my shelf. Maybe it's not a great game, but I'd like to be the judge of that myself. I really enjoyed UT 99 and UT 2004 on Linux.
Sure, someone else's javascript can do that marvy new thing if you're dumb enough to include their javascript in your page.
This isn't javascript connecting to a remote database. This is javascript talking to the local database built into HTML5 for local storage. No worse than making elaborate cookies unless the database for some reason is capable or executing things outside of its sandbox.
It was not clear at all. It looked like they logged in to paymo and started messing with javascript on the page. Anyone could do that with firebug and hose their own account if they wanted.
Where was code being executed from another site to cause problems with someone else's account?
Did the article have a problem with loading potentially harmful javascript code from google's server?
For the little micro PCs that have this crap embedded instead of a PCIe or AGP slot.
That's not entirely correct.
Loki's business model was different.
Loki would pay game companies to license each copy of the game and then port and sell the linux versions. They made bad business decisions like buying way too many licenses of certain games.
Loki would probably be in trouble still even if Linux was as popular then as it is now.
"...that has access to lots of resources in the component that runs eval."
By lots of resources do you mean the cookies for the domain that loaded the page? That's bad, but what else does it have?
"Given that you'd already be writing a parser, it would then make no sense to use eval."
The eval is going to be much more efficient than parsing creating the objects though javascript.
But when you know what you're doing, it's a great tool.