AmiMoJo writes "It looks like Mozilla are finally going to remove the much hated blink tag from the Gecko rendering engine that powers Firefox. Work to remove support for the tag, which was always non-standard and is not supported by the most popular HTML layout engines WebKit and Blink (Chrome, Safari, Opera, Android), is progressing and should show up in a future version of the browser." A comment attached to the discussion of this (not completed) move points out the odd possibility that Google's new Blink rendering engine may feature the blink tag via CSS animation, which would be "hilarious/awesome."

theodp writes "In search of the best corporate cafeteria in the world, Gourmet Live's Tanya Steel visited the Googleplex, where she found Petaluma chicken cacciatore, porcini-encrusted grass-fed beef, whole-wheat spaghetti pomodoro, and Parmesan-creamed onions on the menu in one of the search giant's 25 cafes. So, must all good things come to an end? The WSJ's Mark Maremont reports that it's debatable whether Silicon Valley's daily fringe-benefit meals are taxable, and the issue is now on the IRS's radar. 'What would a food tax on Google's meals look like for the average employee?' Maremont asks. 'Assuming a fair-market value of between $8 and $10 per meal, a Googler chowing down two squares a day could get dinged for taxes on an extra $4,000 to $5,000 a year.' That'd be just fine with UF tax-law Prof. Martin J. McMahon. 'I buy my lunch with after-tax dollars,' said McMahon. 'And I have to pay taxes to support free meals for those Google employees.'"

First time accepted submitter DW100 writes "Microsoft, Nokia and Oracle have taken it upon themselves to moan to the European Commission about Google's Android dominance, which they say is an underhand bid to control the entire mobile market. The firms are part of the FairSearch group, which has just filed a complaint that Google is using Android as a 'Trojan Horse' to take control of the mobile market and all the related advertising revenue. Microsoft would of course know all about this, being at the end of several similar anti-competitive complaints in the past."

colinneagle writes "This week, the team at Digia rolled out the first alpha release of Qt 5.1, which is slated to have the first round of support for Android and iOS, with full support coming in 5.2. The goal is to make 5.1 completely usable for building complete, shippable apps for both mobile platforms. That means Qt can now be used to build native, smooth applications on Linux, Windows, Android, iOS, MacOS X and even BlackBerry 10, all with an excellent integrated development environment – QtCreator. Coming with version 5.1 is also something called 'Qt Quick Controls' — which is a set of nice, reusable user interface controls. Currently, it is focused on Desktop applications, but is expanding to add touchscreen-specific features. And, importantly, this release also brings 'Qt Sensors' into play. 'Qt Sensors' are pretty much exactly what they sound like — access to hardware sensors on devices where they are available, with built-in motion gesture recognition. Definitely a big plus for Android and iOS applications."

snydeq writes "We need bare-bones Linux distros tailored for virtual machines or at least the option for installs, writes Deep End's Paul Venezia. 'As I prepped a new virtual server template the other day, it occurred to me that we need more virtualization-specific Linux distributions or at least specific VM-only options when performing an install. A few distros take steps in this direction, such as Ubuntu and OEL jeOS (just enough OS), but they're not necessarily tuned for virtual servers. For large installations, the distributions in use are typically highly customized on one side or the other — either built as templates and deployed to VMs, or deployed through the use of silent installers or scripts that install only the bits and pieces required for the job. However, these are all handled as one-offs. They're generally not available or suitable for general use.'"

twofishy writes "Struts 1, the venerable Java MVC Web framework, has reached End Of Life status, the Apache foundation has announced. In a sense, the move simply formalises what has already happened, as the Struts team have focused their efforts on version 2; the last release of Struts 1 was version 1.3.10 in December 2008. The change of status does mean however that, whilst the code and documentation will still be available, no further security patches or bug fixes will be issued."

