2,750 karma · joined February 2, 2011
I think the true way forward is in replacing community colleges with certificates from online courses (with some in-person labs, probably). It's cheaper and would make for better quality of education.
Hm, people with 6-digit salaries and doctoral degrees whose main job is to figure out diseases perform worse than some random dude? That's the first thing that comes to my mind.
Yeah, so let's host everything in the world on the servers of a single company. What could possibly go wrong?
Now that you have mentioned it, inventors and technology are treated in a similar fashion. Not sure why. Maybe because historic biographies adopt their methodology from general history where kings and generals are simply dots in a larger picture that does try to describe the society of the time?
Any 2d image is an optical illusion, so it makes no sense to criticize human image recognition based on it being 'fooled' by illusions. The real criteria for whether image recognition works well or not is altogether different.
-
I'm willing to bet that in late 70s many people also thought that rule-based systems could lead to real AI if they were "more complex" and had more computing power available.
Meanwhile, people debugged binaries for several decades before your language even been developed.
Do you see anything wrong with this picture?
<form action="/something" submit-to="#x, #y"></form>
<div id="x" />
<div id="y" />
Normally, the only thing I need to add to go from non-AJAX to AJAX is submit-to="[CSS Selector Here]". Possibly, some IDs. Everything else works automatically. The library adds a certain attribute to the "pasted" parts, so I can add visual transitions via CSS3. I can use form's action URL to rewrite current URL via push state.People often smirk when I mention progressive enhancement these days. But the same people often claim that something is "impossible" to do using PE, while it's not only possible, but downwright easy. This makes me think most of them never even tried this approach seriously.
My overall strategy is creating some crude "date model" of the application in pure HTML, then identifying additional behaviors I need to make it look/work the way I really want to. I implement each behavior as separate JS libraries. The libraries are configured by adding additional directives to my markup, so using and re-using them requires no coding per se.
You would be surprised how much you can accomplish this way. Moreover, it forces you to write highly reusable components that are easy to reuse.
CSS3 is a great help in this regard, because (in most cases) you do not have to specify look-and-feel of anything in the library itself. You can simply generate some additional markup that can be styled separately for every app.
The core language (syntax, available directives) hasn't changed much since the time everyone deservedly hated it. Its performance was optimized, it got many more libraries and it is still the only language supported by browsers. But the question is, why all of this applies to JavaScript and not Python/Ruby/whatever?
A lot of its benefits people claim simply weren't around when they chose to stick with it. It's like saying you chose IIS over Apache because of features of C# 5.0 and ignoring the fact that you chose IIS in 2004, where C# 5.0 was not around. It's a dishonest argument.
Speaking of which. How can people claim that JS benefits from the same language running on client and server when 90% of server-side libraries do not work on the client and there are potentially major differences even in core library (e.g. forEach)?
Also, a huge part of JS ecosystem are kludges, crutches and workarounds that make the stack way, way more complex that it should be. (E.g. source maps. Imagine someone minifying PHP for faster parsing and then asking everyone to use some source mapping technology for debugging. They would be laughed out of any conference or discussion.) This mentality permeates everything. I mean, seriously, require directives need to be implemented as a library? Namespace isolation is a closure-based hack? Can you imaging stuff like that being tolerate for any other language?
It is possible to build extremely dynamic websites that are not SPAs. It is possible to do it in a relatively straightforward fashion. (Using something similar to web components.) So why move?
How are SPAs different from Flash? Sure, you have some remnants of standard HTML there, but with canvas, local storage and JS compilers, those two technologies look remarkably similar both in terms of advantages and problems. You get a blob of non-semantic, imperative code that does non-standard things.
The funny thing is, many of the stated advantages of SPAs can be easily implemented in document-based web apps. A lot of the repetitive info could easily be removed with proper caching, and it would be even more efficient with cacheable client-side includes. Not only it would be roughly as efficient, it would require much less work to implement.
Decentralized work is a bad thing. Instead of Mozilla/W3C solving some problem for everyone, we get every website coming up with their own clever solutions for nearly everything. (Also, thousands of clients re-doing the work that could be done once and served from cache.)
Also, single-page apps increased reliance of the entire web on the handful of CDNs and framework providers.
Because... If you don't believe there is any point to life, what makes you believe there is any point in death? At least with life there is a possibility of change, and capacity to help others who don't share your outlook.
Also, very few companies and no individuals will have the same technical capabilities as Google with it's horde of developers, years of experience in the domain, billions of dollars and ability to control everyone's visitor stream. They shouldn't be the only company that can effectively innovate in this field.
The backend takes the url, gets the HTML source of the website, minifies it, gets rid of the css, javascript, and images, GZIP compresses it, encodes it in Base64, and sends the data as a series of SMS's.
This is yet another interesting idea that will get screwed up in practice because of massive overreliance on JavaScript in modern web development. This is why developers should do progressive enhancement. There are a lot of thing that are possible with declarative markup that are not possible or not safely feasible with imperative code, which generates things on the fly.
I run several non-personal websites. I pay for them because the cost is simply not significant to me. (Getting time to do administrative stuff is much more costly, but that's moistly a matter of bad tooling.) It's not because I'm a billionaire. It's because running a website, even a website with thousands of registered users, is dirt cheap if you it efficiently. When you get to the scale of hundred thousand registered users things begin to get more complicated. But only a fraction of the Web really needs to be that big.
I'd rather have that than the society where everyone silently accepts global surveillance as a norm and treats any kind of self-expression that gets you into trouble as pure stupidity on the part of the speaker (e.g. blames the victim).
What we have right now is a vicious cycle. "Normal" people have no cryptographic capabilities. So they simply adapt their beliefs and behavior to this reality. This makes them think of themselves as different from people who do have cryptographic capabilities. This means they develop "us and them" mentality and can no longer empathize with anyone seeking any level of digital privacy. This means there is no popular support for crypto. So "normal" people have no cryptographic capabilities.
I believe that "consumer cryptography", even if it's weak, would break this cycle.
Widely adapted open-source "bad crypto" can: - Raise user's level of awareness about security. - Create a market that can later be serviced by better crypto. - Encourage creation of infrastructure that can be later used in better crypto. - Encourage investigation of better UI.
Also, other poster are right about increasing the difficulty of executing an attack.
1. Everything is hidden by default. No signifies. That looks less confusing... until you want to find something or something changes and you don't even notice until it's not "there" anymore. It's not clear what will happen when you interact with the UI.
2. Everything is mushed together. I type something and zillion things pop up on the scree. How am I supposed to know what are they and where they come from?
3. No settings in this context sounds like no choice. I don't want every download go to Downloads folder, because it will become a bloated mess in about 3 days. .
The reality is that we don't know how minds really work and we don't have thinking machines. The belief that the limited knowledge about brain chemistry "explains" consciousness is similar to the belief that knowing how semiconductors work "explains" hardware and software engineering.
Edit: Down-votes on an opinion without any explanation in reply simply prove my point. This is a hive-mind belief and opposing world views are not tolerated.