Why browsers are bloated

https://github.com/WebKit/webkit/blob/master/Source/WebCore/platform/Scrollbar.cpp
https://github.com/WebKit/webkit/blob/master/Source/WebCore/platform/win/ScrollbarThemeWin.cpp
Let's reinvent the fucking scrollbar, which every goddamn platform with a UI already has, and make it behave subtly different from the native one!

Right-click a native scrollbar in some other app:
- Scroll Here
- Top
- Bottom
- Page Up
- Page Down
- Scroll Up
- Scroll Down

Right-click a scrollbar in Chrome:
- Back
- Forward
- Reload
- Save As...
...

Right-click a scrollbar in Firefox and Opera:
Absolutely fucking nothing happens!

What the fuck!? How did these terminally retarded idiots get involved in creating one of the most important pieces of software to the average user?

What about this?
https://godoc.org/golang.org/x/net/html

>>681

godoc
golang

Utter garbage.

https://totalizator.wordpress.com/2012/10/03/connect-windows-95-to-the-internet-using-linux-box-and-rs-232-serial-port-null-modem-cable/

With the CSS3 border-radius property, you can give any element "rounded corners".

>>684
HTML+CSS is all people should need. http://codepen.io/philhoyt/pen/ujHzd
But they use JavaShit for everything, for our sadness.

>>683
What's the point? Does someone really think Win95 predates Ethernet?

For those now-borked links to the old /prog/, you will need to get the archive from here:

http://bbs.progrider.org/prog/read/1437614471

>>686
>>687
Hi there!

You seem to have made a bit of a mistake in your post. Luckily, the users of /prog/ are always willing to help you clear this problem right up! You appear to have used a tripcode when posting, but your identity has nothing at all to do with the conversation! Whoops! You should always remember to stop using your tripcode when the thread it was used for is gone, unless another one is started! Posting with a tripcode when it isn't necessary is poor form. You should always try to post anonymously, unless your identity is absolutely vital to the post that you're making!

Now, there's no need to thank me - I'm just doing my bait to help you get used to the anonymous text-board culture!

>>686
LAN networking was the point of ethernet at the time. Since the only real way to access the internet for home users was dialup, the computers sold then rarely had NICs. I doubt that anyone still makes drivers for a Win95, much less hardware that fits a motherboard that old.

This makes me think of a new vaporware I'm going to work on for ten minutes and forget about. How about a BBS that you have to dial in to, but that's hosted over the various free VoIP things like Jewgle Voice or Skype?

>>688
Hi there!

You seem to have gotten dubs with your post. Luckily, the users of /prog/ are always willing to check your dubs right up! You appear to have gotten a post number ending in repeating digits when posting! Great! We will always remember to check your dubs when the board you are posting in is a textboard! Posting with a dubs when it is always necessary is great form. We will always try to check your dubs following the culture of the site, since your dubs are absolutely vital to the post that you're making!

Now, there's no need to thank us - we're just doing our best to help your GET in the text-board culture!

This thread is bloated

>>689
What in the nigger shit are you spouting? There's no difference at the OS endpoint of LAN vs internet networking. Go kill yourself.

>>692
Dailup and ISDN modems used RS-232 not Ethernet, cretin.

>>693
What the fuck does that have anything to do with IP?

If your machine can route IP over a LAN, there's no difference in routing IP over the internet, fuckwad.

>>694
You're the one that's going off on some retarded tangent. Follow the conversation, muttonhead.

Finally with a little more time to work on the CSS part, I've done the matcher and some of the datastructures but still need to figure out a good way to store the properties and their values. Most of them could be stored together with their values in a single 32-bit integer. I just need to map them all...

All word and action none!

>>696

a good way to store the properties and their values

You need a map from properties to values? How about a fucking map?

Does C even have maps?

>>699
Nice dubs
>>700
These too.

>>698
Yes, it will be a map, but exactly what type of map? There's plenty of generic types of map but the space of properties and values is small enough that it should be possible to represent e.g. background-color: black in a single 32-bit value.

Careful design of the data structures is important because it's what sets this browser apart - it's not just another Firefox or Chrome or IE clone. Everthing has been designed from the beginning to be as efficient as it could be, before I write a single line of code. I know you might be thinking "just use a std::map<something, something>" but have you ever seen the actual implementation of such things? They're great for mapping a great many arbitrary objects to other arbitrary objects, but horribly bloated for what this particular application needs: a mapping from ~256 or less keys, to a similarly restricted set of small values ("inherit", "none", one of 2^24 colours, one of 256 opacity levels, etc.) A DOM node is not going to have several thousand CSS properties set on it (there aren't even that many in total in CSS3!), and even a hundred is going to be rare. Using a datastructure designed and optimised for 2 or 3 orders of magnitude more items for this is retarded in the same way as invoking Quicksort on a 4-element array.

>>697
The pen is mightier than the sword.

Why didn't K&R make it to the standardization committee?

They got lost because C doesn't have a map.

>>701
And here we see a Cudder adding unmaintainable bloat to his shit, in a futile attempt to reduce bloat.

>>703

unmaintainable

Buzzword detected.

sage

>>705
Epic sage meme image/b/oard/b/ro!

>>701
What's wrong with just a bitmap of a node's specified properties and a corresponding list of values? The values can be "fat", i.e. background-color, background-repeat squashed into one "background" struct.

>>701
That's a genius idea.

>>707
I'd considered that, but that's 32+ bytes just to keep the bitmap in addition to the values, and the list would still need to be searched. A hash table is a bit rich for the purpose, although something resembling hashing might be a good idea.

>>708
I don't think it's that genius of an idea. Maybe to the incompetents that pass as programmers these days, but the demosceners and other old-school programmers would think nothing of it.

dubs

>>710
NO U

>>704
"Unmaintainable" is a non-ENTERPRISE term learned by any learning programmer who's looked at their own personal projects from 6 months ago.

>>712
s/learning/degrading/

If you can't understand code you wrote before, you're not getting any better - you're getting worse.

http://www.linusakesson.net/programming/kernighans-lever/

I noticed that there's a CSS 2.2 spec being developed:
https://drafts.csswg.org/css2/

>>713
Truly a non-programming poster.

If you can't maintain the project you wrote 6 months ago, and the code looks like bullshit, you've made a step towards satori.

If you've never experienced this early in your programming, you have never learned anything and are destined to be a shit apper.

>>714
You make no sense. But then again, neither do most of the stupid trends in "software engineering".

>>713
No way. I couldn't even begin to explain how http://bbs.progrider.org/prog/read/1444460614 works and I wrote it only a month ago. I certainly don't agree that I've gotten worse.

Your problem, Cudder, is that all those hormone replacement drugs have eaten a hole in the part of your brain that lets you do academic circlejerking properly. You spend too much time on long projects like writing that web browser in 6502 assembly or the IDA killer or the SoftICE replacement or whatever and never just program something that popped into your head on a whim. You're a Michelangelo in a world that needs Picassos. Lighten up a bit, light up a blunt, and program something fun.

>>716
That is expected, you are using lisp.

>>716
You are certainly degrading. That's just Church numerals done using lists instead of function applications. Nothing interesting about that. (I do know about "academic circlejerking" and all that abstract bullshite, but whether I actually want to do that stuff is a different matter.)

light up a blunt

That explains a lot...

>>716
No wonder you can't explain how it works: it's unreadable from all the define bloat! Should've used def instead.

>>719
Clojure is not a LISP.