Speed is always a factor. Remember that kinetic energy is related to the square of velocity: KE = 0.5 * m * v^2.
That energy has to be disipated in an emergency, either through tyres and brakes (and to a degree, the engine) or through friction/impact.
Remember also the rate of energy disipation is normally linear. There's a point where the tyres lose traction and cause the wheels to lock up and the vehicle to skid, which is the limit to how many watts can be disipated. Because energy disipation is linear but KE is the square of the velocity, stopping is faster at lower speeds.
I would rather see daylight at least once per day in winter: make it double DST please! There's a point as you go further north from London where even this doesn't work though.
This has nothing to do with metric vs. Imperial (or pseudo-imperial if youâ(TM)re American), but more to do with people who with people who donâ(TM)t accept change and stick with anachronistic systems. Non-metric people could just as easily use a measure of gallons per 100 miles (or US gallons per 100 miles)
I'm pretty sure Meng Wanzhou disagrees with your viewpoint about free trade for the entire rest of the world. The US Navy is the sharp end of the US trade policy, not the world's.
I lost my Spotify account a few years ago, which was premium through a special deal through my phone company (Vodafone UK). I received an email that my email address had been changed, but no chance to confirm and accept the change. The hacker changed other details on the account preventing me from confirming any details, and apparently Spotify's security team had no access to historical account information. It was a work phone and I was travelling a lot, so I couldn't get the billing information they asked for quickly, but really, why should I have to work around their shoddy security. I won't pay them a penny. I stopped using the free version to check out music because the ads were using too much CPU and draining my battery, although maybe that shoddy programming has been fixed now? I hope in this case they're only banning ad blockers for the free service, rather than premium (if premium has ads now, then another reason I wouldn't subscribe).
The GUI was already popular long before Windows 95 came along. Amigas, Atari STs, Wintel running Win 3, OS/2 2.0 were all going full swing with GUIs, and text based apps like Word Perfect were basically an anachronism by the time Win 95 released.
My first PC, an Amstrad PC1512, came with GEM Desktop, although without the trashcan that the Atari ST version had. This was somewhere between your Windows/286 (Windows 2.0) and Windows 3.0, the latter being when Microsoft started catching up with competition. Win95 was big because it revamped the UI, made the first break from Windows being no more than an app on top of MS-DOS and brought in more preemptive multitasking, although things like the resource limitations that made it start behaving weirdly and then crash helped maintain Microsoftâ(TM)s reputation for making toy operating systems.
Adobe don't seem to understand this. I've been using Lightroom 6 for 3.5 years, and now they've broken one of it's key modules (Adobe apologist blame one of their vendors). I took a look at the latest Lightroom Class CC (v8.1) and I really can't see the benefit: native support for HEIC (I'd already worked around that), a dehaze filter that doesn't seem to do anything I couldn't do with contrast and clarity, autosettings that cause more work because they over compress contrast and pump the colour saturation making photos look like over processed iPhone HDR photos, and all the issues that annoyed me with LR6 still annoy me in the latest version. And the cost... 3.5 years of LR Classic CC is 7x the price of LR6, and increasing, and if you don't want to pay, you lose all editing functionality. What a con.
BTW, you mentioned Office 365. I'm still using Office 2011 on my Mac at home, and I really can't see any benefits over it in the Office 365 at work. Microsoft managed to break moving messages between folders before Christmas for my work G-Suite account. Forced me to switch to Mail.app. Support couldn't offer any rollback options to something that worked for me. I did try to switch to IMAP, but this took four days to download my mail and 3x the SSD space. The latest update this month seems to find Outlook stuck on high CPU, and kernel_task and Window Server getting stuck on high CPU. Useless.
Updates this frequently seems to be an excuse for poorer quality software. Every update fixes problems with the last version and introduces a ton of new issues. The overall average quality of the software stays poor and doesn't incrementally improve. I think I preferred the old way of working where updates were just fixes, and once in a while I got an upgrade that actually felt worthwhile because the impact of all the new features normally out weighed any new issues introduced.
If I've got something I'm happy with then I can wait; I don't need something new every 30s (or even every two weeks)
As an EU citizen, albeit for another two and bit months, I don't find these laws oppressive in any kind of way and I'm glad that a level government that represents me is doing something to protect my interests and privacy. Somebody's had to reign these corporations in and the US government has shown no leadership in this area. Put it down to a failed experiment with a new business model and expect companies to adapt or fail. I won't cry if Google and Facebook fail and go the way of the likes of Yahoo Search and My Space.
I used to do this when I had my own domain. Amazing how quickly after buying tickets that spammers were using my TicketMaster email address. With the advent of GDPR, Iâ(TM)m thinking of starting this again with the goal of getting some of these companies punished.
Itâ(TM)s a bit of a pain managing unique email addresses per company, but it does reduce the effort of changing an email address.
Itâ(TM)s all about cheap development. Cross platform development has never really worked well - in the past this was the same UI toolkit for Windows, macOS and X11, now itâ(TM)s mobile vs. desktop. Actually mobile works worse on desktop than compromises like Java or Neuron Data (GTK has always been too shit to comprehend). It drives me nuts that websites like ba.com can barely show three flights from search results of far more on my laptop, and in general every âoemodernâ website uses text so large I need to step back, yet most of the important details is hidden and requires scrolling to discover. This is worse than the need black, blue and white web sites of the 90â(TM)s.
No, itâ(TM)s not. Every encoder offers configurations that trade off speed against quality. If you donâ(TM)t want to spend much on hardware, or turn around time is important, youâ(TM)ll reduce the quality irrespective of bitrate.
Then live encoding is another issue. x264 is very CPU intensive, and watch the CPU spike during (Iâ(TM)m not sure which, but they could be the same) scene detection or I-frame generation.
Well I ainâ(TM)t no millennial (see my UID). Sounds like you worked at a place with no code review. Even old school places with any gumption have better engineering processes then you describe, and I work at place that develops SDKs with a C API, uses C++11 and assembly optimises important parts of the code. Macros are sometimes important to extend a language to features it doesnâ(TM)t have natively, but donâ(TM)t take the piss.
Given that there are no real BT.2020/BT.2100 screens around, I imagine most people will colour grade on something that supports DCI-P3 D65. HDR10 metadata (SMPTE 2086 "Mastering Display Colour Volume") can convey the colour space of the reference screen used for grading, and presumably something capable of rendering true BT.2020 colours can take this in to account. Does this mean they have to colour grade once or twice for cinema and TV?
The story is really about HDR TVs, so perhaps it's worth being a bit more precise. BT.2020 is different and refers colour gamut, and it can be used with SDR and HDR. We should really be talking about BT.2100 for HDR, which is BT.2020 colour space with PQ (basis of HDR10, Dolby Vision, etc) or HLG transfer characteristics.
DCI-P3 D65 is effectively a subset of the BT.2020 colour space, and screen manufacturers are getting pretty close to 100% coverage. I suppose at some point they will try to achieve complete coverage of the BT.2020 colour space too, but who knows when that will be?
To be honest I don't really understand the point of the story - maybe it shows the author doesn't really understand this? BT's.609,.701 and.2020 map well in to the media pipeline from capture to display, based on YUV colour. Photographers tend to work in RGB, and I guess that's where the author might be coming from. To ask about sRGB ratings for HDR TVs is daft anyway given the coverage of CIE 1931.
I'm not a bike courier, but I cycle to work and this is by far the fastest way to do it. I don't do any of the things you say. In fact, my Garmin tells me that I'm only moving for ~43 mins of my 55 min of 13 mile commute across central London. Public transport is 65-90 mins. Driving is 90 mins.
If you want to talk about law breakers on the road, look no further than car drivers. Funny how they have a blind spot to their speed on the motorway or thinking it's ok to squeeze through after traffic lights have turned red or parking half on the footpath in the no stopping zone outside my son's nursery.
It looks like you donâ(TM)t understand Unicode and all the ways it can be encoded. Itâ(TM)s a shame you donâ(TM)t know enough to contribute here beyond whinging incoherently.
So actually the exact opposite of what you said about it not being difficult. Maybe you shouldnâ(TM) talk out of your arse so much? This has nothing to do with key modifiers. The correct answer to this problem is that/. should fix how they handle the encoding of the posted data. No other website Iâ(TM)ve seen has this problem.
Slashdot Mirror
Speed is always a factor. Remember that kinetic energy is related to the square of velocity: KE = 0.5 * m * v^2.
That energy has to be disipated in an emergency, either through tyres and brakes (and to a degree, the engine) or through friction/impact.
Remember also the rate of energy disipation is normally linear. There's a point where the tyres lose traction and cause the wheels to lock up and the vehicle to skid, which is the limit to how many watts can be disipated. Because energy disipation is linear but KE is the square of the velocity, stopping is faster at lower speeds.
I would rather see daylight at least once per day in winter: make it double DST please! There's a point as you go further north from London where even this doesn't work though.
This has nothing to do with metric vs. Imperial (or pseudo-imperial if youâ(TM)re American), but more to do with people who with people who donâ(TM)t accept change and stick with anachronistic systems. Non-metric people could just as easily use a measure of gallons per 100 miles (or US gallons per 100 miles)
China has been developing so quickly that quoting 2012 figures is pointless as they will be hopelessly out of date.
OMIGOD, /. is so useless. Letâ(TM)s see if I can post a manually urlencoded version of that link: https://en.m.wikipedia.org/wik...
Although in fairness, this can run in to problems and be seen as interfering with other countries: https://en.m.wikipedia.org/wik...étien
It was only introduced two years ago. Enough with the Donald Trump style propaganda. Letâ(TM)s see more evidence before bigging it up.
I'm pretty sure Meng Wanzhou disagrees with your viewpoint about free trade for the entire rest of the world. The US Navy is the sharp end of the US trade policy, not the world's.
I lost my Spotify account a few years ago, which was premium through a special deal through my phone company (Vodafone UK). I received an email that my email address had been changed, but no chance to confirm and accept the change. The hacker changed other details on the account preventing me from confirming any details, and apparently Spotify's security team had no access to historical account information. It was a work phone and I was travelling a lot, so I couldn't get the billing information they asked for quickly, but really, why should I have to work around their shoddy security. I won't pay them a penny. I stopped using the free version to check out music because the ads were using too much CPU and draining my battery, although maybe that shoddy programming has been fixed now? I hope in this case they're only banning ad blockers for the free service, rather than premium (if premium has ads now, then another reason I wouldn't subscribe).
Here's me thinking that cunt Trump can go fuck himself the way he's been treating his 'allies'. You said it so much more politely though.
The GUI was already popular long before Windows 95 came along. Amigas, Atari STs, Wintel running Win 3, OS/2 2.0 were all going full swing with GUIs, and text based apps like Word Perfect were basically an anachronism by the time Win 95 released.
My first PC, an Amstrad PC1512, came with GEM Desktop, although without the trashcan that the Atari ST version had. This was somewhere between your Windows/286 (Windows 2.0) and Windows 3.0, the latter being when Microsoft started catching up with competition. Win95 was big because it revamped the UI, made the first break from Windows being no more than an app on top of MS-DOS and brought in more preemptive multitasking, although things like the resource limitations that made it start behaving weirdly and then crash helped maintain Microsoftâ(TM)s reputation for making toy operating systems.
Adobe don't seem to understand this. I've been using Lightroom 6 for 3.5 years, and now they've broken one of it's key modules (Adobe apologist blame one of their vendors). I took a look at the latest Lightroom Class CC (v8.1) and I really can't see the benefit: native support for HEIC (I'd already worked around that), a dehaze filter that doesn't seem to do anything I couldn't do with contrast and clarity, autosettings that cause more work because they over compress contrast and pump the colour saturation making photos look like over processed iPhone HDR photos, and all the issues that annoyed me with LR6 still annoy me in the latest version. And the cost... 3.5 years of LR Classic CC is 7x the price of LR6, and increasing, and if you don't want to pay, you lose all editing functionality. What a con.
BTW, you mentioned Office 365. I'm still using Office 2011 on my Mac at home, and I really can't see any benefits over it in the Office 365 at work. Microsoft managed to break moving messages between folders before Christmas for my work G-Suite account. Forced me to switch to Mail.app. Support couldn't offer any rollback options to something that worked for me. I did try to switch to IMAP, but this took four days to download my mail and 3x the SSD space. The latest update this month seems to find Outlook stuck on high CPU, and kernel_task and Window Server getting stuck on high CPU. Useless.
Updates this frequently seems to be an excuse for poorer quality software. Every update fixes problems with the last version and introduces a ton of new issues. The overall average quality of the software stays poor and doesn't incrementally improve. I think I preferred the old way of working where updates were just fixes, and once in a while I got an upgrade that actually felt worthwhile because the impact of all the new features normally out weighed any new issues introduced.
If I've got something I'm happy with then I can wait; I don't need something new every 30s (or even every two weeks)
As an EU citizen, albeit for another two and bit months, I don't find these laws oppressive in any kind of way and I'm glad that a level government that represents me is doing something to protect my interests and privacy. Somebody's had to reign these corporations in and the US government has shown no leadership in this area. Put it down to a failed experiment with a new business model and expect companies to adapt or fail. I won't cry if Google and Facebook fail and go the way of the likes of Yahoo Search and My Space.
I used to do this when I had my own domain. Amazing how quickly after buying tickets that spammers were using my TicketMaster email address. With the advent of GDPR, Iâ(TM)m thinking of starting this again with the goal of getting some of these companies punished.
Itâ(TM)s a bit of a pain managing unique email addresses per company, but it does reduce the effort of changing an email address.
They were saying that about record decks 20 years ago. Now you can get them with USB and Bluetooth connections, at a reasonable price.
Itâ(TM)s all about cheap development. Cross platform development has never really worked well - in the past this was the same UI toolkit for Windows, macOS and X11, now itâ(TM)s mobile vs. desktop. Actually mobile works worse on desktop than compromises like Java or Neuron Data (GTK has always been too shit to comprehend). It drives me nuts that websites like ba.com can barely show three flights from search results of far more on my laptop, and in general every âoemodernâ website uses text so large I need to step back, yet most of the important details is hidden and requires scrolling to discover. This is worse than the need black, blue and white web sites of the 90â(TM)s.
No, itâ(TM)s not. Every encoder offers configurations that trade off speed against quality. If you donâ(TM)t want to spend much on hardware, or turn around time is important, youâ(TM)ll reduce the quality irrespective of bitrate.
Then live encoding is another issue. x264 is very CPU intensive, and watch the CPU spike during (Iâ(TM)m not sure which, but they could be the same) scene detection or I-frame generation.
Well I ainâ(TM)t no millennial (see my UID). Sounds like you worked at a place with no code review. Even old school places with any gumption have better engineering processes then you describe, and I work at place that develops SDKs with a C API, uses C++11 and assembly optimises important parts of the code. Macros are sometimes important to extend a language to features it doesnâ(TM)t have natively, but donâ(TM)t take the piss.
Given that there are no real BT.2020/BT.2100 screens around, I imagine most people will colour grade on something that supports DCI-P3 D65. HDR10 metadata (SMPTE 2086 "Mastering Display Colour Volume") can convey the colour space of the reference screen used for grading, and presumably something capable of rendering true BT.2020 colours can take this in to account. Does this mean they have to colour grade once or twice for cinema and TV?
The story is really about HDR TVs, so perhaps it's worth being a bit more precise. BT.2020 is different and refers colour gamut, and it can be used with SDR and HDR. We should really be talking about BT.2100 for HDR, which is BT.2020 colour space with PQ (basis of HDR10, Dolby Vision, etc) or HLG transfer characteristics.
DCI-P3 D65 is effectively a subset of the BT.2020 colour space, and screen manufacturers are getting pretty close to 100% coverage. I suppose at some point they will try to achieve complete coverage of the BT.2020 colour space too, but who knows when that will be?
To be honest I don't really understand the point of the story - maybe it shows the author doesn't really understand this? BT's .609, .701 and .2020 map well in to the media pipeline from capture to display, based on YUV colour. Photographers tend to work in RGB, and I guess that's where the author might be coming from. To ask about sRGB ratings for HDR TVs is daft anyway given the coverage of CIE 1931.
I'm not a bike courier, but I cycle to work and this is by far the fastest way to do it. I don't do any of the things you say. In fact, my Garmin tells me that I'm only moving for ~43 mins of my 55 min of 13 mile commute across central London. Public transport is 65-90 mins. Driving is 90 mins.
If you want to talk about law breakers on the road, look no further than car drivers. Funny how they have a blind spot to their speed on the motorway or thinking it's ok to squeeze through after traffic lights have turned red or parking half on the footpath in the no stopping zone outside my son's nursery.
It looks like you donâ(TM)t understand Unicode and all the ways it can be encoded. Itâ(TM)s a shame you donâ(TM)t know enough to contribute here beyond whinging incoherently.
That's an interesting thought. It had crossed my mind that maybe he was induced to do this in some way...
So actually the exact opposite of what you said about it not being difficult. Maybe you shouldnâ(TM) talk out of your arse so much? This has nothing to do with key modifiers. The correct answer to this problem is that /. should fix how they handle the encoding of the posted data. No other website Iâ(TM)ve seen has this problem.