Javascript, over the years, has become much sought after, having given rise to a whole universe of frameworks with which the Internet today seems not to survive.
Brendan Eich was the creator of the Javascript language in 1995, later the founder of the Mozilla universe, which a few versions ago, in its product Firefox version 23 removed the option to turn off Javascript.
Given that the Mozilla people is a reference in relation to the Internet, use and productivity under it, and given the fact that they have removed the option to turn off Javascript, I would say yes, that personal support (users) without Javascript will end!
Javascript, an option ?
The web does not run without HTML, but any other multimedia content or language on the client side has always been optional: Javascript, CSS, Images, Video, etc.
The point is that nowadays, with the demand of the target audience constantly increasing, with all the demand for dynamism and real-time operations, the constant attempt to "abolish" the boring of page-refresh, it becomes difficult for any professional in the field to satisfy the current market without Javascript.
Not even CSS 2.1 is good for most jobs, so imagine a page without CSS!
The same goes for Javascript:
- Real time data validations;
- Visual effects;
- Timers;
- Dynamic content;
- Additional layers of protection in applications;
And many other practical applications that make Javascript indispensable in modern times, make it no longer an option but a necessity.
This is an acquired fact under which browser providers work to improve and tend, like Mozilla, to evolve rather than stagnate.
Javascript, have a future ?
Who remembers having work in Flash knows that change is inevitable and that from today to tomorrow there is something new, improved that replaces what we are used to.
Flash was a fashion, for years the sites were developed in flash, the Flash itself grew, was improved and became the indispensable tool. Today, HTML5 does what Flash did more simply, more effectively and with fewer compatibility issues and without requiring plugins.
Javascript will reach the stage where the Flash is today, dead in the water! For now, it is a language full of life and future, but with HTML5 and CSS3, much of the need for Javascript has disappeared, at some point it will also disappear.
Ex.:
Check if a given field in a form is empty:
<form name="meuFormulario" method="post">
Pergunta: <input name="question" />
<br />
<input onclick="return IsEmpty();" type="submit" value="Adicionar Pergunta" />
</form>
Javascript
function IsEmpty(){
if(document.forms['meuFormulario'].question.value == "")
{
alert("vazio");
return false;
}
return true;
}
HTML5
Just add the attribute required
to our field, and the navigator takes care of the rest!
The technique is based on a simple principle, create something solid and functional, and then apply a whole layer of extra features that may or may not be used, if the necessary support for them is available.
None of the above paragraph checks on most websites or online platforms today. All you’re looking for is to do it right, fast and modern because half a year from now it’s to erase and do something new!
- Browsers advance from version to version so fast that when I do an update I already go 3 or 4 versions ago;
- Technologies change in such a way that the best solution we have today, a month from now is a "crime" use.
- I do a job today, half a year from now the client wants something new, totally different.
But what is more important: Go forward or waste an infinite amount of time ensuring that a small minority who insists on not moving forward can see what the others who have moved forward are seeing?
that is to say
Work with current technology, among which Javascript or continue to waste an infinite time for garântir who uses Internet Explorer 7 with Javascript off will be able to use Sopt ?
I would say yes, that personal support (users) without Javascript will end!
I have an opinion that many people will not like, but I think at least 70% of sites that do not work without JS are programmer incompetence (today many of the sites I have seen are made by teams of kids, and I say this with the utmost tranquility, donate to anyone who hurts). Graceful Degradation and mainly Progressive Enhancement are two concepts that are already put into practice by a number of good developers, and guarantee access to information by a much wider range of devices. Public service sites such as.br registration, for example, should bear this in mind.
– Bacco
http://answall.com/q/30238/101
– Maniero
Addendum: for some of Sopt it must be hard to believe it, but there are people who do not live centered on the PC, or do not even have conditions to (or simply should not need) change the old PC (does not need to be so old, an Athlon of 3Ghz already has difficulties for not having SSE) and there’s no way to use new browsers. It’s okay that some fool can say that "those poor people who won’t buy my product, then I don’t care", but we have common sense. Others can no longer do anything that is not ready in the fashion framework that depend on JS, and so the thing is going in this direction.
– Bacco
I didn’t know about the concepts of Graceful Degradation and Progressive Enhancement, will definitely be things I will remember when layout a site. Thanks for the feedback, I’ve been doing a search and found a tag called
<noscript>
you may already know. I will try to give maximum support to all users, so it is less an incompetent programmer :]– Rafael Almeida
It has a very interesting site, which shows that we have yes that we worry first with the content, then with the "strings", which do not add much value to the user (yes, CSS and Javascript add value, but the content always wins): http://sighjavascript.tumblr.com/.
– danguilherme
@Bacco all good? I’m a partner in a small company, and I’ll give a slightly different view. I love Graceful Gradation. Hell, I want my websites to work on my Nintendo 2ds. But in the meantime, especially here in brazil, this is expensive. Okay, everything here is expensive. But any more component that we use on the site, requires a little more investment. And if I want to pay someone the fair amount (that is, pay my UX a value really UX, and not a nephew/stable for 34h of freelance..) It does not. We have to take some things out. Support is one of them...
– Malavos
@Malavos think we are talking about different things (I may not have understood it right, of course). I talked about who programs the components, but the scenario you described sounds more like reuse of frameworks. Surely if the person will use what is ready in the market, remake is expensive. But if it is you (or your team) that program, I see no reason not to do something more complete from the beginning, because it takes work once, but you reuse (if you modulate, of course). But I recognize that you have more than one type of target audience, and of course each one has to focus on what works for you.
– Bacco
@Malavos trying to simplify: in my experience, a lot can be done without additional work, just having a minimum of worry. Cases where you really need to do something complex to meet old Vices I’d say that’s the exception. I know that if you want to make everything compatible with everything, it is an endless task, but there is a "middle ground" that the staff does not achieve by excessive convenience. For example, why a google maps on the site without JS gets precarious, but that doesn’t mean you can’t leave the rest of the site navigable with anchors instead of JS (mere example);
– Bacco
@Malavos qq time of these take a look at network chat, Then you can tell us more about these experiences and suddenly we can elaborate more on the subject
– Bacco