Yes, unfortunately too much of a mad scientist with some seriously deficient marketing skills -- but there wouldn't have been the suspense and story otherwise.
It does make me wonder, what can be seen using a wide-band ultrasound microphone and a spectrum analyzer.
Actually, many plants have what is known as antiherbivoral compounds, bitter-tasting and even poisonous chemicals that are supposed to discourage animals from eating them.
Back around 1979-1980, I was talking with my mother about the various minicomputers that were available; I was using a PR1ME at the college, and she had some kind of HP equipment (HP3500 ?) at work. Some of the early home computers running BASIC were available, but it was already obvious that these things were like toys compared with the multi-processing and multi-user big iron. Considering how much larger and complicated programs could be made in FORTRAN, compared with the line-number BASIC of the time, I speculated, that some day, we would have small home computers that could run the same kind of FORTRAN programs.
She said she thought that was unlikely.
As few years later PCs became powerful enough to actually be able to do this (PC/AT, with the 80286 running Xenix). And these days, there are the pocket-sized Raspberry Pi, Rock 64, and others, that are more powerful than all that large hardware from the 1970s.
The 74LS244 is powered at 5V as it must be. Then its inputs are driven from a GPIO line. Low voltage is the same for both the R-Pi and the LS-TTL chip; they are in perfect agreement of that, High voltage thresholds of LS-TTL (2V) are compatible with the High voltage outputs of the 3.3V CMOS outputs from the Raspberry Pi.
The GPIO output does not have any problems driving the 0.2 mA LOW input current, nor the 0.02 mA HIGH input current required by the 74LS244 input. So a direct connection here is good to go.
Is it some of both? Muscle memory for when typing on a keyboard without having to look down, as in the fingers "remembering" where the various letters and other characters are.
And spatial memory, remembering the order of the letters -- noticeable when a screen or keypad has the letter keys in a different order. Using a check-in terminal or parking payment terminal, where there is a keypad or screen with the letters organized in alphabetical order is noticeably harder than if the letters are in QWERTY order -- I've encountered both, with the alphabetical order requiring me to stop and search for each letter much more than with the QWERTY-ordering I've been becoming used to for the last 40 years of near-daily exposure.
UTC or Zulu is great for data-logging and timestamping things, for later retrieval and reference. And also as a basis for figuring out when someone else in another time-zone is likely to be available, given the difference between UTC and their local time, as defined by the timezones. For scheduling any activity that involves people in different parts of the world it makes it unambigious when this activity is to take place. This is actually even more useful during the periods in spring or fall when the Daylight Saving changes go into or out of effect at different times in different places. So for example, deciding on a meeting at 15:00 in Oslo and 9 AM in Houston, by agreeing on this happening at 1400Z removes the ambiguity as to whether Daylight Saving is in effect or not at either of these places.
But as for a wall-clock time for general universal civil use, it is useless. Disregarding for the moment the general public's massive reluctance to this kind of change (compare with the less-than-great success changing to the metric system has been), the biggest problem is that each day will have one date in the morning and one in the afternoon. In timezone UTC-7 for example, such as found in the western US, this date changes happens at 1700 local time (or 5 PM), right in the middle of the afternoon. And since people mostly sleep during the night everywhere, there is still the need for others elsewhere in the world to be able to figure out when night and day occurs, in order to, for example, be able to schedule online meetings. The present-day tiimezone system, with all its warts and sillinesses, does a good job handling ths.
The original problem is that the twice-annual clock-changing caused by Daylight Saving is inconvenient, possibly minimally dangerous, and doesn't seem to serve much of any useful purpose. Any fix other than just leaving the clocks set to the same local time year will be worse than any of these, admittedly minor, problems that Daylight Saving has.
If it were this undocumented, why have there been many successful companies manufacturing and selling time-keeping devices (clocks, controllers, timers, etc) using this as the primary timekeeper source, for the last 70 years or so? Now, whether this is still the optimal way, in the age of solar panels, crystals and electronic frequency-dividers can be open to discussion. But there was, and still is, a promise and even a guarantee made, that the long-term stability of mains AC frequencies corresponding to the exact number of cycles per second in a 24-hour period is something that can be relied upon.
Agree on the big transformers. But there is no big magic to the 60 Hz vs 50 Hz as far as gearing goes. Main difference seen in equipment such as hour-counters and clocks that use the small synchronous motors, is that the 60 Hz model might have a gear with 10 teeth driving another gear somewhere, and the 50 Hz model has a 12 tooth gear in the same place. Or some other, similar difference, generally, a reduction ratio of 6:1 in a 60 Hz model is replaced by 5:1 in a 50 Hz model.
The MM5314 and similar clock chips that National Semiconductors made back in the 1970s were designed for taking the 60 Hz or 50 Hz from the mains as the time-reference; there was a selection input that changed the divider ratio from input to second-counting, between 50 and 60.
These aren't heated significantly by whatever heat might be trapped by slightly more CO2 -- despite what politicians say, seeing as this whole Environment business has become more of just that, with excuses for taxation and making life more difficult for everyone. Unless you pay extra of course.
This ME thing is like a door on the back of the house. It is painted so as to not be easy to tell apart from the wall, but it is not impossible to discover. And it even has a lock, with a key that has a funny and strange shape.
And this backdoor is present on every house on the street. And although the key is of an obscure and not readily available design, it is the same one for all these houses. So once you find out how to open up one of these doors, opening any of the others on all the neighbors' houses from the same manufacturer iis easy, with the knowledge of the design of this key.
Some other houses may have been made by a different manufacturer. Some of these have similar doors with a different key that works on all of them, in much the same way. Then there are still a number of houses that are either too old, or made by a manufacturer that doesn't include this back door.
Point is, once the presence and nature of the back-door and its lock are known, the house is wide open, and security by obscurity has failed.
Fiber is already there, along the railway line from Narvik and eastwards. There is no permafrost in this area, most of it is sea and bedrock, within which the mines were located. As for distance, even a large town such as Tromsø is further north and further away from the rest of Europe.
Bullshit. Look up the etymology of "partisan". Also this is supposedly science. If someone uses names of elements for chemical compounds in a scientific context, I must assume they don't know what they're talking about.
Herein lies the rub... This context is not scientific but political: "Carbon tax" is not science but politics, and the "Carbon" in question is carbon dioxide, not coal or diamonds. "Nitrogen" is similarly used instead of "nitrates" in this speculation about pollution and changes in water quality.
Maybe I mostly remember the slings and arrows -- these so-called BASIC program listings that were about eight lines of actual readable (and thus re-writeable) BASIC code and the rest of the page or pages being DATA statements with numbers. Then the PCs came, and we could, if sufficiently masochistic, type in similar listings to use with DEBUG.EXE. Later, as software grew larger, there soon came the need of faffing about with config.sys and autoexec.bat so that available memory was maximized. In the late 1980s onwards, there were the expanded memory nonsense too and more and more options and things in config.sys. There there would be jumper settings so DMA channels, port-addresses and interrupt lines on the various plug-in cards in the PCs. This continued well into the 1990s, then that got replaced by something called Plug-and-play which maybe, maybe not, did work, thus everyone called it "Plug-and-pray". And all on the original 640K plus whatever High memory had been put into place. I do not miss any of all this. TFS mentions the dreariness of business computing. they are absolutely right!
But I might not be typical -- I started with learning FORTRAN, then after that BASIC seemed primitive (no functions? and thus no data hiding? i have to make sure I don't re-use any of the variable-names anywhere else? and only one letter? at least FORTRAN allowed me to use six! bah) but the PC-compatible had Turbo Pascal, and there was also the assembler and later, Turbo C, so that became a nice set-up, with direct control of the pins on the parallell and serial ports, and even some DIY card with A-D converters! Yay!
Then there were the wonderful Unix systems, HP-UX and AIX back around the mid-1980s, where you could actually do more than one thing at a time without the machine crashing. And even if your program decided to hang, or accessed some memory out of bounds, it would say "bus error" or "segmentation fault" and stop, but the rest of the system, including other programs, would continue happily along as if nothing had happened. These even had networking so we could have programs on one machine talk with programs on another machine.
Of course this didn't last. Those Unix systems were way too expensive. Instead, Windows NT happened, and a form of multitasking and even eventually a useful networking system (TCP/IP is useful, all the other weird and wonderful variants turned out not to be so) and the access to the parallell port vanished, while the support for the serial ports became increasingly wobbly. ISA, EISA, Micro Channel, and MS-DOS became dinosaurs soon after; parallell and serial ports followed on as being branded "legacy". And like the dinosaurs, some of their descendants are still around now: RS-232 serial ports never really went away completely. USB came, but turned out to not be as hacker-friendly as those serial ports -- there is a reason everyone today runs (RS-232 style) serial via USB using a pl2303 or FTDI or similar chip to talk and listen to the UART in their SBC or microcontroller board.
There was a sort of dark age, of PCs running klunky MS-DOS or slightly less klunky Windows, until the late half of the 1990s, when Linux distros became easily available, and so good that they actually worked right on some reasonable random PC hardware that would be available, and all the good old Unix ways of doing things finally became economically feasible, intially on PCs, many of them second-hand. Around the middle of the 2000s the first single-board computers started showing up, and some of these are now becoming as understandable and documented as those old 8088 PCs with their MS-DOS once were.
The most common way of highlighting special items such as filenames, functions, variables, command-line invocations and suchlike in documentary text is to put them in an alternate font, sometimes italics or bold. In code, quote-characters mark the beginning and end of a string to be displayed, and there are escape-conventions for including the same quote characters within the string as part of it. As far as the compiler looking at that is concerned only the non-escaped quote characters at the ends are taken as meaning begin and end string.
If there is something more of a nontechnical work, say, a novel where protagonists A and B are discussing their concerns raised by the absence of a file and the spelling of its name, it might be useful to show what we could call human and non-human audience quote characters. But here the audience is human, and we are known to be pretty good at understanding even when faced with moderately severe syntax errors.
Consider also the convention in print that long quotations that go over several paragraphs have open quote characters at the beginning of each paragraph, but only one closing quote character at the end. Useful for human readers, but makes for many complications to a system that expects quote-characters to appear in pairs separating what is inside and outside.
Indeed, they also would confuse us using those fancy text-figure numerals that makes lowercase o and zero indistinguishable, just so that even if you can read and ignore the curly-ness of the quotes, you won't be able to get this other distinction right when it isn't obvious from context. Same for uppercase I and lowercase l in most sans-serif fonts, but copy-and-paste might be able to handle these. It it wasn't for these stupid quotes of course...
It all comes from having overloaded some characters: the ASCII 0x22 character has been pressed into service for denoting inches, seconds of arc, beginning a quote, ending a quote, ditto mark. Similarly, there is the characters for minus, em-dash, en-dash, hyphen all being represented by ASCII 0x2d. So how do we know which ones we will want to use? I can think of writing prose where the storyline might have to include pieces of programming code, and thus will want to have all these different ones there at the same time.
Teslas and other electrical cars do not have VAT charged on the sale price, and once on the road it can be driven for free on all the toll roads and toll-enclosed city centers. Annual registration charge is also the minimum rate otherwise applicable to veteran cars, older than 30 years, and they are allowed in most of the bus and taxi lanes. The term subsidy has been used for this, maybe it should be called tax relief, or incentives, or something else. However, whether the government pays extra for something or just refrains from charging taxes on something doesn't make much of a difference in the end: it does make these cars much more popular than they would have been otherwise.
Now as for autonomous cars in this place where the winter is an inferno in white with snow or an inferno in black with the grime and mud produced by salt and studded tires grinding up the pavement ending up all over the cars and the road; snow or mud covering road markings such as the center, lane divider, and edge lines (provided there are any there at all) -- then add the unique tendency of Oslo pedestrians to wander into the street in front of anything that moves (cars, buses, streetcars, bicyclists) never mind trafic lights... and the large population of moose and deer in the woodlands all over the place which isn't exactly known for their good traffic discipline either, and it is going to be really interesting to see how this experiment turns out!
Changing everyone to use UTC all the time in order to obviate the problems with Daylight Saving Time is offering a cure rather worse than the disease. Nothing is all that wrong with the system of timezones, defined so 12 Noon is more or less in the middle of the day for everyone. By itself and for certain technical purposes UTC is a good choice, in the same way that base-16 number encoding is, but for everyday civil use it doesn't do the job well. Local time and base-10 works much better there.
If the Daylight Saving is the problem then the solution is to get rid of that then? Stay on local solar time as the existing timezone stipulates, and do not turn the clocks one hour back and forth every few months. The easiest solution is the negative one, in that it means not doing the stupid thing anymore.
Well since he is Italian, and was on his way to Canada, and if he were doing applied engineering math he might have been using metric units.
However, as his field of learning is economy, the most likely specific units that he might have been using would have been dollars... which if not exactly metric, at least have the familiar base-10 divisions. But as he was working on some differential equations at the time, the use of specific units or even much in the ways of numbers would not be likely.
25 MPH (or 40 km/h) on a road of the quality seen in the video will usually feel like it is too slow, and it is not surprising that there are many that exceed this limit.
I notice that most arterial roads around here have the equivalent of 30 MPH (50 km/h) though reduced to 40 km/h or 25 MPH past schools. Where there also is at least one speed bump or raised pedestrian crossing (basically a speed bump with the crosswalk on top). Non-arterial roads have 30 km/h (which would correspond to 20 MPH), and there are always speed bumps.
Loops in the road would work, but that would require permission from the city to make the grooves and put down the wire into the top layer of pavement. The non-contact nature of this camera approach does not require anything to be done to or on the actual road.
Unless these multiple locations are less than 3 meters apart, there is no way there can be 10 ns accuracy as an event at one place cannot possibly affect anything happening at any of the other places.
There is nothing as wasted as an ad for something that I just bought... yet that has happened several times: I have just bought something on ebay (or wherever) and sure enough, here comes an advertisement for the same exact thing. That model is simply broken.
Slashdot Mirror
Yes, unfortunately too much of a mad scientist with some seriously deficient marketing skills -- but there wouldn't have been the suspense and story otherwise.
It does make me wonder, what can be seen using a wide-band ultrasound microphone and a spectrum analyzer.
Actually, many plants have what is known as antiherbivoral compounds, bitter-tasting and even poisonous chemicals that are supposed to discourage animals from eating them.
Back around 1979-1980, I was talking with my mother about the various minicomputers that were available; I was using a PR1ME at the college, and she had some kind of HP equipment (HP3500 ?) at work. Some of the early home computers running BASIC were available, but it was already obvious that these things were like toys compared with the multi-processing and multi-user big iron. Considering how much larger and complicated programs could be made in FORTRAN, compared with the line-number BASIC of the time, I speculated, that some day, we would have small home computers that could run the same kind of FORTRAN programs.
She said she thought that was unlikely.
As few years later PCs became powerful enough to actually be able to do this (PC/AT, with the 80286 running Xenix). And these days, there are the pocket-sized Raspberry Pi, Rock 64, and others, that are more powerful than all that large hardware from the 1970s.
74ls244? At 3.3V?
The 74LS244 is powered at 5V as it must be. Then its inputs are driven from a GPIO line. Low voltage is the same for both the R-Pi and the LS-TTL chip; they are in perfect agreement of that, High voltage thresholds of LS-TTL (2V) are compatible with the High voltage outputs of the 3.3V CMOS outputs from the Raspberry Pi.
The GPIO output does not have any problems driving the 0.2 mA LOW input current, nor the 0.02 mA HIGH input current required by the 74LS244 input. So a direct connection here is good to go.
Is it some of both? Muscle memory for when typing on a keyboard without having to look down, as in the fingers "remembering" where the various letters and other characters are.
And spatial memory, remembering the order of the letters -- noticeable when a screen or keypad has the letter keys in a different order. Using a check-in terminal or parking payment terminal, where there is a keypad or screen with the letters organized in alphabetical order is noticeably harder than if the letters are in QWERTY order -- I've encountered both, with the alphabetical order requiring me to stop and search for each letter much more than with the QWERTY-ordering I've been becoming used to for the last 40 years of near-daily exposure.
UTC or Zulu is great for data-logging and timestamping things, for later retrieval and reference. And also as a basis for figuring out when someone else in another time-zone is likely to be available, given the difference between UTC and their local time, as defined by the timezones. For scheduling any activity that involves people in different parts of the world it makes it unambigious when this activity is to take place. This is actually even more useful during the periods in spring or fall when the Daylight Saving changes go into or out of effect at different times in different places. So for example, deciding on a meeting at 15:00 in Oslo and 9 AM in Houston, by agreeing on this happening at 1400Z removes the ambiguity as to whether Daylight Saving is in effect or not at either of these places.
But as for a wall-clock time for general universal civil use, it is useless. Disregarding for the moment the general public's massive reluctance to this kind of change (compare with the less-than-great success changing to the metric system has been), the biggest problem is that each day will have one date in the morning and one in the afternoon. In timezone UTC-7 for example, such as found in the western US, this date changes happens at 1700 local time (or 5 PM), right in the middle of the afternoon. And since people mostly sleep during the night everywhere, there is still the need for others elsewhere in the world to be able to figure out when night and day occurs, in order to, for example, be able to schedule online meetings. The present-day tiimezone system, with all its warts and sillinesses, does a good job handling ths.
The original problem is that the twice-annual clock-changing caused by Daylight Saving is inconvenient, possibly minimally dangerous, and doesn't seem to serve much of any useful purpose. Any fix other than just leaving the clocks set to the same local time year will be worse than any of these, admittedly minor, problems that Daylight Saving has.
If it were this undocumented, why have there been many successful companies manufacturing and selling time-keeping devices (clocks, controllers, timers, etc) using this as the primary timekeeper source, for the last 70 years or so? Now, whether this is still the optimal way, in the age of solar panels, crystals and electronic frequency-dividers can be open to discussion. But there was, and still is, a promise and even a guarantee made, that the long-term stability of mains AC frequencies corresponding to the exact number of cycles per second in a 24-hour period is something that can be relied upon.
Agree on the big transformers. But there is no big magic to the 60 Hz vs 50 Hz as far as gearing goes. Main difference seen in equipment such as hour-counters and clocks that use the small synchronous motors, is that the 60 Hz model might have a gear with 10 teeth driving another gear somewhere, and the 50 Hz model has a 12 tooth gear in the same place. Or some other, similar difference, generally, a reduction ratio of 6:1 in a 60 Hz model is replaced by 5:1 in a 50 Hz model.
The MM5314 and similar clock chips that National Semiconductors made back in the 1970s were designed for taking the 60 Hz or 50 Hz from the mains as the time-reference; there was a selection input that changed the divider ratio from input to second-counting, between 50 and 60.
Then there is this, which is also bad, in several ways:
The computer has had a malfunction. Press any key to continue
[A]
Do you want to save the work done? [y/n]
[N]
Do you want to exit the program now? [y/n]
[Y]
(darkness follows)
These aren't heated significantly by whatever heat might be trapped by slightly more CO2 -- despite what politicians say, seeing as this whole Environment business has become more of just that, with excuses for taxation and making life more difficult for everyone. Unless you pay extra of course.
Instead, just the other week, there was news about some large hot magma plumes being present underneath the Twaites Glacier and other nearby areas, and that is what is heating up this ice. So it may still break out and put a lot of water into the ocean but for different reasons.
This ME thing is like a door on the back of the house. It is painted so as to not be easy to tell apart from the wall, but it is not impossible to discover. And it even has a lock, with a key that has a funny and strange shape.
And this backdoor is present on every house on the street. And although the key is of an obscure and not readily available design, it is the same one for all these houses. So once you find out how to open up one of these doors, opening any of the others on all the neighbors' houses from the same manufacturer iis easy, with the knowledge of the design of this key.
Some other houses may have been made by a different manufacturer. Some of these have similar doors with a different key that works on all of them, in much the same way. Then there are still a number of houses that are either too old, or made by a manufacturer that doesn't include this back door.
Point is, once the presence and nature of the back-door and its lock are known, the house is wide open, and security by obscurity has failed.
Fiber is already there, along the railway line from Narvik and eastwards. There is no permafrost in this area, most of it is sea and bedrock, within which the mines were located. As for distance, even a large town such as Tromsø is further north and further away from the rest of Europe.
There is no permafrost in this area. This is built on bedrock, and close to the coast.
Bullshit. Look up the etymology of "partisan". Also this is supposedly science. If someone uses names of elements for chemical compounds in a scientific context, I must assume they don't know what they're talking about.
Herein lies the rub... This context is not scientific but political: "Carbon tax" is not science but politics, and the "Carbon" in question is carbon dioxide, not coal or diamonds. "Nitrogen" is similarly used instead of "nitrates" in this speculation about pollution and changes in water quality.
Maybe I mostly remember the slings and arrows -- these so-called BASIC program listings that were about eight lines of actual readable (and thus re-writeable) BASIC code and the rest of the page or pages being DATA statements with numbers. Then the PCs came, and we could, if sufficiently masochistic, type in similar listings to use with DEBUG.EXE. Later, as software grew larger, there soon came the need of faffing about with config.sys and autoexec.bat so that available memory was maximized. In the late 1980s onwards, there were the expanded memory nonsense too and more and more options and things in config.sys. There there would be jumper settings so DMA channels, port-addresses and interrupt lines on the various plug-in cards in the PCs. This continued well into the 1990s, then that got replaced by something called Plug-and-play which maybe, maybe not, did work, thus everyone called it "Plug-and-pray". And all on the original 640K plus whatever High memory had been put into place. I do not miss any of all this. TFS mentions the dreariness of business computing. they are absolutely right!
But I might not be typical -- I started with learning FORTRAN, then after that BASIC seemed primitive (no functions? and thus no data hiding? i have to make sure I don't re-use any of the variable-names anywhere else? and only one letter? at least FORTRAN allowed me to use six! bah) but the PC-compatible had Turbo Pascal, and there was also the assembler and later, Turbo C, so that became a nice set-up, with direct control of the pins on the parallell and serial ports, and even some DIY card with A-D converters! Yay!
Then there were the wonderful Unix systems, HP-UX and AIX back around the mid-1980s, where you could actually do more than one thing at a time without the machine crashing. And even if your program decided to hang, or accessed some memory out of bounds, it would say "bus error" or "segmentation fault" and stop, but the rest of the system, including other programs, would continue happily along as if nothing had happened. These even had networking so we could have programs on one machine talk with programs on another machine.
Of course this didn't last. Those Unix systems were way too expensive. Instead, Windows NT happened, and a form of multitasking and even eventually a useful networking system (TCP/IP is useful, all the other weird and wonderful variants turned out not to be so) and the access to the parallell port vanished, while the support for the serial ports became increasingly wobbly. ISA, EISA, Micro Channel, and MS-DOS became dinosaurs soon after; parallell and serial ports followed on as being branded "legacy". And like the dinosaurs, some of their descendants are still around now: RS-232 serial ports never really went away completely. USB came, but turned out to not be as hacker-friendly as those serial ports -- there is a reason everyone today runs (RS-232 style) serial via USB using a pl2303 or FTDI or similar chip to talk and listen to the UART in their SBC or microcontroller board.
There was a sort of dark age, of PCs running klunky MS-DOS or slightly less klunky Windows, until the late half of the 1990s, when Linux distros became easily available, and so good that they actually worked right on some reasonable random PC hardware that would be available, and all the good old Unix ways of doing things finally became economically feasible, intially on PCs, many of them second-hand. Around the middle of the 2000s the first single-board computers started showing up, and some of these are now becoming as understandable and documented as those old 8088 PCs with their MS-DOS once were.
To some extent we are in a golden age right now.
The most common way of highlighting special items such as filenames, functions, variables, command-line invocations and suchlike in documentary text is to put them in an alternate font, sometimes italics or bold. In code, quote-characters mark the beginning and end of a string to be displayed, and there are escape-conventions for including the same quote characters within the string as part of it. As far as the compiler looking at that is concerned only the non-escaped quote characters at the ends are taken as meaning begin and end string.
If there is something more of a nontechnical work, say, a novel where protagonists A and B are discussing their concerns raised by the absence of a file and the spelling of its name, it might be useful to show what we could call human and non-human audience quote characters. But here the audience is human, and we are known to be pretty good at understanding even when faced with moderately severe syntax errors.
Consider also the convention in print that long quotations that go over several paragraphs have open quote characters at the beginning of each paragraph, but only one closing quote character at the end. Useful for human readers, but makes for many complications to a system that expects quote-characters to appear in pairs separating what is inside and outside.
Indeed, they also would confuse us using those fancy text-figure numerals that makes lowercase o and zero indistinguishable, just so that even if you can read and ignore the curly-ness of the quotes, you won't be able to get this other distinction right when it isn't obvious from context. Same for uppercase I and lowercase l in most sans-serif fonts, but copy-and-paste might be able to handle these. It it wasn't for these stupid quotes of course...
It all comes from having overloaded some characters: the ASCII 0x22 character has been pressed into service for denoting inches, seconds of arc, beginning a quote, ending a quote, ditto mark. Similarly, there is the characters for minus, em-dash, en-dash, hyphen all being represented by ASCII 0x2d. So how do we know which ones we will want to use? I can think of writing prose where the storyline might have to include pieces of programming code, and thus will want to have all these different ones there at the same time.
Teslas and other electrical cars do not have VAT charged on the sale price, and once on the road it can be driven for free on all the toll roads and toll-enclosed city centers. Annual registration charge is also the minimum rate otherwise applicable to veteran cars, older than 30 years, and they are allowed in most of the bus and taxi lanes. The term subsidy has been used for this, maybe it should be called tax relief, or incentives, or something else. However, whether the government pays extra for something or just refrains from charging taxes on something doesn't make much of a difference in the end: it does make these cars much more popular than they would have been otherwise.
Now as for autonomous cars in this place where the winter is an inferno in white with snow or an inferno in black with the grime and mud produced by salt and studded tires grinding up the pavement ending up all over the cars and the road; snow or mud covering road markings such as the center, lane divider, and edge lines (provided there are any there at all) -- then add the unique tendency of Oslo pedestrians to wander into the street in front of anything that moves (cars, buses, streetcars, bicyclists) never mind trafic lights... and the large population of moose and deer in the woodlands all over the place which isn't exactly known for their good traffic discipline either, and it is going to be really interesting to see how this experiment turns out!
And meanwhile 4:20 enjoys a joint off to the side.
Changing everyone to use UTC all the time in order to obviate the problems with Daylight Saving Time is offering a cure rather worse than the disease. Nothing is all that wrong with the system of timezones, defined so 12 Noon is more or less in the middle of the day for everyone. By itself and for certain technical purposes UTC is a good choice, in the same way that base-16 number encoding is, but for everyday civil use it doesn't do the job well. Local time and base-10 works much better there.
If the Daylight Saving is the problem then the solution is to get rid of that then? Stay on local solar time as the existing timezone stipulates, and do not turn the clocks one hour back and forth every few months. The easiest solution is the negative one, in that it means not doing the stupid thing anymore.
Well since he is Italian, and was on his way to Canada, and if he were doing applied engineering math he might have been using metric units.
However, as his field of learning is economy, the most likely specific units that he might have been using would have been dollars ... which if not exactly metric, at least have the familiar base-10 divisions. But as he was working on some differential equations at the time, the use of specific units or even much in the ways of numbers would not be likely.
25 MPH (or 40 km/h) on a road of the quality seen in the video will usually feel like it is too slow, and it is not surprising that there are many that exceed this limit.
I notice that most arterial roads around here have the equivalent of 30 MPH (50 km/h) though reduced to 40 km/h or 25 MPH past schools. Where there also is at least one speed bump or raised pedestrian crossing (basically a speed bump with the crosswalk on top). Non-arterial roads have 30 km/h (which would correspond to 20 MPH), and there are always speed bumps.
Loops in the road would work, but that would require permission from the city to make the grooves and put down the wire into the top layer of pavement. The non-contact nature of this camera approach does not require anything to be done to or on the actual road.
Unless these multiple locations are less than 3 meters apart, there is no way there can be 10 ns accuracy as an event at one place cannot possibly affect anything happening at any of the other places.
This.
There is nothing as wasted as an ad for something that I just bought... yet that has happened several times: I have just bought something on ebay (or wherever) and sure enough, here comes an advertisement for the same exact thing. That model is simply broken.