Become a fan of Slashdot on Facebook


Forgot your password?

Comment: Re:Social Networking is a mess (Score 1) 58

by BronsCon (#48897329) Attached to: Twitter Moves To Curb Instagram Links

Especially static content, and especially when the content of the article is a series of sentences punctuated by big squares that, rather than loading images, contain redirects to the images that some doofus tweeted.

And this is where your understanding of the problem fails.

Again, this is a middle-management and bean counter problem, not a developer problem. The developers don't sit there and ask "How can we add more Twitter to our pages?" On the contrary, the bean counters say "We can save on bandwidth by letting Twitter and Instagram host our images, while at the same time monetizing our users through forced interaction" and the managers relay that as "Give us the ability to easily link to Twitter and Instagram images or go find another job".

And, of course, the developers do it. Why? And why shouldn't you fault them for it? Because they know damn well that if they go work somewhere else, it's just more of the same, from the same kind of shitty bean counters and managers who don't understand that this shit kills their user base, in turn killing their income. If they don't do it for their current employer, they'll be asked to do it for their next, and the one after that, and after that, and so on, and so forth, until they are unemployable. Even McDonalds won't hire them after they're on their 6th job in a year. Then they starve.

Comment: Re:Social Networking is a mess (Score 1) 58

by BronsCon (#48897307) Attached to: Twitter Moves To Curb Instagram Links
Jerky scrolling sounds more like they've got you using underpowered machines. There's no excuse, on modern hardware, for the process of loading and rendering an image to bog the machine down to the point that the UI is affected. I say this having used, and developed on, a single-core Atom based netbook, exclusively, from 2007-2010, without issue; but then, I tend to develop as though resources are limited, since that was actually the case for me for the first 28 years of my life.

I can totally see other developers, who haven't been conditioned to realize that system resources are finite and not everyone has the latest and greatest CPU and GPU with oodles of RAM and gigabit internet (I wish... 150mbps is the best I can get and it's not worth the expense), assuming, since their code only lags slightly on their maching (which they blame, of course, on the browser dev tools), that it will, at worst, only lag a little on the user's machine which, typically, is much *much* less powerful.

I struggled for over 4 years to get my former boss to see this as a problem. Former boss. For a reason. We started losing clients as more and more javascript was added to the sites we were hosting and page render times went through the roof, but optimizing client-side code was forbidden; it didn't run on our servers, so it wasn't our problem and, besides, it ran fine for us, so there must not actually have been a problem. Or so he said. Of course, I knew better, and I still do, but that knowledge failed to transfer and the bloat continues in my absence, getting worse by the week.

So, I really don't blame the developers implementing the shit code, even; it all comes back to the idiot telling them not to fix what's broken, because they don't see how or why it's broken in the first place.

I worked for myself for 7 years before taking that job and I watched the quality of my code steadily decline while I was there. I've only been working for myself again for a little less than 2 months and I'm already seeing the quality of my output shooting back up to where it was 4 years ago, and still climbing, as I've learned much over the past 4 years, on top of simply having better tools now than I did then.

Without that perspective, though, I see how easy it is to blame developers for everything, but the reality is much, much different in most cases and developers don't get to choose to write good code; they only get to choose between writing shit code for their current employer or for their next. Sometimes that's because the employer sucks and sometimes it's because they suck; I've talked about both here.

Comment: Re:Social Networking is a mess (Score 1) 58

by BronsCon (#48897123) Attached to: Twitter Moves To Curb Instagram Links
Bingo. Well, almost. What you're complaining about can be done effectively and correctly, as well. Assuming it's done intelligently, with properly-sized placeholders so loading the images won't move other content around and ensuring that images less than one full-screen-scroll away are loaded, it's a decent way to save bandwidth without annoying users. That said, it also requires estimating the user's connection speed based on load times for the images that have loaded thus far, so you can disable it and just load the remaining images (in order of appearance) if the user is on a connection slow enough that they might miss images while scrolling because they haven't loaded by the time the user scrolls past.

Don't get me started on sites that don't even start loading the images until they're scrolled into view and don't use placeholders, so the images, when they finally do load push down the content you were reading. If I understand correctly, that's what you're talking about and yes, as a web developer, it annoys me to no end when some code monkey pulls that shit and sullies my good name, and that of the other competent developers I know.

Comment: Re:Social Networking is a mess (Score 1) 58

by BronsCon (#48897099) Attached to: Twitter Moves To Curb Instagram Links
That is most definitely "not used properly". I may have misspoke when I said no image tags, actually, as my preferred implementation is to use a 1px transparent PNG as the default SRC for the image tags, so they can still be inline on the page, with width and height specified (via CSS, of course). Done correctly, as I was saying, no images or scripts load until the text content of the page has loaded and rendered and you are able to start reading the article.

It's not even that hard to do, but most devs don't take the time to think about it, usually because they're not allowed to spend their time on such things. Again, blame shit-tire middle management and bean counters for that.

Comment: Re:Social Networking is a mess (Score 1) 58

by BronsCon (#48897011) Attached to: Twitter Moves To Curb Instagram Links
Actually, genius, "Javashit", as you call it, when used properly, is leaps and bounds better than iFrames. Imagine the article loading in its entirety, so you can start reading it, before there's even a single image tag on the page; then, well-written javascript popping the images in as you read. The content loads and renders faster and you have an over-all better experience, especialy if you happen to be on a mobile device or slow connection.

But that's cool, just go on blaming web developers and technology, keep shielding the bean counters and middle managers who refuse to consider the end users and force us to either create complete shite or move on to the next job, where we'll be forced to make the same decision again... and again... and again.

Comment: Re: Fuck Me (Score 1) 552

by BronsCon (#48824991) Attached to: SystemD Gains New Networking Features
First of all, parsing error... after reading your response a few times, I think I've deciphered it, though, so here goes...

You do realize that Ubuntu does, in fact, already have a systemd unit for NSS, right? I'm not the only one having this issue and both Debian and Ubuntu maintainers don't seem to know what to do to fix it, but go on ahead and assume it's my failing; deity-forbid you take 2 seconds to google the issue.


Comment: Re:Fuck Me (Score 2) 552

by BronsCon (#48823321) Attached to: SystemD Gains New Networking Features

I never had the problem you describe

Good for you? Is your NSS configured to require LDAP (other than the fact that the only local user account with a shell is root)? Otherwise, if NSS will fall back to "files" if LDAP fails, it sounds like your configuration and my workaround are one and the same.

This is BS, I can't even believe Debian and Ubuntu maintainers are so bad, where's the bug report ?

Right here.

So this must actually be a bug tied to sysv compatibility, as you're talking about these broken ifup/ifdown scripts.

No. Read what I wrote.

The current "recommended" workaround is a pair of ifup/down scripts...

In other words, the scripts aren't broken, they don't exist; the workaround is to create them. It's actually the sysv compatibility layer that allows the fix.

The reason that every major university maintains a department of mathematics is that it's cheaper than institutionalizing all those people.