hp

16 ms·

91.
by hp 15y ago
EasyGit, single script, very well thought out, longstanding tested project, doesn't "conflict with" or conceal the underlying git just fixes up the UI. http://people.gnome.org/~newren/eg/ https://github.com/blog/333-easy-git
92.
by hp 15y ago
here is a great post from Owen Taylor in 1999 after this idea was repeatedly raised for the "g" stack on Linux: http://mail.gnome.org/archives/gnome-list/1999-December/msg0... it kept coming up, too: http://mail.gnome.org/archives/gtk-de
93.
by hp 15y ago
as someone who has used libpng I'd describe it as an example of why this is a terrible idea.
94.
by hp 15y ago
The Scala community is more of a blend on this front. It has FP aficionados, but it's also in production use and has commercial contributors focusing on practical issues. If Scala continues to gain popularity, it will probably continue to g
95.
by hp 15y ago
The bug in this post is thinking that if you have someone willing to contribute feature X to an open source project, they were also available to contribute feature Y. Open source patches are all itch-scratchings. For Scala macros, it's a re
96.
by hp 15y ago
Play is really not a large amount of code though and it's all in one source tree. It generally doesn't have a lot of "layers" compared to even something like Tomcat; the stack just doesn't get as deep. I've had an easy time digging in to th
97.
by hp 15y ago
"They didn't take a patch on one occasion, and then we had a couple never-diagnosed bugs that we think could have been in the framework." Fair enough, but I wouldn't switch to an inferior framework over it.
98.
by hp 15y ago
An alternative to C++ in this situation is to have a C core or set of C libraries, with bindings up to something like JavaScript or Lua. World of Warcraft, Emacs, Firefox are a few popular examples of that architecture. GNOME 3 works this w
99.
by hp 15y ago
it seems to allow duplicate keys but drops all but one. I have no idea if this is correct since the JSON spec doesn't really cover it. personally I think the spec should ban it because it means you need to parse the closing brace for an obj
100.
by hp 15y ago
A standing desk eliminated my arm and wrist pain, for whatever reason. I think I move around more when standing and maybe tend to rest some body weight on my arms when sitting.
101.
by hp 15y ago
Don't know what to tell you. I was in the room and writing the code on a lot of this, and what you're saying doesn't correspond to the whys and the whats that were on the whiteboard at that time. "It is hard to have two smart, outspoken, an
102.
by hp 15y ago
yeah, it's a tradeoff. If the software does more, then the software is more complex... OK, but, sometimes it's nice that it does more. People are used to other systems (iOS, Android, Windows, MacOS) and those are setting the bar pretty high
103.
by hp 15y ago
This article is not well-informed. I worked on or sat next to people who worked on a lot of the stuff mentioned. So you can take me as biased or as having a clue or both as you wish. A general point, the changes described here have been ove
104.
by hp 15y ago
Yeah, it sucks. It's pretty hard to fix though, one of those bugs where the multi-week or even multi-month effort to fix it probably isn't ever going to make sense to anybody. (Say IDLE in particular is bothering you; you could probably spe
105.
by hp 15y ago
Back in the era this is talking about, I ported the Tk text widget over to GTK+ which became GTK's still-used text widget (GtkTextView). I think the author is right that it was a mistake to ignore Linux. It didn't have the desktop user mark
106.
by hp 15y ago
That said, I'm not sure UI matching the implementation is the problem with git's UI; it's more that git's UI is inconsistent, has poorly-chosen names for commands/options, and has bad default behaviors.
107.
by hp 15y ago
Elijah has a nice detailed breakdown of the EasyGit UI rationale as well: http://people.gnome.org/~newren/eg/git-eg-differences.html I've been using EasyGit for years, it's very good and addresses exactly the complaint made in this articl
108.
by hp 15y ago
One source of Scala's design is Java interoperability, much as C++ has to live with its C legacy. This compromise may also be why people are able to use Scala in practice, though; they need to talk to Java libraries or need the performance
109.
by hp 15y ago
I found it essential to read Martin Odersky's Programming in Scala book - if you haven't then I recommend it. It makes many things clear that can be hard to pick up using only the free online resources. There's also a new docs site and it's
110.
by hp 15y ago
To me, a big advantage of Scala's "enrichment" over monkey-patching in Ruby or JS is that it isn't global. That is, you have to import the enrichment. Another code module in the program won't be unexpectedly affected by it. In practice, I a
111.
by hp 15y ago
On Heroku, you can use any Scala version that SBT will use. I even used parallel collections in the sample app: http://devcenter.heroku.com/articles/scaling-out-with-scala-...
112.
by hp 15y ago
Play support came out a while ago: http://blog.heroku.com/archives/2011/8/29/play/ One trick with play-scala is that the default welcome page is broken because it depends on a module that's only enabled in dev mode, and Heroku runs play
113.
by hp 15y ago
If you follow the "how to run it on Heroku" section in the README here: https://github.com/typesafehub/webwords/tree/heroku-devcente... then you would get something like this running app here: http://webwords.herokuapp.com/ That's prett
114.
by hp 15y ago
hey, I was just idly chattering about C and the way people in general often approach it. Not intended to be a review of an unwritten book or imply that you plan to approach it in any particular way. I am a bad ass of course. But I thought i
115.
by hp 15y ago
I was just going off on a generic tangent, obviously I don't know what your book will be like. Just talking about C since it's 1am and vaguely on-topic.
116.
by hp 15y ago
Maybe "low level" is a bit ambiguous. I certainly agree that C is most appropriate when you are "low in the stack," just above the operating system and maybe implementing something like a virtual machine. I don't make a habit of writing stu
117.
by hp 15y ago
Agreed, but it's still sort of a weird case, I think. The considerations related to things like memory allocation, performance, concurrency, internationalization, security, IO, etc. are pretty different in the kernel.
118.
by hp 15y ago
Ohloh says I've changed at least half million lines of C code ( https://www.ohloh.net/accounts/rhp/positions/total ) Play me a tiny violin ;-) What kinda bugs me is that whenever people go to teach C, they make out like it _has_ to be a low
119.
by hp 15y ago
It would be pretty simple conceptually (maybe not practically) to make node.js work in an actor-like way, here's a piece of toy code I wrote that does it for JS (not node, but no reason the same couldn't be done for node): http://blog.omet
120.
by hp 16y ago
if nobody could show their portfolio, then nobody would get an advantage from doing so. but since people can show it in the programming world, you are at a disadvantage if you don't. if a civil engineer had some way to show what they could

More ›