-
This weekend I ported the sfxr sound effect generator to TypeScript, mainly as an exercise in using TypeScript and webpack together.
-
ruby is dynamic enough that I wonder why they didn’t just add this as a library? I wrote a wrapper class that does safe navigation in python as a joke a few years ago:
-
Something like this? https://github.com/raganwald/andand
-
Well, ActiveSupport has
try!and Avdi Grimm’s Naught library has a Maybe(thing) . So it’s not like there aren’t approaches to doing this already in Ruby, but this is far terser.To add to the alternate name suggestions above, I heard somebody calling it the “claw of demeter operator” which I thought was funny.
My personal take on the operator: it’s going to make novice code a lot uglier, but it could be handy when used sparingly. For the most part I see it as a code smell, but that pattern is not going away so I guess embracing it in the language is alright.
-
-
It seems like a waste of effort to me, FWIW. It’s not at all practical to use a browser without javascript on today’s web, so only a tiny number of people would benefit. Having extra code to support an obscure feature increases the future maintenance burden of the site.
-
-
What is the motivation behind this? Do you frequently use a browser that doesn’t use JavaScript?
For the record, I’m not against this…
-
-
-
That is the wrong way to look at it. Unnecessarily running javascript, accepting cookies and generally being a negligent web user puts you and your privacy in harm. I use NoScript, RequestPolicy and Adblock with Firefox. After whitelisting all my main sites, I no longer need to even touch it, and my web experience is better because of this proactive discipline.
-
-
-
-
-
-
I built a lightweight promise library for javascript inspired by jQuery.Deferred. Yeah, there are a few of those already but I enjoyed making it.
-
I built a tiny library for making social network widgets (mainly Like/Share buttons with counters for facebook, linkedin, pinterest, github, gittip…), pulling the data straight from the source over AJAX with CORS and JSONP. This avoids loading all the crap the regular widgets shove down your pipe.
Been trying to come up with a name for it…
-
“low-pro-so”
-
-
Uh, no thanks. You can pry my JSON and YAML out of my cold, dead hands.
-
-
Yes, jcs fixed a bug I introduced in the code. Sorry about that, should be good now.
-
I don’t particularly like Go, for probably-subjective reasons, but I would still like to read technical articles about it. It seems obviously on-topic and relevant, so the request to stop posting about Go comes across as rude.
-
I believe Go is actively harming the software industry by providing a very incapable tool for building working software, yet it’s presented as a real alternative. I do not think it’s responsible to let others get introduced to such silliness.
-
-
I will have to disagree and claim that the suitability is an illusion.
-
-
-
No parametric polymorphism (i.e. generics) - let’s not even go past this point. It’s so fundamental that giving it up is accepting defeat by your programming language.
Types are proofs (see the Curry-Howard isomorphism) - this has many consequences but one is that we can use types to prove properties about values and functions. Easy, right? People will say “I don’t care about proving that an int is an int” but they’re missing a huge implications - one being: parametric functions create cases where there’s only a limited amount of implementations.
Given a function with the type:
a -> a(i.e.
aimpliesa)What are the possible implementation(s)? Let’s try to implement it:
parametric :: a -> a parametric a = _What can we put in the underscore hole? We need to produce an
a, what are the possibleavalues which we have in scope? The only reasonable answer we have isa. This means, that given the signaturea -> a, there is only a single implementation.We don’t need anything else from this function, no tests, no names, no comments - nothing but the type signature to know exactly what this function does.
That’s a pretty simple example, right? Let’s take a real world problem that I had yesterday:
I wanted a function which would take a list of disjunctive types and give me a list of just the right sides:
[Either3 a b c] -> [c]Now, I could write this function directly against the list and
Either3types but there’s a chance I could do something like:getRights :: [Either3 a b c] -> [c] getRights xs = []So, getting all the rights from my list returns an empty list - not what I want! If we make this type signature very generic, then we get to a place where we only have a single possible implementation:
unite :: (Monad m, Plus m, Foldable t) => m (t a) -> m a unite value = value >>= foldMapPlus returnHere are example usages:
unite [Right 1, Right 2, Left "Whoops", Middle False, Right 3] -- [1, 2, 3] unite [Just 1, Nothing, Just 2] -- [1, 2]Not only have we specified exactly what should happen in the type but we’ve gotten a function which works for infinite types.
I consider writing programs without free theorems to be absolutely archaic. Recommending for people to do exactly that (by advocating Go, for example) is harmful.
-
You didn’t actually say how it was harming the industry. You just stated that you prefer programming languages with certain properties.
Also, it’s clear that you care very deeply about advocating for the functional paradigm. It would help your case if you didn’t include flame bait in your comments. (For instance, I’ve used Go effectively. But your comments would have me believe that I’m just deluded. But I’ve also used Haskell effectively. Am I deluded about that, too?)
-
It’s not a preference, advocating programming without free theorems is harmful. I did say that:
I consider writing programs without free theorems to be absolutely archaic. Recommending for people to do exactly that (by advocating Go, for example) is harmful.
And yes, I believe it’s an illusion that Go is effective at solving problems.
-
-
-
-
-
-
-
Yes and I will, keeping in mind that Java is the most capable.
-
-
That’s exactly like saying “Let’s not talk about drugs because they’re bad.” Well, how do you tell others that drugs are bad without talking about them, discussing them, etc?
The same argument has been made about sex-ed and abstinence-only education. Guess what, when persons who’ve only been told “just don’t do it” do it and don’t know the first thing about the consequences, bad things happen.
So let the topic come up here. And if Go really is so terrible, then let it be discussed. Give others the opportunity to learn and understand what makes Go the “literally Hitler” of programming languages (or whatever might be good about it).
-
Let’s talk about drugs. Let’s not present drugs to people without experience, telling them that it’s a great idea.
-
-
-
-
-
This would probably have to be done server-side, otherwise you’d end up with pages with fewer stories (or even none, if you hide them all).
Compensating for that on the client-side would be… yucky.
Edit: re-read your suggestion and yes, if the stories are grayed out instead of hidden, then client-side is doable..
-
Agreed. I realized that when done client-side, you’d end up with gaps. Greyed-out would at least allow me to see that I’ve already read read the post (or I’m not interested etc) without rendering issues.
-
-
Yes it does. Of course, I have to open those posts to grey them out. If the post doesn’t interest me, this activity is a waste of time. If I’ve already read the post contents via the lobste.rs email, this is redundant.
I can see how this request is probably a niche desire though.
-
Actually, I agree it has some value.
On the serverside, though, it requires keeping track of every story that you’ve hidden and filtering on that. I guess that’s probably not that much worse than per-user filters we already have. Maybe the hidden stories could be “aged” out, so that you don’t accumulate too many over time.
-
-
-
-
-
I’ll be working on an iOS/Android client for lobste.rs called Pinchy!
I made a start on the iOS client over the weekend, and have some basic functionality done.
-
Cool! Have you seen this Github issue about a previous attempt? The API never fully materialized because OAuth scares me.
-
-
-
@mongey: Yes, even without an authenticated API, fetching JSON representations of pages would be much easier. Just stick .json at the end of a story ID like https://lobste.rs/s/e04ccq.json
-
-
-
-
-
-
-
-
tldr; lots of Storm related stuff
at the day job:
Building a new 64 node Storm 0.9.0.1 cluster at work. New offline jobseeker - job matching infrastructure to run inside of Storm.
at night:
More work on the book I’m coauthor of “Storm Applied”.
-
-
I like weekly threads, they build a semblance of community.
I set up a Dokku / postgres box and migrated all my stuff over from supervisor / SQLite this past weekend. There’s a bunch of miscellaneous cleanup stuff left.
I want to get back to contributing to Rust once I finish up writing the tests for autojump.
-
Yes, please let’s make this a tradition, asking “what are you working on this week”. It’s like a coarse-grained twitter for programmers and open-source projects.
I’m on vacation, but contemplating moving a project from sockets to zeromq (https://github.com/vjoel/tupelo) and writing a talk proposal for MountainWest Ruby Conf (http://mtnwestrubyconf.org).
-
-
Thanks for the tip. A little put off by “WARNING: nanomsg is still in alpha stage!”. Nanomsg has been mentioned twice before on lobste.rs, but without discussion:
https://lobste.rs/s/buukh6/nanomsg_mit-licensed_zeromq_alternative https://lobste.rs/s/9lmnfh/gettings_started_with_nanomsg_examples_in_c
I will start a new thread asking for comments on nanomsg vs zeromq.
-
-
-
-
-
After suffring the babel polyfill insanity, we switched to TypeScript for all our projects. Never going back to babel.