[Translations: Arabic, ...]
When DVD Jon was arrested after breaking the CSS encryption algorithm, he was charged with “unauthorized computer trespassing.” That led his lawyers to ask the obvious question, “On whose computer did he trespass?” The prosecutor’s answer: “his own.”
If that doesn’t make your heart skip a beat, you can stop reading now.
When I was growing up, “trespassing” was something you could only do to other people’s computers. But let’s set that aside and come back to it.
My father was a college professor for much of his adult life. One year, he took a sabbatical to write a book. He had saved up enough money to buy a computer and a newfangled thing called a word processing program. And he wrote, and he edited, and he wrote some more. It was so obviously better than working on a typewriter that he never questioned that it was money well spent.
As it happens, this computer came with the BASIC programming language pre-installed. You didn’t even need to boot a disk operating system. You could turn on the computer and press Ctrl-Reset and you’d get a prompt. And at this prompt, you could type in an entire program, and then type RUN, and it would motherfucking run.
I was 10. That was 27 years ago, but I still remember what it felt like when I realized that you — that I — could get this computer to do anything by typing the right words in the right order and telling it to RUN and it would motherfucking run.
That computer was an Apple ][e.
By age 12, I was writing BASIC programs so complex that the computer was running out of memory to hold them. By age 13, I was writing programs in Pascal. By age 14, I was writing programs in assembly language. By age 17, I was competing in the Programming event in the National Science Olympiad (and winning). By age 22, I was employed as a computer programmer.
Today I am a programmer, a technical writer, and a hacker in the Hackers and Painters sense of the word. But you don’t become a hacker by programming; you become a hacker by tinkering. It’s the tinkering that provides that sense of wonder. You have to jump out of the system, tear down the safety gates, peel away the layers of abstraction that the computer provides for the vast majority of people who don’t want to know how it all works. It’s about using the Copy ][+ sector editor to learn how the disk operating system boots, then modifying it so the computer makes a sound every time it reads a sector from the disk. Or displaying a graphical splash screen on startup before it lists the disk catalog and takes you to that BASIC prompt. Or copying a myriad of wondrous commands from the Beagle Bros. Peeks & Pokes Chart and trying to figure out what the fuck I had just done. Just for the hell of it. Because it was fun. Because it scared my parents. Because I absolutely had to know how it all worked.
Later, there was an Apple IIgs. And later still, a Mac IIci. MacsBug. ResEdit. Norton Disk Editor. Stop me if any of this sounds familiar.
Apple made the machines that made me who I am. I became who I am by tinkering.
This post’s title is stolen from Alex Payne’s “On the iPad,” which I shall now quote at great length.
The iPad is an attractive, thoughtfully designed, deeply cynical thing. It is a digital consumption machine. As Tim Bray and Peter Kirn have pointed out, it’s a device that does little to enable creativity...
The tragedy of the iPad is that it truly seems to offer a better model of computing for many people — perhaps the majority of people. Gone are the confusing concepts and metaphors of the last thirty years of computing. Gone is the ability to endlessly tweak and twiddle towards no particular gain. The iPad is simple, straightforward, maintenance-free...
The thing that bothers me most about the iPad is this: if I had an iPad rather than a real computer as a kid, I’d never be a programmer today. I’d never have had the ability to run whatever stupid, potentially harmful, hugely educational programs I could download or write. I wouldn’t have been able to fire up ResEdit and edit out the Mac startup sound so I could tinker on the computer at all hours without waking my parents.
Now, I am aware that you will be able to develop your own programs for the iPad, the same way you can develop for the iPhone today. Anyone can develop! All you need is a Mac, XCode, an iPhone “simulator,” and $99 for an auto-expiring developer certificate. The “developer certificate” is really a cryptographic key that (temporarily) allows you (slightly) elevated access to... your own computer. And that’s fine — or at least workable — for the developers of today, because they already know that they’re developers. But the developers of tomorrow don’t know it yet. And without the freedom to tinker, some of them never will.
(As a side note, I was wrong and Fredrik was right, and Chrome OS devices will have a switch for developers to run their own local code. I don’t know the specifics of what it will look like, whether it will be a hardware button or switch or whatever. But it will be there, an officially supported mode for the developers of today and, more importantly, the developers of tomorrow.)
And I know, I know, I know you can “jailbreak” your iPhone, (re)gain root access, and run anything that can motherfucking run. And I have no doubt that someone will figure out how to “jailbreak” the iPad, too. But I don’t want to live in a world where you have to break into your own computer before you can start tinkering. And I certainly don’t want to live in a world where tinkering with your own computer is illegal. (DVD Jon was acquitted, by the way. The prosecutor appealed, and he was acquitted again. But who needs the law when you have public key cryptography on your side?)
Once upon a time, Apple made the machines that made me who I am. I became who I am by tinkering. Now it seems they’re doing everything in their power to stop my kids from finding that sense of wonder. Apple has declared war on the tinkerers of the world. With every software update, the previous generation of “jailbreaks” stop working, and people have to find new ways to break into their own computers. There won’t ever be a MacsBug for the iPad. There won’t be a ResEdit, or a Copy ][+ sector editor, or an iPad Peeks & Pokes Chart. And that’s a real loss. Maybe not to you, but to somebody who doesn’t even know it yet.
Who Can Do Something About Those Blue Boxes?. John Gruber makes the case for the fading significance of Flash, brought about by Apple’s point-blank refusal to support it on the iPhone or iPad. “Flash is no longer ubiquitous. There’s a big difference between “everywhere” and “almost everywhere”.”
Python и его тормоза - http://www.slideshare.net/shigin...
|
How to recognise a good programmer - http://www.inter-sections.net/2007...
|
Shared by artyСкажите, граждане, а это только у меня надо добавлять к
забавный wtf, рекомендую : )
p { text-align:left; }
еще и !important
, чтобы Safari перестал выравнивать абзацы по ширине? Почему?Reexamining Python 3 Text I/O. Python 3.1’s IO performance is a huge improvement over 3.0, but still considerably slower than 2.6. It turns out it’s all to do with Python 3’s unicode support: When you read a file in to a string, you’re asking Python to decode the bytes in to UTF-8 (the new default encoding) at the same time. If you open the file in binary mode Python 3 will read raw bytes in to a bytestring instead, avoiding the conversion overhead and performing only 4% slower than the equivalent code in Python 2.6.4.
теперь это кажется очевидным, ага ; )
Steve Krug has written a follow up to his usability classic Don’t Make Me Think. The sequel, Rocket Surgery Made Easy, is a terrific, short, concise, fun guide to running simple “hallway” usability tests to improve the usability of your software and websites. Highly recommended.
Need to hire a really great programmer? Want a job that doesn't drive you crazy? Visit the Joel on Software Job Board: Great software jobs, great people.
сейчас среди приверженцев html5 идёт тихий шум на тему того, что ютюб и вимео начали поддерживать тег video
, но кодеки для этого они выбрали неправильно. На эту тему я хочу сказать, казалось бы, очевидные вещи, упоминания которых я ещё нигде не видел.
для начала: если кто-то вдруг этого ещё не знает, во флеш встроена поддержка кодека H.264. То есть, условно говоря, плеер для такого видео делается на флеше за пять минут. Этим пользуются ютюб и вимео, храня петабайты своего видео именно в этом формате. С их серверов эти готовые файлы напрямую отдаются флеш-плееру на вашем компьютере.
итак, очевидное: к этому моменту всё, что сделали ютюб и вимео — потратили один день программиста и неделю тестировщика, чтобы по желанию юзера вместо embed
на странице оказывался тег video
. Всё. Это вся «поддержка html5 video». Соотношение затрат и позитивной реакции на это событие очень впечатляет, так что шаг умный, не спорю. Меня удивляет скорее радость юзеров: чему тут радоваться?
а вот чего не сделал ни один из этих сайтов (но давно уже сделал dailymotion) — это перекодирования имеющегося архива видео в открытый и бесплатный Ogg Theora. Поэтому если за спиной вашего браузера не стоит богатейшая компания типа Google или Apple, способная заплатить до $5.000.000 за право встраивать в свои продукты кодек H.264, если вы пользуетесь собранным энтузиастами браузером Chromium или Firefox, то вам остаётся тормозной флеш или разные ухищрения.
естественно, перекодирование таких объёмов требует огромных ресурсов. Поэтому ютюб не будет этим заниматься сейчас. Нет, пока что они соберут хорошую карму за упоминание html 5 и потестируют фичу на широких массах юзеров. А вот через полгода-год, если не через два, возможно, начнётся конвертация. Если всё будет хорошо.
впрочем, спору нет, для сообщества веб-разработчиков и производителей браузеров это был очень полезный шаг. Заодно и patent awareness вырастет.
А теперь вспомните, что лицензия на используемый YouTube кодек H.263 стоит до $5.000.000
RT @osvaldas: Bill Gates uses IE hacks on his personal website — www.gatesnotes.com — I'd call it a boomerang effect
|
Don’t Hash Secrets. A well written explanation from 2008 of why you must use hmac instead of raw SHA-1 when hashing against a secret.
несколько лет назад опера научилась запускать в отдельных системных окнах маленькие приложения-виджеты, вроде тех, что сейчас часто можно видеть на стартовых экранах смартфонов. Конечно, так можно было запускать и приложения покрупнее, но этим мало кто занимался. Тем более, что эти приложения работали только до тех пор, пока работала опера. А использовать отдельный процесс оперы с отдельным профилем — хлопотно.
но вот недавно виджеты стали стандартом W3C, а опера кардинально улучшила их поддержку: теперь они работают как независимые программы, и так же независимо их можно устанавливать и удалять. Немедленно множество людей сообразило, что в таком виджете можно запускать уже существующие веб-приложения, достаточно одного ифрейма. Правда, с первых попыток у меня это не заработало, но я оставил себе заметку на будущее.
будущее наступило : ) И теперь достаточно нескольких кликов, чтобы превратить веб-приложение в «настольное»! Зайдите оперой на страничку Opera Prism: desktop web-applications, введите урл и нажмите Install. Или скачайте его на диск, чтобы поредактировать. Или отправьте конечную ссылку другу. Update: лучше всего использовать Widgetize.
конечно, я не буду утверждать, что опера была первее всех — это очевидно даже из названия заметки. До неё таким трюкам научились Mozilla Prism и Хром. Однако у оперы есть преимущество: она ест заметно меньше памяти, и эти приложения более похожи системные (вплоть до автопакетирования в deb в убунте).
а иконок нет пока только из-за моей лени ; ) Вернее, я не знаю ещё нормального способа добывать их автоматически или вручную.
Shared by arty
любопытно, что если у вас нет флеша, то и кнопочку «Switch to HTML5 player» вы не увидите ; )
However... ...We've heard a lot of feedback around supporting HTML5 and are working hard to meet your request, so stay tuned. We'll be following up when we have more information. We're answering this idea now because there are so many similar HTML5 ideas and we want to give other ideas a chance to be seen.
A successful Git branching model (via). This looks eminently sensible. The master branch is used for production-ready code, and is only updated by merging from either release branches or emergency hotfix branches. A develop branch is used for integration (from feature branches), and is branched to create release branches when a release is nearly ready. It’s all comprehensively documented and comes with some well-designed diagrams.
Inside every large program is a small program struggling to get out... — T. Hoare, Efficient Production of Large Programs (1970)
|
Internet Explorer would lose 38.03% of its European market share, Chrome would gain 10.11% the European share, and Firefox would gain 3.79%.
The Firebug Working Group proudly announces the availability of Firebug 1.5.0!
After more than 6 months of development and 36 alpha and beta releases, the new Firebug is ready. Among the major enhancements:
In addition to the people named above, we have had a lot of contributions from users. We especially want to thank locale contributors, we now support 32 languages.
We’ve listed the main new features and changes in the Firebug 1.5 release notes on our new wiki. Please take a few minutes to read through them and ask for clarifications. We’ll use your input to add more information.
For this release we’ve worked especially hard on quality. Our pre-release test suite continues to grow: Firebug 1.5 passes all tests on both Firefox 3.5 and 3.6. We’ve fixed a lot of bugs, while also adding enhancements requested by the community. Ultimately this quality derives from community contributions of good bug reports with test cases. We thank everyone who takes the time to help.
The addons.mozilla.org users will be updated to 1.5.0 next week. Based on past experience, some issues will arise that our getfirebug.com users did not hit. We expect a couple of minor update releases in the next few weeks. All new features and significant bug fixes will now appear on Firebug 1.6.
Support for Firebug extension bundles did not make it into 1.5. We are working on that now and hope to have some prototypes ready soon.
jjb
When you encounter a website that has accessibility problems, it can be a good idea to contact the organisation behind the website to let them know about the problem and encourage them to fix it. To help make this a little easier, the W3C WAI has published a draft document called Contacting Organizations about Inaccessible Websites.
The document contains tips, discusses different approaches, and includes a few sample e-mails to show you what a message describing an accessibility problem can look like. Shawn Lawton Henry talks about the initiative a bit more in Take a few minutes to encourage web accessibility. You can make a difference. on the W3C Blog.
Posted in Accessibility.
<body onload="new Gordon.Movie('trip.swf', {id: 'stage', width: 500, height: 400})"></a>
<div id="stage"></a></div>
</body>
Ура! Последний бастион пал, и на Mail.Ru наконец появилась поддержка OpenID! К сожалению, там ещё нет Directed Identity, но емейл очень легко трансформировать в openid-идентификатор.
Shared by artyvideo
как нарастает узость восприятия: человек, дающий ссылку, пишет только про chrome, при том, что автор демки подумал и о гекко, а все нужные технологии есть ещё и в опере
What I’m writing here is the single most important take-away from my Sun years, and it fits in a sentence: The community of developers whose work you see on the Web, who probably don’t know what ADO or UML or JPA even stand for, deploy better systems at less cost in less time at lower risk than we see in the Enterprise.
- Tim Bray
As a part of Microsoft’s continued commitment to interoperability and standards support, yesterday we submitted our request to join the Scalable Vector Graphics (SVG) Working Group of the World Wide Web Consortium (W3C). We’re excited to take part in ensuring future versions of the SVG spec will meet the needs of developers and end users.
As stated on its Web site, “the mission of the SVG Working Group is to continue the evolution of Scalable Vector Graphics as a format and a platform, and enhance the adoption and usability of SVG in combination with other technologies.” We recognize that vector graphics are an important component of the next generation Web platform. As evidenced by our ongoing involvement in W3C working groups, we are committed to participating in the standards process to help ensure a healthy future for the Web. Our involvement with the SVG working group builds on that commitment.
To date, I have had several interactions with the SVG working group, and their clear dedication to creating a great technology for end users and developers alike stands out. I personally look forward to future and more direct involvement with this great set of folks.
Patrick Dengler
Senior Program Manager
Internet Explorer Team
OpenID Connect - http://factoryjoe.com/blog...
|
22 companies including NTT docomo, KDDI, Sony, NEC, etc. have formed “ID Platform Federation Forum”. With JPY12 billion (approx. US$1.3M) in funding from the Ministry of Internal Affairs and Communication, the forum members will initiate the experiment, based largely on OpenID, by the end of the year. The forum itself is operated by Nomura Research Institute (NRI).
Mobile content and commerce has flourished in Japan after the deployment of mobile browser communication for the mobile phones in Japan. As of 2008, it amounts to JPY1,352,400,000,000 (approx. US$15M) and showing 17% growth even under stagnant market conditions [1]. It has become so important that it is often said that a service will not be viable without mobile web support.
One of the key factors of its success has been attributed to the ability to identify the user reliably in the mobile carrier network. This characteristic combined with the micropayments provided by the mobile carriers enable a zero-hassle login and payment user experience. However, these features have only been available via mobile browser and not on the PC and other internet-connected devices. The forum aims to expand the success of the identification and payment service capability from the mobile arena into the wider internet, using OpenID as the underlying technology. The forum will provide insights on the implementation and recommendations obtained from the experiment back to the international community through bodies such as the OpenID Foundation. Currently, the forum expects the feedback to impact the Mobile Profile of OpenID, the Attribute schema, and Level of Protection of the Relying Parties.
Chairman
Prof. Aida, Tokyo University
Vice-chair
Prof. Morikawa, Tokyo University
Secretariat
Nomura Research Institute, Ltd.
Members
Access Co. Ltd.
KDDI Corporation
Nextwave Co. Ltd.
NEC Corporation
Nihon Unisys Ltd.
Nomura Research Institute, Ltd.
NTT Comunications
NTT docomo Inc.
Fujitsu
Hitachi Ltd.
Softbank BB Corp.
Sony Corporation
Willcom Inc.
in addition, there are observers.
[1] Source: Ministry of Internal Affaires and Communication (http://www.soumu.go.jp/menu_news/s-news/02ryutsu04_000016.html)