If knowledge of how to use macros was better, I think some of the macro FUD would go away. If you're not using macros then you might as well not use a LISP. I'd agree though that using macros improperly leads to all kinds of problems.
258 karma · joined August 21, 2012
If knowledge of how to use macros was better, I think some of the macro FUD would go away. If you're not using macros then you might as well not use a LISP. I'd agree though that using macros improperly leads to all kinds of problems.
To start, you could try making a 1-to-1 mapping by closing over the web worker methods with cljs functions. To keep track of the web workers, you could put them in a cljs map inside an atom. This is what servant does to handle web workers.[0]
The other interfaces could be handled in a similar way by closing over methods with functions too.
It might be better after brute forcing a basic 1-to-1 style to create one or more layers of abstraction to make the interop more usable and Clojure-y. There could be cljs deftypes for the threads or web workers which hook into core cljs protocols[1] so that cljs.core functions would work over them. Macros could add syntactic sugar to lower level functions to make your API easier to use (looks like servant did that).
There are lots of options for how to build a good API depending on how powerful an abstraction you want to make for yourself. Getting basic support for the library could work by just closing over functions and adding some glue though.
[0]https://github.com/MarcoPolo/servant/blob/master/src/cljs/se...
[1]https://github.com/clojure/clojurescript/blob/master/src/mai...
webcomponents.org has tons more info about web components.
I think it's pretty awesome to get templating, custom elements, scoped styling, and HTML imports as a browser feature without JS frameworks. It'll be neat to have as an option in the future when browser support gets better and people start using it.
NOVA used to have a neat video about it so I just linked to the first thing after searching for nanoshells. Here's an article about it at least:
IIRC brain tumors can be really tricky to treat and this method showed some promise. The testing on mice was working well back around 2010 and I figured it would be further along by now.
Remote: No
Willing to relocate: Yes, please
Technologies: HTML5/CSS3/JavaScript, Clojure(Script), ElasticSearch, Ring+Compojure, Progressive Web Apps, React, Om/Reagent, Polymer, Google Closure, Node.js
Résumé/CV: https://edbabcock.com/resume
Email: Ed@edbabcock.com
I have been developing mostly in Clojure for the past few years. In my last job, I worked primarily as a back-end Clojure developer. I have experience with web front-ends too and just finished a Senior Web Developer Nanodegree from Udacity last month.
I am looking for either a front-end position or back-end if it's in a functional language like Clojure.
Thanks for your consideration :)
idk, there could be client-side Bitcoin mining if somehow you can find a breakthrough mining algorithm (maybe using Algebraic Cryptography or Satisfiability Theory) that runs an order of magnitude faster than current and users are OK with running it.
e-commerce could have some kind of payment system with escrow where you could charge a small operating tax. Hard to ensure everything works though since all code is running client-side, which can't be trusted.
pay per download probably still works.
others?
I agree that ads, tracking, IAP, and other stuff should be left out.
It's weird to think about services which as the creator you really have no control over once it's released (I'm thinking of Freenet or GNU social style services). There aren't any services that I know of which are both 100% distributed and making money on the regular.
Not really well thought out ideas, just putting stuff out there.
The biggest outstanding problem that nobody seems to be talking about though is how to monetize a decentralized business. With the current web there are lots of options that have varying degrees of nastiness for their users but ultimately pay developer salaries: 3rd party ads, IP/API licensing, pay for product, data collection, in-app purchases, e-commerce, etc. Since not all of these carry over well to a decentralized web, how can it be profitable for companies?
The problem of building a generic, distributed platform (or at least some technology for decentralized services) probably comes first but putting money behind its development couldn't hurt. I think if engineers won't be able to make money with it, then it will be much harder to sustain development in the long run.
Any ideas for this part?
Most P2P systems use things like DHTs to relate IP addresses to the overlay network's addressing protocol so encrypted routing can be done over the internet.
It shouldn't be too hard to self host a service but the caveat is that you'd have to access it through whatever P2P network you choose. As an example, it'd be easy to host your own services through a Tor hidden site or I2P. I don't know much about how sandstorm works but things like a git server should be easy to host over P2P. The bandwidth over Tor and others can be really slow but some P2P protocols have high bandwidth[2].
[1] https://en.wikipedia.org/wiki/Overlay_network [2] https://code.google.com/archive/p/phantom/
For less commonly used commands you usually can do M-x [command-name] or just memorize a random Emacs keybinding.
In the end I thought it was 100% worth it for working in LISP dialects like Clojure, Scheme, and Common LISP. The good REPL integration and the ability to control everything makes Emacs pretty fun.
Remote: Yes
Willing to relocate: Yes
Technologies: Clojure(Script), Om/Reagent, ElasticSearch, Datomic, SQL, HTML/CSS, Linux (some PHP, Java, and JavaScript too)
Résumé/CV: https://EdBabcock.com/resume
Email: (str "Ed" '@EdBabcock ".com")
I'm looking for a mid-level, full time position, preferably as a Clojure or ClojureScript developer. I have worked as a full stack developer in the past and would be comfortable working on both front-end and back-end tasks.
While I specialize in Clojure(Script), I am aware that it's not the most common commonly used language. I also have experience working in PHP, Java, and JavaScript and would be open to a more junior position in them if available.
Yeah, the reader macros on that wikibooks page are built into the language. The best the Clojure offers are tagged literals[1] but these run after the code is read (so they're not reader macros).
[1] http://clojure.org/reader?responseToken=08f63df34820f8da967f...
Unfortunately, this spot still has lots of early merging. Some high traffic areas have special lanes for zipper merging, but I think the emphasis is on changing drivers' habits through public service announcements rather than redoing the lane structure.
While I'm away from home I use a usb-stick with a custom dev envrionment all set up. Then just backup and fetch files from there as needed. Something like this gets the job done: rsync -avze ssh ~/my/backupfile user@(home ip address):~/backup/location
Probably a bit weird to understand but this is just one example command for backing up a local file (there are more advanced options too).
http://www.publishersweekly.com/pw/by-topic/columns-and-blog...
Why use DRM? Demand an alternative, buy a physical copy, or holdout. Hopefully the ship will begin turning around soon.
A nicer sshuttle command for VPN may be: $ ./sshuttle -v --remote=server_USERNAME@serverIP:port_number --dns 0/0
If you sshuttle to your home router you may be able to samba or nfs to the ARM on your home network (using tcp and udp, I think).
Alternatively, SSHFS or something more normal could be used for mounting the ARM filesystem without a VPN but if you want to try Samba over SSH you could try: $ ssh -C -c blowfish -L[host_bind_port]:localhost:445 server_USERNAME@serverIP $ mkdir /Users/username/mount_spot $ mount -t smbfs //server_USERNAME@localhost:[host_bind_port]/server_drive ~/mount_spot
Tools like rsync over SSH and UFTP are also nice for moving large files to and from the ARM server.
I tried making an instructible on this last week but it's kinda poor: http://www.instructables.com/id/Personal-ARM-Cloud-Server/