nupark2

37 ms·

301.
by nupark2 15y ago
> But it's basically impossible to judge the talent of a software engineer by looking at their past code -- there's too much context required. I'm not really sure how this is true. I find that I can judge a software engineer very accu
302.
by nupark2 15y ago
Could you expand on your position regarding the relative cost of developing a native vs. flash application? Is it simply constrained supply? The limited number of Objective-C developers, or that native development requires a higher skill le
303.
by nupark2 15y ago
The animation is glitchy on an iPad 1, and it doesn't feel anything like the native UIScrollView's paging support. It's sort of acceptable enough for a web page, but it's not a replacement for a native UIScrollView.
304.
by nupark2 15y ago
> ... so that web apps can more seamlessly replace alternatives. One native feature down (at least until Apple evolves it again), countless pile of more features to go. This is a losing battle.
305.
by nupark2 15y ago
Ads on mobile is going to be a marginal business compared to the web. Screen real estate is at an absolute premium, alternative revenue models exist (such as charging your users directly), and there's a high barrier to any call to action (s
306.
by nupark2 15y ago
> ... this kind of 'protectionism' doesn't make much sense. This is obviously open to some debate; your condescending declarations of certainty are grating and rude.
307.
by nupark2 15y ago
I'm not sure why you think geeks unilaterally oppose protectionism (or that we'd even call it protectionism). Seems like a broad, inaccurate generalization. Personally, I like keeping money in the local economy when it makes sense to.
308.
by nupark2 15y ago
It would be slow in terms of fixing the oceans of OSS code that doesn't cleanly configure/compile in a cross-compilation environment, rather than the compilation process itself.
309.
by nupark2 15y ago
I sure hope this doesn't mean a move away from release formalism. Github -- due in large part to complex social cues around encouraging public forking in a top-level namespace -- seems to encourage the assumption that developers will track
310.
by nupark2 15y ago
Cheers to the peer comment regarding HN discourse. Unfortunately (?) I have more :) > This doesn't affect interchanging Objective-C types though. Yes, the arity and order are important, but the compiler doesn't enforce anything beyond
311.
by nupark2 15y ago
> Did you even try my example? No compiler warnings are generated (nor should the be). Only because it managed to match on a defined method type. If a class declaration hadn't been found at compile time with the given declared metho
312.
by nupark2 15y ago
Most of what you just said is simply not true. Without the method types, the compiler will print a warning, infer the wrong ABI and generate the wrong code. If am ambigious match ia made, the wrong code will be generated. What you just wrot
313.
by nupark2 15y ago
Objective-C is typed, and that's considered (by Apple, and most developers) as a feature, not just a legacy inheritance from C.
314.
by nupark2 15y ago
When you remove the C bits, Objective-C and Ruby use the same type system, conceptually speaking. They are both descendant from Smalltalk; the main feature differences really come down to the syntax alone. Objective-C is typed -- not just
315.
by nupark2 15y ago
I wouldn't say useless -- just a lot less useful. Maybe they'll add cycle handling on top of it later.
316.
by nupark2 15y ago
A non-runtime type system. First class familiar Objective-C-style messaging and block syntax. Stable, mature, well defined language invariants on par with Apple's requirements for its own APIs and languages. "Objective-C without the C"
317.
by nupark2 15y ago
I don't think it's quite the certainty you're making it out to be. Ruby is a step sideways, if not backwards, from Apple's current strategy. We're far more likely to see an Objective-C without the C than we are to see Ruby as a first class
318.
by nupark2 15y ago
Unfortunately, it doesn't handle cycles in the object graph[1], which was almost the entire reason I wanted GC. Manually dealing with cycles is one of the worst parts of working with blocks (the other is the lack of parameterized types).
319.
by nupark2 15y ago
I agree with this sentiment, but not the expression of it.
320.
by nupark2 15y ago
> If anyone is interested to learn what can be done, send me an email. Are you checking that the Mach-O binary is encrypted? I'm not aware of that being worked around by any of the automated tools (and it an approach that is widely di
321.
by nupark2 15y ago
This sounds more like a narrative that supports your entrenched position, personal worldview, and target audience, rather than an actual useful summary of the many lucid arguments put forward in the original link.
322.
by nupark2 15y ago
Local concurrency and shared memory can be used to improve performance of operations that may be distributed; assuming proper implementations, a shared memory mailbox will always be cheaper than forcing multiple data copies of network/pip
323.
by nupark2 15y ago
This is a false dichotomy; taking advantage of language-level parallelism doesn't prevent you from supporting a full-blown distributed architecture. In fact, if so inclined, you can model your distributed architecture on top of language-lev
324.
by nupark2 15y ago
Your experience sounds great. I agree that we don't need to abandon college. However, I do believe we must abandon the idea that a college degree is a mechanism by which we can accurately determine an potential employee's baseline educati
325.
by nupark2 15y ago
Personally, I'd rather have the vendors kill off Flash, forcing the web to switch to alternatives, resulting in an environment where I never need (or want) to use Flash. I'm even willing to suffer slightly for this in the meantime -- even i
326.
by nupark2 15y ago
The Ruby/Rails way: When the drama created by oversized egos inevitably comes to a head, fork/replace the project and badmouth the other guys. Allow me to rewrite your statement to be ruby-drama-free: We have been working on several JavaScr
327.
by nupark2 15y ago
Driving the exact same commuter route day after day is a very different experience than driving for fun. I do enjoy driving for fun, but no more than I enjoy other activities. What I don't enjoy is the incredible commitment and mental invol
328.
by nupark2 15y ago
Sorry, looks like you replied before I edited down my comment. I mentioned $3000 laptops (and how unwise it is to pull one out); Occasionally I see a tourist with: * A MacBook Pro balanced precariously on their lap. * Sitting right next to
329.
by nupark2 15y ago
> Internet and cell phone access is not available underground, and most of the NYC subway line is underground. I have no trouble reading a book on my iPhone on the subway. The ride just isn't long enough to make having internet access
330.
by nupark2 15y ago
That's 1 to 1.5 wasted hours, every single day. That's not what I would call a reasonable (or productive) use of time. I'd rather spend that time somewhere more pleasant than the freeway, doing something more pleasant than driving a car. I

More ›