Why do organizations target specific versions of browsers - I really don't understand why its so hard for people to write cross-browser web applications - I do it every day at my job..
It sounds more like you're used to what you're used to and don't want to change. Meanwhile thoose "overexcited college grads" don't want to be weighed down by the 20 years of trash thats part of the PHP code base... I'm a PHP dev now, and was a rails dev for 5 years - I'll take ruby/rails any day.
I've spent alot of time writing code in Ruby/Rails... I've now been a PHP dev for 2 years and have used alot of what I learned in rails and applied it to PHP..
I don't see why you'd prefer php language constructs over Ruby - they are more tedious in every way right down to having to write "array" in front of every array.. (thank heavens they finally changed the latest version)
@array.map! {|x| x**2 } is much easier to read/understand than using the equivlent array_map function in php.. (Or for that matter using foreach or classic index-based for loop)
PHP's biggest problem - to me - is the lack of a FastCGI-style environment where code is already running and requests are just fed to the running daemon.. For this reason, its always going to be slower than other languages.... APC is an attempt to do this but its not very mature yet and still requires byte code to be interpreted on each request. Facebook wrote a PHP->C++ translator and that should say alot about the state of the language...
Windows 8 will be just as relevant to the business market as they ever were once you disable the terrible new UI, and that's all that matters anyway (whether businesses choose to skip Windows 8 in favor of waiting for the next iteration is another possibility, but unrelated to all the tablet nonsense).
Atleast in the consumer preview, there is no way to disable metro, there is no start menu to fallback to..
Depends on the prescription.. If you're taking a controlled substance - like Ritalin, the current (dumb) setup is you are supposed to physically go to the dr. and pick up a prescription that has to be hand signed and then bring that to the pharmacy. no refills allowed..
Its really annoying and a waste of time - nor do I see how this manual process is really any better than phoning it in...
Computer Science departments (atleast the one I went to) don't teach "Cisco Networking".. they teach "Networking"... They don't teach "Windows", they teach "Operating Systems".. You might get an intro to programming in $language, but they'll choose any language for any particular course and figure you'll figure it out..
If you're bright enough to do well in competent CS program, you can pick of the specifics of $solution you happen to be working on and you'll have an edge on keeping up in the long term versus those MIS kids..
I wish ActiveX was dead, but sadly it is not, at least not yet. There are too many sites and applications that use it, making it impossible to switch browsers for this reason.
Its not a matter of if, its a matter of when they rewrite those apps to run on modern web standards...
I seriously hope CIOs don't think that 5, 7 years from now - they can keep their entire company on IE6 just because of some ancient internal infrastructure...
IE6/8 -> IE8 is a headache because in IE8 they finally fixed the box model.... IE8, IE9, Firefox, Chrome, Safari all pretty much render everything the same with only a few differences....
I'm a software engineer for a medium sized internet site and I routinely ensure that the application works in and looks correct in all browser, and it doesn't take that much extra time if you know what you're doing in the first place....
Telnet is wide open to a MITM attack - besides just sniffing the password, suppose you have a shell open - then a MITM hijacking your TCP session could write an arbitrary rlogin file.
My professor for the computer security class at my college demoed this exact scenario - its not a safe protocol.
So at what point can programmers make a change then? Never? Things change.. In the case of windows 7, they finally got search right, which obsoleted the menu system.
I'm sure there were people complaining back in the day too when their company got rid of their dumb terminal and shell interfaces for the mainframe because some fulfillment person was used to that system. We can't stay like that forever.. Change happens, users need to accept it. Developers and designers otoh need to make the process as careful as possible.
One place the Apple really accels is thinking over a UI extremely thoroughly when they design it and then they stick with it... Theres not as much churn because they get it right the first time.. IPhone's interface has been relatively static since the beginning...
You do realize that OSX has had command + spacebar, type first few letters thing for a while now?
Re:No, that's what you get for using a dying langu
on
GitHub Hacked
·
· Score: 1
So if he just told the model that this is a protected attribute, he would have been fine...
Its not hard to do this and its a bug like any other bug, not some systematic problem with Rails itself.
Re:No, that's what you get for using a dying langu
on
GitHub Hacked
·
· Score: 4, Insightful
This isn't actually a hole in rails.. If you use mass assignment, you need to protect attributes you don't want assigned with attr_protected on your model.
Slashdot Mirror
Riight..
Because looking at code littered with var e = document.getElementById('stuff'); is just so much more elegant and non-shit-looking than $('#stuff')..
Why do organizations target specific versions of browsers - I really don't understand why its so hard for people to write cross-browser web applications - I do it every day at my job..
It's not like anyone will want to buy that franken-ui anyways...
2. Ruby: You go to war with the webserver they give you, not the one you want.
Huh? WebBrick is really only meant for development use.. You can hook any web server up to rails easily. For apache, just gem install passenger...
It sounds more like you're used to what you're used to and don't want to change. Meanwhile thoose "overexcited college grads" don't want to be weighed down by the 20 years of trash thats part of the PHP code base... I'm a PHP dev now, and was a rails dev for 5 years - I'll take ruby/rails any day.
There ya go, fine tune passenger to your hearts content...
I've spent alot of time writing code in Ruby/Rails... I've now been a PHP dev for 2 years and have used alot of what I learned in rails and applied it to PHP..
I don't see why you'd prefer php language constructs over Ruby - they are more tedious in every way right down to having to write "array" in front of every array.. (thank heavens they finally changed the latest version)
@array.map! {|x| x**2 } is much easier to read/understand than using the equivlent array_map function in php.. (Or for that matter using foreach or classic index-based for loop)
PHP's biggest problem - to me - is the lack of a FastCGI-style environment where code is already running and requests are just fed to the running daemon.. For this reason, its always going to be slower than other languages.... APC is an attempt to do this but its not very mature yet and still requires byte code to be interpreted on each request. Facebook wrote a PHP->C++ translator and that should say alot about the state of the language...
IE9+ is pretty much standards compliant out of the box and requires little to no effort to support over chrome, FF, etc...
IE8 got us about half way there..
IE7 uses the broken box model and, ergo, a pain in the ass..
Windows 8 will be just as relevant to the business market as they ever were once you disable the terrible new UI, and that's all that matters anyway (whether businesses choose to skip Windows 8 in favor of waiting for the next iteration is another possibility, but unrelated to all the tablet nonsense).
Atleast in the consumer preview, there is no way to disable metro, there is no start menu to fallback to..
IE7 still uses the broken box model... IE8+ is pretty easy.. IE9+ pretty much just works...
Depends on the prescription.. If you're taking a controlled substance - like Ritalin, the current (dumb) setup is you are supposed to physically go to the dr. and pick up a prescription that has to be hand signed and then bring that to the pharmacy. no refills allowed..
Its really annoying and a waste of time - nor do I see how this manual process is really any better than phoning it in...
My CS department did everything with Linux/Unix, C, C++, Java....
What are these licensing fees you speak of?
Yes.
Fundamentally, networking and the related algorithms are very much within the domain computer science.....
More like "Spotlight" in OSX which really was a clone of QuickSilver...
Computer Science departments (atleast the one I went to) don't teach "Cisco Networking".. they teach "Networking"... They don't teach "Windows", they teach "Operating Systems".. You might get an intro to programming in $language, but they'll choose any language for any particular course and figure you'll figure it out..
If you're bright enough to do well in competent CS program, you can pick of the specifics of $solution you happen to be working on and you'll have an edge on keeping up in the long term versus those MIS kids..
I wish ActiveX was dead, but sadly it is not, at least not yet. There are too many sites and applications that use it, making it impossible to switch browsers for this reason.
Its not a matter of if, its a matter of when they rewrite those apps to run on modern web standards...
I seriously hope CIOs don't think that 5, 7 years from now - they can keep their entire company on IE6 just because of some ancient internal infrastructure...
You'd think they'd be more concerned about all the murder in games over the gay flings...
Last I checked God was pretty down on murder...
You're out of touch with reality - ActiveX is a dead technology and people will migrate away from it, not the other way around.
IE6/8 -> IE8 is a headache because in IE8 they finally fixed the box model.... IE8, IE9, Firefox, Chrome, Safari all pretty much render everything the same with only a few differences....
I'm a software engineer for a medium sized internet site and I routinely ensure that the application works in and looks correct in all browser, and it doesn't take that much extra time if you know what you're doing in the first place....
Telnet is wide open to a MITM attack - besides just sniffing the password, suppose you have a shell open - then a MITM hijacking your TCP session could write an arbitrary rlogin file.
My professor for the computer security class at my college demoed this exact scenario - its not a safe protocol.
You're missing the point - regardless of who does the design, things will change over time and you can't expect constant.
So at what point can programmers make a change then? Never? Things change.. In the case of windows 7, they finally got search right, which obsoleted the menu system.
I'm sure there were people complaining back in the day too when their company got rid of their dumb terminal and shell interfaces for the mainframe because some fulfillment person was used to that system. We can't stay like that forever.. Change happens, users need to accept it. Developers and designers otoh need to make the process as careful as possible.
One place the Apple really accels is thinking over a UI extremely thoroughly when they design it and then they stick with it... Theres not as much churn because they get it right the first time.. IPhone's interface has been relatively static since the beginning...
You do realize that OSX has had command + spacebar, type first few letters thing for a while now?
So if he just told the model that this is a protected attribute, he would have been fine... Its not hard to do this and its a bug like any other bug, not some systematic problem with Rails itself.
This isn't actually a hole in rails.. If you use mass assignment, you need to protect attributes you don't want assigned with attr_protected on your model.
:password => 'hacked'})
:password
If you don't want people to do this:
@user.update_attributes({:favorite_color => 'blue',
You need to do this:
class User < ActiveRecord::Base
attr_protected
end