<commit_before>## Dannnno's WebBrowser

This is a very long term project I'm going to play around with.  In general I'm interested in how to most effectively
write parsers and I'd like to practice using a well solved problem (html, js, css).  This way I can compare my
implementation to existing implementations and better locate edge cases I wouldn't otherwise notice.

I'm also interested in browser rendering - I'm curious how something parses an HTML file (and associated CSS, JS, etc)
and then displays it appropriately.  I want to play around with that as well.

Eventually I'd like to take a crack at a JavaScript interpreter.

I'd like for all of this to be written in Python.  I'm planning on starting in CPython and getting things working properly 
there.  Eventually I'd like to find the important bits (probably the JavaScript interpreter) and use ctypes or
cython to speed it up.  

In short, this rather ambitiously named project will eventually seek to have some level of functionality consistent with
other webbrowsers (on a much smaller scale in all likelihood)


Approximate timeline/order of events
1. Getting a working implementation of a CSS Parser.  This will probably be a gradual process, lots of coming back and 
covering edge cases and such.
2. Getting a working implementation of an HTML Parser.  Again, gradual.  Going to take a lot of work... <understatement
of the year>
3. HTML rendering.  I frankly have no idea how I'm even going to approach this
4. CSS rendering.  See above
5. Working implementation of a JavaScript Parser.  See <1>, <2>
6. JavaScript interpreter.  See <3>
7. JavaScript rendering (ie rendering things based on JavaScript)
8. Actual browser implementation.  Don't really know what this will entail, but I imagine a lot of stuff with HTTP 
requests
9. Use my new browser semi-exclusively.  Fix edge cases as they come up.
10. ???
11. Profit!


...

At least where I'm standing, that is an entire list of non-trivial problems.  This isn't ambitious; its insane as
a one man project.  It'll be fun though. Learn a lot.<commit_msg>Fixed formatting errors in readme<commit_after>## Dannnno's WebBrowser

This is a very long term project I'm going to play around with.  In general I'm interested in how to most effectively
write parsers and I'd like to practice using a well solved problem (html, js, css).  This way I can compare my
implementation to existing implementations and better locate edge cases I wouldn't otherwise notice.

I'm also interested in browser rendering - I'm curious how something parses an HTML file (and associated CSS, JS, etc)
and then displays it appropriately.  I want to play around with that as well.

Eventually I'd like to take a crack at a JavaScript interpreter.

I'd like for all of this to be written in Python.  I'm planning on starting in CPython and getting things working properly 
there.  Eventually I'd like to find the important bits (probably the JavaScript interpreter) and use ctypes or
cython to speed it up.  

In short, this rather ambitiously named project will eventually seek to have some level of functionality consistent with
other webbrowsers (on a much smaller scale in all likelihood)


###Approximate timeline/order of events:
  1. Getting a working implementation of a CSS Parser.  This will probably be a gradual process, lots of coming back and 
covering edge cases and such.
  2. Getting a working implementation of an HTML Parser.  Again, gradual.  Going to take a lot of work... <understatement
of the year>
  3. HTML rendering.  I frankly have no idea how I'm even going to approach this
  4. CSS rendering.  See above
  5. Working implementation of a JavaScript Parser.  See <1>, <2>
  6. JavaScript interpreter.  See <3>
  7. JavaScript rendering (ie rendering things based on JavaScript)
  8. Actual browser implementation.  Don't really know what this will entail, but I imagine a lot of stuff with HTTP 
requests
  9. Use my new browser semi-exclusively.  Fix edge cases as they come up.
  10. ???
  11. Profit!


...

At least where I'm standing, that is an entire list of non-trivial problems.  This isn't ambitious; its insane as
a one man project.  It'll be fun though. Learn a lot.
{'fraction_non_alphanumeric': 0.04804947668886775, 'fraction_numerical': 0.007611798287345386, 'mean_word_length': 3.8952270081490106, 'pattern_counts': {'":': 0, '<': 11, '<?xml version=': 0, '>': 11, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5460717', 'n_tokens_mistral': 1127, 'n_tokens_neox': 1049, 'n_words': 679}