bascule

67 ms·

601.
by bascule 15y ago
> especially when you consider the fact that much of the software is native code, not hampered by the resource overhead of a managed code runtime. Really Ars? Really? Sure, they're probably right there is a difference, but have they act
602.
by bascule 15y ago
"Effortless, scalable, pub/sub baked right in" I was curious how this system scaled beyond one node and thus a single point of failure. I then saw it used Redis. Hooray, they relocated the single point of failure. But hey, Redis is really r
603.
by bascule 15y ago
I don't think all software needs to meet that specific definition to be considered "realtime" in some aspect of the word. Google agrees: http://www.google.com/realtime Does that meet the criteria of realtime computing? If not, is Google w
604.
by bascule 15y ago
Holy crap, memory barriers! It's a modern architecture that's finally caught up to where Symbolics was at in the '80s. Seriously though, this is good news for concurrent garbage collected languages.
605.
Introducing Celluloid: a concurrent object framework for Ruby(unlimitednovelty.com)
1 points by bascule 15y ago|0 comments
606.
Distributed systems and dynamic typing(unlimitednovelty.com)
3 points by bascule 16y ago|0 comments
607.
by bascule 16y ago
That's a false dichotomy, especially for most Rails applications, and one that can easily be shown false using tools like NewRelic. Of course YMMV depending on the nature of your Ruby application, but in general (and particularly for Rails
608.
by bascule 16y ago
I'm the author of cool.io and Revactor (the latter was mentioned in this article), and as much fun as it is to experiment with these ideas, the path of least surprise, especially for Rails applications, is to use threads. I wrote about that
609.
by bascule 16y ago
Am I the only one who noticed this? "This entire site is serving 16million pages a month and we’re doing it off of 2 servers, which are almost completely unloaded. So we’ve got a ton of headroom on those 2 servers – one server is a webserve
610.
Video of Reia (Ruby-flavored Erlang) talk from mountain.rb 2010(confreaks.net)
1 points by bascule 16y ago|0 comments
611.
by bascule 16y ago
Perhaps. Rebar is cool. But I'd like for as much of Reia as possible to be accessible to Rubyists with little or no knowledge of Erlang.
612.
by bascule 16y ago
Yes, I've wanted to implement for loops and while loops that can alter the local binding for awhile (that compile to separate functions in the same way Erlang compiles list comprehensions to separate functions) I still haven't gotten around
613.
by bascule 16y ago
Reia isn't "interpreted" in any manner different from the Erlang language itself. It's somewhat similar to CoffeeScript in that it uses parse transforms to produce Erlang parse trees which are then compiled by the Erlang compiler just like
614.
by bascule 16y ago
Hi. I created Reia. Erlang's semantics are so very different from most other languages that having an arcane Prolog-derived syntax is just insult to injury. In addition to all the conceptual, semantic leaps that Erlang asks you to make, you
615.
by bascule 16y ago
Hi, I created Reia. I used to agree with you but now I don't. I was particularly moved by some of what Joe Armstrong, Erlang's creator, had to say in the book "Coders at Work". He noted that after attending several functional language confe
616.
by bascule 16y ago
Hi, Reia's my thing. My view on waffling on language design decisions: If you're working on a language project, fuck it up, and don't do a rewrite, you get PHP. That said, your other criticisms are valid: much of Erlang's functionality does
617.
by bascule 16y ago
They have iOS development for iOS now? Awesome. What will Apple think of next?
618.
ROFLSCALE: a discussion of fibers vs threads based on a real IRC conversation(youtube.com)
1 points by bascule 16y ago|2 comments
619.
How to make a cheap CI traffic light(unlimitednovelty.com)
3 points by bascule 16y ago|0 comments
620.
Multithreaded Rails is better than Async Rails, and Rainbows is cooler than Node(unlimitednovelty.com)
63 points by bascule 16y ago|16 comments
621.
Reia: Pluggable Parsers(unlimitednovelty.com)
4 points by bascule 16y ago|0 comments
622.
How to properly utilize modern computers(unlimitednovelty.com)
2 points by bascule 16y ago|0 comments
623.
by bascule 16y ago
-extend() is another half-assed solution. It's closer to mix-ins than inheritance. Object orientation in Reia is baked into the core language itself. Like Ruby, all of its core types are objects. In Perl and Erlang they are not. Reia fa
624.
by bascule 16y ago
For what it's worth I know Erlang a hell of a lot better than I know Perl
625.
by bascule 16y ago
Parameterized modules don't have constructors. That doesn't matter in a trivial case, but it does when you want some complex state set-up which you don't want to repeat every single time you "instantiate" a parameterized module? Also, Reia
626.
If Ruby is object-oriented Perl, then Reia is object-oriented Erlang(unlimitednovelty.com)
42 points by bascule 16y ago|13 comments
627.
Is Reia an object oriented language Joe Armstrong could actually like?(unlimitednovelty.com)
6 points by bascule 18y ago|0 comments
628.
How Erlang evaluates funs (i.e. lambdas)(gist.github.com)
12 points by bascule 18y ago|3 comments
629.
Reia: a Ruby-like scripting language for Erlang(wiki.reia-lang.info)
5 points by bascule 18y ago|0 comments