Ir al contenido principal

Internet Explorer 6 es lo peor que le ha sucedido a la industria web.

Es ya normal y corriente tener que darse de topes y PERDER horas y horas arreglando el código CSS y Javascript -muchas veces teniendo que salir de los estándares- para que las páginas web funcionen con IE6.

Este es el peor de los casos que he tenido:

Resulta que un comentario. Sí, un COMENTARIO de código determina si el script funciona o no:

En cierta función dentro de un archivo .js que cargo en la cabeza de mi página tengo:

var funcionDeMenu;
if (is_ie && !is_ie7up)
funcionDeMenu = function(dom){Effect.toggle(dom, 'appear');}
funcionDeMenu = function(dom){Effect.toggle(dom, 'appear', {duration:0.7});}

E increiblemente no funciona si agregamos este comentario:

var funcionDeMenu;
// Lo que sea <-- ESTE COMENTARIO
if (is_ie && !is_ie7up)
funcionDeMenu = function(dom){Effect.toggle(dom, 'appear');}
funcionDeMenu = function(dom){Effect.toggle(dom, 'appear', {duration:0.7});}

No sé si sea un bug ya detectado o qué pero no puedo creerlo. ¿Cómo puedo yo confiar en Microsoft como empresa o comprar sus productos cuando me han hecho perder tanto tiempo = dinero?


Entradas populares de este blog

sqlalchemy ProgrammingError can't adapt type numpy.float64 - Python troubleshooting

Are you getting a

sqlalchemy.exc.ProgrammingError: (ProgrammingError) can't adapt type 'numpy.float64'

It's because psycopg (psycopg2) - which is used inherently by SQL Alchemy but if you're just dealing directly with alchemy you might not know this - has no idea how to make the numpy.core.numerictypes.float64 (complete type path: another thing they don't tell you) a string for SQL querying.

Simple solution, add:

# solution by Jorge Orpinel found at rehalcon.blogspotcom
import numpy
from psycopg2.extensions import register_adapter, AsIs
def addapt_numpy_float64(numpy_float64):
return AsIs(numpy_float64)
register_adapter(numpy.float64, addapt_numpy_float64)
somewhere in the program.

For a more complete reference of the problem see

I don't git it.

A lot of people praise git. I liked it at first, now I don't geet it.

Some weird stuff I've found in git, in no particular order:

You can pretend to be anyone. Just change your [user] name and email in .git/config and commit away. As long as when you push you use valid credentials, the commits will be recorded as from someone else. (At least this is possible on GitHub, I know git doesn't implement any specific user access control.)
* I guess you could try to enforce signing commits but as anything besides the basics, that gets pretty complicated on git.Steep learning curve that keeps getting steeper. Ok: git init, git add, git rm -r, git commit -am, git remote add, git fetch, git merge -ff, git push and pull -u of course, git checkout -b, git reset --mixed, git revert HEAD ... Those are just some of the basics... Ever tried to incorporate git subtree pull -P prefix --squash > into your workflow? I have, it's not fun (keep reading).Its super complicated to collaborate…

Dockerize your Django App (for local development on macOS)

I'm writing this guide on how to containerize an existing (simple) Python Django App into Docker for local development since this is how I learned to to develop with Docker, seeing that the existing django images and guides seem to focus on new projects.

For more complete (production-level) stack guides you can refer to Real Python's Django Development with Docker Compose and Machine or transposedmessenger's Deploying Cookiecutter-Django with Docker-Compose.

Pre-requisitesAn existing Django app which you can run locally (directly or in Virtualenv). We will run the local dev server with runserver.A requirements.txt file with the app dependencies, as is standard for Python projects; including MySQL-python.Working local MySQL server and existing database. (This guide could easily be adapted for other SQL engines such as Postgres.)Install Docker. You can see Docker as a virtual machine running Linux on top of your OS ("the host"), which in turn can run con…