Paul Irish on Chrome Moving to Blink
I know you’ve been asked this plenty of times already, but: no new vendor prefixes, right? Right? Nope, none! They’re great in theory but turns out they fail in practice, so we’re joining Mozilla and the W3C CSS WG and moving away them. There’s a few parts to this. Firstly, we won’t be migrating the existing -webkit- prefixed properties to a -chrome- or -blink- prefix, that’d just make extra work for everyone. Secondly, we inherited some existing properties that are prefixed. Some, like -webkit-transform , are standards track and we work with the CSS WG to move ahead those standards while we fix any remaining issues in our implementation and we’ll unprefix them when they’re ready. Others, like -webkit-box-reflect are not standards track and we’ll bring them to standards bodies or responsibly deprecate these on a case-by-case basis. Lastly, we’re not introducing any new CSS properties behind a prefix. Pinky swear? Totes. New stuff will be available to experiment with behind ...
adobe
ambitions
android
apple
applications
blink-powered
canary
chris
chrome
chromebook
chromeos
chromium
coffeescript
commitment
compatibility
confirmation
conformance
css
darin
dart
decision
deprecation
dev
development
devtools
divergence
dom
emscripten
expectations
experience
experiment
firstly
fisher
freedom
google
haha
implementation
integration
interoperability
ios
irish
javascript
javascriptcore
lastly
limitations
linux
mac
maintenance
management
mention
mozilla
non-webkit
nope
oilpan
opera
paul
performance
pinky
policy
practice
priority
quality
rangeexception
recalculation
resistance
safari
scalability
secondly
simplicity
technology
tradition
typescript
vbscript-y
version
webkit
webkit-based
wilson
windows
xmlhttprequestexception
Node at Work: A Walkthrough
In my first article, “ Even Better In-Browser Mockups with Node.js ,” I explained why Node.js makes designing applications easier and more efficient, and how to get started. Now it’s time to see your new design process in action. Rather than figuring out all your requirements and API schemas just to design your comps with mockup content hard-coded and server interactions faked—only to throw it all away when you go back and implement things “for real”—you can use Node.js to skip the hard-coding and produce client-side code that’s ready for beta at the end of the design stage. The process looks a lot like good ol’ designing in the browser , but with more JavaScript and an additional layer: Design the layout and styling Convert the markup to a JavaScript template Create an initialization function Create a simple Node.js server Add a mockup data object to the server Add server functions to serve static pages and JSON Request and consume the JSON on the client Sound daunting? ...
ability
abstraction
acrobats
action
api
applications
artist
choice
compatibility
configuration
consumption
css
detailtmpl
devices
dot
express
expression
function
github
html
implement
initialization
initializing
instance
interaction
interactivity
jade
javascript
jquery
json
node
options
pablo picasso
policy
position
production
representation
requirements
showdetail
simplicity
substitution
version
violations
xhr
xhrs
xmlhttprequest
zillion
Firefox development versions show privacy plans moving forward
A new cookie policy and new do not track options are in the most recent development versions of Mozilla's Firefox and appear to cement privacy as one of the major features of the browser in the future
development
firefox
mozilla
options
policy
privacy
version
Nearly 60K Low-Quality Apps Booted From Google Play Store In February, Points To Increased Spam-Fighting
Google has stepped up its efforts to remove spammy or otherwise non-compliant applications from its mobile application marketplace, Google Play, in recent weeks. App deletions hit a record high in February, with 60,000 apps removed during the course of the month – the largest round of app deletions to date. The news of this massive app removal comes just ahead of the rumored launch of a revamped version of Google Play (version 4.0), which is expected to arrive in the near future. We learned of this large, new round of app deletions from a company in the mobile app industry which has insight into changes like this. To be clear, not all of these apps were deleted by Google. Some, such as a handful of Sprint bundles and apps, as well as the product from startup cautionary tale Color and several others, were likely pulled by the publishers themselves. But with a number as high as 60,000, it’s clear that many of these were pulled by Google directly. Below is a summary of those findings, indicating ...
apple
applications
capabilities
comments
deletion
google
placement
policy
publication
section
service
situation
sprint
version
UK Government Mandates 'Preference' For Open Source
An anonymous reader writes "ComputerWeekly reports that the U.K. government 'has, for the first time, mandated a preference for using open source software for future developments.' This comes from the newly released version of the Government Service Design Manual, which has a section about when government agencies should use open source. It says: 'Use open source software in preference to proprietary or closed source alternatives, in particular for operating systems, networking software, web servers, databases and programming languages.' The document also warns against vendor lock-in. This policy shift comes under the direction of government CTO Liam Maxwell, who said, 'In digital public services, open source software is clearly the way forward.' He added, 'We're not dogmatic about this – we'll always use the best tool for the job – but open source has major advantages for the public sector.'"
agency
computerweekly
cto
development
direction
documents
government
liam
maxwell
policy
preferences
section
service
version
Found more than 1 month ago on channel
Slashdot