Bahaya copy paste ke Terminal

Copy paste
Copy paste is no more.

Anda sering melakukan copy paste langsung dari halaman web ke Terminal? Melakukan copy paste langsung dari halaman web ke Terminal tentu jauh lebih mudah dibandingkan dengan mengetik langsung ke Terminal, apalagi kalau perintahnya cukup panjang. Tapi, mulai sekarang Anda harus berhati-hati dengan kebiasaan ini karena dengan sedikit trik HTML, sebuah perintah bash sederhana bisa jadi berbahaya kalau langsung di-paste ke Terminal.

What you see is not what you copy.
Continue reading “Bahaya copy paste ke Terminal”

Google forked WebKit into Blink. What does that mean?

Krzysztof Kowalczyk:

Apple is in a tight spot. Suddenly WebKit will be getting 50% less code.That’s a big drop.

Which is why Apple is in a tight spot: if WebKit suddenly looses non-Apple contributions, they’ll have a hard time catching up with Blink. And while they really don’t care if web technologies advance quickly, they’ll be forced to at least keep pace with Mozilla and Google, both of which are putting the foot on the pedal recently.

Google forks WebKit, calls it Blink

Blink

However, Chromium uses a different multi-process architecture than other WebKit-based browsers, and supporting multiple architectures over the years has led to increasing complexity for both the WebKit and Chromium projects. This has slowed down the collective pace of innovation – so today, we are introducing Blink, a new open source rendering engine based on WebKit.

And thus Chrome now uses Blink, which is forked from WebKit, and pretended to be Safari, and WebKit pretended to be KHTML, and KHTML pretended to be Gecko, and all browsers pretended to be Mozilla.

John Resig: WebKit adalah jQuery dari browser

Berita mengenai Opera yang beralih ke WebKit mendapat perhatian dari John Resig, pembuat jQuery, the missing JavaScript library. John Resig berpendapat bahwa WebKit bagi browser layaknya jQuery bagi JavaScript.

I would argue that WebKit (a common framework for implementing the standards-compatible portion of a web browser) is exactly like jQuery (a common framework for implementing a DOM standards-compatible experience in a web page) at this point.

John Resig

Selain itu, John Resig juga mengomentari beberapa argumen terkait masalah WebKit dan web standar. Misalnya, tentang stagnasi, dan masalah bug yang bisa menjadi de facto.

As to the bugs: WebKit is a common code base that a number of browsers contribute to, however every browser vendor has the ability to make changes to their own fork of the code base. I see no reason why these “now-standard” WebKit bugs wouldn’t be fixed by any single vendor.

Anda bisa membacanya secara lengkap dari blog John Resig.

“Sad day for the Web”

The news about Opera switching to Webkit is disappointing. It’s a sad day for the Web, since I thought highly of their Presto engine and their Web standards work. Their impact on Web standards will be dramatically reduced, especially where they want to do something differently to Apple and Google.

Robert O’Callahan

-o-pera beralih ke -webkit-

WebKit

Opera mengumumkan bahwa saat ini pengguna browser Opera telah berjumlah sekitar 300 juta orang.

Namun saya tidak peduli dengan jumlah tersebut, berita yang lebih penting dari pengumunan tersebut adalah Opera akan beralih ke WebKit 🙂

On the same day as announcing that Opera has 300 million users, we’re also announcing that for all new products Opera will use WebKit as its rendering engine and V8 as its JavaScript engine. It’s built using the open-source Chromium browser as one of its components.

Seperti yang diungkapkan di blognya, produk Opera berikutnya akan menggunakan WebKit sebagai rendering engine dan V8 sebagai JavaScript engine-nya. Spec seperti ini memang mirip dengan yang digunakan pada Google Chrome karena pada dasarnya komponen tersebut dikembangkan dan digunakan pada Chromium, proyek open source dari Google Chrome milik Google.
Continue reading “-o-pera beralih ke -webkit-“

Why other browsers have “Mozilla” in the User Agent

Inilah sejarahnya mengapa di setiap browser punya User Agent yang ada “Mozilla”-nya:

And then Google built Chrome, and Chrome used Webkit, and it was like Safari, and wanted pages built for Safari, and so pretended to be Safari. And thus Chrome used WebKit, and pretended to be Safari, and WebKit pretended to be KHTML, and KHTML pretended to be Gecko, and all browsers pretended to be Mozilla, and Chrome called itself Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.13 (KHTML, like Gecko) Chrome/0.2.149.27 Safari/525.13, and the user agent string was a complete mess, and near useless, and everyone pretended to be everyone else, and confusion abounded.

Spotify web player

Spotify

Spotify yang berbasis web yang saat ini masih versi beta kini sudah bisa diakses untuk beberapa pengguna. Buat Anda yang sudah ingin mencobanya, silakan mengaksesnya dari link berikut ini:

Open Spotify

Internet Explorer is evil

Salah seorang member Reddit yang merupakan mantan web developer menjelaskan mengapa Microsoft begitu jahat dengan Internet Explorer-nya.

Microsoft intentionally made the engine (Trident) incompatible with the W3C standards, created an incompatible JavaScript implementation and even attempted a incompatible Java implementation (for which they were sued). The point of this is their wel-known EEE (embrace, extend and extinguish) policy. First they implement your stuff, then they introduce incompatibilities, and then, through the power of monopoly, they pushed the original inventor out of the game. They tried to kill Sun. Literally. And to get rid of the W3C. For total web dominance.

Their implementation of the standards was therefore of course horribly bad. By far the most time it took to develop a web page/site was IE workaround time. Making webdev three to five times more expensive for clients. And the bugs. Oh the bugs. I swear to you, that from time to time I still have horrible nightmares from when I was paid to write a real web application (think: OS X mock-up with network file system without the AJAX API, full widget toolkit and video player) for IE 6. Every single one of us loathed IE, and still does.

Saya sarankan Anda membaca semuanya penjelasannya. Kelakuan Microsoft dengan Internet Explorer dimasa lalu sangat buruk. Dan bahkan sekarang, Microsoft sekali lagi ingin melakukan hal yang sama dengan Windows Phone:

when they recently got rid of their probation officer, for the last crime they were convicted for. The very next day, they injected the mole that is Steven Elop into Nokia, basically killing it, with 9000 engineers and workers leaving the company in protest on the spot. And they put their shitty WP7/8 on Nokia phones. And what did they do?
They again, made IE non-replaceable and “hard-wired” into the OS. And promptly got sued for it. (Guess I’m not the only one who did not forget.)