3 ms·
Relevant: "Cool URIs Don't Change": https://www.w3.org/Provider/Style/URI https://www.w3.org/Provider/Style/URI
by webmaven 5y ago
Relevant: "Cool URIs Don't Change": https://www.w3.org/Provider/Style/URI https://www.w3.org/Provider/Style/URI
- martindale 5y agoFirst thing that came to mind as well.
- Cullinet 5y agoI honestly thought that Jakob Nielson earned his keep by having gotten the basics enough mind share to make the situation better than fond memories for turn of the century web designers. Being surrounded by designers at the time, all who became developers soon after, the loss of elementary design and UI knowledge I believe is due to the vacuum left behind when the on ramp to get a Internet job became programmatic instead of visual arts. However possibly the same effect can't happen in the same way again because early in the century coding for the web meant mainly fancy graphics and Flash, nothing related to let alone connected with the plumbing. (ActionSctipt was good enough for a friend who was a novice but desiccated and earnest programmer to write a Flash demo of a insulin regulator device that was so good his simulation from the specifications was used as a reference through to certification of the C and assembly embedded implementation. A ESP8266 for ActionSctipt would be awesome. This guy lost windows for Linux the instant the penny dropped that the greatest most important barrier to this profession, for the majority, is voodoo FUD and a matter of self confidence and reading the right books. This most recent generation doesn't seem to have a equivalent reading culture similar to how we assembled libraries of O'Reilley titles in our offices and homes - everyone who I remember purchased additional titles in fields that they didn't know about, every single time they bought required references something additional got smuggled into patiently awaiting brains. I copied this at my office letting anyone add a extra title every ten references. This almost immediately became a proper budget for a library but suddenly the requests dried up unexpectedly. We realised the attraction was having snuck the expense onto the job budget people took them home to read only afterwards bringing them back into circulation out of unnecessary sensitivity. This is why I passionately hate hermetically sealed corporate systems. Creativity needs inspiration even from a little lisp (or whatever) learning larceny.
- Cullinet 5y agoHTTP/1.1 Status Code Definitions : https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html It has always bugged me, e.g. to get 403: Forbidden when the intended message and situation is 401: Unauthorised. I am mesmerised to this day why HTTP, maybe a rapidly enforced required HTTP/1.2 spec, didn't make it mandatory for servers to enforce strict management of URI errors especially, together with a crud layer of enforcement and even FTP protocol extensions for providing a UI to enable intelligent use as standard. For example : if you follow the standard date formats including the date in the filename, it's trivial to implement 300: Multiple Choices whenever you confirm that you really do want to upload _National_News_Headlines_for_1995.12.25.htm after _National_News_Headlines_for_1995.12.24.htm