After working for several years in a large clojure code-base, and having
been bitten by laziness a few times, I think I am still a fan of "lazy by
default".
I have not been bitten by issues related to agents and laziness. Mostly
it's resources going out of scope because I was using a dynamic bin
[ Full disclosure: I am the technical lead on this product and the hiring
manager in this case. Feel free to contact me with questions, and to pass
this around. We are also looking for Go hackers on another team, if you are
of that persuasion. ]
Clojure Developer for Malware Analysis Product
The
On our non-trivial application, we have broken our testing into the
following sets:
* Unit Tests -- written by devs, run as part of our integration builder and
when doing dev
* Integration Tests -- automated, hitting our external APIs, written in
clojure, maintained by the devs mostly, run as part
ogic, but I'm wondering if maybe some
>implementation changes lead to this?
You could use the Issues system in github for reporting this to pldb's
maintainers. Details of what "not works at all" looks like would help
them too.
--
Craig Brozefsky
Premature reifica
Craig Brozefsky writes:
..
Sorry, didn't reaze you wanted the output to be base64 encoded, in which
case, add these funcs:
(defn base64-encode [^bytes v]
(javax.xml.bind.DatatypeConverter/printBase64Binary v))
(defn sha1-base64 [^String v]
(-> (.getBytes v)
larry google groups writes:
> Hmm, interesting. I had assumed that I wanted a string run through
> SHA1, so I created the string, then called getBytes on it to feed it
> to SHA1:
>
> digest-as-string (apply str nonce created secret)
> digest (.digest (java.security.MessageDigest/getInstance "sh
Without this, I have almost no hope of
translating them to dire.
--
Craig Brozefsky
Premature reification is the root of all evil
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
a
structure Enlive used. JSoup provides a sufficient API on it's java
objects for use to do our work in this case.
--
Craig Brozefsky
Premature reification is the root of all evil
--
You received this message because you are subscribed to the Google
Groups "Clojure" group
ain.
That was mentioned in the talk actually, as part of the bookkeeping that
comes with such histories.
--
Craig Brozefsky
Premature reification is the root of all evil
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To pos
a line of logic that only exists as a strawman, an
expansion to the absurd -- changing the argument from one of sufficient
flexibility to one of abstractly greater, and therefor cumulative,
flexibility.
--
Craig Brozefsky
Premature reification is the root of all evil
--
You received this message becau
Warren Lynn writes:
>If it does not do any harm to anybody but have benefits for some people
>(of course not just me), I reason it is a good feature.
You should check out Perl. 8^)
--
Craig Brozefsky
Premature reification is the root of all evil
--
You received this message b
g else in general.
Current dev machine is a mid-2012 Macbook Air with 8g RAM, dual core i7
@2ghz, and of course the sata3 SSD. It's running Arch Linux (latest
installer worked damn near flawlessly) and is blazing fast. My x100e
Thinkpad was not bad either for it's size/price/weight ra
y, and plan on using it to learn a bit more about clojurescript.
I like to make purty pictures too.
I have not done any work to make this a standalone project either.
--
Craig Brozefsky
Premature reification is the root of all evil
--
You received this message because you are subscribed
out digging into the code and
understanding how things work, followed by asking for others to be do
the coding and be and advocate for your rather vague feeling of unease,
strikes me as passive-aggressive attention seeking. To do such while
top posting, well, it's just too much for me. 8
last is defined as part of the very base of core,
before protocols get loaded, and even before defn is available. Using a
protocol to optimize at that level is gonna get dirty dirty.
See my reply to Warren my proposed change to core. Those defs can be
dropped into clojurescript too, btw.
-
seq ret))
These changes don't really bring any new entanglement between
clojure.core and the clojure.lang java objects -- because the language
defines explicitely how vector conj/peek. However, going thru
clojure.core and optimizing it based on knowledge of implementation in
clojure.lang would
1.2.0
1.2.0
20100914121821
--
Craig Brozefsky
Premature reification is the root of all evil
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note
s a better
> proplem indicator than just a simple true/false
I think adding a note to read and friends is sufficient. There could be
other dispatch macros to be considered, not just EvalReader. Having
*read-eval* default to false may also be a good idea.
--
Craig Brozefsky
Premature reifica
a shell process you
call from your Java program.
Also, you will need to invoke sudo with the -S argument so it reads from
stdin, and not from a pty.
--
Craig Brozefsky
Premature reification is the root of all evil
--
You received this message because you are subscribed to the Google
Groups &quo
-
You should checkout proces output to make sure, but I'm betting that
sudo is opening a tty to read the password and not getting it from
stdout. The properly solution here, here, may be to define shutdown as
a sudo action for you
on, contact me at
cr...@threatgrid.com
The job is also posted here:
http://www.threatgrid.com/jobs/
--
Craig Brozefsky
Premature reification is the root of all evil
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send ema
data tables, no notion of
object identity for the most part either. We have these soft "entities"
which conventiently map into sql data types, so work as key values
themselves.
I don't wanna diss on Korma tho, just that the data model it is aiming
at is not the one I want.
--
Craig
explicit :else nil, in a situation where the negation of
the logical operation is implicitely nil, just stinks in my nose.
Seriously though, don't let my aesthetic griping stop you from rocking
out whatever kinda clojure code tickles your brain.
--
Craig Brozefsky
Premature reification is the
Tassilo Horn writes:
> Craig Brozefsky writes:
>
> Hi Craig,
>
>> Also, people have been writing lisp for a real long time, and they
>> haven't invented a chucklehead macro like let? yet, so prolly not
>> really needed to improve the readability...
>
&
been writing lisp for a real long time, and they
haven't invented a chucklehead macro like let? yet, so prolly not really
needed to improve the readability...
--
Craig Brozefsky
Premature reification is the root of all evil
--
You received this message because you are subscribed to the Go
Phil Hagelberg writes:
> Yes, what a great object lesson in the usefulness of being able to
> disable locals clearing. Gave me a lot to think about regarding what
> kind of feedback tools should provide.
I don't understand what "disable locals clearing" means.
--
Cr
Ambrose Bonnaire-Sergeant writes:
> What are you making?
Malware behavior analysis tool. I'll be able to release most of the
non-malware specific portions once this gets out of the proof of concept
phase.
--
Craig Brozefsky
Premature reification is the root of all evil
--
You
,
data.json, clojure-csv, core.logic, ring, compojure, lein, and swank.
You make this old Common Lisp hacker happy.
--
Craig Brozefsky
Premature reification is the root of all evil
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To pos
r Programming (Van Roy and Haridi). It's a great
tour of many "paradigms" of programming. If you are enjoying this
topic, you might want to check it out. It is less Lisp specific,
obviously.
--
Craig Brozefsky
Premature reification is the root of all evil
--
You received this
l/language was often the reason we were able to make
those projects work, you know, so that there was someone getting paid to
work on it later, who could curse us.
--
Craig Brozefsky
Premature reification is the root of all evil
--
You received this message because you are subscribed to the
ssues. Is there some Maven black magick I should familiarize myself
with in order to list packages and their deps?
--
Craig Brozefsky
Premature reification is the root of all evil
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to th
the reader-table, and which
reader macros where active or needed at a given time, was rather
informal and prone to confusion. The win of some syntactic brevity is
not that big a deal.
--
Craig Brozefsky
Premature reification is the root of all evil
--
You received this message because you ar
Julian writes:
> I wonder what would be required for a modification to the clojure reader in
> order to do this...
No intention of picking on Julian, but do we really have to re-live all
of the flamewars and jawflapping of comp.lang.lisp on the clojure group
again? You're giving me flashbacks 8
33 matches
Mail list logo
