Linked by Thom Holwerda on Wed 26th Dec 2012 00:32 UTC
OSNews, Generic OSes Now that the holidays are upon us (happy holidays!) and the year is about to end, we at OSNews thought it time to finally lift the veil a little bit on the next version of OSNews - OSNews 5. I've hinted at this next version of OSNews here and there in the comments, but we think it's time to make it all a little bit more official by taking in some initial feedback.
Thread beginning with comment 546326
To read all comments associated with this story, please click here.
Here's hoping
by deathshadow on Wed 26th Dec 2012 11:26 UTC
deathshadow
Member since:
2005-07-12

You do NOT waste time with HTML 5 asshattery, do NOT have a major case of divitus and classitus, and actually have semantic markup with separation of presentation from content.

Colors look ok, though a bit washed out. Here's hoping you do NOT make it a crappy fixed width, do NOT declare all the fonts in PX so I have to shove custom user.css at it to even make the page usable, and here's hoping that you might just leverage responsive layout via media queries so instead of screwing around wasting time making custom versions for each and every stupid handheld, you just send the same markup to everybody and adjust it via CSS to each device.

Though I really do cringe whenever people mention off the shelf CMS systems -- I've yet to see one that didn't shove half assed crappy markup down your throat that you either cannot change using the skinning system, or fixing somehow neuters the upgrade path... It's like the people writing CMS and forum softwares don't know enough HTML/CSS to be opening their mouths on the topic.

Though it could be worse, you could have said you were using Turdpress. King of the "What do you mean I don't need ten separate classes on every LI?!?" and "WCAG, what's that?!?"

Edited 2012-12-26 11:26 UTC

Reply Score: 2

RE: Here's hoping
by BallmerKnowsBest on Thu 27th Dec 2012 15:17 in reply to "Here's hoping"
BallmerKnowsBest Member since:
2008-06-02

Though I really do cringe whenever people mention off the shelf CMS systems -- I've yet to see one that didn't shove half assed crappy markup down your throat that you either cannot change using the skinning system, or fixing somehow neuters the upgrade path... It's like the people writing CMS and forum softwares don't know enough HTML/CSS to be opening their mouths on the topic.


The big problem with Drupal is that 95% (conservative estimate) of the people working with it have no experience with any other CMS, so they assume it's the best solution for every site. You can spot them immediately, they're the folks recommending Drupal for 3-5 page sites that barely warrant a CMS in the first place (much less one as heavyweight as Drupal).

Though it could be worse, you could have said you were using Turdpress. King of the "What do you mean I don't need ten separate classes on every LI?!?" and "WCAG, what's that?!?"


Hey now, WordPress is awesome... if you don't mind having your site compromised every other week, usually because of vulnerabilities in incompetently-written 3rd party plugins, which are necessary if you need anything other than the most basic functionality, at least until the next WordPress upgrade breaks compatibility with them, leaving you high and dry because the plugin's developer abandoned it 2 or 3 years ago, etc.

But at least WordPress isn't Joomla... or Zope/Plone.

Reply Parent Score: 3

RE[2]: Here's hoping
by deathshadow on Fri 28th Dec 2012 07:55 in reply to "RE: Here's hoping"
deathshadow Member since:
2005-07-12

Hey now, WordPress is awesome...

If you don't mind the idiotic wasteful use of the TITLE attribute and ten classes on every LI wasting all your bandwidth, and other garbage like that hardcoded into the system with ZERO control over it from the theme -- to the point the only way to fix it neuters the upgrade path.

... and it's easy to blame third party plugins, but that's like blaming a locked screen door for a completely open inner door -- you can peel it wide open with a knife in under a second. The underlying code wasn't built with even the slightest knowledge of security -- see the absolutely mind-numbingly stupid practice of putting the SQL Username, passwords and hostnames in global scope as DEFINE -- meaning even the simplest code elevation has 100% access to EVERYTHING. One ring protection is no protection at all.

... and of course the use of the steaming pile of manure known as HTML 5 has only made all these CMS even MORE of a mess -- what with the HTML 3.2 that used to masquerade as 4 Tranny, now having 5's lip-service wrapped around it; bad coding practices suddenly being advocated by the pointlessly redundant new allegedly "semantic" tags... resulting in even fatter bloated skins with code to content ranges that make sites from a decade ago sleazed out in Frontpage look good...

...and that's before we even get into idiotic BS like jquery or mootools that dev's now seem to have raging boners for, pissing all over the functionality, usability and speed of sites.

Reply Parent Score: 2