This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-13
Channels
- # beginners (43)
- # boot (318)
- # cider (1)
- # cljs-dev (6)
- # clojure (30)
- # clojure-brasil (2)
- # clojure-korea (2)
- # clojure-russia (31)
- # clojure-spec (13)
- # clojure-uk (7)
- # clojurebridge (1)
- # clojurescript (17)
- # code-reviews (1)
- # cursive (2)
- # data-science (1)
- # datascript (10)
- # hoplon (116)
- # javascript (2)
- # juxt (1)
- # mount (2)
- # onyx (12)
- # parinfer (2)
- # pedestal (1)
- # protorepl (1)
- # re-frame (3)
- # ring (1)
- # untangled (1)
is there a project on github that has clojure as backend, clojurescript as frontend, that i can take a look at?
hey guys, got a general question about programming: How do you usually keep track of the state of your code base when hacking on a moderatly sized project? The problem I get all the time is that before I start, I only have a general idea about the implementation (something like a architectural diagram or a list of modules with their responsibilities). When I actually start coding, I need to decide on the concrete shape of my data or the calling conventions of my functions and those depend on my use cases and implementation difficulty. As a result I end up jumping all over the place in my code base and writing bits of stuff everywhere, most of the time I'll forget to implement a piece of code somewhere when I try to run it. How do you guys tackle this problem? or is there something wrong with my approach?
@akiroz We tend to write tests to describe the behavior we want (and now we also write clojure.spec definitions for the data). That serves as documentation and also drives our development.
Sounds like you need a little organization / focus. ๐ What tests help you do is focus on implementing exactly what's necessary to implement a specific scenario. If you think of something to touch later, that can actually be a good place to drop something like a 'TODO comment', since it's searchable. Then, once the test has passed, you can go back to all those marked points, fix anything you had in mind, decide whether to make new tests to cover scenarios you'd thought of along the way, etc.
Basically, give yourself a way to focus on one thing at once; leaving markers in the code for in-place modifications, tests for new slices of functionality to add, or perhaps a whole document for design directions to explore.
Then it's out of your head, on paper, searchable, revisitable, and you won't have to bounce around so much just to make sure you caught everything. ๐
@pivinis not sure exactly what youโre looking for. for Hello World Iโd recommend something like this: https://github.com/clojure/clojurescript/wiki/Quick-Start. For real-world apps, there are plenty. A good place to start looking might be https://github.com/omcljs/om under "Applications built with Om"
Hi! Would someone take a look at this question please? http://stackoverflow.com/questions/40573821/why-do-a-clojure-instant-uses-a-instead-of-a-when-describing-timezones
> otherwise, just use maps
that got my attention !
suppose I have my own namespace foo.http
and I have my function get
something like that
(defn get [url]
(clj/http url))
or u can use with-redefs
to redefine the get function to return the response - https://clojuredocs.org/clojure.core/with-redefs
Hi, I did an introductory "lunch and learn" lecture on Clojure at my workplace last week (some teams at my work use Clojure, some have never seen it). Here are the slides if anyone wants to use them for their own intro talk (as is or as a reference). https://docs.google.com/presentation/d/1GGqkAlBSmZtRAlGEylDjTioUbmdLEAcRenBbif8VZhA/edit?usp=sharing
What is the best way to recieve some 4700 images from a external api. I did this on ruby and I wonder if this can be made faster with clojure and maybe luminus
For the people who can read ruby . Here is the code I used for the reading : https://bitbucket.org/rwobben/proefopdracht/src/4383655298b8d8c777ab6c548a3f32b3dc54e568/lib/tasks/read_database2.rake?at=master&fileviewer=file-view-default
@roelofw Looked over ruby and multi-threading, and it seems to suffer the same issues with the Global Interpreter Lock as python, so multi-threading might not offer up as much of a performance increase as in clojure (at least it won't be as easy) There are several ways to receive from an external API quickly, but lets focus on being able to perform parallel requests. The preferred way might be via core.async, which offers the ability to perform several requests in parallel through either a thread-pool, or through an asynchronous event loop. Even if you don't end up using core.async, I recommend you read up on it, it makes a lot of parallel operations ten times easier.