flatline3

35 ms·

361.
by flatline3 14y ago
It's perfectly equivalently poor. What makes those platform APIs useful are all the tools they provide to simplify the creation of great, well-performing UIs that exceed the user's expectations.
362.
by flatline3 14y ago
I don't really understand why this provides a better environment for producing top-quality media applications over the platforms on the market today.
363.
by flatline3 14y ago
> And now you can see why JavaScript was made a first-class language for the WinRT (not Windows RT) API - content-consumption via touch is now going to be a big feature for Win 8 and nothing serves this better than HTML5/JavaScript. I
364.
by flatline3 14y ago
I've been using Windows 7 on and off. It's largely OK, but not great. Cygwin is awful, the open-source community is nascent (at best!), the development tools are a OK, but semi-free (VS Studio Express is free, but if you need more, Visual S
365.
by flatline3 14y ago
It seems more valuable to judge them by the fruits of their labor. This applies to more than just file systems.
366.
by flatline3 14y ago
FreeBSD ships with ZFS in their standard kernel, and has for years, if you're willing to consider an OS other than Linux.
367.
by flatline3 14y ago
What will you replace it with? That's my problem -- I require Mac OS X.
368.
by flatline3 14y ago
This isn't hacker news. It's DHH and car racing fan news. Spend less time hero-worshipping and more time being a hero.
369.
by flatline3 14y ago
Or, build it yourself very easily (I did so in a weekend) using XMPP + Strophe.js: http://strophe.im/
370.
by flatline3 14y ago
Carbon et al was an issue. Rosetta wasn't there until the very end. You can get an idea of the lower level work by diffing the divergent Darwin sources from the time (two source branches were used, and Apple released distinct x86/ppc source
371.
by flatline3 14y ago
Speaking as someone that had Marklar running on a beige box under my desk at Apple, this story is close enough to the reality of things. As people noted, there was half a decade between NeXTStep and OS X, and a lot of room for bitrot and di
372.
by flatline3 14y ago
This exactly mirrors our use of (and experience with) protobuf. I think that people over-value human readability when using non-checked encoders that require debugging the serialized data.
373.
by flatline3 14y ago
Putting it into public version control and accepting patches is a fork -- name it something new. If it's just a mirror, then call it that, and don't accept patches. This is basic OSS politeness and the cultural norm. Only recently has Githu
374.
by flatline3 14y ago
I like JSPX. Designers and HTML front-end engineers intuitively understand custom tags, and any imperative non-declarative logic should ideally be pushed back into Java or a custom JSP tag, such that you rarely see it.
375.
by flatline3 14y ago
Forking a project has always been an option of last resort in open source. Doing so while stealing the name is downright nasty.
376.
by flatline3 14y ago
To elaborate, it's rude to take someone else's project, and under the same name, publish it elsewhere. This has been a rule of open-source for a very long time. If you're going to fork someone else's project, either rename, or call your git
377.
by flatline3 14y ago
In the case of the NetBSD project, users and developers were the same people, and there wasn't much interest. When looking for people with the necessary skills to contribute, you'll find that the majority qualified individuals are Mac OS X
378.
by flatline3 14y ago
That would be rude.
379.
by flatline3 14y ago
I'm going to take christina_b seriously because this is a seriously complex problem, and it's impressive that she's gotten so far with it. I don't expect that any of the people saying "you should use github to get contributors" actually h
380.
by flatline3 14y ago
The choice of SCM is the least important factor when it comes to contributors to a genuinely complex problem like this one.
381.
by flatline3 14y ago
As cool as this project is, virtualizing OS X -- or emulating an ARM system for iOS -- is much more likely to be useful for testing iOS internals / lower-level bits without requiring Apple hardware. For example: http://www.iemu.org/index.p
382.
by flatline3 14y ago
There are a number of past projects very similar to this one. The two I remember off-hand: - http://hcpnet.free.fr/applebsd.html -- NetBSD in-kernel COMPAT_MACH / COMPAT_DARWIN support. This got to the point of being able to run XDarwin,