HNHacker News
TopNewBestAskShowJobs

greenyouse

258 karma · joined August 21, 2012

ed@edbabcock.com
submissionscomments
greenyouse··on The Next Five Years of ClojureScript
I think macros can still be used for developing simple systems but it comes at a more difficult development cost. Unless you're used to macros, they're weird to write and there aren't many places to learn about macro design patterns (On LISP and LOL are good IMHO). There are examples of major projects that use macros effectively though. Look at core.logic, om.next, core.async, or many other large cljs projects.

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.

greenyouse··on Trane: a language for automating data science [video]
Research articles on the system are:

http://dai.lids.mit.edu/Trane.pdf

http://dai.lids.mit.edu/Pred_eng.pdf

greenyouse··on Macchiato: ClojureScript on the Server
It'd be doable but getting a nice Clojure-y API over it would take a little more work.

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...

greenyouse··on Spec-ulation – Rich Hickey [video]
When I was listening to the part about breakage vs accretion, I kept thinking back to the Nix pkg manager from NixOS. It does a pretty good job of separating out the artifacts by indexing them by version number and a hash of the username (i.e. artifact-name = sha($user) + $project-name + $semver). There have to be other examples of pkg managers that do this kind of thing too...
greenyouse··on Spec-ulation – Rich Hickey [video]
Hey, I usually take notes when reading or watching stuff. If you're willing to read through my semi-coherent org-mode notes, it summarizes the talk better than a full transcript.[0]

[0]http://pastebin.com/bmF0xc7y

greenyouse··on Introducing Custom Elements
This looks like it's for the custom elements part of the web components spec. Doing HTML templates is already supported in most browsers [0]. I think they were just trying to show how to create custom HTML tags and left out other parts because it would be outside the scope of the article.

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.

[0]http://caniuse.com/#feat=template

greenyouse··on Gold Nanoshell Cancer Therapy (2005)
Haha, wrong video sorry!

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:

http://www.pbs.org/wgbh/nova/body/halas-nanoshell.html

greenyouse··on Gold Nanoshell Cancer Therapy (2005)
Anyone know what happened to research on this? It seemed like a reasonable approach to treating some types of cancer like subcutaneous tumors and brain tumors. There's a wikipedia article[1] where the last reference is from 2011 and things were looking good at that point.

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.

[1]https://en.wikipedia.org/wiki/Nanoshell

greenyouse··on Ask HN: Who wants to be hired? (November 2016)
Location: Minneapolis, Minnesota

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 :)

greenyouse··on A decentralized web would give power back to the people online
I wasn't really suggesting that businesses keep using the same web 2.0 models. Just fishing for ideas for the distributed web. If teams are actually going to commit thousands or millions of work hours into making products, then there should be a way for them to be rewarded for their job. Making money isn't inherently evil, but making it at the users' expense is.

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.

greenyouse··on A decentralized web would give power back to the people online
The is awesome! I hope they're able to bring their vision of a decentralized web to fruition!

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?

greenyouse··on Samizdat – Platform for self-hosted, P2P, encrypted communication (2014)
Isn't this a problem that people solve using overlay networks[1]?

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/

greenyouse··on Facebook AI Research Team Open Source DeepMask and SharpMask
Or maybe more like Dennou Coil :) https://en.wikipedia.org/wiki/Denn%C5%8D_Coil
greenyouse··on Why GNU Emacs?
I had this problem a few years ago when I switched from Vim to Emacs. You could try writing your own evil-leader shortcuts for common commands + major mode commands. It initially takes a day or two to set up basic commands (like buffer switching, commands for your favourite programming language, and REPL stuff) but after that there's minimal tweaking to do.

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.

greenyouse··on Ask HN: Who wants to be hired? (February 2016)
Location: Minneapolis, MN

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.

greenyouse··on Let Over Lambda (2008)
> Clojure does not allow you to define your own reader macros

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...

greenyouse··on Regex Crossword
This is fun! I feel like it is also good practice for logic programming too. Combine the regexes and put one or all possible solutions into each cell of the matrix :)
greenyouse··on Washington, Minnesota officially endorse a “safer, faster” traffic merge
Hey, I'm from Minnesota. Here is a merge spot that I take pretty often: https://www.google.com/maps/@45.008271,-93.203054,3a,75y,63....

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.

greenyouse··on Replace Dropbox with BitTorrent Sync and a Raspberry Pi
I don't want to sound like a lamer but can't this basically be done with ssh and rsync? I've been storing and fetching files from my home cubox with a setup like this.

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).

greenyouse··on Outlawed by Amazon DRM
DRM isn't exactly great for authors or artists either. Here's a Doctorow article on DRM implications for book authors:

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.

greenyouse··on Never again be thwarted by restrictive “guest” wifi (e.g. on buses or airplanes)
Instead of using an Amazon machine, why not use a low-power ARM device? I have been running a small ARM computer at home for doing sshuttle, iodine, and samba over ssh (with port binding) for the past few weeks and it works very well. I know tcp over tcp is usually not good but it still works quickly for some reason. This costs less than a VM on Amazon and gives you more flexibility.

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/

← PreviousPage 5 of 5