The Conference Manifesto.
Original URL: http://opinionator.blogs.nytimes.com/2015/05/04/the-conference-manifesto/?smid=fb-nytimes&smtyp=cur&bicmp=AD&bicmlukp=WT.mc_id&bicmst=1409232722000&bicmet=1419773522000
The Conference Manifesto.
This tutorial shows the installation of a Ubuntu 15.04 minimal server in detail with many screenshots. The purpose of the guide is to show the basic installation of Ubuntu 15.04 that can be used as basis for our other Ubuntu 15.04 tutorials here at howtoforge like our perfect server guides.
Dual-core? Quad-core? Octa-core? Yesterday’s news (I kid, I kid…). Why do I say this? Intel, one of the top processor manufacturers (arguably the best) has released some new Xeon processors with up to 18 dual-threaded cores. Yes, you are reading that correctly — 18! While Xeon processors are not meant for consumers, they can be used by them, although pricing usually prevents that.
The cost of these new Xeon E7 v3 processors start at $1,224 and go all the way up to $7,175. While this is likely — OK, definitely — way too expensive for people like you and I, for the Enterprise, this may be acceptable for workstations and server environments.
Diane Bryant, SVP and GM of the Data Center Group, Intel says, “in the digital services economy, success or failure can depend on how quickly businesses act on insight from vast stores of data. The Intel Xeon processor E7 v3 family is the engine for accelerating business intelligence through real-time analytics, enabling businesses to improve customer satisfaction through more personalized products and services, generate new revenue streams and enhance operational efficiency”.
Intel shares the following information on the new chips.
|Processor||Number of Cores||TDP|
|Intel® Xeon® Processor E7-8890 v3 (45M Cache, 2.50 GHz)||18||165 W|
|Intel® Xeon® Processor E7-8880L v3 (45M Cache, 2.00 GHz)||18||115 W|
|Intel® Xeon® Processor E7-8880 v3 (45M Cache, 2.30 GHz)||18||150 W|
|Intel® Xeon® Processor E7-8870 v3 (45M Cache, 2.10 GHz)||18||140 W|
|Intel® Xeon® Processor E7-8867 v3 (45M Cache, 2.50 GHz)||16||165 W|
|Intel® Xeon® Processor E7-8860 v3 (40M Cache, 2.20 GHz)||16||140 W|
|Intel® Xeon® Processor E7-4850 v3 (35M Cache, 2.20 GHz)||14||115 W|
|Intel® Xeon® Processor E7-4830 v3 (30M Cache, 2.10 GHz)||12||115 W|
|Intel® Xeon® Processor E7-4820 v3 (25M Cache, 1.90 GHz)||10||115 W|
|Intel® Xeon® Processor E7-8891 v3 (45M Cache, 2.80 GHz)||10||165 W|
|Intel® Xeon® Processor E7-4809 v3 (20M Cache, 2.00 GHz)||8||115 W|
|Intel® Xeon® Processor E7-8893 v3 (45M Cache, 3.20 GHz)||4||140 W|
So, will your next gaming machine be powered by an 18 core Xeon? Probably not (unless you are a maniac like Barnacules!). Hopefully 18 core chips will trickle down to consumers in the future, though.
Keep in mind the focus of these processors — business. IT managers may be hesitant to spend the big bucks on such expensive chips, but depending on the business needs, it may be worth it. Time is money and if you can get results quicker, it may be a valuable investment.
Do you work in IT in a decision-making role? Will you be taking advantage of Xeon E7 v3 processors? Tell me in the comments.
After 4.5 years of service, the PageSpeed Service team regretfully decided
that the time had come to re-focus their efforts elsewhere and on
5th May announced that PageSpeed Service will
be turned down. If you are using PageSpeed Service, you must change your
DNS before 3rd August 2015 or your site(s) will become
completely unavailable on that date.
Explicit notification will soon be sent to users that we believe are
affected, however you should not rely on this! We recommend that you
login to the
console and look at your list of domains. Anything that shows up as
“Enabled” is at risk.
For every site currently using PageSpeed Service, you will have to make DNS
changes to remove your site safely. The console will offer advice if you try and
delete a domain that is live. Remember, you must do this by
3rd August or your site will break.
Please see the detailed instructions
If you wish to continue enjoying many of the performance benefits of
PageSpeed Service, the same Google PageSpeed technology is available in a number
of alternative packagings which you may wish to consider using. These
alternatives are not affected by the deprecation announcement and continue to
Many web hosting providers already integrate PageSpeed. If you are
using such a web hosting provider, check your provider’s documentation. It may
be as simple as checking a box in your provider’s control panel.
There are PageSpeed modules for many common web servers. If you run your
own web server, you may wish to install one of these.
Google has developed the open-source Apache module
mod_pagespeed. Pre-built binary modules for Apache 2.2 and 2.4 are
available. For more information,
Google has also developed a plugin for Nginx. Due to the nature of Nginx,
it must be compiled from source. You can read the instructions
The folks over at WeAmp have a commercial port of PageSpeed to Microsoft
IIS. You can learn more about it at
WeAmp has ported PageSpeed to Apache Traffic server. More information,
including build instructions, can be found at
OpenLiteSpeed supports a PageSpeed module that you can compile and load
into your webserver. Please see their instructions
If you wish to continue using cloud-based product,
Optimizer integrates Google PageSpeed with their CDN offering.
Alternatively, many CDNs offer comparable functionality that does not use
I wrote this piece as part of the business planning process for UserLand Software.
I thought it was interesting, a continuation of Outliners & Programming and wanted to get it on my personal site.
This is my story, told from my point of view…
An Apple product?
I started development of Frontier after leaving Symantec in the spring of 1988. It was the result of several meetings with Jean-Louis Gassee, then the top product guy at Apple. The goal was to come up with a scripting tool for the Macintosh OS, that would be similar in depth and power to the shell languages on Unix and the batch language on MS-DOS.
I designed, along with the scripting language, a new Finder, based on outlining. The scripting language was very simple, based on the syntax of Pascal, and deeply integrated into the new Finder. 2click on a script and a window opens in the new Finder. One layer, the scripting is deeply part of the OS.
I presented a prototype of the software six months later and negotiated with Apple for its acquisition. We couldn’t agree on terms, so we decided to do two products, one by them, and another by UserLand, and we agreed to make them compatible.
Developing alongside Apple
I decided to go deeper and more powerful, believing that Apple would basically implement the idea I showed them. They had the source code to the Finder, I didn’t.
I think it was sometime in 1990 that Doug Baron came on. For a while both of us worked on the Frontier kernel, but as we got closer to shipping Frontier 1.0, I concentrated on working in the environment, and Doug concentrated on developing the environment. That’s why so much of the functionality of Frontier is implemented in scripts.
All the while, Apple was cancelling and restarting the AppleScript effort quite a few times. Eventually they settled down, and in January 1992, just as we were shipping Frontier 1.0, they held a one day developer’s conference for developers on scripting in SF.
Frontier sold well for the first few months, we were building distribution (mostly mail order, but a few dealers carried the product) when in May 1992 they announced AppleScript publicly. Our sales plumetted.
We shipped Frontier 2.0, in September 1992 and Frontier 3.0 in December 1993. We tried a lot of angles to co-exist with Apple’s at-first vaporous product, and by early 1994, shipping product. But we were dependent on working with other developers for much of our functionality, and for the most part the developers ignored Frontier in favor of AppleScript.
We did deliver compatibility with Apple’s protocols, we actually supported them more completely than Apple did, but there was still work involved to glue our software to other products. That work fell to us or our community, but we were stretched very thin and not prospering, and our community consisted mostly of non-commercial programmers (not all though) so the results were mostly quirky and difficult to use.
In some cases we delivered superior results, as with THINK C and Quark XPress, but even then people in the Mac world of the early-mid 90s were still revolving around Apple. It was totally an uphill battle, and we couldn’t capture any hilltops.
Out of gas
I ran out of gas, personally, in January 1994, and stopped working on Frontier. Dave Carlick was there at the meeting I had with Jack Russo and Doug Baron in early 1994, where I made it clear that I was finished, didn’t want to fight with Apple anymore, and was leaving.
Jack and Doug and Carolyn Franz and John Baxter made a go of it, I’m not even sure what they did, I stayed far away. I appreciate the effort they made, but it was clear by May 1995 that it wasn’t working. By then I had a new career as a web writer. DaveNet started in late 1994, I became a contributing editor at HotWired, one of the hottest early websites.
Sometime in the spring of 1995 Mason Hale sent me a challenging email. I don’t remember exactly what he said, but it went something like this. “Someone told me I should take a look at Frontier because it’s exactly what I’m looking for in a CGI scripting environment.”
I barely understood what a CGI scripting environment was. Later I understood that he was right. In doing Frontier as a Mac scripting environment, we were putting together an ideal environment for Internet programming. The object database, native interpreter, multithreaded runtime, outliner, interapplication communication. All these were essential pieces, and they tied together.
At the time I was working on my second generation of website management software, AutoWeb. The experience is documented in DaveNet. I was more interested in applying some of what we learned in publishing systems built with Frontier and Quark to the new problem of website management.
At HotWired, we had a simple groupware system (the WebMonkey guys just documented it publicly on their website late last week). I wanted to do the same thing they were doing on Unix on the Mac. Lots more Macs out there, I figured!
Mason’s email, the failure of the commercial effort, excitement over the Internet, and the success MacHTTP and Netscape were having, led me to the exciting turn we took in May 1995, we freed Frontier, renamed it Aretha, and uploaded the software to a website on hotwired.com.
We shipped some really buggy software! Tried a million ideas out. Web pages that contained scripts that ran on the client. A multi-user root, a BBS implemented in Frontier, a classified ads server, what else? A substantial stockpile of done or partially-done R&D.
I also did a third generation site manager, Clay Basket. The model was website development as a productivity app. But I hit a brick wall on this when I did a 1000-person site in February 1996, 24 Hours of Democracy. It’s become kind of a classic website, still gets a lot of hits. It’s a time capsule in a way.
Clay couldn’t handle it. I realized then that website work is groupware. Then in March 1996 I figured it out. We had the perfect environment for website development, Frontier! It wasn’t pretty like Clay, but it had everything I needed.
So I spent March-May doing the new framework in Frontier. In May 1996 I released Frontier 4.0. It was a big hit. I loved it. We attracted a new class of Frontier people to replace Mason and others who had gone onto other platforms.
I believed we had a hit, but for a variety of reasons, believed it couldn’t be a commercial success on the Mac. So I hired Doug back in the summer of 1996, and then Bob Bierman in the fall, to port the Frontier environment to Windows. Brent came on in early 1997 and I hired Matt Neuburg to write two tutorials for Frontier 4. In March Matt went to O’Reilly to work on their Frontier book.
Frontier 5 will ship in late January 1998 for Mac and Windows. Whatever features we’re committed to that don’t ship in 5.0 will ship in 5.1 (June 1998). For the forseeable future we are committed to simultaneous Mac and Windows releases. Our core user base still uses Macs, but a transition is happening. How that goes will influence our direction.
Whew! That was a lot of writing!
PPS: Jack Russo has comments.
A vulnerability within two widely used WordPress plugins is already being exploited by hackers, putting millions of WordPress sites at risk, according to a computer security firm.
The plugins are JetPack, a customization and performance tool, and Twenty Fifteen, used for infinite scrolling, wrote David Dede, a malware researcher with Sucuri. WordPress installs Twenty Fifteen by default, which increases the number of vulnerable sites.
Both plugins use a package called genericons, which contains vector icons embedded in a font. In the package, there is an insecure file called “example.html” which makes the package vulnerable, Dede wrote.
Kaplan University creates new “competency reports” for all 45,000 students, a move that adds momentum, and risks, for competency-based education’s spread.
The news that Google has officially discontinued the Nexus 7 line of tablets will be greeted with indifference or even outright enthusiasm by some. After all, the device has lately been causing a lot of vexation in the wake of Google’s rollout of Android 5.0 Lollipop – although at least that delivered on the original […]
The post Alas poor Nexus, I knew you well … appeared first on TeleRead: News and views on e-books, libraries, publishing and related topics.