IntelliJ IDEA Ultimate brings you nearly all the feature that are available in the other version. PyCharm, WebStorm and others are cheaper but more focused on a single language.
174 karma · joined February 1, 2012
That said, even if we choose a defense in depth, it still is not a valid reason to throw away XHTML as it was done.
The same way you will not remove your firewall because it does not block dormant viruses, but add an antivirus, the browsers could have still continue putting effort in rendering the correct, and powerful, XHTML, while setting down some decent fallbacks to recover. Being we a be red warning to raise awareness that something need to be fixed.
It IS a bug that the blog engine developers should have catch, in the same way they should have protect the trackback from XSS injection.
Guaranteeing your output will always be valid might not be trivial, but it is way less harder that some people pretend it to be.
HTML went the same way other popular languages (e.g.: VB, PHP, Perl), they got broad adoption because the compiler/interpreter/renderer would be too kind in working hard to fix user mistake instead of reporting them.
And then, when they tried to fix it, the same user base complain (despite being bitten many times by the language) that it should stay like it is, because it has always been like that.
When bad habits became traditions, you are really in a bad position.
Now, I know that _some_ databases offer some level of support to include DLL operations within a transaction, but its far from being common, and most of the implementations are quite recent.
The initial described problem (organising ideas in a hierarchical way) has already been solved efficiently years ago with visual mind maps. They have been used successfully to not only create the hierarchy, but also to realise that sometimes, the tree is more like a graph.
As a reader, it's infuriating to have to click all the time (or use keyboard) and have this page scrolling all around. I just want to READ, not being distracted by some kind of useless parallax effect.
As a writer, moving ideas around to get them properly organised is really painful. There is no distraction-free interface neither.
If you really want to make tool for writers, I would strongly suggest you that you take a look at tools like Ulysses or Scrivener and try to understand the rationale behind the UI choice they made.
Again we are re-inventing the wheel (xml) with some quirks. It looks like people never tried to fix the root cause of the VHS vs BetaMax battle .
Balsamiq is about creating wireframes. Wireframes are there especially to not mimic too much the "final" product so that you can concentrate more on the feature an flow aspect without suffering of the interference that the visual elements could create.
Keynote, at least the way you are using it, is to create mockups. Mockups are there to crystalize (or invalidate) the ideas expressed in the wireframes together with the branding you are creating for your application.
From what I learned during my medical training, this king of issue is not so uncommon, but it is usually diagnosed very easily. Her peacemaker can be disabled using a simple magnet. This is a common test in nearly all protocol to check how the heart is working without the help of the device. Doing this simple test while upside-down would have shown that the paecemaker was effectively working in that position. That should have be enough to ring a bell to most of the cardiologists.
By changing a single line, the java version can also produce XML or text response. By changing two lines, it can also respond to POST requests.
And that's just the top of the iceberg. Oh, and in the ends, it's way faster than Node, Ruby, Python and most of the dynamic languages.