I suppose it depends tremendously on the application you are developing but combining Haskell with things like Haxl[1] and opaleye-sot[2] can help simplify the database aspect of things tremendously.
Once you've abstracted away the persistence and querying details, I think you get to the best part of FP which is modeling the actual behaviour/flow of data and types. In a typical app lifecycle Haskell starts shining more as time goes on and the app grows past CRUD and in size.
Last semester for a compiler course I was taking we had to implement a compiler for a subset of Go (called GoLite), with free reign over language choices. I chose to implement a compiler[0] using Haskell and LLVM, this article helped a _lot_ when I was writing codegen, especially since it was my first real Haskell project.
However, some of the most interesting and important issues are left out of it. Some examples are implementing exceptions, threading, imports, garbage collection, closures , etc.. I would love a more advanced version of this article that discusses how to implement a more advanced compiler with more modern features (specifically in LLVM).
Your stock market idea is interesting, however it wouldn't work well at all and would destroy the entire pro scene. If you check http://dotabuff.com/heroes/played you'll see the list of most played heroes and their win rates. The heroes who most likely need buffs will be at the bottom of that list. In a stock market simulation you would have people bidding on their favorite (popular) hero or against their most hated (popular) hero. Heroes like Invoker who have a 40% pub win rate are actually balanced for pro players with a 50% win rate. Given the popularity of invoker and the low win rate, we could expect a good amount of buffs causing the pro-metagame to shift to invoker being #1 pick.
Security by obscurity is perfectly fine when it's part of a layered approach. It will help keep attackers from learning the details of your architecture and will also stop skiddies in their tracks.
One of my issues is that this article discusses the Zumwalt's main failures as being too 'avant-garde' where it was a classic example of a jack of all trades, master of none. The whole ship was supposed to have swappable 'mission packs' that would let it do anything while being stealthy, fast, cheap, modern etc... The article has a very pro-Zumwalt / Bath Iron works (mentioned several times) spin to it. The EM Briefcase was written by the president of the company cited in the article (Metatech). It sounds a lot like PG's suits essay.
But the whole point is that this browser isn't meant for technical people. It's not meant for the kind of people that feel the need for a different `Downloads` folder.
It seems like DDG is positioning itself to become WolframAlpha for tech. Hopefully, this will allow it to better catch the exact market segment that would be wary of search engine tracking (educated tech-savvy people).
While it may be too expensive to have it made entirely by a craftsman the US, if you're up to the challenge you can join a woodworking shop and learn how to build it. It will certainly take more time but you will get a more complete experience than simply designing it.
can this algorithm be run lazily? ie, can you continue to generate continuous terrain using this technique or do you need to generate the whole map ahead of time?
I heard a saying at work: "Python is the second best language for anything." Scientific computing is a perfect example. By being close to the best, Python ends up taking over each sub-section of the SC world.
Hey jmbmxer, we're currently in talks with sustainableharvest to get access to all of their images and videos about their farms. We built this on a bus from Seattle to San Antonio so we haven't had enough resources to fully flesh out the imagery. We definitely have coffee experts on board, besides all being addicts ourselves our CEO is actually the owner of two coffee shops in Seattle! We'll definitely try to make more information visible and make easier to understand what we provide.
So far we've gotten a lot of positive responses from importers in the north east (Seattle, Portland). We've also talked to micro roasteries both physically and on the phone, and a lot of would be interested in a system to make their purchasing simpler.
So we are collaborating with both warehouses and importers to allow the warehouse employees to package orders that need beans from multiple importers.
The reason it hasn't been done before is because there didn't exist a single platform that pulled all the different orders from importers and told the warehouse exactly what needs to be combined.
The difference is that we don't actually hold any product. We allows importers to list their beans and warehouses on the sit e and provide a standard view for them. Though I agree that there is too little discussion about the beans, this is also a very targeted specialty market (B2B) where our customers already know what kind of product they are looking for.
You're forgetting costs associated with crew beyond pay. You also have to pay for food, insurance etc.. there's the risk of hostages being taken. Additionally, removing the bridge/crew quarters makes for more space to put containers, the ships could end up looking like barges with the entire top surface covered in containers.
As the author said "counter-intelligence". It allows Kim to post pictures of him visiting a factory in one city when he is really at a completely different one. The less any one knows with certitude about him the safer he is.
Every time I see these X0-work week (where X > 4) posts I keep on thinking of this: http://visitnormandy.files.wordpress.com/2010/04/1mai.jpg?w=...
It took us a long time to have the right to a 40 hour week, lets not give that up especially for salaried employees.
Very nitpicky but I find the ligatures on all the "t" characters very distracting.
Additionally, I don't know Closure, but are there any default hash-table implementations? If so, how does this implementation compare against the base one?
The problem is expectations. When I pull up my map application, I want to find a position on it, usually navigate to it, and do so quickly. Having to navigate menus containing way too many unnecessary options slows me down and discourages most people from using it when gMaps has a simpler interface. Additionally, the maps seem very cluttered with useless information (for immediate navigation). Perhaps the best option would be to get rid of some of the features, since more features != better application. In the end though complexity isn't an excuse for a difficult interface.
This is really awesome, we've been building similar solutions to our course websites at McGill. However, the administration does not seem to care yet (that might be due to the low adoption) about the different unofficial APIs and sites. The idea of adding course ratings / workload descriptions is really good we might have to implement a similar system on our end.
Would there any way to fake the beginning of an OAuth session with Facebook, Google or any other OAuth authenticated site? Kind of like replaying cookies to hijack sessions?
You're looking at a very high level picture of the CPU. The different coloured sections represent the different logical segments of the CPU. I can't tell you specifically what each section is and maybe someone more informed could clear that up but among there will be: registers (memory), alu (math), CU (control, brain), buses (transport), the GPU, and some other miscellaneous sections (IR,PC,etc..). For the holes, I don't know what they mean I have never seen those on a cpu die.