That's why the investigation is taking so long: the rules for "classified" are vague, arbitrary, inconsistent, poorly documented, and basically fscked up.
They really need a working group to study and clean up the rules and procedures, not a criminal investigation. It's hard to bust somebody for vaguing the fuzz.
Because everyone has perfect sight, wants the same size browser window as the developer, browses at 100% zoom level
You don't appear to understand what I'm asking for. I'm not against zooming. Basic zooming is just simple coordinate multiplication and doesn't need to trigger re-flow.
And I'm not against device-specific re-formatting: I just want the SERVER to do it so that one is working with a single layout engine instead of gajillion different layout engines per client brand/version.
with the same fonts
Why the hell does the web surfer need to dick with the fonts?
And I'm not against semantic info being supplied in the background for ADA (disability) etc. Just don't strangle layout to get it. Existing stuff already does similar with ALT attributes.
Right now, with a modern browser, it's pretty simple to build a page with just html and css that adjusts perfectly to fit the viewport, scaling everything (text included) as though you were scaling vector image as the size and aspect ratio of the viewport changes.
The computer cannot make practical esthetic adjustments for coincidental oddities that one would normally hand-fix with WYSIWYG layouts. It's following brain-dead rules, and is OFTEN different between client brands/versions.
If a boss says "I want this to appear right here", you want it to be right there and only right there.
The current way might give one "good enough" with enough tuning, but it's a lot of fiddle faddle and cross-device testing.
Maybe the very very best can pull it off, but it's driving the other 90% of us crazy, like quantum rules: it's a particle on device X but a wave on device Y, and kills cats on device Z.
but there's already very little variation in the basic layout of websites today.
If you mean fads, yes, but fads also change like the wind.
We'd lose a bit of creative freedom
Again, it's NOT where the boss/customer asked you to put it, but has a mind of its own. It's not just me, the customer wants what the customer wants.
And I am not against device-specific layout adjustment, I'm just against the CLIENT calculating it. Let the server do it if you want it so that you can control it and the same logic happens regardless of client brand/version.
It's far far easier to tame the server. Easier to work with ONE layout engine than 47 (client brand/versions).
I'd rather see is far less control over formatting and layout and more emphasis on semantic markup
Server-centric resizing/re-reflowing doesn't conflict with that goal.
At least the industry should experiment. I'm pretty damned sure we are nowhere near the best possible way to do it (or we don't have enough alternatives per need variation).
Set sail, Server-Controlled Columbus, and discover the New Land. The old land is strangled with maggot-filled pasta.
Partly because PDF is based around paper's pagination; and it wasn't originally designed for interaction, which would be needed for GUI's. Parts of it could be borrowed for the new World Wide GUI when we replace the damned auto-flow crap and burn the bastard to the ground and dance around the fire. Oops, I forgot to shut off rant-mode.
Another thing, why are CSS and HTML different languages? Can we find a common language and/or syntax style? Do we really need them to be so different? Some kind of tag inheritance seems a better way to go. A "style" can be based around a prototype tag(s), and an actual tag inherits the attributes. Rough idea:
<style>
<class name="foo">
<* font-size="10pt"/> <!-- wild-card tag --> <div color="#334455"/> <!-- only applies to DIV's --} </class> ... </style> <body> ... <div class="foo">My Text</div>
need something like this to get a good look at Planet IX once we find it.
Indeed! It would take a traditional probe roughly 50 years to reach the estimated distance.
Plus, communication is a much easier problem for Planet IX-like distances than for stars.
It would be interesting to test such a gizmo on Pluto even. We didn't get a decent look at one entire hemisphere because New Horizons was moving too fast relative to Pluto's 6-day rotational period. Send a nano-probe to check out the "blurry" side.
*sigh* The error message isn't for that user, it's for the person they call for help.
Then it's a crap error message...
The error message should be for BOTH. You can give the user a decent general idea of what went wrong, but also give tech details for the help-desk etc. Example:
"Sorry, the email service cannot accept your message. It's not responding as expected. Click for details [button or hyperlink]."
The detail screen would then say something like:
Error Details Error Code: 48271 Full Description: "The SMTP server that is designated to process messages is responding, but could not understand one or more commands that this application sent to it. Suggestion: switch on SMTP logging in the [application's] Settings, Messaging, Logging menu."
Why is the www so complicated, just give me my HTML 1.0
Because people want desktop-like UI's in HTML browsers, and that's NOT what they were designed for, and kludges to get it are uglier than Trump's ass after a long sweaty horse-ride while lost in the mountains.
Time for new GUI-friendly standard. For one, get rid of client-side "auto-flow" and make it coordinate based so that each browser and version doesn't put things in different places. WYSIWYG, dammit.
It's why designers miss Flash: client-side autoflow doesn't fuck your design and spacing to hell. Fuck auto-flow to hell! Burn Baby Burn! Autoburn! It's the Iraq-invasion of IT standards decisions.
Dev was 5x faster without goddam auto-flow issues. Any window resizing calcs can take place on the server. If resize calcs happen on the server, then the results are consistent across device versions and makes (and custom OS settings). People don't resize that often, so it doesn't matter much if it's slower doing server-side sizing, so don't give that complaint.
I've read of attempts to calculate the odds of a fatal impact for such high-speed probes, and it's surprisingly low considering, roughly like between 0.5% and 5%. Outside of planetary systems, space is quite sparse.
Relax, you have 20 years before the encounter to figure it out. Just don't procrastinate until year 19 and try to rush breakthroughs.
Otherwise, you'll feel like the New Horizons crew when the probe croaked 10 days from Pluto encounter. I bet that was a mega-stresser. (Fortunately they solved the glitch in time.)
There must be some interesting forms at such orgs:
Strike Category:
1. (_) Intimidation Only:
1.1 (_) Fake horse head in bed 1.2 (_) Real horse head in bed (high budget only) 1.3 (_) Install Windows 10 on home PC 1.4 (_) Smash car: . . . . [_] Windshield [_] Body [_] Tire pop
2. (_) Injury:
2.1 (_) Strike to Knee: # of strikes: _____ 2.2 (_) Gut hit: # of hits: _____
3. (_) Finish Off:
3.1 (_) Cement galoshes 3.2 (_) Swimmin' with d' fishies 3.3 (_) Car "accident" 3.4 (_) Other: ____________________
In my observation, men seem to be inherently careless about house-work relative to the average/typical woman. Women notice details that men seem lackadaisical about.
Maybe it's only a generational thing and it will someday even out, but my gut feeling is that women have an inherent "nesting instinct" that man don't. We don't have enough empirical data to prove it either way because social factors of the current society are difficult to remove from "tests".
In the 15 years of my professional career, there's only been one day when I didn't want to come to work...That was the day after the IT department accused me of intentionally crashing their network
I once was accused of sabotaging a project also, so I know the feeling. I argued back, but what I should have done is said in calm but direct voice, "I'm personally and deeply offended by that accusation." and then walked out for the rest of the day.
They probably wouldn't make it an issue with HR because an investigation would have exposed their own incompetence, and they knew it.
Well, it will be interesting if the new social dynamic affords men not to be judged on the size of their bank accounts, and allows them to be less competitive in the workplace.
I suspect it's fairly ingrained in women's biology, similar to how men naturally pay attention to a female's appearance. Lecturing isn't going change what makes our wanker happy, and our wanker has a hell of a lot of voting power in the male decision process, thanks to Mother/Father Nature.
Maybe the availability of porn and perhaps fake robo-females will make men care less about attracting real females and women will just have to put up with "basement rats" that men are becoming.
Hell, I hope the next big war is fought [also] by women. Let them [participate in] blood sacrifice...
Indeed! A case of "be careful what you ask for"...
And why is auto insurance lopsided by gender but not medical insurance?
"Computer Studies" is the most generic term I have been able to think of to cover a sufficient gamut.
BUT it sounds too fluffy, closer to liberal arts. People pay an arm and leg for college, and they don't want a fluffy-sounding result.
People won't attend a college who gives them a fluffy-sounding degree when they have reasonable alternatives. They fear it makes their resume look weak.
Thus, for appearance/marketing reasons, "Computer Science" won't go away any time soon. Humans are that way.
Well, okay, I will agree that it can make a fairly large impact on general language design, but it seems there's a need for BOTH kinds of GC handling, and it's probably still better to have a "near twin" pair of languages that caters to both types to simplify the learning curve and perhaps library creation.
Making it a mere keyword or compile switch would be nice, but if the differences MUST be great enough to force having two different languages, at least make them similar. Maybe there is a way to consolidate that nobody's thought of yet...
I'm not sure how to explain this without sounding like a misogynist, but careers are often more important to men because men are more often judged by income. There is strong social pressure on men to work hard for raises and promotions because of this. Women tend to be socially judged on looks, not earnings, and thus they focus more on that.
This is not saying women are inherently lazy, only that there is less social pressure on them to succeed in the work-place, and thus more women on average just coast in their career.
Women also end up having to deal with family issues more, in part because they care more about family and home, and in part because men are on average domestically flaky. This means women will focus on domestic issues more, distracting them from career.
I'm not sure how to measure or address these, but if they are not addressed, there could be some unpleasant side-effects.
easier to get a new phone number than [move your] farm
True, but the flip side is that more families were affected, being there are hundreds of area codes with the same phone number (last 7 digits).
One screws a handful of families really badly (lat/long), and the other lightly screws hundreds of families. The total "pain" is roughly a wash, as measured by the estimated volume of Pepto-Bismol sold.
Slashdot Mirror
That's why the investigation is taking so long: the rules for "classified" are vague, arbitrary, inconsistent, poorly documented, and basically fscked up.
They really need a working group to study and clean up the rules and procedures, not a criminal investigation. It's hard to bust somebody for vaguing the fuzz.
You don't appear to understand what I'm asking for. I'm not against zooming. Basic zooming is just simple coordinate multiplication and doesn't need to trigger re-flow.
And I'm not against device-specific re-formatting: I just want the SERVER to do it so that one is working with a single layout engine instead of gajillion different layout engines per client brand/version.
Why the hell does the web surfer need to dick with the fonts?
And I'm not against semantic info being supplied in the background for ADA (disability) etc. Just don't strangle layout to get it. Existing stuff already does similar with ALT attributes.
The computer cannot make practical esthetic adjustments for coincidental oddities that one would normally hand-fix with WYSIWYG layouts. It's following brain-dead rules, and is OFTEN different between client brands/versions.
If a boss says "I want this to appear right here", you want it to be right there and only right there.
The current way might give one "good enough" with enough tuning, but it's a lot of fiddle faddle and cross-device testing.
Maybe the very very best can pull it off, but it's driving the other 90% of us crazy, like quantum rules: it's a particle on device X but a wave on device Y, and kills cats on device Z.
If you mean fads, yes, but fads also change like the wind.
Again, it's NOT where the boss/customer asked you to put it, but has a mind of its own. It's not just me, the customer wants what the customer wants.
And I am not against device-specific layout adjustment, I'm just against the CLIENT calculating it. Let the server do it if you want it so that you can control it and the same logic happens regardless of client brand/version.
It's far far easier to tame the server. Easier to work with ONE layout engine than 47 (client brand/versions).
Server-centric resizing/re-reflowing doesn't conflict with that goal.
At least the industry should experiment. I'm pretty damned sure we are nowhere near the best possible way to do it (or we don't have enough alternatives per need variation).
Set sail, Server-Controlled Columbus, and discover the New Land. The old land is strangled with maggot-filled pasta.
Sorry, my indentation somehow went kaphlooey. Let me try underscores this time:
The wild-card tag looks to much like a comment. Ponder...
Partly because PDF is based around paper's pagination; and it wasn't originally designed for interaction, which would be needed for GUI's. Parts of it could be borrowed for the new World Wide GUI when we replace the damned auto-flow crap and burn the bastard to the ground and dance around the fire. Oops, I forgot to shut off rant-mode.
Another thing, why are CSS and HTML different languages? Can we find a common language and/or syntax style? Do we really need them to be so different? Some kind of tag inheritance seems a better way to go. A "style" can be based around a prototype tag(s), and an actual tag inherits the attributes. Rough idea:
Indeed! It would take a traditional probe roughly 50 years to reach the estimated distance.
Plus, communication is a much easier problem for Planet IX-like distances than for stars.
It would be interesting to test such a gizmo on Pluto even. We didn't get a decent look at one entire hemisphere because New Horizons was moving too fast relative to Pluto's 6-day rotational period. Send a nano-probe to check out the "blurry" side.
The error message should be for BOTH. You can give the user a decent general idea of what went wrong, but also give tech details for the help-desk etc. Example:
"Sorry, the email service cannot accept your message. It's not responding as expected. Click for details [button or hyperlink]."
The detail screen would then say something like:
Error Details
Error Code: 48271
Full Description: "The SMTP server that is designated to process messages is responding, but could not understand one or more commands that this application sent to it. Suggestion: switch on SMTP logging in the [application's] Settings, Messaging, Logging menu."
For this topic, I'll keep it that way, thanks
Just take away beer now also, and then you'll have a real impact.
Because people want desktop-like UI's in HTML browsers, and that's NOT what they were designed for, and kludges to get it are uglier than Trump's ass after a long sweaty horse-ride while lost in the mountains.
Time for new GUI-friendly standard. For one, get rid of client-side "auto-flow" and make it coordinate based so that each browser and version doesn't put things in different places. WYSIWYG, dammit.
It's why designers miss Flash: client-side autoflow doesn't fuck your design and spacing to hell. Fuck auto-flow to hell! Burn Baby Burn! Autoburn! It's the Iraq-invasion of IT standards decisions.
Dev was 5x faster without goddam auto-flow issues. Any window resizing calcs can take place on the server. If resize calcs happen on the server, then the results are consistent across device versions and makes (and custom OS settings). People don't resize that often, so it doesn't matter much if it's slower doing server-side sizing, so don't give that complaint.
Be Brave:
Throw it Out!
Do it Right!
I've read of attempts to calculate the odds of a fatal impact for such high-speed probes, and it's surprisingly low considering, roughly like between 0.5% and 5%. Outside of planetary systems, space is quite sparse.
Relax, you have 20 years before the encounter to figure it out. Just don't procrastinate until year 19 and try to rush breakthroughs.
Otherwise, you'll feel like the New Horizons crew when the probe croaked 10 days from Pluto encounter. I bet that was a mega-stresser. (Fortunately they solved the glitch in time.)
There must be some interesting forms at such orgs:
Strike Category:
1. (_) Intimidation Only:
1.1 (_) Fake horse head in bed
1.2 (_) Real horse head in bed (high budget only)
1.3 (_) Install Windows 10 on home PC
1.4 (_) Smash car:
. . . . [_] Windshield [_] Body [_] Tire pop
2. (_) Injury:
2.1 (_) Strike to Knee: # of strikes: _____
2.2 (_) Gut hit: # of hits: _____
3. (_) Finish Off:
3.1 (_) Cement galoshes
3.2 (_) Swimmin' with d' fishies
3.3 (_) Car "accident"
3.4 (_) Other: ____________________
In my observation, men seem to be inherently careless about house-work relative to the average/typical woman. Women notice details that men seem lackadaisical about.
Maybe it's only a generational thing and it will someday even out, but my gut feeling is that women have an inherent "nesting instinct" that man don't. We don't have enough empirical data to prove it either way because social factors of the current society are difficult to remove from "tests".
I don't normally study vomit that carefully, and I have no intention of starting.
I once was accused of sabotaging a project also, so I know the feeling. I argued back, but what I should have done is said in calm but direct voice, "I'm personally and deeply offended by that accusation." and then walked out for the rest of the day.
They probably wouldn't make it an issue with HR because an investigation would have exposed their own incompetence, and they knew it.
Reply: Well, you were dumb enough to use them
Here's the last time MS over-did BSOD's
I found an appropriate emoji.
I think that's a core dump.
If he loses the election: NO.
If he wins the election: YES.
If he wins the election but triggers Armageddon: NO. (There won't be any history books)
If he loses the election but triggers Armageddon anyhow via his YUUUGE mouth: NO.
I suspect it's fairly ingrained in women's biology, similar to how men naturally pay attention to a female's appearance. Lecturing isn't going change what makes our wanker happy, and our wanker has a hell of a lot of voting power in the male decision process, thanks to Mother/Father Nature.
Maybe the availability of porn and perhaps fake robo-females will make men care less about attracting real females and women will just have to put up with "basement rats" that men are becoming.
Indeed! A case of "be careful what you ask for"...
And why is auto insurance lopsided by gender but not medical insurance?
And alimony in some states.
"Computer Studies" is the most generic term I have been able to think of to cover a sufficient gamut.
BUT it sounds too fluffy, closer to liberal arts. People pay an arm and leg for college, and they don't want a fluffy-sounding result.
People won't attend a college who gives them a fluffy-sounding degree when they have reasonable alternatives. They fear it makes their resume look weak.
Thus, for appearance/marketing reasons, "Computer Science" won't go away any time soon. Humans are that way.
Well, okay, I will agree that it can make a fairly large impact on general language design, but it seems there's a need for BOTH kinds of GC handling, and it's probably still better to have a "near twin" pair of languages that caters to both types to simplify the learning curve and perhaps library creation.
Making it a mere keyword or compile switch would be nice, but if the differences MUST be great enough to force having two different languages, at least make them similar. Maybe there is a way to consolidate that nobody's thought of yet...
I'm not sure how to explain this without sounding like a misogynist, but careers are often more important to men because men are more often judged by income. There is strong social pressure on men to work hard for raises and promotions because of this. Women tend to be socially judged on looks, not earnings, and thus they focus more on that.
This is not saying women are inherently lazy, only that there is less social pressure on them to succeed in the work-place, and thus more women on average just coast in their career.
Women also end up having to deal with family issues more, in part because they care more about family and home, and in part because men are on average domestically flaky. This means women will focus on domestic issues more, distracting them from career.
I'm not sure how to measure or address these, but if they are not addressed, there could be some unpleasant side-effects.
True, but the flip side is that more families were affected, being there are hundreds of area codes with the same phone number (last 7 digits).
One screws a handful of families really badly (lat/long), and the other lightly screws hundreds of families. The total "pain" is roughly a wash, as measured by the estimated volume of Pepto-Bismol sold.
(Yes, the ol' Pepto-Bismol metric of anguish.)