LoonyPandora
I think you have a bit of a problem with whatever system you are using to send notifications!
Also, I think the deprecation of core CGI.pm is pretty major. For now it just issues a deprecation warning, but will be removed totally from core in future versions, only being available via the CPAN.
https://metacpan.org/pod/release/RJBS/perl-5.20.0/pod/perlde...
While your point that mobile first design inevitably causes a lack of information density at desktop resolutions has some merit, it does not apply in this case.
http://ycombinator.com/newsguidelines.html
Don't abuse the text field in the submission form to add
commentary to links. The text field is for starting
discussions. If you're submitting a link, put it in the url
field. If you want to add initial commentary on the link,
write a blog post about it and submit that instead.I suggest you email <[email protected]> to let them know more than one person would like the feature :)
There may be reasons, but I find there is often a lack of understanding about the context in which that rule was developed, and the compromises that were made. A developer not understanding why things must be done in a certain way, but doing it anyway sounds pretty cargo-culty to me.
[1] https://github.com/dotcloud/docker/wiki/Docker-0.5.0:-extern...
The Perl core team are getting very good at timeboxing their development and releasing on time.
3 years of use from a product, plus we now have the almost-guaranteed support and speedier development because of it's Open Source nature. I think it was worth the money.
If you paid for it last week, I can understand frustration.
The ReadMe, build process, and licensing instructions all point towards this being a well planned Open Sourcing of a product.
I'm pleased with this, and hopefully it will spur development of TM2, allowing it to truly compete with the up-and-coming Sublime Text 2.
The bundle itself looks very appealing.
Also, someone needs to practice spelling "recipes". There are two instances of the same typo on the page. Combined with the HTTPS issue mentioned earlier, this looks scarily like a scammers page.
"Tasty bonus recipies" "recipies with backbone"
Specifically the talk titled "Unicode Support Shootout: The Good, The Bad, & the (mostly) Ugly"
It's a year old now, but it's still relevant. It gives a very detailed look at unicode support across JavaScript, PHP, Go, Ruby, Python, Java, and Perl.
Minimum specs have changed between beta and released version in the past. Apple has also released firmware updates to make machines boot in 64-bit mode as well. It is well within the realms of possibility that your machine could become "compatible" before 10.8 is released.
Secondly, as a point of reference the current MacBook Pro's do have upgradable hard drives and RAM. However the battery is not easily replaceable.
The part of this situation that upsets me the most is not the missiles, but what comes along with them - the heavily armed soldiers billeted for up to 2 months.
We have no choice in this, and were informed by a leaflet through the door.
This isn't war time and the Olympics only last for a few weeks. We shouldn't have to have soldiers and weapons in a residential complex!
On the wider issue of semicolons I am in agreement of you, and all my own code is written with that in mind - though I respect the bootstrap authors preference and would style my pull requests without semicolons.
If their insistence on not using semicolons causes conflict with other popular software, I would hope they see sense and fix those conflicts - even if that meant adding a semicolon or two.
Now, this could be easily solved – by adding the friggin semicolon.
For reference, I sometimes use semicolons in my javascript, sometimes I don't. It depends on context and whether it makes the code more readable. It's not an issue I care enough about to get involved in a holy war, one only marginally more relevant than tabs vs spaces.
[1] https://github.com/twitter/bootstrap/issues/3057#issuecommen...
[1] http://perldoc.perl.org/perlsec.html#Algorithmic-Complexity-...
I think you would do better if you could show people the code.
My honest suggestion would be to just open-source what you have and build a bit of buzz within the community. From what I can see, you don't have anything that is worth buying right now. Perhaps that buzz you build will attract the right sort of hacker to help you build version 2.0
Perhaps it was just a badly phrased submission title, but it set the tone and direction of the discussion. The title effectively told people they are doing CSS wrong. People don't like to be wrong, and will go to great lengths to prove themselves right [2]. It's nothing personal and I bet if the title was less preachy, it would have gathered more productive comments and had a friendly tone.
In general your articles are high quality and the advice sound. I think this issue was caused solely by a bad title. Though I still don't understand why you hate IDs so much!
[1] http://csswizardry.com/2011/12/on-html-and-css-best-practice...
All it needs is someone to pick a master format for the text and run with it. That should be someone with enough domain knowledge to choose wisely. I would say something like markdown with embedded metadata (like how you format a blog post with jekyll), but I admit I don't know anything about the requirements of the project.
A simple table showing browser support for different methods in .ajax() calls would help a lot!