(I do Android and iOS for a living)
990 karma · joined September 27, 2009
(I do Android and iOS for a living)
Thanks.
Unless you mean to suggest continuously integrating developer commits to trunk into the live branch, in which case, no, that's a horrible idea. Not every bug manifests itself that quickly.
As for merging, my memory is pretty hazy but I believe pushing and merging went hand in hand, and stuff that conflicted meant someone wasn't communicating yet working on the same code as someone else. Code was often documented with its owner. The code review utility at the time would (I think) take that✝, and (I think) run a blame and automatically CC those people on the code review, so it could be caught before it went out.
✝ Unless that was just done by convention so you know who to ask about a bit of code you might need to revise. Sorry my memory is unreliable on that bit.
Also, Java may be verbose, but the way I see it, the programmer didn't have to write more than a few letters out of each word before letting autocomplete do its job, and has the added benefit of an IDE that can reason logically about his code. I'm not anti-dynamic language by any stretch (I love Python), and Java is almost never visually beautiful, but extensive machine-assisted code reasoning abilities can be awfully useful.
More cool stuff: Writing recurring background jobs: http://www.playframework.org/documentation/1.2/jobs
Async HTTP/Continuations and a note on WebSockets: http://www.playframework.org/documentation/1.2/asynchronous
If anyone wants to mess around with Play + Scala + facebook connect, I rewrote the play-fbconnect module in Scala: https://github.com/toulouse/play-scala-facebook-connect-exam..., although in doing so I coupled it with the controller using it, throwing away the Java reflection, as it didn't seem to work well with my classes for some reason. Not the best way of doing things, to be sure. As it turns out, though, writing a Play module is quite straightforward, in Java and in Scala (!!! awesome!), so there's no reason I couldn't rip it back out.
It's definitely a work in progress, and I'm still learning Scala in whatever time I can spare from work, but if anyone wants to learn Scala and Play with me, it could be fun!
The thing is, I actually take offense to people who call a language ugly. Just because it doesn't prioritize the kind of expressiveness you desire doesn't mean whining about it makes you cool or a better programmer. What everyone here who says 'Objective-C is ugly and outdated' should be decrying is the relative lack of choice of implementation language for iOS.
I like Objective-C, because I look at it from the point of view of C. It's a systems language with support for OOP that I find completely satisfactory, which prioritizes flexibility, predictability, and maintainability over raw speed and constraints. On the other hand, I love that Java and similar languages in its family can reason a great deal about classes and their interactions, and I love that Python and Ruby step out of the programmer's way when you just want to make something --
-- But to write software for an embedded platform that can be natively fast when needed (the C part of ObjC), but offer a solid OOP abstraction, and to reconcile these two needs as well as expose some of the lower-level workings of the OOP system to the developer when they really know what they're doing and need it? I think Objective-C is hard to beat there. It's a language fitting for projects from small-medium size to very large. It's not the only language that I feel can scale like this, but again; that's a problem (availability of alternatives), not a reflection on Objective-C's language. The language combines the low-level with the high-level, and is many things for many needs, yet is without the rigidity of a Java-style type system, yet is also without the inability or difficulty to deeply reason about high-level language structures as in some more dynamic languages, Objective-C manages to allow sufficient and sloppy "it just works" implementations, for when you just need to bang out code that works well enough, as well as encourages polished and well-engineered APIs (such as Cocoa's).
I think Objective-C balances these concerns - small or big, dynamic or inflexible, as well as the reality of mobile devices' limited memory capacity, particularly well. I would make a more cogent argument were I more awake and if I did not have a splitting headache, but I think it's extremely unfair to call (or imply it) Objective-C strange, or that it survives merely because Cocoa would not be supported if another language were to replace it. Although I may be in the minority (at least amongst those who are posting here in this thread), I think it is a fantastic language.
* NSInvocation should serve the same purpose in most cases.
* I find the block syntax atrocious if compared to Lisp lambdas. It's not that bad. Blocks are objects, so you're creating an object, with all the same predictable retain/release semantics. Maybe a few gotchas if you're not reading the documentation and realize you should avoid retain loops. Hardly different from Java, only it's easier to miss it in Java, because you never release, anywhere.
I don't think this is invalid, but at the same time, it seems like it's suggesting that, rather than searching for a need you want solved and framing it in terms of a realistic goal and whittling it down to a compelling product, you should be identifying someone else's need and building that product.
A fun idea without a plan may need some serious thought and modifications to make it a compelling product, but I think that perhaps a compelling idea with no fun is pretty difficult to make fun.
Perhaps my core philosophical objection can be summarized in contrast to this:
> Any sufficiently big market will give you tons of interesting ideas. Why do you need to come up one of your own?
I don't think this is a market-driven approach, in the sense that the market is merely setting the context, and it's still interest-driven, and you're still searching (and hopefully coming up with) ideas you find interesting. Just identifying exploitable needs isn't necessarily going to expose something you're going to enjoy.
In my opinion, any fair observer would have to conclude that Android is still about as open as it always was. This isn't necessarily hypocritical; I have never viewed Android as "open".
Now, personally, I think that it's more customizable and flexible because it isn't mature enough as a platform to be able to afford to lock down APIs. Not that I think that the end result of an API should be to lock it down, but orthogonality in a SDK can be very beautiful, as it is with Cocoa touch.
Now take a look back and notice just how deeply the telephone companies influence politics. Do I even need to provide examples? Think about Net Neutrality. Facebook doesn't just want it, it depends on it to keep its costs down and its site fast.
Explain to me, how can they battle this without having the ear of Washington? It's a good strategic move, and I expect that far more of their clout will be focused on maintaining the status quo than federally mandating Facebook use. As an organization with a great deal of hackers (as in hacker news 'hacker'), I think that enforcing a global ID would face major resistance even within the company. Far more plausible is that they're looking for influence to keep the internet open, as that is in their best interests.
Guess I'm not going after all.
> The hardware-optimized packet format of IPv6 is worth basically zero to us on modern technology
No. Basically zero is not zero.
> Every HTTP Server on Earth Could Be Sharing a Single IP Address and You Wouldn't Know The Difference
No. Though he lampshades this towards the end, he still gets it wrong - the SNI extensions to TLS allow secured virtual hosting on recent browsers - but not older ones, where it simply just doesn't work.
> if I accidentally leave a daemon running on my server, it's not automatically a security hole
No. NATs are unfairly equated with firewalls. There is nothing stopping a firewall from preventing connections to a computer that is now addressable from the outside, just as they do today. If you are running a publicly-deployed service and do not restrict inbound and outbound traffic, I would advise you to do it, now.
> Because of the way TCP and UDP work, you can safely NAT many, many private addresses onto a single public address
> I won't go into this too much, other than to say that there are already various NAT traversal protocols out there, and as NAT gets more and more annoyingly mandatory, those protocols and implementations are going to get much better.
No. UDP hole-punching isn't that simple. It requires a third party, and implementations of NAT are very heterogeneous. Arguing that it's possible to do safely (and implicitly, on a large scale) is ignoring reality.
So his solution to a newer spec that, despite a rough and in-progress transition, accounts for legacy, is to move to a newer, incomplete, solution that breaks abstraction boundaries, is incompatible with current network hardware, requires major server and router rearchitecture? No. A thousand times no.
> NAT (and DHCP) has largely eliminated another big motivation behind IPv6
No. I find it laughable that he argues that he argues, essentially, that private IP subnets make handling DNS simple, while simultaneously (later) arguing that DNS service records should be used so people don't have to remember IPs + ports, while also saying "So here's what I really hate about IPv6: 16-byte (32 hex digit) addresses are impossible to memorize". How about, instead of kludging up a hack nobody's on board with, using an existing solution with widespread support? Stateless autoconfig or DHCPv6 do the same job.
> If GUIDs were a good idea, we would use them instead of URLs
No. What the ever-living FUCK. Did he not already read his own words about DNS? So sysadmins now have to copy-paste instead of memorizing IPs, or spend a few extra lines in their host files or DNS servers aliasing it to some DNS address. This is a simple and sufficient solution.
> But furthermore, DNS on the Internet is still a steaming pile of hopeless garbage. When I bring my laptop to my friend's house and join his WLAN, why can't he ping it by name? Because DNS sucks. Why doesn't it show up by name in his router control panel so he knows which box is using his bandwidth? Because DNS sucks. Why can the Windows server browse list see it by name (sometimes, after a random delay, if you're lucky), even though DNS can't? Because they got sick of DNS and wrote something that works.
> Of course, I can't really take credit for this idea. It's already been invented and is being used in a few places. (links to wikipedia article on SRV records)
No. JESUS CHRIST. s/because DNS sucks/because Windows sucks/ - for some of the stuff he's talking about, multicast DNS fixed. Oh, and by the way, Bonjour has been using multicast DNS + SRV records for freakin' years, and works pleasantly on !Windows - and it does so for IPv6, as well. I can't speak for Windows because I have had the pleasure of not using it for anything other than games for the past several years. I have set up a Time Machine service on a FreeBSD box that advertised itself as such with no problem whatsoever.
> IPv4 addresses aren't really 32-bits. They're actually 48 bits: a 32-bit IP address plus a 16-bit port number
No! This is like saying that your keyboard and mouse are actually a mouseboard, because they're almost always together. IPv6 still uses TCP - doing what he suggests would not only be a massive kludge, it would obsolete an incredible amount of infrastructure already in place - this cannot be implemented incrementally! Throwing the bathtub out with the bathwater in order to destroy a working layer of abstraction is insane!
> This proposal has very minor chicken-and-egg problems No! Unless by 'minor' you mean bigger than the fucking universe.
This article is founded on so many faulty premises it proposes a technologically intensive non-solution to a problem that suffers from much worse flaws the solution it complains about. Readers should disregard any and all advice proffered by this blog post, as it is grossly inaccurate and incorrect.
IMO, ideas need harsh critique, and it's not always easy or worth it to spend the extra time padding the conversation to soften your point - it can even be counterproductive.
So while I won't say that someone is stupid or dumb for suggesting the idea, I may say an idea was not well thought out if it really isn't. I expect my peers to do the same, because we're not going to see which ideas stick if we bicker over how we iterate on them.
http://probablyinteractive.com/2010/8/20/ios-interactive-con...
I'm planning on trying it out whenever I get time.
It's not. That's not easy, that's a fundamentally realignment of the product.
What if you're a normal guy and you get famous from some youtube video? Now you're a celebrity. Pay up - but oops, you're broke? Fuck it, you're off Twitter.
Not gonna work. :/
git tag -a tagname
git push --tags
git checkout tagname
http://git.or.cz/course/svn.html
BTW, it's also worth noting that hg can have tag merge conflicts (http://mercurial.selenic.com/wiki/GitConcepts), which is just weird.
For anyone looking to learn more about git, I haven't found a better resource than this talk: (video) http://blip.tv/file/4094854 (slides) http://www.slideshare.net/chacon/getting-git
That said, I migrated from hg to git, and I love them both way more than svn.