Which tools are out there (open source and as easy to use as Selenium IDE)?
2,750 karma · joined February 2, 2011
Which tools are out there (open source and as easy to use as Selenium IDE)?
I think it would be much better for the web if browsers had a sane API for extending behaviors of any tag via attributes. This would make things easily composable and eliminate most problems of traditional component-based systems.
<button does-stuff does-more-stuff></button>
It would be even better if people working on these specs spent some time reading research papers on how a sane component-based system could work. For example: http://alumni.media.mit.edu/~mt/thesis/mt-thesis-Contents.ht... A lot of interesting ideas regarding extensible behaviors and ease of understanding.Edit: And yes, I'm aware of is="" functionality. It's not exactly what I'm talking about. In fact, if the specs were designed the way I mentioned, there would be no need for making anything special for built-in elements as opposed to the new ones.
I think a much better approach to this pronblem would be a compression format that's designed specifically for JavaScript. It could still be negotiable, like GZIP, so anyone wanting to see the source would be able to see it. It could also be designed in a way that allows direct parsing without (full?) decompression.
https://www.youtube.com/watch?v=G8X-yvDWClc
The ideas were great, but it all went horribly wrong with C++ and never fully recovered. Modern OOP has few benefits of the original vision, while introducing a lot of pitfalls that need to be constantly avoided.
The whole Web 2.0 movement vilified editor, but I think this was a great disservice to the Web. I'd love to have a website like I described above for programming stuff. It would allow me to concentrate on content, rather than maintenance of my own website and constant self-promotion.
I also believe that researches have responsibility to outline the limits of their own algorithms in research papers. (For example, presenting examples that aren't recognized or data sets on which the approach doesn't work at all.) That is valuable information and they almost certainly have it at the time of publication.
No centralized framework. Everything is decomposed into "behaviors" that have no direct dependencies. Attributes are used for configuration and storing the running "state" of all libraries. Liberal use of CSS selectors as a kind of query language to remove the need for tree-traversal code.
The interesting thing about this approach is that it enables libraries/behaviors to interact and effectively "compose" at run-time without any direct code dependencies. It has some similarities to the idea of agent-oriented programming, which I think is a powerful idea worth a deeper look.
Of course, this is more of a proof-of-concept than a complete set of libraries needed for a complex website. However, I find this "behavioral" approach very enjoyable to use, because it makes development very immediate and incremental. Add an attribute, observe that it works, add another attribute, observe that it works, etc.
You also get progressive enhancement "by default".
The biggest thing that's dragging Surface down is its UI. Neither classic Windows apps, nor Metro apps are very pleasant to use on the given hardware.
I wonder what Alan Kay thinks of Surfaces compared to iPads.
https://www.youtube.com/watch?v=ZDM33CMJvp8
https://www.youtube.com/watch?v=DIR6Rmhm3To
(I'm trying to watch all of his recent talks. Despite [or because of?] being critical of the industry, they are some of the most inspiring videos I've seen in years.)
https://www.youtube.com/watch?v=-pb3z2w9gDg&list=PLUl4u3cNGP...
https://www.youtube.com/watch?v=O1oJzUSlTeY
Obviously, it's not entirely equivalent to what's described in the article, but the point still stands.
You might counter that this is the domain of MIT Media Lab rather than Microsoft and Google, but at this stage new UI concepts have to be adopted by entities with significant influence to be adopted at all.
https://youtu.be/275FQ9koAw8?t=7647
Very interesting view, especially considering how long ago that was and how relevant they still are.
1. Read the code and think about what it's really doing.
2. If that leads nowhere, write (more?) unit/integration tests.
3. Only if the above two fail, run the debugger.
"Contemplating" code has another benefit: since you're looking at the whole picture rather than jumping line-by-line it develops your intuition about why things fail.
This isn't true. The biggest cause of spaghetti code in "traditional" JS is due to having multiple conflicting sources of truth for the same pieces of state information (usually split between JS variables and DOM) and subsequent multi-directional synchronization.
Having a model that drives all DOM is one way to solve this. However, having "canonical" representation of your state in DOM works as well.
That said, I wonder what's Discord's official stance on such things. Their bread and butter is voice chat, and they seem to be fairly open minded. Maybe they will eventually provide a public API for basic text messages.
For example: https://www.youtube.com/watch?v=gTAghAJcO1o
Excellent video. I highly recommend everyone working in or with IT to see it.
I think he is right.
PCs and smartphone are mostly recreating thing from the past, and not the best things either. However, this isn't because we invented everything there is to invent. It has more to do with how research in computing is currently funded and how companies approach invention and innovation.