I imagine an FPGA in every chipset would go a long way towards writing the software to put them to practical use, though that may also be wishful thinking on my part.
990 karma · joined September 27, 2009
I imagine an FPGA in every chipset would go a long way towards writing the software to put them to practical use, though that may also be wishful thinking on my part.
With the right programming model, 50x seems very, very reasonable, not even magical. A typical computer does a decently high amount of context-switching and cache-loading.
Your points are made in a needlessly provocative manner.
Tons of people roll their own interfaces to their source control, and a lot of people benefit from somewhat centralized repositories. Not only is there room for both, but I don't see any data indicating how prevalent private, non-GitHub repositories are, or how those would even be counted accurately given the distributed model
Almost nobody? Very few people use Mercurial? Nowhere good? Hell-bent on killing? Few people use it? very sad self-fulfilling prophesy? Jeez, there's opinionated, then there's recklessly authoritative. Mercurial isn't as popular as git, but neither are dependent on GitHub/bitbucket for continued relevance.
To address your point more directly, I personally think that merging the concepts of versioned data and developer tasks makes for less flexibility; I prefer simple, pluggable, and modular to integrated when it comes to version control.
> You're right in that a large degree of my preference owes itself to familiarity bordering on second nature – I gave IntelliJ another shot recently, and I didn't feel right adapting to it. Autocomplete was typically the very first keystroke I changed - to escape - so it was never frustrating to me. I'm also fond of an old plugin that generates class builders, which made creating immutable POJOs with autogenerated constructors/hash/equals/toString super fast and easy.
> Thanks for your reply!
Please make a more reasonable and detailed critique.
Sincerely,
Someone who prefers Eclipse over IntelliJ (strongly, I cannot STAND IntelliJ), Textmate, Atom, Sublime Text 3, Vim, Emacs, and NetBeans.
(EDIT: davnicwil, your reply to me disappeared. Was it deleted? I appreciated the discussion and had written a reply.)
From a language design point of view, the things needed to get a language to the point where it could successfully and efficiently compile itself would skew or re-order priorities in a much different fashion than if they were to focus on building and iterating on an applications and systems language.
tl;dr: LLVM and Clang and their assorted toolsets do quite a bit of valuable work; reinventing that to serve the language they're building is a feedback loop is a downside that also removes some upside from the equation, too.
Out of all of the art that is done I am pretty sure only a portion are a hook for a Kickstarter or marketing material.
The difference being, of course, that one would redistribute the original code under the FSL and so the work as a whole would remain licensed under it.
#define DISPATCH_SOURCE_TYPE_DATA_ADD
#define DISPATCH_SOURCE_TYPE_DATA_OR
#define DISPATCH_SOURCE_TYPE_MACH_RECV
#define DISPATCH_SOURCE_TYPE_MACH_SEND
#define DISPATCH_SOURCE_TYPE_PROC
#define DISPATCH_SOURCE_TYPE_READ
#define DISPATCH_SOURCE_TYPE_SIGNAL
#define DISPATCH_SOURCE_TYPE_TIMER
#define DISPATCH_SOURCE_TYPE_VNODE
#define DISPATCH_SOURCE_TYPE_WRITE
#define DISPATCH_SOURCE_TYPE_MEMORYPRESSUREHold on, it's not that we don't want to build cross-platform apps, at least not universally. In my case, it's because I believe the contortions involved in abstracting out multiple wildly-divergent APIs built for different languages to a common system runtime necessarily lowers fidelity and quality for both.
"Write once run anywhere" ends up being a lot harder than "Learn once write anywhere" - I'm hopeful that React Native will demonstrate the success of this approach on mobile (even though, personally, I wish there were a non-JS option).
> Those "whales" are going to want a more integrated solution, so Amazon, Google, and Msft will take their cloud services one step further--further away than Dell/VM will ever be able to take it: dedicated fiber for their largest customers. How? Any of these three can lour their existing client base as bait and cut a deal with the Verizon and ATTs of the world for bulk (dedicated) bandwidth purchases. And if they don't have enough existing clients (Azure) they can post a cash-bond guaranteeing revenues to the telecom (just like msft did with the record companies to sell music in Win8).
You're kidding, right? Dell has provided the solutions for two of those three companies. The datacenter segment of their business is both successful and demolishing its only real competitor: a crumbling HP.
Dell's able to build and deliver ridiculously energy efficient datacenters at scale, very quickly. And they do, for Microsoft, eBay, and a number of other companies.
Their competitive advantage on the hardware side is substantial. Controlling VMWare would catapult the software side of things very, very far forward. If they want to build a new cloud platform, they've got extremely strong fundamentals to launch it from. If not, well, they'll probably power whoever does build it in some way (and profit handsomely).
Also worth noting is that Sony cameras already run a customized and locked-down version of Android, though you wouldn't know from using it.
DK1&2 owner. I felt the same, but the Crescent Bay demo blew me the heck away. More amazing than experiencing the DK1 for the first time.
Then, recently, I tried the Oculus Touch demos. For an hour or so afterwards, I felt like reality was less real than the simulation, even despite its limitations. I felt like the realm of possibilities within that box was infinite, and real-life was limited in comparison.
Sure, that means it has some legacy bits that need to be supported, but to some degree that's the price of having a mature codebase.
Having compiled LLVM and rooted through its internals trying to implement a plugin, it looks pretty well-architected and internally consistent. Codebases that cover as much as LLVM+Clang do being that clean is a rare sight, IMO. And it's not slow.
reddit explicitly defined their language around harassment to mean:
> Systematic and/or continued actions to torment or demean someone in a way that would make a reasonable person (1) conclude that reddit is not a safe platform to express their ideas or participate in the conversation, or (2) fear for their safety or the safety of those around them.
http://www.redditblog.com/2015/05/promote-ideas-protect-peop...
Key words to pay attention to here are: systematic, continued, fear. This isn't about being a jerk, or even being a jerk randomly. It's about being a jerk in a targeted way, a lot and over time, in a very intentional way to the degree that it causes fear to speak up or fear for one's self.
Look at the extent to which reddit admins allow hateful speech so long as they don't step outside their boundaries, and you'll understand that they're actually sticking to that definition.
If that information is deleted, the difference between frizbee and reddit becomes so extremely marginal that one really wonders whether this really is a rationalization for allowing people to organize around threatening and stalking people online.
If that information is not removed, does such a site deserve to exist? It may pass some legal standard, but is that a site that differentiates itself in any way except in its support of systematic and continued online stalking??
No thanks.
No censorship as in no punishing the stalking and threatening of others?
Also no thanks.
I want free speech where people are free with their speech, not unrestrained speech (specifically) where people feel free to hurt others.
While I've thought that there might be interesting ways of editing code before, I have literally never once asked myself why programmers are "still programming" with text files. All things considered, structured text files are a pretty darn good way of describing program behavior.
Even if Apple is predictably bad about this, each instance of them bringing the hammer down is still a surprise, because that's the nature of the problem.