But world does revolve around developers. We are reason why companies like Apple are successful.
And if even cheap Chromebook provides better experience, than it is time to move on. MacBook Pro today actually has some competition, Dell XPS is very nice machine.
"Kiev has claimed that Ukrainian troops have destroyed one separatist L-39 military trainer aircraft, two An-2 agricultural aircraft, one Yak-52 trainer airplane and four Mi-24 attack helicopters -- the latter being the most dangerous aircraft in the list, and the only ones built expressly for an armed role."
"It was regular war zone with dozens other planes shoot down"
with dozens of Ukrainian planes shoot down. (who shot them? where did they got weapons for that? where did they got skills for that?)
"Ukraine army shoot down civil airliner with 90 people on board just a few years ago" How many planes (korean planes to be specific) were shot down by USSR (that includes Russia)
I meant difference not about the fact that somebody shot the plane, but the difference in reaction.
Why Russia blocked tribunal? What about all that clowning around investigation, throwing a new weird version about accident (what about the version that goes about frozen bodies or version about shooting down the plane by Ukrainian Su-25 that can't reach that altitude? All of this went through Russian state TV channels and other state people (Investigation Committee etc.)
- Just because that they can, doesn't mean that they would.
- The list lists Ukrainian aircraft lost during the conflict, not the separatist/Russian aircraft.
- Yes, separatist-held territory is Ukraine territory, and separatists are (at times) Ukrainian citizens, although Ukraine currently cannot guarantee the safety of its, or other citizens in the separatist-held territory.
- As to the last point, who knows. Who produced what, and sold where in the post-Soviet world is a lot harder to debunk than the publicly exposed news.
Russia never took on, and still does not take on its moral obligation to proactively control its border with the conflict zone. Similarly, Ukraine didn't take appropriate action to ban flights over the conflict zone. Ukraine did take action - when will Russia? Both are "guilty" in the case of MH17, due to their inaction.
"There are risks and costs to action. But they are far less than the long range risks of comfortable inaction." - John F. Kennedy.
This paper also explains each rule. They use code analysis tools a lot, and do not like stuff which makes analysis harder (recursion, unbounded loops..)
Recursion and unbounded loops are far too risky on their own, even ignoring the problems they cause for static analysis. The code that goes on NASA spacecraft is bombarded by cosmic rays on a daily basis, something a server sitting in a building at the bottom of the atmosphere doesn't have to worry about nearly as much. Even if the code is perfect, if a ray hits the right spot it's possible for it to flip a bit and then your perfect recursive function will do who knows what. [1]
They use error-correcting memory to combat this, but it's still better to be safe than sorry when your software controls a multimillion dollar space oasis with human beings inside who have no means of escape.
A keyword search inside the link to the publication you shared returns no results for linear programming or simplex. I don't see how your links support your claim that he should have been mentioned in an article devoted to linear programming; which, btw, is different from linear targeting.
To be fair, I understand your respect for the man and I don't think anyone would downplay Svoboda's contributions to computer design and mathematical/scientific computing.
What would prevent people from disassembling this, replacing a few parts and making new gun? Making hand gun is very simple once you have basic components, such as barrel and bullets.
I am worried that this will become yet another obstruction for gun holders. Germany (and EU) is crazy, pepper sprays or even pocket knives are banned. Neighbouring Czech rep. is more liberal and has comparable crime rate.
> What would prevent people from disassembling this, replacing a few parts and making new gun? Making hand gun is very simple once you have basic components, such as barrel and bullets.
Nothing, but why would you want to? The whole point is so you can buy a gun that only you can use (and not e.g. your kid). I guess a thief might still steal a gun and then disable the system, but making life harder for such a thief is a good thing even if it doesn't make it impossible (just like an engine immobilizer). But if you're worried about "bad guys", the point is just to stop accidental shootings. There's nothing in the system that would stop you deliberately e.g. shooting a cop with one (as long as you had the wristband on).
I'm not sure, but I never saw it as a trap payload.
Rather, it's something that could go wrong when overclocking, since the Xtals were often locked to the video sync rate (my Falcon's "Nemesis" was a real bugger for it); maybe it'd try to change into a mode that actually didn't have the clock it was expecting!
I don't know about "blowing up", but yes, if you put a bad signal into them, some of them might break. I had (probably still have, actually, somewhere, albeit modified for SCART with an LM1881 and my crappy soldering!) an Atari SC1224 RGB monitor in which you fed the horizontal and vertical sync frequencies separately (rather than composite - hence the LM1881 being needed to split the sync). And at one point I had a Falcon, with Nemesis, and Videlity. The monitor did NOT like it if you fed it a horizontal sync outside the 15.6-15.8KHz range (like, say, VGA's 31468.5Hz; oops!).
The result was the big transformer in the back (line output transformer?) heating up and whining and the caps building up voltage, the screen's black level warming to an alarming dull green… I don't think I'd have wanted to keep the power on another few seconds! Although it'd probably only have burnt something out, I didn't want to break anything.
Point is, some CRTs are a bit more… direct than others. I hear the vector monitors (as used in Tempest) are particularly hairy beasts.
There were failure modes they didn't always think about.
I once killed off an 80's era TV I was using for a display on a microcontroller. At the time, I was writing low level NTSC driver code, and was abusing the standard a little for some color advantages.
A combination of bright screens, overly dark ones ( sync in the visible raster), and misplaced vertical blank pulses popped that TV. It never displayed the same again.
Still worked, but was just crappy.
As monitors age, they can become vulnerable to this kind of thing. Not so much a single value, or poke, but ugly code intended to stress a display could take a few of the edge case ones out.
It was a fairly common thing, I think? Modern CRTs can detect out of range inputs but at one point you just had to be careful not to supply out of range frequencies. No more onerous than putting the right fuel in your car...
