It can catch all kinds of bugs, but you have to ask the correct questions. So it comes down to define what a bug is and the assumptions you use for testing. And therein lies the problem: what constitutes a bug? A function that add two numbers but bever terminates might be considered bugfree if forget to include as a bug that not giving an answer before the end of the universe is faulty behaviour. We humans are terrible at writing these kind of specifications, so formal verification as a method just pushes the correctness from code to specification.
Unless understand your comment wrong: most older EU banks run their core on mainframe. Sure the webapp to see your account is running on some websphere/j2ee or nowadays maybe even angular server. But that's just a gateway to the real accounting system on the mainframe.
I like my log to include where something happened and in some complex cases having a few thousand lines of logging info per request is not unreasonable. So stuffing al that info into a single log event/line doesn't make sense to me. I recently had the unfortunate situation where two seemingly independant sessions were interfering, here a sequential logfile where things were logged in the order occurring was the only way to correlate them. Even though we do telemetry via events, old school logfiles are a godsend to debug the complex cases.
Just look into log4j: mdc/ndc to include context (user/session), include the thread name in your pattern and use an async appender to take care of performance. All of these things have been solved already.
That's why you disable JavaScript: we scrutinize downloaded exe files carefully and have virusscanners running all the time while allowing untrusted JavaScript to reach your CPU. As long as there is no effectieve way to tell trusted and untrusted JavaScript apart, having it enabled is silly.
The change is far from cosmetic: ethernet used to detect collisions on a shared cable and by restricting cable length and timeouts was able to work. What we have now with switches has no collisions and each device has a private cable to the switch. This is a fundamental change and not some cosmetic change.
By counting the number of returned items and service calls: that's way cheaper than upfront checking and in the short run will suffice. That's MBA logic for you.
> No, but they do have parallel config utilities fighting each other in the case of Linux mint. Took me a few hours to figure out why I was unable to switch from a static IP to DHCP.
Windows 10 had this as as well: the new user friendly ui can show dhcp while the interface actually is statically assigned An ip address. Took me while. Seems they dropped not only any consistency but also the prolog part in the new ui.
Nice idea, but please check your local tax office. At least here in the Netherlands, you are required to use a monotically increasing series for invoice numbers. So I wouldn't do this if I were you.
The problem with lobbying in general is that it's a one-sided information stream: politicians are generally uninformed about a topic and only get the information from the wealthy side (ie. the one able to pay a lobbyist). No need to bribe in general, just overwhelm the poor politicians with "facts" and they have no choice but to walk in line.
As far as I know, it was Nasa that put a man on the moon, not some coorporation. Also: the internet was invented by the government. What nice things have corporations given you?
Hmm. Let's see how they do it in practise: funnel all money to another entity for 'licensing' their own brand. Net effect: no profit == no tax. Benefits for society: zero. Sure you don't want to change that?
Any machine that runs only verified code (ie. no JavaScript in the browser, no downloading nifty things and running them) don't need the flushes. Problem is (as shown by the Solarwind hack) even code you should be able to trust can be backdoored. However: if that is the attack vector, spectre and its' offspring are not your real concern: there are much more efficient and effective ways to compromise your machine if a blob of binary ends of being backdoored.
I've read the word "mitigation" so much (not only here, and not only you; so this comment is not directed at you personally) that I only hear doublespeak now: when people say mitigation I immediately think of a slab of concrete in the back of my car to compensate for not having any brakes installed. Please recognize for what it is: a design failure that is pampered upon. A mitigation is not a solution, it lessens the impact of the failure mode that was identified. Afaik, if the flushes and changes actually work, it is not a mitigation but a workaround: the failure mode cannot occur anymore. Mitigation sounds better than workaround though (and is probably the reason it was choosen).
Something overlooked in this (and many other articles about stack based VMs): if the stack based VM requires a well balanced stack (as is the case for JVM), the bytecode can be trivially rewritten to a register based VM: number each stack location and trace all basic-blocks to see which stackslot they hit. Then just replace all the push 10, pop with "move 10 to slot/register-1", "load slot/register-1" etc. The converse is much harder, so I really prefer to work with stack based VMs as they are more condense and if speed is needed a linear (in function size) scan can rewrite it to make the mapping to cpu registers much easier.
There is a secondary effect here besides ROI: image. In my mind I now link LinkedIn to "not even able to handle a creditcard payment". Get enough of those and ROI gets impacted.
The game also allows multiplayer (I've seen 500+ players on a server). That requires some really strong consistency guarantees that you loose by adding threads.
That's who i bought a Panasonic. They cost more but don't have a shitty track record. In fact, my washing machine was the last Samsung here. It broke and got replaced by a German machine. These days I try to avoid the cheapest offering and try to buy quality instead. Upfront cost is higher but I really value my time too much to bother fighting with nonsense like ads on my tv.
I see no issue except from the entities. Which by and large have died anyway as those come from DTDs and not from XSDs. I do not see why closing tags are a problem: my editor will insert them and it makes parsing the XML much easier/less error prone. XSLT is brilliant indeed (and to my eye quite readable, but then again I also like regexp ;-)
It's trivial until you run into a date-field. I've connected some JSON based exchanges to each other and just created an XML intermediary format to have a single canonical model and do the various translations to/from the other systems from there.
For IPv4 it can be done, but it would take at least 512Mb of kernel memory. A hashmap would be inefficient in that case, just use a bit-array. For IPv6 however, you run out of memory with a bit-array. Using a dynamically allocated hashmap in the kernel in that would help the initial allocation, but then you can easily be DOS'ed by having a lot's of banned access and running out of kernel memory.