The Python developers have been busy this weekend, releasing three new versions at different points on the Python continuum: 2.7.4 (a 2.7 series bugfix release), 3.2.4 (what's new), and production releases 3.3.1. Here's what's new in 3.3.1.

hypnosec writes "Mozilla has developed an open payment service API to support app purchases in Firefox OS, and has released a draft version allowing app developers to process payments. Pointing out the drawbacks of the different models for payments on the web that are currently available, Mozilla has revealed that it is looking to introduce a common web API that would make payments through web devices easier and more secure while being flexible and retaining today's checkout button features that are available for merchants. Partly based on Google Wallet, Mozilla's WebPayment API will remain open to ensure that it is used by a wide range of payment service providers. As a first step towards this, Mozilla has introduced the navigator.mozPay function, allowing web apps to accept payments."

First time accepted submitter Dawn Kawamoto writes "Employers stampeding into the U.S. Citizenship and Immigration Service to get their H-1B petitions filed before the cap is reached are getting the door slammed in their face today. The cap was hit in near record time of 5 days, compared to the 10 weeks it took last year to have more than enough petitions to fulfill the combined cap of 85,000 statutory and advanced degree H-1B petitions. While U.S. tech workers scream that they're losing out on jobs as H-1B workers are hired, employers are countering that the talent pool is lacking and they need to increase the cap. Of course, Congress is wrangling in on this one as to whether it's time to raise the bar."

hypnosec writes "WebKit developers have already started discussing the removal of Chrome- and Chromium-specific code from the rendering engine in a bid to make the code easier to maintain. Just a couple of days back, Google announced it will go ahead with a WebKit fork to develop a new browser engine — Blink. According to Google, having multiple rendering engines — just like multiple browsers — will allow for innovation as well as contribute toward a healthy open-web ecosystem. The discussion was started by Geoffery Garen, an Apple WebKit developer. He said Google's departure is an 'opportunity to streamline' the code of WebKit, which would eventually make development 'easier and more coherent for everyone.' Garen expects that developers who will be working on WebKit in the future should help to clean up the code. However, Adam Barth and Eric Seidel — two Google WebKit developers — have already offered their help." Google plans on making the switch to Blink in the stable Chrome release in around 10 weeks. They've posted a half-hour video explaining how the transition will work.

DaBombDotCom writes "R, a popular software environment for statistical computing and graphics, version 3.0.0 codename "Masked Marvel" was released. From the announcement: 'Major R releases have not previously marked great landslides in terms of new features. Rather, they represent that the codebase has developed to a new level of maturity. This is not going to be an exception to the rule. Version 3.0.0, as of this writing, contains only [one] really major new feature: The inclusion of long vectors (containing more than 2^31-1 elements!). More changes are likely to make it into the final release, but the main reason for having it as a new major release is that R over the last 8.5 years has reached a new level: we now have 64 bit support on all platforms, support for parallel processing, the Matrix package, and much more.'"

An anonymous reader writes with a link to this "CNET story about arguably the most important technical documents in Apple's early history: the source code, contract letters, schematics and notes for the creation of the Apple II Disk Operating System (DOS). From 1977 and 1978, these documents chronicle Apple's first OS and what made the Apple II into a serious computer for the masses, able to support killer apps like Visicalc and build the PC industry."

hypnosec writes "Activision and Raven Software game studios have open sourced a couple of their games so that people can play as well learn from the code. The gaming companies have released the source code of Star Wars Jedi Knight: Jedi Academy and Jedi Outcast through SourceForge."

An anonymous reader writes with this bit from The Next Web: "Mozilla and Samsung on Wednesday announced a new partnership to build a 'next generation' web browser engine called Servo. The ultimate goal is to bring the technology to Android and ARM, though the two companies have not shared a timeframe for a possible launch. With the help of Samsung, Mozilla is bringing both the Rust programming language as well as Servo to Android and ARM. Samsung's contribution so far has been an ARM backend to Rust as well as the build infrastructure necessary to cross-compile to Android. In fact, the code is available now on GitHub, as is the source for Rust and Servo." For those unfamiliar, Rust is Mozilla's new safe systems programming language (kind of like BitC), and Servo is their general project to write a brand new engine using Rust. Rust has an interesting memory model that eliminates much difficulty in reasoning about threaded programs. If you know what you're doing, they claim you can cross compile the code for Android, but no functionality guarantees have been made.

Niris writes "I am currently a senior in computer science, and am expecting to graduate in December. I have an internship lined up in Android development with medium sized company that builds apps for much larger corporations, and I have recently begun a foray into iOS development. So far my experience with Android ranges from a small mobile game (basically Asteroids), a Japanese language study aid, and a fairly large mobile app for a local non-profit that uses RSS feeds, Google Cloud Messaging and various APIs. I have also recently started working with some machine learning algorithms and sensors/the ADK to start putting together a prototype for a mobile business application for mobile inspectors. My question: is my background diverse enough that I don't have to worry about finding a job if all the predictions that the 'app bubble' will pop soon come true? Is there another, similar area of programming that I should look into in order to have some contingencies in place if things go south? My general interests and experience have so far been in mobile app development with Java and C++ (using the NDK), and some web development on both the client and server side. Thank you!"

Xcott Craver writes "After several years of inactivity, the Underhanded C contest has returned. The object is to write a short, readable, innocent-looking computer program that nevertheless performs some evil function for reasons that are not obvious under code review. The prize is a $200 gift certificate to ThinkGeek." The deadline is July 4th, so get to hacking.

From Joe Armstrong comes news that Erlang will soon feature a new process flag for those processes that just really need memory, or else: "Too big to fail processes behave like regular processes until they get too big and memory congestion occurs. If a memory allocation error is triggered when a too_big_to_fail process needs more memory, then a random smaller process is killed, and the system reattempts memory allocation for the too_big_to_fail process. An interesting situation can occur if the too big to fail process has killed all other processes and still cannot get enough memory. In this case the node running the process tries to memory steal from other nodes." Read below for your FREE logged-in-reader's-eye view of the special rot-39 version!

An anonymous reader writes in with a story about some of the ramifications of the Oracle-Google lawsuit. "You could hear a collective sigh of relief from the software developer world when Judge William Alsup issued his ruling in the Oracle-Google lawsuit. Oracle lost on pretty much every point, but the thing that must have stuck most firmly in Oracle’s throat was this: 'So long as the specific code used to implement a method is different, anyone is free under the Copyright Act to write his or her own code to carry out exactly the same function or specification of any methods used in the Java API. It does not matter that the declaration or method header lines are identical. Under the rules of Java, they must be identical to declare a method specifying the same functionality — even when the implementation is different. When there is only one way to express an idea or function, then everyone is free to do so and no one can monopolize that expression. And, while the Android method and class names could have been different from the names of their counterparts in Java and still have worked, copyright protection never extends to names or short phrases as a matter of law.'"

theodp writes "In a move that would do Bill Lumbergh (YouTube homage) proud, Microsoft has been pulling in about $25 million a year through its unusual practice of charging its vendors for occupying office space on its campus while working on Microsoft projects, according to the real estate firm that manages the program. And that's before a planned July 1st rate increase that Microsoft informed vendors of earlier this week, which will boost the 'chargeback' rate for its 'shadow workforce' from $450 per month ($5,400 per year) for every workstation to $510 per month (or $6,120 per year). So, is there a discount if you're moved downstairs into Storage B?"

sfcrazy writes "ZFS on Linux has reached what Brian Behlendorf calls an important milestone with the official 0.6.1 release. Version 0.6.1 not only brings the usual bug fixes but also introduces a new property called 'snapdev.' Brian explains, 'The snapdev property was introduced to control the visibility of zvol snapshot devices and may be set to either visible or hidden. When set to hidden, which is the default, zvol snapshot devices will not be created under /dev/. To gain access to these devices the property must be set to visible. This behavior is analogous to the existing snapdir property.'"