shepmaster

32 ms·

271.
by shepmaster 11y ago
This may not be universally true. The Rust docs[1] point out that as of today, compiled binaries use either jemalloc[2] or the system allocator: > Binaries generated by the compiler will use `alloc_jemalloc` by default (where available).
272.
by shepmaster 11y ago
It's also spelled "Nickel.rs", as shown in the link ^_^
273.
by shepmaster 11y ago
If I understand the keyword correctly, it's not really needed in Rust. The Rust compiler keeps very close track of who has a reference (many immutable or one mutable) to a value. There isn't really "accidental" aliasing.
274.
by shepmaster 11y ago
I've seen a lot of interest recently in using Rust in an FFI context. I started the Omnibus to collect a set of examples that people can just use to get going. I'd love to get feedback (here or in the github issues[1]) about mis
275.
The Rust FFI Omnibus – Soliciting Suggestions and Feedback(jakegoulding.com)
4 points by shepmaster 11y ago|1 comments
276.
Rock, Paper, Scissors in Clojure using core.typed and core.async(github.com)
1 points by shepmaster 12y ago|0 comments
277.
Type-directed TDD in Rust(github.com)
2 points by shepmaster 12y ago|0 comments
278.
Accessibility: The Missing Ingredient(alistapart.com)
4 points by shepmaster 12y ago|0 comments
279.
A little dip into Ruby's Marshal format (Part 1 / 3)(jakegoulding.com)
1 points by shepmaster 14y ago|0 comments
280.
Refactor and make changes in different commits(jakegoulding.com)
5 points by shepmaster 14y ago|0 comments
281.
Finding a race condition in Capybara with Selenium(jakegoulding.com)
4 points by shepmaster 14y ago|1 comments
282.
The stages of code review(jakegoulding.com)
1 points by shepmaster 14y ago|0 comments
283.
Test double terminology - The misuse of the term "mock"(jakegoulding.com)
1 points by shepmaster 15y ago|0 comments
284.
When refactoring isn't refactoring(jakegoulding.com)
5 points by shepmaster 15y ago|0 comments
285.
Coderetreat: A first-time facilitator’s view(andrewcox.org)
1 points by shepmaster 15y ago|0 comments
286.
What I've learned about testing over the last year(jakegoulding.com)
3 points by shepmaster 15y ago|0 comments
287.
by shepmaster 15y ago
In addition to your point, when writing in a language like Java, the overhead of writing code makes doing things the right way (in this case, using a design pattern) harder. Steve's example of the Strategy pattern is a good example of this.
288.
by shepmaster 15y ago
Steve states: "objects > functions. At least in the context of getting stuff done in Ruby". I completely agree that one should write idiomatic code. When you write Haskell, you write idiomatic Haskell. When you write Ruby, you should wr
289.
by shepmaster 15y ago
I think that he's referring to a quote from Dijkstra: "Computer science is no more about computers than astronomy is about telescopes." [1] Said another way: it's just a joke :-). [1] http://thinkexist.com/quotation/computer_science_is_no_
290.
by shepmaster 15y ago
Pittsburgh, PA Vivisimo is hiring application developers, systems programmers, and QA folks to work on our top notch information retrieval products. We code and test in a variety of languages including C, Java, and Ruby. http://vivisimo.c
291.
by shepmaster 16y ago
Ah, I think I understand your point now... correct me if Im wrong, but I think you are mostly pointing out how my headline is sensationalist. I'd probably agree with that, and blame it on my inexperience with "hardcore" Gantt charts. :-) My
292.
by shepmaster 16y ago
I certainly didn't mean to suggest that creating mock objects is free. In the second graph, I added an extra week to develop the application logic and the UI. Originally these were scheduled to take 2 weeks, so 1 week is a pretty big chunk
293.
by shepmaster 16y ago
Great point, but does having multiple predecessors negate the argument? Each predecessor is simply another set of mock objects to create. The idea is that Gantt charts show an explicit dependency graph, but mock objects allow you to break t
294.
How mock objects make Gantt charts (more) useless(jakegoulding.posterous.com)
15 points by shepmaster 16y ago|10 comments
295.
by shepmaster 16y ago
Same here - having the DAG up and being able to change where things point easily is awesome. If I were pressed to explain git without being in person, I rather liked the Git Parable.
296.
SQLite, 64-bit integers, and the impossible number(jakegoulding.posterous.com)
2 points by shepmaster 16y ago|0 comments