I wonder if a medical study for something like this would be feasible. I also wonder if there could be negative long term or developmental effects from a treatment like this.
1 karma · joined May 19, 2022
I wonder if a medical study for something like this would be feasible. I also wonder if there could be negative long term or developmental effects from a treatment like this.
I suffer from chronic tinnitus myself, and I would be a changed man if I could get the ringing to go away. But I'm also pretty skeptical of any treatments that claim to reduce ringing, considering everything I've heard from doctors is, "you're stuck with it."
I think a new browser engine offers a lot more opportunity for more tangible, up front enhancements to a user's web experience than client-side offline storage would, at least in an immediate sense.
Consider the following scenario: YouTube releases a suite of new features, but they require some new functionality from HTML5. This is fine for Firefox, Safari, Opera, etc., but if you're using IE it'll prompt you to install Chrome Frame, just like it prompts you to install Flash. I could see it getting to the point where people instinctively do this just as they do with Flash.
Hell, maybe it could even be used to subvert Flash itself. Suddenly IE users everywhere are viewing <video>-based YouTube videos.
mod_wsgi should allow you to just drop in a .wsgi anywhere and run it, provided your host allows for that. Do you think there's anything preventing it from catching on?
PlugSuit, on the other hand, is SIMBL-compatible and uses a completely different method of injection. The author just needs to work around some new limitations introduced in Snow Leopard before it works with 64-bit apps. I would keep your eyes peeled for an update.
def greetings(ladies: int, gentlemen: (int, 80, 40)): passI'd like to think my cursive is legible, but I generally write notes, papers, etc. for others in print.
"The only clever feature is that if the first line of the script starts with #! and contains the word “python”, the Distutils will adjust the first line to refer to the current interpreter location. By default, it is replaced with the current interpreter location. The --executable (or -e) option will allow the interpreter path to be explicitly overridden."
Cmd+left arrow/Cmd+right arrow
Ctrl+left arrow/Ctrl+right arrow
Ctrl+a/Ctrl+e
And Cmd+up/Cmd+down will send you to the beginning or end of a textarea.I personally use the built-in Emacs bindings whenever possible.
And it's not the end of the world if his changes aren't accepted. He'll still have his own libraries, and people can enjoy them through PyPI.
That said, Guido is definitely very picky about changes to the language itself. I think that's a good thing.
Off the top of my head:
- Poorly written, half written, scattered, or plain old missing documentation all over the place.
- Poor release coordination and communication.
- Version incompatibility hell between different releases of its components/dependencies.
- Incomplete solutions for basic things like form generation. At the time that I was using Pylons they seemed to jump between a quite a few different libraries, none of which really worked well.
- Tons of magic that both offended my sensibilities and made debugging a nightmare.
To be honest, I don't think any Python web framework was quite "there" at that time, but I think today Django has far exceeded Pylons.
Also, I'm not sure I'd consider Pylons a micro-framework.
Speaking from direct experience, I wouldn't underestimate the amount of bureaucracy internally that would come down on this like a ton of bricks. Like others have mentioned, his best bet is to get someone to champion his cause internally. It doesn't even necessarily have to be someone in their ITS department - it could be a faculty member, or even someone in administration.
Hell, you might be able to get a job out of this.
The first part is more of a set of guarantees that browser vendors can agree upon, and I believe it's largely based on IE's behavior.
The new features are already slowly trickling into browsers. For example, Firefox, Opera, and Safari all implement <canvas>. There are a number of other features that are already implemented in browsers, which you can read about here: http://wiki.whatwg.org/wiki/Implementations_in_Web_browsers.
So, right now some new features are closer to the mainstream than others, especially where there are 3rd party implementations for IE (like ExplorerCanvas, and Google Gears which will probably have HTML5 APIs at some point). I wouldn't hesitate to play around with these new technologies, especially at the rate they're being implemented.
Besides being able to say they're eating their own dog food, I think having the ability to easily extend their version control system was a factor in the choice. The Python developers would just be writing Python, after all, and Mercurial has a very simple extension system.
I believe Guido has had direct communication with some of the core developers of Mercurial as well, which was probably another factor. I'm not sure what Brett's DVCS usage survey had to say about Mercurial or Git, but that could also play a role in his decision.
Here's the original thread that led up to the PEP: http://thread.gmane.org/gmane.comp.python.devel/98191. From what I understand, there wasn't supposed to be a lot of discussion until the PEP was written, but people couldn't help but voice their opinions on the matter. I'm guessing this is why Guido put his foot down: to prevent an endless religious debate. Hopefully the PEP will be revised with a more detailed explanation of his rationale.