Your response to his rant is lacking in thought IMHO. If we all use a different device then the solution will be to keep our minds in the past. Just as re-writing the source could be performed at the server level to accommodate these nuances, there is no reason that the jQuery library (et al) cannot properly detect and change aspects which would hinder the user experience such as touch vs click inter alia. A small portion of code would be able to test element geometry and subtract for features which would not add to the experience unless specifically wanted by the developer of the site just as browser detection was performed in the past. Until the content is called to be rendered on the device there is really no expectation of it and thus we have to change the way we develop out sites so that the above concepts can be fluidly applied to the rendering environment and provide for the experience we desire on all platforms. :cool:
jfriedman
Posts
-
A rant against jquery and the blogs that use them -
Into the Void: Why void is a bad ideaI think void is a representation anything which is something. The way I see it NULL cannot be void but the void can be NULL if that makes sense...
-
Is Ruby on Rails Suitable for Banking?I think that in the end the users wouldn't and shouldn't know anyway, especially in such a situation.
-
New Library - Manged Media AggregationAcknowledged! Sorry & Thanks!
-
New Library - Manged Media AggregationI don't see any of your comments on the article. I just updated it again with more examples and diagrams. I will post in the Free Tools section next time. Thanks for the input!
-
New Library - Manged Media AggregationDelivering media to clients can be a complex and expensive process. This project's goal is to allow developers to deliver media to clients in less then 10 lines of code utilizing standards complaint protocol implementations. Article currently pending on CodeProject.com (Managed Media Aggregation using Rtsp and Rtp) Homepage -> https://net7mma.codeplex.com/ The size of the compiled code is about 100k and it can be used in both 32 and 64 bit environments. It should not leak memory and should be efficient in the sense you will never lose a source packet which comes in from the source stream and you should never have a backlog of packets. This library also has an implementation of encoding and decoding JPEG over RTP a.k.a RFC2435 Library has an Apache 2 Style License. Enjoy!
-
what are hidden links??