5 ms·
a drastically simpler set of web standards, so that making web browsers would become much simpler Yes, yes, yes! would be relatively fast moving, not focused
by userbinator 6y ago
a drastically simpler set of web standards, so that making web browsers would become much simpler
Yes, yes, yes!
would be relatively fast moving, not focused on backwards compatibility
No, no, no! Constant churn is precisely the problem with the web today, as it is what creates all that complexity and bloat. What you really need is a simple and stable set of standards, ideally something that won't change in decades (somewhat like how ASCII has been) so that any implementors don't have to engage in mindless trendchasing.
In fact, we already have a simpler set of web standards. It's called HTML4 and CSS2. Browsers like Dillo and NetSurf handle them well, and site like HN and Craigslist are an example of what the resulting format is like.
- p4bl0 6y agoWhat you say makes me think of the gemini project :). https://gemini.circumlunar.space/ https://gemini.circumlunar.space/
- Aeolun 6y agoThere is no chance in hell that you’d get the general web to move back to floating divs to manage layout.
- core-questions 6y agoNo problem, you don't need that. Just use tables.
- dathinab 6y agoNo just css grid, that's all we ever wanted ;=) (But honestly tables suck bad time, I did wrote some table base hobby website back in 2009? or so and it wasn't nice (the experience, not the website which was quite fine). Sure basing a GUI on a grid is the best thing to do in many cases but tables are no grids. Grids are more flexible.)
- inopinatus 6y agoNot sure if you’re joking, because CSS Grid does provide 99% of my layout needs. (or it would if 5% of my users weren’t still using IE11, but that’s another story.)
- koolba 6y agoThe biggest problem with tables was that they worked.
- bluejekyll 6y agoExcept if you need to support different device sizes and dynamic layout.
- laumars 6y agoI’m not defending table based layout but in fairness different device sizes was less of an issue back then because almost all browsing was done on a PC or Mac and thus dynamic layout wasn't even something you needed to considerate.
- bluejekyll 6y agoWell, my point was more that it’s not a great option today. You’re right, back in the day when everyone’s screen sizes were somewhat consistent, it worked, though still had many quirks.
- chriswarbo 6y ago> different device sizes was less of an issue back then because almost all browsing was done on a PC or Mac and thus dynamic layout wasn't even something you needed to considerate. It saddens me when Web sites assume they are in a full-screen window :(
- _underfl0w_ 6y agoImpressive that you remembered having two sets of nested parentheses going by the end of your comment and closed them correctly. Perhaps that's part of the problem...
- zzo38computer 6y agoTables should be used for data, not for layout.
- wildrhythms 6y agoThis is true, <table> elements are for tabular data. But look at almost any web layout, and you will notice things are in a table layout most of the time. Even flexbox conceptualizes the flow of children as flex-direction: row/column. I think tabular concepts like rows and columns just make sense to humans making websites, and our 2D x/y axis conditioning. The real issue with using <table> is semanticism, breaking DOM flow (sometimes creates issues for screen readers), and separation of concerns wrt data and style like you mentioned. Also, <table>s are hard to style over, like wtf is display: table-cell? Nobody seems to know. But the number of times I see a colleague or fellow frontend cretin re-creating a tabular interface with a bunch of <div class="row"> etc... or wondering how to dynamically size the nested columns to fit the largest cell, I remind them: just use a table. Please. You might notice that Hacker News layout uses <table>.
- core-questions 6y agoAll I can say is whatever, man. The semantic web and all the RDF tuple goodness we were supposed to get is mostly a dead dream. Make whatever works for your users. Accept that things aren't going to be pure and perfect. If tables gets me to where I need to be, then that's what I'll use. Worked 20 years ago, works now, will work 20 years from now too.
- goto11 6y agoI can't imagine any actual web designer wanting to trade flexbox/grid for tables.
- core-questions 6y agoWhat if I told you that there are people who make "web applications" that aren't beautiful or "designer" quality?
- goto11 6y agoGood for them - but a browser which only cater to them is not going to be successful.
- Grumbledour 6y agoI never really understood what people have against float. I think it works fine for most use cases and is not to difficult. Now table layouts where quite a pain because they got very complex very fast. Flexbox and Grid are fine I guess, but I always found them a bit harder to understand than float and did not so much they offered that I needed.
- deleted 6y ago[deleted]
- kybernetikos 6y agoThat's the key problem - everyone who thinks the web is broken thinks it's broken in different ways.
- dathinab 6y ago> ASCII has been Which of the view tens or so ascii's you mean? Probably us-ascii right? I.e. a thing so limited that it's only supports english and not even most of the other Latin writing based languages. On the other side if we speak about plain text it hasn't be that stable at all for many years and only somewhat stabilized now with Unicode + utf-8 and utf-16 for legacy reasons. And even now we still frequently get Unicode updates. The idea that us-ascii is enough/usable/acceptable for anything interfacing with users is IMHO a bubble limited to (small? part of) IT people from certain english native countries. > In fact, we already have a simpler set of web standards. It's called HTML4 and CSS2. CSS2 isn't simple. It's also fundamentally unsuited for web applications, which IMHO was still also true for CSS3 until recently (css gid). I mean think about how frameworks (e.g. bootstrap) for years did all kinds of tricks to emulate a css gird like features. Also HTML5 tags like header/footer/article etc. are a must have IMHO and something like custom elements for better composition and reuse are a must have, too. The problem with the current complexity of the web lies in my opinion in the combination of how all kind of features where bolted on top of a foundation which wasn't designed for given use cases and many of this features being over engineered. So I believe such an approach needs to fundamentally revamp or replace both the DOM API and CSS.
- Uther 6y agoThe only real charset we should call ASCII is the 7-bit original standard. The 8-bits charsets are ASCII extensions.
- inopinatus 6y agoBring back DSSSL. After all, what language has a better ratio of fundamental simplicity to expressive power than Scheme? Much of the emergent complexity of styles is due to CSS selectors being intentionally non-Turing-complete.
- dllthomas 6y ago> better ratio of fundamental simplicity to power That's an odd ratio to consider. Is high better or low? Or is there some particular positive optimal value we want to target?
- inopinatus 6y agoAh, that’s meant as a qualitative figure of speech, not a measurable objective function. Intended to express that Scheme is a simple language that remains apparently simple even when you build tremendously powerful constructs within it and upon it. In this case by contrast with CSS where no matter how much sophistication one tries to introduce into the styles its capabilities seem to be horizontally asymptotic or very substantially sublinear. I reach for the word ratio because the concept (of two parameters whose magnitude varies and that would be meaningful in some relation) is a friend, and the word “better” is a writing trick to avoid having to define exactly what those are whilst still expressing the sentiment.
- deleted 6y ago[deleted]
- dllthomas 6y ago> I reach for the word ratio because the concept (of two parameters whose magnitude varies and that would be meaningful in some relation) is a friend, and the word “better” is a writing trick to avoid having to define exactly what those are whilst still expressing the sentiment. The use of ratio is entirely appropriate for conveying this, even in non-technical settings (and such use is pretty common). But to my ear, there's a definite implication that the relationship involves the two things typically moving in the same direction (and roughly linearly) such that it's notable when they've moved in opposite directions. (It's still very much qualitative - we're not really going to be able to assign meaningful numbers). Had you spoken of complexity/power, I wouldn't have noticed anything unusual. Even so, I only really commented because I was enjoying playing with the idea of a simplicity/power ratio being somehow informative.
- om2 6y agoHTML4 and CSS2 are drastically underspecified. Even for sites where that's a sufficient feature set, you need to reverse-engineer browsers to figure out error handling and such.
- efojs 6y agoMaybe something like Pipfile.lock for a site and browser knows what standards to use?
- bzbarsky 6y agoUnfortunately, HTML4 and CSS2 are severely underspecified, so actually implementing them interoperably without reverse-engineering is impossible. Oh, and some places where they _are_ clearly specified that specification is more or less broken. For example, implementing comment parsing per the letter of the HTML4 spec is extremely not-web-compatible, and I doubt that either Dillo or NetSurf do it... Now if you know which things to avoid (e.g. never put "--" inside your comments) and don't care about "pixel-perfect" rendering or any sort of interesting layout, HTML4 and CSS2 are not terrible. But if you care about any of that, watch out for dragons. And before someone brings up "tables" for "interesting layout": table layout is unspecified. In CSS2, and CSS3 for that matter. Not only is it unspecified, it's not entirely interoperable across browsers even now, after literally decades of reverse-engineering each other. And for extra fun, WebKit/Blink's implementation is definitely not interoperable with the IE (Trident) implementation most table-based layouts targeted... As one example, changing the order of rows in the table can change the column widths in Blink but not in Trident. Anyway, if one wanted to start with HTML4 and CSS2, one _could_ try to turn them into proper standards that can be interoperably implemented. It would take quite a lot of effort to do that, I suspect. 50 person-years is my initial guess, but there are a _lot_ of unknowns involved and a lot would depend on how much of the HTML5 and CSS-post-2 work that defined things rigorously could be leveraged.
- userbinator 6y agoand don't care about "pixel-perfect" rendering or any sort of interesting layout A common theme in all these "reinvent the web/browser" discussion is going back to the web as a hyperlinked document library and not an application platform, in which case pixel-perfect rendering is neither necesary nor even a goal. For example, implementing comment parsing per the letter of the HTML4 spec is extremely not-web-compatible HTML5 parsing is completely specified and definitely compatible, even the error cases. Any stream of bytes will turn into a DOM. (Philosophical question: are they even errors anymore, if all implementations will produce the same output?) Perhaps that would be a good starting point.
- tannhaeuser 6y agoRegarding your philosophical question: a markup language that accepts any byte sequence is clearly useless and a travesty of the concept of markup languages as an authoring format.
- mikorym 6y agoWouldn't the first stable release of HTML count as "a drastically simpler set of web standards" together with the fact that any browser should support it? Everything else is to me a matter of compression. Netflix's success seemed to me 50% good marketing and content and 50% compression and data handling. It is wrong to think that a webpage has some sort of canonical view on it. And FB, Twitter and even Forbes is all about generating the impression of group perspective being one thing as opposed to be views on one, perhaps elusive, thing.
- goto11 6y ago> HTML4 and CSS2 So no flexbox and grid? Back to using tables and floats for layout? (And reintroducing framesets and font tags!) Good luck getting web designers on board.