jdaley

An allusion to the accumulated rounding bug that caused the Patriot missile incident in 1991? That system was likewise intended to operate for only short periods.

From https://autarkaw.wordpress.com/2008/06/02/round-off-errors-a...

In the Patriot missile, time was saved in a fixed point register that had a length of 24 bits. Since the internal clock of the system is measured every one-tenth of a second, 1/10 expressed in a 24 bit fixed point register is 0.0001100110011001100110011 (the exact value is 209715/2097152).

On the day of the mishap, the battery on the Patriot missile was left on for 100 consecutive hours, hence causing an inaccuracy of 9.5E-8x10x60x60x100=0.34 seconds.

The shift calculated in the range gate due to the error of 0.342 seconds was calculated as 687m. The shift of larger than 137m resulted in the Scud not being targeted and hence killing 28 Americans in the barracks of Saudi Arabia.

I've worked on enterprise products, off-the-shelf and in-house, which use message brokers, and every time I could not fathom how the extra complexity was justified. If the messages were just queued in a simple database table instead, the implementations would have been much easier to work with: easier setup and admin (it's just part of the existing database), easier to check and monitor (just select counts from the table), easier to inspect the pending messages and fix problematic messages. In all cases I get the feeling the architects were just looking for an excuse to use a new technology.

I can only see high-load scenarios as a possible justification, where the volume of incoming message data is physically too much for the RDMS.

https://www.youtube.com/watch?v=1j2Duy_xzEA

I used it to build a LINQ provider for a legacy mainframe database system, abstracting away the incomprehensible table and column naming, weird date systems, EBCDIC, and other nastiness involved in querying that system using straight-up SQL.

One thing I found is that implementing a custom LINQ provider gives you a better understanding of how Entity Framework runs your queries. You get to see how queries get split up into the parts executed in the CLR versus the parts that get translated, and how expressions get rearranged and rewritten.

Developing for Internet Explorer 8 is my present-day reality too, but if IT departments were instead mandating Firefox 3.0 or Chrome 1.0 I'm not sure how much better it would be.

But if the app is injecting unescaped user input into code, wouldn't a simple ";alert(1);// achieve the same thing? Why do you need to be tricky?

The examples seem to be based on the premise that web apps commonly forgo the simple escaping of quotes, and instead implement a complex parsing and analysis of user input as code to identify malicious statements, which can be defeated as long as you obfuscate enough.

You've got a beautifully produced and captivating video, which makes no secret about advertising something. People enjoy it and engage with it, but then suddenly catch themselves: "Oh no! What if this advertisement was created... for profit?"

Of course it was! So what?

Other than minor things it's working well so far.

In 2009, the Australian Labor Party, in power as the federal government of Australia, initiated construction of Australia's National Broadband Network (NBN). The network is replacing copper phone lines across Australia with a new fibre to the home (FTTH), also known as fibre to the premises (FTTP) network, meaning optical fibre will be run around the country, down every street, through every front yard, and into our houses (except some regional areas, where satellite will be used).

Two days ago, a federal election was held. The Australian Labor Party was defeated by the Coalition, an alliance led by the other major political party in Australia - the Liberal Party. The Liberal Party's policy for the NBN is to build fibre to the node (FTTN) instead, meaning optical fibre will be run to cabinets on street corners, which will service small areas, but the existing copper lines will still be used for the "last mile".

The petition is to convince the Liberal Party, now in power, to stick with the original plan of FTTH.

Yet the Malaysian constitution includes "every citizen has the right to freedom of speech and expression".

The first two sentences are too blurry for me. I think the third (left-most) sentence is:

○ 授業と休み時間の区別をしよう

"Let's distinguish between class time and break time."