Matthias Kretschmann
299084de93
* basic astro setup, kick out all gatsby configs * move content folder * src/pages setup * more file reorg * more config updates * more reorgs * refactor * refactor * bump astro * refactor * svg icon build system, theme switch * remark plugin for lead paragraph, more refactor * make images work * post meta * custom Picture component * Pagination, More component, 404 fixes * linking fixes * add table of contents * post actions fixes * tag fixes * content changes * content changes: move media files to their posts * more content moving, remove media folder * refactor remark-lead-paragraph * link css file when defined in post frontmatter * move content up again * kbd post update * allow js * downloads solution * add astro check * redirect_from solution * githubLink solution * reorg * exif solution as prebuild step * exif solution on each post during build * isolate lead paragraph extraction to articles * restore Exif components * deploy script update * fix redirects * xml & json feeds * build fix * fix exif readout in production * head and seo tweaks, add feeds * tweak image display * archive pages with single layout * restore tags archive * sitemap setup * restore thanks page functionality * reorg * cleanup * parallel scripts during prebuild * restore jest setup * remove jest, switch to vitest as test runner * adapt CI * test refactor * typescript tweaks * avatar fixes * typings * restore search functionality * theme switch with nanostores * fixes * test fixes * restore changelog functionality * umami script * border color tweak * related posts with fuse.js * plawright e2e testing setup * search tweaks * simplify typekit loading * photo fix * e2e tests * related posts fix * fix tags archive * tweaks * tweaks * linux snapshots * fix header test * new symlink tactic * fix dev server in codespaces * fix yaml * ci fixes * changelog loading tweaks * e2e against dev server on ci * changelog tweaks * ci tweaks * ci tweaks * ci tweaks * docs updates * ci tweaks * refactor photo creation script * package updates * refactor search * ci tweak * ci tweaks * test tweaks, more unit tests * more unit tests * post creation script tweaks * refactor new scripts, test them for real life * more tests * refactor * codeclimate-action update * uses update * limit ci runs * fix theme toggle, test it * more tests * favicon files cleanup * icon components location change * type checking through ci * command fixes * ci fix * search tweaks * ci tweaks * revised favicons, write post draft about it * drafts filtering fix * lint fix, favicon fixes * copy changes * fix related search images * content updates * new codeblock styles, copy tweaks, fixes * package updates * typing fixes * lint fix * content updates * restore link posts * faster theme switching * split up astro utils * related posts fixes * fix * refactor * fixes * copy tweaks * fixes * picture tweaks * image fixes * feed fixes, adapt for json feed v1.1 * e2e test updates * layout tweaks * update snaphots * migrate to createMarkdownProcessor * ci cache tweaks * activate more browsers for e2e testing * switch to macos-13 images * build caching tweaks * markdown fix * set image quality * remove avif generation * picture tweaks * head fixes * add og:image:alt * create-icons test * new post: Favicon Generation with Astro
3.1 KiB
| title | date | tags | |||
|---|---|---|---|---|---|
| A New Browser Is Coming: Google Chrome | 2008-09-01 20:40:38+00:00 |
|
Today some information about Google's new open source browser called Google Chrome came up.
First published as a comic on Blogoscoped.com and confirmed by Kara Swisher, Google Chrome will be a WebKit-based browser with a new JavaScript Virtual Machine called V8 and with Google Gears included.
Google Chrome has a different UI-Design compared to other browsers especially regarding tabs. Google Chrome tabs will be on top of the address bar so every tab has its own address bar. Beside that every tab will run its own process to improve stability.
Using WebKit as its rendering engine, Google Chrome will have all the cool WebKit stuff included like CSS Gradients, CSS Masks and the CSS3 property text-shadow, which I've covered earlier in detail.
Google Chrome will be optimized for use with web applications and, instead of using WebKit's new core JavaScript engine Squirrelfish, Google decided to use a new, multi-core processor optimized JavaScript virtual machine developed by the V8-team in Denmark.
More information on the features leaked can be found in the Google Blogoscoped article or in the corresponding scanned comic.
Update: Google's official blog was updated with informations about the new browser project. They say the first beta of Google Chrome will be released tomorrow just for Windows while versions for Mac OS X and Linux will follow soon.
Update 2: Google Chrome can now be downloaded for Windows from google.com/chrome. Google also posted a feature page for Chrome.
Update 3: Google Chrome seems to have problems with some of my transparent PNGs:
Update 4: There are some nice articles about various aspects of Chrome available in the web:
- Matt Cutts tries to prevent paranoia and explains when Google Chrome talks home.
- Gina from lifehacker.com dissects Google Chrome's Full List of Special about: Pages.
- Google explains their priorities regarding different Platforms.
- The Chromium Developer Documentation is available too.
- And it seems Google cut out some features of WebKit like text-shadow.