惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Cisco Talos Blog
Cisco Talos Blog
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
爱范儿
爱范儿
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Jina AI
Jina AI
雷峰网
雷峰网
The Register - Security
The Register - Security
The Cloudflare Blog
博客园 - 【当耐特】
M
MIT News - Artificial intelligence
I
InfoQ
博客园 - 三生石上(FineUI控件)
H
Help Net Security
博客园 - 司徒正美
Vercel News
Vercel News
WordPress大学
WordPress大学
S
SegmentFault 最新的问题
云风的 BLOG
云风的 BLOG
B
Blog
Google DeepMind News
Google DeepMind News
B
Blog RSS Feed
L
LangChain Blog
人人都是产品经理
人人都是产品经理
GbyAI
GbyAI
T
The Blog of Author Tim Ferriss
T
Tailwind CSS Blog
aimingoo的专栏
aimingoo的专栏
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Recorded Future
Recorded Future
小众软件
小众软件
Martin Fowler
Martin Fowler
罗磊的独立博客
Stack Overflow Blog
Stack Overflow Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
酷 壳 – CoolShell
酷 壳 – CoolShell
腾讯CDC
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
Apple Machine Learning Research
Apple Machine Learning Research
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
博客园 - Franky
Hugging Face - Blog
Hugging Face - Blog
Y
Y Combinator Blog
V
Visual Studio Blog
F
Fortinet All Blogs
Microsoft Azure Blog
Microsoft Azure Blog
大猫的无限游戏
大猫的无限游戏
Engineering at Meta
Engineering at Meta
N
Netflix TechBlog - Medium
V
V2EX
Blog — PlanetScale
Blog — PlanetScale

Henri Sivonen’s pages

Parin vuoden tutkimattomuus crates.io: Rust Package Registry Asiakirjatonta toimintaa It’s not wrong that "🤦🏼‍♂️".length == 7 Koulutartuntojen tilastointimenettely Perusteasiakirjoja hallussapitämättä ikärajoitettu Asiantuntijat ja nukkuva vallan vahtikoira Koronapassilausunto Suppealla tietopohjalla ohimeneväksi väitetty Text Encoding Menu in 2021 The Text Encoding Submenu Is Gone An HTML5 Conformance Checker Not Part of the Technology Stack Browser Technology Stack Bogo-XML Declaration Returns to Gecko A Look at Encoding Detection and Encoding Menu Telemetry from Firefox 86 Why Supporting Unlabeled UTF-8 in HTML on the Web Would Be Problematic Rust Target Names Aren’t Passed to LLVM Toimintamalli Activating Browser Modes with Doctype Johtopäätöksiä mallin rakenteesta Tehtävänmäärittelyä kirjoittamatta ja kuolemia laskematta laumasuojamallinnettu Character Encoding Menu in 2014 Erillissuosituksen tarpeettomuudesta yleissuosituksen poikkeukseksi? STM:n maskiaikajana Rust 2021 Oma-aloitteisesti mallinnettu Kokopinovaatimuksin kilpailutettu chardetng: A More Compact Character Encoding Detector for the Legacy Web Varauksia paisutellen tiedotettu Perusteasiakirjoitta tiedotettu Always Use UTF-8 & Always Label Your HTML Saying So IME Smoke Testing The Validator.nu HTML Parser About the Hiragino Fonts with CSS It’s Time to Stop Adding New Features for Non-Unicode Execution Encodings in C++ Rust 2020 The Last of the Parsing Quirks About about:blank Rust 2019 a Web-Compatible Character Encoding Library in Rust How I Wrote a Modern C++ Library in Rust Using cargo-fuzz to Transfer Code Review of Simple Safe Code to Complex Code that Uses unsafe A Rust Crate that Also Quacks Like a Modern C++ Library #Rust2018 No Namespaces in JSON, Please A Lecture about HTML5 Julkisesti luotettu varmenne ikidomainille TLS:ää (SSL:ää) varten -webkit-HTML5 Lists in Attribute Values The Sad Story of PNG Gamma “Correction” If You Want Software Freedom on Phones, You Should Work on Firefox OS, Custom Hardware and Web App Self-Hostablility HTML5 Parser Improvements ARIA in HTML5 Integration: Document Conformance (Draft, Take Two) Schema.org and Pre-Existing Communities Lowering memory requirements by replacing Schematron HTML5 Parsing in Gecko: A Build Introducing SAX Tree NVDL Support in Validator.nu HOWTO Avoid Being Called a Bozo When Producing XML An Unofficial Q&A about the Discontinuation of the XHTML2 WG Thoughts on HTML5 Becoming a W3C Recommendation Four Finnish Banks Training Users to Give Banking Credentials to Another Site Unimpressed by Leopard Sergeant Semantics The Content Sink Inheritance Diagram – 2006-06-30 What is EME? About Points and Pixels as Units The Performance Cost of the HTML Tree Builder Social Media Impression Management The spacer Element Is Gone Openmind 2006 Performance Mistake XHTML and Mobile Devices WebM-Enabled Browser Usage Share Exceeds H.264-Enabled Browser Usage Share on Desktop (in StatCounter Numbers) HTML5 Parser-Based View Source Syntax Highlighting Vendor Prefixes Are Hurting the Web Accept-Charset Is No More Dualroids Writing Structural Stylable Document in Mozilla Editor ISO-8859-15 on haitallinen Hourglass The Scientific Method According to Hixie Maemo Source Code Karpelan lukkovertaus ontuu Digitaalisesta arkistoinnista ARIA in HTML5 Integration: Document Conformance (Draft) XHTML—What’s the Point? (Draft, incomplete) Mac OS X Browser Comparison HOWTO Spot a Wannabe Web Standards Advocate An Idea About Intermediate Language Trees and Web UI Generation Thoughts on Using SSL/TLS Certificates as the Solution to Phishing Bureaucracy Meets the Web Europe Day HOWTO Establish a 100% Literacy Rate What to Do with All These Photos? Charmod Norm Checking Validator Web Service Interface Ideas DTDs Don’t Work on the Web EFFI’s Day in Court
Kesäkoodi Wrap-Up – 2006-09-19
Henri Sivonen · 2011-12-22 · via Henri Sivonen’s pages

