101–110 of 280 posts
Makes you wonder why HN won't budge with those tags in the source code. One day I hope to see "Table layouts are back with tags" and the HN programmers would have saved themselves so much work.
What, exactly, is the problem with the tag in the first place? Been a long, long time since I last touched HTML
Earlier quoted context omitted.
We had a simpler standard in 1995. It was called tables and it did this exceptionally well and more importantly was easy enough for even amateurs to understand. And then armchair demagogues decided that markup should no longer be used for markup, setting web layout back decades and creating the field of web designers whose major accomplishment was understanding stupid div hacks.
Your comment is the best example of the demagogue. Zero understanding of the issue, the problems that tables caused. But it was easy, right?
Makes you wonder why HN won't budge with those tags in the source code. One day I hope to see "Table layouts are back with tags" and the HN programmers would have saved themselves so much work.
What, exactly, is the problem with the tag in the first place? Been a long, long time since I last touched HTML
I still use plain old tables in 2017. Number of unhappy customers: 0
Number of unhappy front-end developers : 1 ( me, so far ). Hope nobody will have to modify your stylesheets.
I still use plain old tables in 2017. Number of unhappy customers: 0
Of course this is anecdotal, but I wonder wether it'd be just easier for browsers to just improve table performance.
Earlier quoted context omitted.
What, exactly, is the problem with the tag in the first place? Been a long, long time since I last touched HTML
Little irritations like: A form is not allowed to be a child element of a table, tbody or tr. There are workarounds.
Earlier quoted context omitted.
That's a problem to be sure, but sometimes I wonder if this is much better:
That's a problem for sure but last week I looked into creating a family tree with the basics of HTML and CSS and the following nested lists seems to be the best solution according to forums. Now, try to add into these nested lists some siblings(the people kind) and some new branches as you discover people in census reports from 100 years ago. Now add in a newborn. Is this the best we can do? (apologies, but I haven't…
Earlier quoted context omitted.
I think there's a distinction to be made between "web pages" and "web apps". Web pages like news articles and blog posts fit well in the semantic document model of HTML. Web apps extend past this model -- something like DPS would make more sense for them.
I think the lack of such a clear distinction is part of the web's success. For example, is Facebook a web page or a web app?
Is this a trick question? :) On the scale from pages to apps, where one end is someone's static geocities page about their cats and the other end is, let's say, github: Facebook is definitely an app.
This is excellent. And with the fast pace of browsers, and the improved habits of users (or automatic updates), it should be available for 95%+ of users within a year (It's in the current Safari Technology Preview, so Safari should get it with the next macOS point update). This is also a good moment to remind people that you don't need Bootstrap and the like as much as you used to. Grids were 90% or the reason people…
> it should be available for 95%+ of users within a year only if you don't have enterprise customers. Those will continue to run IE11 for the foreseeable future as IE11 will remain supported in Windows 10 until 2025. While Microsoft is pushing Edge as an IE replacement, Edge is still lacking features and looks too different from IE for companies to feel comfortable pushing it to their users without retraining them.
I chuckle when Google announces that Chrome will support this feature as the next big thing, while it was clear years ago that this approach is much better than flexbox. But, I'm glad it finally lands in all browsers.
Earlier quoted context omitted.
I do to, sometimes. I wonder if there is any thought given to making tables responsive rather than reinventing the wheel here.
The (theoretical) issue here is that a "table" has a certain semantic meaning ("a container for tabular data"), and that using a table for something outside that semantic meaning can introduce confusion, be it for fellow programmers (including your future self!) or for those who are interpreting your page in weird ways (robots, people using screen readers, etc.). In the few times I actually bother with frontend "desi…
And yes, I've been in this space for years, and this is one of the better example why I feel most of the webdev world is cargo-cult advice that's internally inconsistent if you look at it carefully.