Quite a few people are absolutely happy to pay the premium (and you do need to be a stupid animal to even start looking at 'hey, who might be selling lossless DSD stream zips?') although not realizing that what they actually want is not the extra 8 bits bit rather the fact that no monkey execs have been let near the compression button.
But since MSFT is gone - it's about time to switch over and listen to crappy compressed records only now in 32bit/192khz quality!
Normal user will not differentiate between underlying OS (Android) and whatever manufacturer inspired gimmics are on top (HTC sense crap in example) or even worse: Operator dictated piles of steamy unsupported runny poo (and it always is. It just always is...).
Most of the security nonsense in European aeroports are due to requirements from USA, btw. Given that there's an occasional flight over to LA or whatever.
foreign aid is USA way of keeping smaller countries dependant on it and happily saying yes to anything USA wants.
Afghanistan might not have started if all the smaller states wouldn't have said 'Yes, let's pretend we all want it' under threats of withdrawing it. Iraq.
Exactly. Shut down a couple of backbone links (5 mins*) and the rest of the network will be immediately (2-3s) saturated enough to become unusable (from TCP perspective). While the wider internet tries to react (drop youtube traffic, expand peer arrangements, manually reroute stuff - 2-3h once it's clear core is down**) - plenty of time to go after core peering points in major cities.
Lather, rinse and repeat.
* Assumes that LE knows that they will need to action this at least 30 mins beforehand. ** Actually assumes that DR plans exist, which is... optimistic.
Uhm? And what's wrong with that? Given that the wikipedia articles are public, it would be expected that focus is on keeping the public-exposed content consistent with the editorial standards of the site (whether you like them or not, that's a different matter).
Leaving the unattributed edit in there would mean that anybody can put in anything and then just stall, also starting to track partial edits and edits modified in-flight would be a mess. Reverting with a clear message as to the cause sounds only fair.
You are aware that movies generally re-record sound in studio (even if it's only a bedroom with some sheets hanged 2cm from the walls)? Also, even if the visuals are not up to the standards you expect, a reasonable sound track can quite likely pull it up a notch or two!
So, let's just summarize. They want to give control of (no matter how insignificant) chunks of hardware in space to stuff that:
- Is designed at best for 60-70*C temp range (+/- 30-40 usually) - Is assembled planning for 1atm +/- 0.10atm ish. - Has a projected design life of 36 months (or thereabouts, again) - Is re-designed every 12-18 months leaving previous designs generally unsupported - Is considered and counted to be field-updateable for any more complex implementation - Is fab'd/assembled by the lowest bidder
Sure, why not! Also, let's hope that the failures will end up re-entering and buring out instead of sticking on some kind of weird trajectory contributing to the junk already out there.
Well, how about not allocating memory left and right then? Of course you'll need to spend a little bit more time to get it done nicely, perhaps think ahead a little bit and preallocate some memory where you'll need it, perhaps jump down to actually couple of arrays of primitives, etc... Almost like if you'd be using a 'proper' tool...
And still have a choice to quickly throw together those parts of app that are non-critical to users experience.
If android was implemented in 'proper' low level stuff, we would still be looking at version 1.5.3.
Slashdot Mirror
Proper 'war' can be actually quite civil. It's the invasions that USA loves that get ugly...
Ok: 620,136,825,991,110,068,701,238,785,423,046,926,253,574,342, 803,192,842,192,413,588,385,845,373,153,881,997,605,496,447, 502,203,281,863,013,616,477,148,203,584,163,378,722,078,177, 200,480,785,205,159,329,285,477,907,571,939,330,603,772,960, 859,086,270,429,174,547,882,424,912,726,344,305,670,173,270, 769,461,062,802,310,452,644,218,878,789,465,754,777,149,863, 494,367,781,037,644,274,033,827,365,397,471,386,477,878,495, 438,489,595,537,537,990,423,241,061,271,326,984,327,745,715, 546,309,977,202,781,014,561,081,188,373,709,531,016,356,324, 432,987,029,563,896,628,911,658,974,769,572,087,926,928,871, 281,780,070,265,174,507,768,410,719,624,390,394,322,536,422, 605,234,945,850,129,918,571,501,248,706,961,568,141,625,359, 056,693,423,813,008,856,249,246,891,564,126,775,654,481,886, 506,593,847,951,775,360,894,005,745,238,940,335,798,476,363, 944,905,313,062,323,749,066,445,048,824,665,075,946,735,862, 074,637,925,184,200,459,369,692,981,022,263,971,952,597,190, 945,217,823,331,756,934,581,508,552,332,820,762,820,023,402, 626,907,898,342,451,712,006,207,714,640,979,456,116,127,629, 145,951,237,229,913,340,169,552,363,850,942,885,592,018,727, 433,795,173,014,586,357,570,828,355,780,158,735,432,768,888, 680,120,399,882,384,702,151,467,605,445,407,663,535,984,174, 430,480,128,938,313,896,881,639,487,469,658,817,504,506,926, 365,338,175,055,478,128,640,000,000,000,000,000,000,000,000, 000,000,000,000,000,000,000,000,000,000,000,000,000,000,000, 000,000,000,000,000,000,000,000,000,000,000,000,000,000,000, 000,000,000*
*Haven't verified the numbers, just halved it.
And a jury would have the right of nullification, then.
compression.
or way more commonly - badly mastered.
lossless shit is worse than just shit.
Quite a few people are absolutely happy to pay the premium (and you do need to be a stupid animal to even start looking at 'hey, who might be selling lossless DSD stream zips?') although not realizing that what they actually want is not the extra 8 bits bit rather the fact that no monkey execs have been let near the compression button.
But since MSFT is gone - it's about time to switch over and listen to crappy compressed records only now in 32bit/192khz quality!
lifetime is actually quite short.
That's twitter.
Yet at the core of symbian is a brilliant microkernel dating back to the epoc days...
I disagree.
Normal user will not differentiate between underlying OS (Android) and whatever manufacturer inspired gimmics are on top (HTC sense crap in example) or even worse: Operator dictated piles of steamy unsupported runny poo (and it always is. It just always is...).
Most of the security nonsense in European aeroports are due to requirements from USA, btw. Given that there's an occasional flight over to LA or whatever.
foreign aid is USA way of keeping smaller countries dependant on it and happily saying yes to anything USA wants.
Afghanistan might not have started if all the smaller states wouldn't have said 'Yes, let's pretend we all want it' under threats of withdrawing it. Iraq.
are you referring to the popular hand-egg season finale per chance?
tcpdump?
Exactly. Shut down a couple of backbone links (5 mins*) and the rest of the network will be immediately (2-3s) saturated enough to become unusable (from TCP perspective). While the wider internet tries to react (drop youtube traffic, expand peer arrangements, manually reroute stuff - 2-3h once it's clear core is down**) - plenty of time to go after core peering points in major cities.
Lather, rinse and repeat.
* Assumes that LE knows that they will need to action this at least 30 mins beforehand. ... optimistic.
** Actually assumes that DR plans exist, which is
Uhm? And what's wrong with that? Given that the wikipedia articles are public, it would be expected that focus is on keeping the public-exposed content consistent with the editorial standards of the site (whether you like them or not, that's a different matter).
Leaving the unattributed edit in there would mean that anybody can put in anything and then just stall, also starting to track partial edits and edits modified in-flight would be a mess. Reverting with a clear message as to the cause sounds only fair.
You are aware that movies generally re-record sound in studio (even if it's only a bedroom with some sheets hanged 2cm from the walls)? Also, even if the visuals are not up to the standards you expect, a reasonable sound track can quite likely pull it up a notch or two!
So, let's just summarize. They want to give control of (no matter how insignificant) chunks of hardware in space to stuff that:
- Is designed at best for 60-70*C temp range (+/- 30-40 usually)
- Is assembled planning for 1atm +/- 0.10atm ish.
- Has a projected design life of 36 months (or thereabouts, again)
- Is re-designed every 12-18 months leaving previous designs generally unsupported
- Is considered and counted to be field-updateable for any more complex implementation
- Is fab'd/assembled by the lowest bidder
Sure, why not! Also, let's hope that the failures will end up re-entering and buring out instead of sticking on some kind of weird trajectory contributing to the junk already out there.
uhm? Wasn't it completed the moment CD left the premises?
And then there are those who settle on sub-par supplies too, of course.
Pah, brute force is P although the problem moves over to defining the input set.
How many crayons he has?
But it is :)
Well, how about not allocating memory left and right then? Of course you'll need to spend a little bit more time to get it done nicely, perhaps think ahead a little bit and preallocate some memory where you'll need it, perhaps jump down to actually couple of arrays of primitives, etc... Almost like if you'd be using a 'proper' tool...
And still have a choice to quickly throw together those parts of app that are non-critical to users experience.
If android was implemented in 'proper' low level stuff, we would still be looking at version 1.5.3.