The last week of Kesäkoodi stretched to two sparse weeks. Here are the main points:

  • Attended a seminar celebrating the 15-year birthday of Linux at University of Helsinki.

  • Attended Open Tuesday.

  • Released the font autozoom feature as an extension for Firefox 1.5.

  • Published a document about clipboard formats.

  • Uploaded the XPCOM string / Cocoa string conversion code to Bugzilla.

  • Uploaded the Cocoa clipboard code to Bugzilla.

In Summary

Here’s a very short summary of what went right and wrong.

What Went Right?

  • I made a patch that make the XML content sink incremental. As far as I can tell, the code works exactly as expected. Code-wise, the main part of the project was successful.

  • I implemented a new front end for the font zoom that works exactly as expected and designed.

  • I implemented the clipboard using the Cocoa API. The implementation works and I believe that it is more compatible within the platform than any Gecko clipboard implementation for any platform.

  • I learned a lot about the Mozilla codebase and had a chance to do something real in C++ and Objective-C++.

  • Having three subprojects that I could suspend and resume was a very good idea, because at times one of the subprojects was blocking when waiting for advice from others.

  • The time I had allocated to the content sink work was remarkably well guessed considering how bad software project timing estimates tend to be.

What Went Wrong?

  • When putting together my pitch and plan, I imagined some contingencies that were due to the nature of the Firefox project and that could make my project go less smoothly. All those contingencies were realized. My proposed zoom changes were not welcome, the content sink code got stuck in the review phase and it wasn’t a good time to hack on the graphics code (so the clipboard had to be used as a substitute subproject).

  • The font zoom subproject took a lot more time than initially budgeted. The magnitude of the JavaScript performance problems caught me by surprise. The repercussions of having to rewrite the code in C++ were significant in terms of project time used.

  • I spent too much time fighting with Eclipse CDT. I should have given up earlier.

  • When the clipboard code was mostly done, there were too many loose ends to tie and too little time to tackle another non-trivial bug. As a result, the last weeks of the project weren’t nowhere near as productive as the earlier weeks.

  • No code that I wrote during the project got into the Mozilla CVS repository during the project. (But I didn’t even expect code to get in during the project.)

Overall?

Since objectives were reached (except for check-in), I think the project was successful.

I’d like to thank COSS/Hermia, FILOSI, Nokia, IBM, Ericsson, Novell and everyone who helped make the project happen. (I don’t know if everyone who helped behind the scenes want to be named, so I’ll leave this on a general level.)

What’s Next

I’ll continue work on my Master’s Thesis and the associated HTML5 conformance checking software—with funding from the Mozilla Foundation. I won’t be working on Firefox actively. I expect the content sink code to get into CVS later this year. Realistically, I don’t expect the font zoom code to end up in the Mozilla CVS repository. I expect the bulk of my clipboard code to be used in the Cocoa widget implementation once someone else writes a companion drag&drop implementation.