513 karma · joined June 6, 2014
I believe the 1st amendment provides for this.
My hope is that Google does not settle the case with Oracle, as I'm sure this case shows up at the top of their legal budget.
So the agencies that are paid to do research / competitive intelligence and rate a competitor's viewership numbers using a highly biased sample pool using a method (audio sampling) that is highly unreliable and wildly inaccurate (so much so, that for all intents and purposes, it should be classified a divining rod), has reported exactly the numbers that the TV Network execs expect -- numbers that color network TV as still favorable for advertisers? Well, I'm amazed.
Thank you, TSA, for protecting us from making small and minor mistakes!
partition_id = well_distributed_hash(normalize_domain_name(<domain>))
really don't think this would be an issue, or even a concern, as 1 billion writes per second are "Google-levels" of writes. One would likely run out of financial resources supporting an expansion of 86 terrabytes / day (assuming 1kb minimum new data per write), far faster than you would ever max out the capabilities of the technology.
It's more a finance/business exercise to determine if revenue inflows would actually meet, cover, or exceed revenue outflows on a project like this. You can always make the technology scale and meet the demand.
And actually, yes, I looked at your site, your LinkedIn profile, and whatever. You don't know what you're talking about and are not any good at technology. You may think you are, but you're not. For reference, rank 80,000 is "hobbyist." Break the top 5,000, and we'll discuss whether or not you need xcache or HHVM.
Actually, no. This discussion is about development and configuration of a workstation for development and the necessity to have the developers run the same unit tests that also need to run the same on the integration servers (not Windows). For the vast majority of cases, actually yes, all one needs is a apt-get/yum/port install of the package dependencies and that's it -- most if not all "out of the box" configuration for most developers will work just fine for the development environment (ie, the developer's workstation). Additionally, those system package managers provide a much simpler and easier way for a developer to manage system updates (have you ever used Windows update? it's unbelievably slow).
And, to your above reference, re: Ubuntu, while I've personally never had any issues with using Ubuntu as a production server, I wouldn't recommend doing that (and do not use it where I have direct authority/control or choice), because for production one would want 'debian stable' (and is what I have recommended for years). One would not want a headless server environment to use Ubuntu, as the differences that make 'Ubuntu' vs 'debian testing' are primarily downstream additions that are only good/applicable to the desktop and do nothing to help the underlying stability of the system.
To emphasize here, I am not discussing simple one-off Wordpress deployments for your hobbyist blog that likely no one reads, and that you most likely don't even need xcache for. I highly doubt you have the traffic volumes wherein xcache would actually show significant improvement/performance over nothing at all (do you even understand what xcache does?). And if you did, you should likely move on to HHVM (which, btw, is production ready, and works out of the box for the most popular distributions).
Quite frankly, the fact that you are discussing compiling a .so for xcache on Ubuntu shows just how far behind the time you are on the state of Ubuntu and PHP as there are working xcache apt repositories that you can use quite simply, please see: https://www.dotdeb.org/ . Your anecdotal failure of having a problem building a single .so (which you shouldn't have been wasting time compiling yourself anyways), is only representative of your particular issues and is not at all representative of how software is actually used, developed, tested, and deployed in large, significant (monetarily, culturally, politically, etc) systems.
Additionally, the most basic "best practices" for system administration would call for the use of packages wherever possible. Manually compiling extensions (or other dependencies) that you did not write (xcache), directly, on your production linode instance, really shows that you are likely treating your server instances as pets and not as cattle, which doesn't really work in the cloud / server 'farm' paradigm. It also shows that you're likely not working in a large, audited secure environment wherein all commands/actions/configuration changes need to be signed off / logged. I'm also going to guess you do not understand the intricacies of continuous integration/deployment, security, and many other basic aspects/tenets of system administration, and, thus, do not fully grasp why what you did -- manually compiling a .so on a server -- is such a no-no.
Please understand, I am coming from a background of building large, mission-critical software projects with large, geographically diverse teams who have varied skillset levels (from newbie to guru), and that the necessity to conform to corporate and governmental regulations (audit or otherwise) is non-negotiable, and thus certain things must be done (automated testing, etc) which in turn limits the scope of what can be done with minimal resources/time. Bringing this back to relevancy and 'Spartan', this is why without working ports that fit into existing toolchains (unit testing on Unix-likes), it will never be a relevant (nor in my book, "modern") browser unless it magically gains significant market share overnight. I find that highly unlikely since Windows is a dying platform, and the majority of users have shifted to mobile. I also find it highly unlikely that Windows will start to outpace Android or iOS anytime soon as a mobile platform. While I welcome the new browser, Microsoft is unlikely to gain the needed marketshare unless they give developers the features/tools they need to integrate into existing, well-developed workflows/infrastructure. That isn't going to happen without a Unix port.
Also, the thing here is that it's not optimal, and there's also non-trivial licensing costs when building large continuous integration/deployment systems. Additionally, I don't believe you would be very supportive of the experience on Windows if you were more familiar with what is possible on Linux, OSX or any other Unix, and if you had strong understanding/knowledge/command of the toolsets available on those ecosystems.
There is nothing fundamentally wrong with using Windows as a regular desktop environment (I'm forced to almost every day). It's actually a fairly good experience (from a desktop perspective), but it doesn't give developers and system admins true, powerful out of the box toolsets. For instance, installing PostgreSQL/MySQL/Apache/Nginx/or whatever on Windows is extremely painful, cumbersome, and not standardized across systems. Conversely, compare this: (yum|apt-get|port) install (postgresql|mysql|apache|nginx).
To do proper automation on large sets of Windows systems, you need Windows Server, Active Directory, and Domains properly setup configured, and licensed, especially if you have any kind of security policy and need to push / control updates from a central server and keep strict control of / standardized versions across systems (for instance, in a strict, actually PCI compliant environment). Why bother with any of that when all of that mess / problem is taken care of by your distribution (OSX/Linux/etc), as one would expect it to be. There's no dependency graphs with large sets of Unix-likes, unlike in the Windows ecosystem -- and that really is the main issue here.
Additionally, there are many other large databases (Hadoop, etc) that will scale linearly. While it may not be ideal for this use case, but a proper multi-master setup with many read slaves in either PostgreSQL or MySQL could be described as being able to scale linearly to some unspecified extremely large upper limit (see work done previously at Yahoo, Google, Amazon, et al). Much of this also depends on what you define as scaling linearly (are you looking for linear scaling for memory, reads, writes, storage, latency, costs, etc?).
Real time stats for pages, sites, hosts for a shared annotation system across browsers doesn't mesh well with your initial condition of "privacy concerns."
[0] http://techblog.netflix.com/2011/11/benchmarking-cassandra-s...
The quickest, fastest way that I know to get the Unix shell commands/stuff up on Windows is to use the packaged Git installation (which I referenced in my previous post), but the issue then is that if you have ever dealt with semi-large code bases that involve one or two separate programming languages, then every developer has to track down all the various packages (if they exist), build them, or otherwise install / get them to work. This is often why in companies Windows devs are just given a shell account on a central Linux server to run their unit tests, or runs them inside a VM on Windows. Windows doesn't have any kind of central package manager akin to apt / yum / port for Unix systems that would allow for easy and quick installation of widely used open source software. While they are trying to push their own package manager on Windows, I don't see that as being successful anytime soon.
And, ultimately this approach (of installing Unix toolchains on Windows) is just a hackish workaround, and doesn't address the root issue that the most powerful automation toolsets in the world are all written / developed on / designed for Unix-like systems, and they simply do not run natively on Windows. If Microsoft genuinely wants to join the modern development ecosystem, they will provide cross platform versions of their browser and keep them synced and up to date across platforms, so that they can be plugged into the existing infrastructure (and thus investment) companies have made in their development environments, automated testing, and continuous integration/deployment.
Microsoft can not ignore (by virtue of exclusion) Linux / OSX (and other Unix-es) if they want wide-spread adoption of this new Spartan browser, simply because they want to push the Windows platform. That strategy may have worked in the late 90s, early 2000s when there was no other options for a readily usable, simple user experience desktop platform , but that's not the case any more.
I honestly couldn't care much if they supported Android or iOS. I'm simply pointing out that the competition -- Chrome, Firefox, Opera -- all have these features, and are what people consider "modern." You can't go backwards on featureset and still be considered modern.
One of the primary reasons why Microsoft needs to immediately halt, backpedal and release a version that can run on Linux/OSX (beyond the obvious need to port to Android/iOS) is that so many high quality sites are tested using automated testing suites (through Selenium, or otherwise), and those testing instances typically run through bash shells / scripts. While I'm sure you could jury-rig Windows 10 to do that (I've used bash on Windows previously, via Git Bash), you would need to rewrite extensive build and testing tool chains to use non-Unix-y commands --- and even then, you'll likely find many of the open source libraries you rely on are broken, unmaintained, or otherwise unusable on Windows.
As an anecdote, and fairly recently, I actually tried getting unit tests for a pre-existing, fairly sizable project with 10s of developers and many hundreds of thousands of lines of code to run on Windows, and realized it was cheaper to just hand all the developers Mac Books than to either train them on installing Unix tool chains on Windows, or on "properly" using Linux -- especially considering they were not responsible to write the unit tests, just run them. It's also much easier to cross-build for Windows from a Unix system, thus it was possible to completely eliminate Windows in the release process almost completely, other than for later manual testing/verification that can't be automated anyways.
This is actually fairly trivial to do right.