Funny thing is, when recommending it to a friend, they mistakenly assumed from the title that it was a book of underhand tactics, which couldn't really be further from the truth. There's a lot to be said for being genuinely nice to others.
423 karma · joined November 7, 2010
Funny thing is, when recommending it to a friend, they mistakenly assumed from the title that it was a book of underhand tactics, which couldn't really be further from the truth. There's a lot to be said for being genuinely nice to others.
The .Net FOSS community has been gaining momentum in the past few years, with most new developments having moved to GitHub, which is where I would generally recommend people start looking for new libraries. Of course there are exceptions, but it is a good starting point.
Alternatively, NuGet seems to have become ubiquitous in the past few years too, so that's the other route for finding new libraries. (Incidentally NuGet seems to be having an outage today, but that is a rare occurence).
A list like this might have value for some people, but only with better curation to reflect what is still active today.
Having read about differencing disks, they seem like the perfect solution to this problem, by allowing VMs to share the same parent disk, without needing to copy it (as each VM only needs to keep track of differences to the base disk). From what I've read of differencing disks, this seems like a no-brainer for Vagrant (but unfortunately my experience extends no further than what I've read).
Is there a reason Vagrant doesn't use this approach? Any plans to put this on the roadmap? It seems like this feature is supported by both VirtualBox and Hyper-v.
(This page describes differencing disks, and the first diagram under "Using multiple differencing disks with one parent disk" accurately depicts the sort of thing I have in mind here http://technet.microsoft.com/en-us/library/cc720381(v=WS.10)... )
Still, I can definitely see myself using this to share little pieces of code where currently I write it up in linqpad and email to colleagues.
Any chance you could add an extension method like linqpad's Dump() to pretty print objects?
It is designed to generate input for your code (the public surface by default) to determine whether it runs correctly. It can use code contract features in .Net to help inform whether your code is correct. It is great for finding those 'weird cases', and where you find a particularly interesting case, it is easy to add it as a test in your suite.
You can see it used (and play around yourself) through the browser here: http://www.pexforfun.com
However, as the buttons are on the outside, the designers clearly thought they would aid things where a large group all want to go to the same floor. Press the special people button, enter how many of you there are, and the lift system will optimise to ensure it doesn't needlessly stop at interim floors if you have filled that lift to capacity, or send you a lift already filled that wouldn't fit your group in.
So the trick is to say, even if you are a single rider (lifter?), that you are a party of 14, guaranteeing your lift won't stop at any other floor on the way to yours. An 'express mode', if you will.
Problem is, everyone working in the building seems to know this trick, and it does not scale. Whilst it might make the time in the lift shorter, I notice that the wait time for a lift appears longer (from observing those going to my floor who have done the trick before I then select the same floor normally). The real trick then is to use the lifts as they were intended. The irony is that all these 'super busy' types who are slowing everyone up are simply slowing themselves up too.
Then again, who was expecting a building full of lawyers and traders to behave like good citizens?
The problem comes when you want the *nix tooling to interact with the Windows environment. Personally I like the clear separation between the host and guest environments, but YMMV. At the very least you can mount some share the Windows host provides inside the guest OS.
Where is this bleeding edge Opera Developer version that they mention in the post available for download, so I can at least see if the little things that have kept me on Opera for 9 years are in the pipeline?
I'm glad you've decided to follow your own advice and stop digging.
Ignoring your original reply to arianvanp, you'll see that interesting discussion has arisen in response to their original bold statement. This is why I read HN.
You have entered this thread, seemingly to show off your superior knowledge of PL creators, without actually contributing to the discussion. My attempt to diffuse things clearly had the opposite effect (FWIW, I was trying to point out that the words used in the article could lead to the interesting discussion that has happened, and certainly wasn't defending an attack on Joe Armstrong - an attack that you have read into but I don't feel is there).
Instead, what has been achieved?
To go meta for a moment, this is the problem with with HN that gets discussed from time to time (and I am well aware that I'm replying to a highly active user). Why do people feel the need to be so combative, just to win internet points (something someone is down 555 of by your count)? Perhaps after having pointed out who the author was, you could have explained why that matters. Maybe we aren't all as clever as you are.
Yes, arianvanp's original post was also phrased in a somewhat combative way, but at least it sparked interesting discussion. This subthread is the antithesis of that.
I had a similar thought when reading the article, unaware to who wrote it... I wondered how currying and the like factored into the language, and thought that comparing |> to unix pipes was a big simplification. And whilst this simplification might be intentional for the article's purpose of giving an overview, it instead read - to me at least prior to realising who the author was - like the author was not fully informed on its use in other FP languages.
No mouse chording (distinct from gestures). Wikipedia even highlights Opera as a key implementation of mouse chording, and now its gone. http://en.wikipedia.org/wiki/Mouse_chording
No closed tabs drop down. Its not uncommon for me to want to dig out a tab I may have closed 20 tabs ago. Reopening one-by-one is terrible.
No forward slash search (á la Vim, or indeed, Firefox)
If these things aren't tabled for Opera 15's release, then thats it, I'll be back to Firefox after 9 years on Opera. These sort of small features are Opera's bread and butter, things that have become second nature to me, and I suspect many. Certainly for me, its these little things that have kept me on Opera until now.
Where can we go to provide feedback? The OP provides no obvious link.
Trying to be positive, Stash looks like it might be useful.
Perhaps this is the reason for the introduction of the 'stash', which in fairness might be a better solution (as I'm not necessarily defending 100+ tabs, but its a habit that has worked for me so far)
Though my French boss goes for the latter, but with a very soft J. In fact, he pronounces it like 'Gîte'
http://en.wikipedia.org/wiki/Gîte for the pronunciation guide.
Everything I've seen just says that this is simply a subset of OData's functionality. And the features that are being asked for by users commenting on the OP are ones already provided by the existing standard.
And what about querying the data? There have already been questions elsewhere in this thread about how this would work. OData already provides very rich query support, including document projection (returning a subset of a document) through to complex queries navigating multiple relationships (I easily could ask, through a GET query string, to return all the actors who have starred in films that belong to the comedy genre - navigating 3 collections, actors,films,genres). If queries are out of the scope, then fine, but its clear people want to query their data.
So please answer what this offers over existing standards if you want to compete.
Oh, and in response to your earlier post of what OData JSON looks like, you're much better served by linking to v4, not v2 as you did:
http://docs.oasis-open.org/odata/odata-json-format/v4.0/cspr...
That doesn't look so dissimilar.
To address your issues around defining a standard JSON API - OData is itself the standard API for any OData service. All that would differ between your OData service and mine is the schema and the data inside. How you explore that schema and access that data is what OData defines.
http://tvtropes.org/pmwiki/pmwiki.php/Main/BritishBrevity
...usual warning about a tvtropes link, and your subsequent drop in productivity
9 months ago, they announced they stored twice this amount - 4 trillion objects. A year before that, 1 Trillion. Given that previous rate of growth, we can expect they have a lot more than this now.
They also announced peaks of 880,000 requests a second. Whilst Amazon wins here, I'd say its fair to assume this number has increased in those 9 months.
http://blogs.msdn.com/b/windowsazurestorage/archive/2012/07/...
Perhaps a .Net decompiler could help. Reflector used to be the only good tool around, but since it became a paid tool, other free ones have sprung up. dotPeek is one (no idea how good it is).
http://thepcspy.com/kittenauth/ http://arstechnica.com/uncategorized/2006/04/6554-2/
I appreciate there's some HN submission guideline about keeping the same title as the pages you are linking to, but surely a slight bending of the rules is the much better choice in this case? The link isn't really to the page, but a specific data point on that page.