Sorry, still sore about that repackaged and bricked WRT54g.. If anyone's going to brick things, it'll be ME! :)
515 karma · joined December 6, 2009
Sorry, still sore about that repackaged and bricked WRT54g.. If anyone's going to brick things, it'll be ME! :)
I don't think they are leaving it on the table, I think their schedule of fees means they are carving out a spot that the rental companies totally ignored.
When dealing with JNI, both Maven and SBT have to delegate the task to less pure build systems. For projects that cannot nest nicely above a very high and consistent layer of abstraction, these "archaic" systems are essential because of their lack of interfering abstractions. They observe a different definition of "simple", instead of being "simple to use in a specific problem domain" they go to "simple to adapt to a different problem domain."
For projects simple enough to be manageable with those build systems, I'm already happily using make and a reasonably GNU environment (if not GNU's compiler.) For the other projects, where recursive makes and complexity becomes a distraction, I've already exceeded the parameters where these build systems are comfortable.
The acid test for me is MOSREF. MOSREF has a fairly portable ANSI C virtual machine and linker, but the compiler is metacircular and obviously nobody is going to target MOSREF for their packaged in recipes. One build system after another drove me to distraction trying to simplify MOSREF's process -- despite the fact that each step was quite simple, the order of steps was very tricky, especially when hacking on the compiler.
Redo looks like a better evolution away from Make for me, since it means no new syntax and it doesn't try to protect me from bash. Thanks for the recommendation -- I don't work much on MOSREF anymore, but maybe this offers an escape route from "go build", which has been a bit of pest for configuration management.
Trello has been a big hit with my wife who is a writer. She uses it to organize scenes, chapters and various snippets before integrating them into her draft. I've tried introducing various storyboarding applications to her with very high resistance -- Trello was the only thing that really "took" with her.
If you just want to jot down notes and don't need to organize them, Trello's probably just a bit too rich an interface. Once you've got more balls in the air and jugglers in the mix, Trello becomes a lot more interesting.
These are three things that are not offered as "turnkey" for a reason. They have serious usability impacts and in all but the most disruptive configurations tend to be incomplete and leaky. Trying to provide them in a magic appliance is either dangerous or improbable.
Then I fled. And a lot of other people probably will, too -- Adobe has a lot of things to make up for with the kind of people who could actually make a meaningful contribution.
What I took away from it? Apple is paying market rates for its semi-skilled employees in a high unemployment market. The market is the problem, not the employer.
If you are going to measure the distance and use that as a basis -- just report the distance. Otherwise, the estimates based on time will just flip the bozo bit in your customers.
Something I’ve been doing recently is making a screen recording of my talks using QuickTime on my Mac."
This is really true, and really good advice. Organizers have a lot on their hands leading up to a conference, and, after, getting recordings posted languishes until they manage to recover enough of their personal lives to start ramping up for the next.
I've had several instances where I've given a talk, been very happy with the response, and then realized that I had no way to share it with a wider audience except trundling off to the next conference. Next time, I'm making my peace with a screen recording app.
There are a number of the usual installation and adoption issues with FreeBSD and Illumos / OpenIndiana. I love the FreeBSD community, and using dtrace again is a joy. I just don't like having to use them for things I already have solved in Linux or can quickly find documented on either Ubuntu or Arch's wikis.
It's nice after the OS wars to be able to say "well, it's easier for us to use linux because it has a broad user base." :)
It's not transfer speed that they seem to trade off for, it's access times. That may have been part of the problem -- our reads are extremely random over a very broad range of sectors. This isn't exactly a log or video server usage model. :)
These "green" hard drives tend to be very aggressive about parking heads and spinning down the platters. While this is fine if a disk is going to sit idle for a long period of time, in cases like an OS partition and memory buffering, these drives start destroying themselves spinning down and cranking up several times a minute.
We had 4 out of 16 fail one week after burn-in in a raidz configuration. We had plenty of hot spares for various reasons of paranoia, and they didn't go all at once, so we recovered and replaced the entire batch with Constellations.
The only positive note was that we are now firmly in love with zpools and zfs.. It made egregious hardware failure a manageable problem.
I respect the idea of trying to offset our common diet of interactive and distracting social media and news trolling. But in the context of a "To Do" list, I prefer the immediacy of something like Trello -- an endorphine fueled feedback loop encouraging people to get things done seems more practical for me.
The Best Buy in my neighborhood is more convenient by about 90m than the Apple Store. But I generally refuse to go to Best Buy for anything that I can't find on a pegboard, like cables or a USB drive. Everything else, I get random unavailability, clueless salespeople, and a really strange mildew smell from the upholstery.
Smells like doom, really.
GoSublime and go.vim both integrate gofmt into the editor; you start to miss it when refactoring, because you can just shrug and say "gofmt will clean it up when I save" when you move a block to a different function or indent level.
I agree with the grandparent -- seeing non-gofmt code is jarring and deliberately distracting. It's like someone writing an entire Python program with nothing but lambdas.
Same distro, same config, and half the batch has a death wish, shutting down the fan in response to increased CPU temp.
Using Go in a professional setting really isn't a technical challenge. The biggest concern is if you have to grow your team, you're either going to have to teach Go (which isn't that hard -- I've seen two different people come from dynamic languages and pick the basics up in a week) or hire people who know Go (often already happily employed).
To further mangle Charles V: "I speak Spanish to God, German to my horse, and Go to connections that might make me wait."
Due to Go's pervasive use of io.Writer / io.Reader / net.Conn interfaces, once you have the problem of loading keys sorted, everything else is the same as writing a plain old TCP/IP listener. Configuring TLS will always be a pain -- decades, committees and broken implementations have seen to that.
As for actually verifying passwords and session integrity, Go's crypto packages are also pretty straightforwards and composable. The crypto/hmac [4] package is easily combined with various implementations of hash.Hash. In exchange for this simplicity, though, Go gives you plenty of opportunity to emulate LinkedIn and blow your own foot off, forgetting salt and common sense. There are plenty of higher level packages that offer to do it for you. (Blow your foot off, or hash your passwords -- I recommend reading implementations to decide which. :))
Also of interest when dealing with writing webapps in Go, the database/sql [5] package is an important abstraction. Since it is a more recent package, it often doesn't show up in google searches for sqlite, postgres, etc. This can give an impression that Go's database support is fragmented.
1 -- http://golang.org/pkg/net/http/#ListenAndServeTLS
2 -- http://golang.org/pkg/net/http/#Transport
3 -- http://golang.org/pkg/crypto/tls/#Listener