mononcqc

27 ms·

211.
by mononcqc 14y ago
They both work absolutely fine. I tend to use d/<regex>, but the dv/<regex> example highlights the sublanguage and composition a bit more :)
212.
by mononcqc 14y ago
My favorite form of this is when using regular expressions. You have 'v' for visual mode, where you move the cursor around and can select stuff. You have 'd' to delete things. If I press 'v' then move around, then press 'd', I'll delete the
213.
Generic Piece Of Technology(ferd.ca)
1 points by mononcqc 14y ago|0 comments
214.
by mononcqc 15y ago
I think this is entirely depending on the attitude or mindset you have when approaching the teaching task, at least for technical subjects. If you're trying things in a vacuum, do not get reviews from people in know of how things work, do n
215.
by mononcqc 15y ago
Opa was actually there way before node.js. Let's mirror that comment to node, then. Also 'real time' as mentioned in the context of socket.io, or more generally node.js, is not real time at all. It's just live. Real time has a precise meani
216.
by mononcqc 15y ago
This thing about discount on axes would likely still happen without tracking. Tracking in itself will allow to do things like do frequency capping (do not want to display the same ad 400 times to the same person), give higher values to disp
217.
by mononcqc 15y ago
Not exactly. Mini compresses far more than what Mobile can do (when going through the Opera proxies is enabled with Turbo), and is useful on networks that are extremely slow or when you want to use as little bandwidth as possible. The chain
218.
by mononcqc 15y ago
Technically you can have at most two of the three of the same time. It's well possible for some stores to provide only one or no property at all!
219.
by mononcqc 15y ago
It depends. Some state needs to live, some needs to go. Long-lived processes should ideally do few state manipulations, or be easy to replace (so they store less state). Risky or frequent operations should be done far down in the supervisio
220.
Learn You Some Erlang - Distributed OTP Applications(learnyousomeerlang.com)
5 points by mononcqc 15y ago|0 comments
221.
by mononcqc 15y ago
Unless you specifically need a timer, I wouldn't use that and would simply return {ok, N} or {error, not_found}; that would avoid useless copying and message passing. Something like: find_x(N) -> find_x (N, [1, 3, 5]). find_x(
222.
Obfuscated Erlang Example and an Explanation(ferd.ca)
3 points by mononcqc 15y ago|0 comments
223.
by mononcqc 15y ago
You gave the money to Louis, he spent it however he felt like, which includes giving to charity. Where's the problem?
224.
by mononcqc 15y ago
You will have incomplete stacktraces; tail calls will be removed from the stack trace. However, you'll be able to know where in the current call (and file) the error lies, which was a big problem in Erlang as soon as you had somewhat leng
225.
by mononcqc 15y ago
you're right. Looking at the numbers again, it ought to be 0.56%!
226.
by mononcqc 15y ago
Reply from the author: "In the 0.54%."
227.
RFC 0: Introducing Forth(sites.google.com)
3 points by mononcqc 15y ago|4 comments
228.
by mononcqc 15y ago
Erlang isn't exactly about parallelism as much as concurrency. There is a different to both; concurrency is about running independent units of code (at the same time or not) while parallelism has the explicit requirement of things running a
229.
by mononcqc 15y ago
It makes perfect sense not to use Erlang because of its string manipulation caoabilities if you're used to working with strings. The programming languages we use and the problems we solve with them will influence the way we think about buil
230.
by mononcqc 15y ago
That's often true of tests that were only used to check the validity of code, not its design. In many uses of TDD, you will use somewhat broader specifications to test things. "The login system accepts any user with a valid name by returnin
231.
by mononcqc 15y ago
This doesn't beat the CAP theorem. The approach can be quickly described as a log-based append-only database with read-repair code based on last-write-wins. The system will have inconsistent views for the whole time a netsplit lasts. If I h
232.
Your Favorite Language is Probably Terrible at Concurrency too (functional-orbitz.blogspot.com)
14 points by mononcqc 15y ago|2 comments
233.
by mononcqc 15y ago
I haven't done it myself, but a reader of the site has written a script to do it for you: https://github.com/igstan/learn-you-some-erlang-kindle . I've worked with him to make sure vital images are kept -- the rest he might have dropped,
234.
Learn You Some Erlang: Buckets of Sockets(learnyousomeerlang.com)
63 points by mononcqc 15y ago|7 comments
235.
by mononcqc 15y ago
Oh, hi! I left on Tuesday morning (as you may know). I was wondering if the power ever came back on before you guys left. Thanks for the nice comments too! Your group was pretty fantastic at that. Being motivated with the weird conditions f
236.
by mononcqc 15y ago
This was one of the reasons for me to write Learn You Some Erlang in the first place. All good information to learn the language had to be taken from books (which cost money, although there are very good books out there) or training courses
237.
by mononcqc 15y ago
Author here. To be fair, there is one new chapter coming out every 4-5 weeks on average (for over 2 years now), depending on how fast or busy I am. This one is on Relups and Appups, or a way to do hot-code loading and live software upgrades
238.
by mononcqc 15y ago
“Finally, we use a few stateful, global data structures to track incoming requests and funnel them off to the right backend queues. In Erlang, the right way to do this is to spawn off a separate set of actors to manage each data structure a
239.
by mononcqc 15y ago
You make the assumption that tax money goes into the population's pockets instead of government-funded projects. Your argument is easily reversible to raise taxes across the board in order to concentrate the money into government projects r
240.
by mononcqc 15y ago
Erlang actually came from needs in proprietary languages like PLEX and other stuff used within Ericsson. The ideas were to have better concurrency (not parallelism) and better fault tolerance (through distribution and whatnot), properties t

More ›