Why browsers are bloated [Part 2]

Cudder is all talk and no action!

>>111
it's funny that basic stuff like maintainability is considered 'enterprise' by optimization zealots. a web browser is a good example why even a minimalist one-man project needs to be maintainable: because web standards (HTML, JS and to a lesser extent HTTP) are changing and to stay useful, a browser needs to change with them.

also check dubs

>>120
Is it needed for Acid2? If not, it's not in the immediate future.

>>124
what happens after Acid2? do you have plans for Acid3?

Guys, guys...
Let's just hope Cudder actually delivers for the first time and releases a browser that passes Acid2.
Let's not get ahead of ourselves.

cudder-kun, what is it written in?

>>126
*Cudder is all talk and no action*

>>125
In the very distant future.

yall a bunch of fools, cdr'ing down Cudder's list.

>>132
check my cdrs
* (car >>133)
1

* (cdr >>133)
33

* (dubcheck >>133)
T

I've discovered that all of the HTML5 character entity references (&xxxx;) are at least as long as the codepoints they represent in UTF-8, meaning that I can do the conversion in-place or on an allocation the exact same size as the original string...

...except for these two bastards which are one more byte longer:

≫⃒ U+226B U+20D2 ; E2 89 AB E2 83 92
≪⃒ U+226A U+20D2 ; E2 89 AA E2 83 92

Two out of 2000+! I'm not going to support those, because it's absolutely idiotic to have to redo and complexify the whole buffer allocation logic just to handle these 0.1% of them which is probably very rarely going to occur in real pages anyway.

What's even more idiotic, is that if someone paid some attention to implementation and made them just a single byte longer e.g. &nGGt; or &nLLt; , they would've fit in perfectly with the rest of them. But it might be too much to expect of the W3C.

"Plan Ahead"

>>135
what are those entities?
Will they break the browser?

>>137
Wtf man. Of course not.
http://www.w3schools.com/html/html_entities.asp
It's just that ≪ and ≫ won't be supported, all other 2000(+) entities will be.

HIBT? Can't you google simple shit like this yourself?

Mr. >>137, I'm the guy that posted >>138.
Sorry if I was a little rude, but you really have to think more and research more before posting.
I hope we're on good terms.
Have a nice one.

>>137
They are probably almost never going to be used. They just won't be recognised.

Can't you just create a browser? I mean, most languages have sockets and also graphics.

>>142
Yes, I can.

>>143
Feel the empowerment taking hold of you. Yes, you can. You are no longer a subject to the caprices of others, but are taking matters into your own hands. Yes, you can!

>>142
Think of it: Can you build a house all by yourself?

>>142
Also, people asking:why can't I create an OS? Should ask themself: can you create a car from scratch?

>>147
It's certainly all possible in theory. The real question is whether the individual is willing to invest their life into making it happen.

>>147
Can you create a cdr from scratch?

>>148
Yes. The actual question is what kind of car it will be?
https://i.imgur.com/Vwdionk.jpg

>>151
From the address, I thought it'd be a Volkswagen Dionk.

I'm going to build a car fuelled by feces and redpills.

>>151,152
https://www.youtube.com/watch?v=h0SJhoSZfEs
https://www.youtube.com/watch?v=N3c-qgJKEdU

>>155
that's pretty cool tbh

Upon closer examination, there's even more retardedness in the entities list --- some are defined more than once! What sort of fucked-up design-by-committee lead to this idiocy?

We start with some "only slightly retarded" duplication...
ast; U+0002A
midast; U+0002A

lbrack; U+0005B
lsqb; U+0005B

...move onto WTF-inducing "you're an idiot if you think this is even the slightest bit useful"...

lowbar; U+0005F
UnderBar; U+0005F

grave; U+00060
DiacriticalGrave; U+00060

nbsp; U+000A0
NonBreakingSpace; U+000A0

...and finish with "ARE YOU FUCKING INSANE!?!?"

die; U+000A8
Dot; U+000A8
DoubleDot; U+000A8
uml; U+000A8

ap; U+02248
approx; U+02248
asymp; U+02248
thickapprox; U+02248
thkap; U+02248
TildeTilde; U+02248

Bonus level:

NegativeMediumSpace; U+0200B
NegativeThickSpace; U+0200B
NegativeThinSpace; U+0200B
NegativeVeryThinSpace; U+0200B
ZeroWidthSpace; U+0200B
Completely different names, yet the exact same codepoint. :quintuple-facepalm:

See it yourself at https://www.w3.org/TR/html5/syntax.html (scroll to bottom, extract table, sort by codepoint.)

Now I know why there are 2K+ entities. Around half of them are duplicates with an extra ';' at the end (easily handled by the parsing code, but the brainless turds that wrote the spec did not even think...), the other 1/4 are useless duplicates, and what's left is possibly, maybe sometimes, actually useful. But supposedly to be "HTML5 compliant" you would need to parse them all, regardless of whether anyone will actually use them except in demo pages and the like (probably not). Fuck that bullshit.

"Why browsers are bloated".

>>159
Horrible!
I hope in the end you report all this bullshit so they update their spec.