thedoctor79

I don't know if this comment is satire or not, but I thought the company existed to provide a fast and (relatively) safe means of travel over long distances to people. I guess the old engineering adage applies here too: fast, cheap, safe, pick any two.

Maybe the connection to this topic won't be obvious, but I used to read Animal Farm and think that the Donkey was supeior to the Horse. Nowadays I don't think that anymore. The Horse was never alone for a day in his life. The Donkey survived the Horse but was left alone. So I now think "I will work harder" is the right approach most of the time.

A great tool, trully a programmer's text editor. Used it for more than 10 years, it seemed like it had plugins for virtually eveything. I remember one time we had to work with huge XML files, like 100 MB in size or so, and everyone was grepping them or struggling with other editors, while jEdit had that nice XML parser plugin which showed a nice hierarchical tree :) Thanks for all the work put into it. Nowadays I tend to gravitate towards KDevelop and others but I hope jEdit continues on.

This answer: https://aviation.stackexchange.com/a/34627 is most likely correct. Based on the fact that main carriage is off the ground, flap setting and wing AoA. During departure the rotation angle would be larger before main wheels leave the ground.

500 milliseconds is huge. I don't know what that app does, but in my world if you have as much as 10 microseconds delay you've blown your time budget and you're missing all your KPI and your goals. Have you ever tried to have a voice conversation with a delay of half a second? It's a very frustrating experience. Also, if your framebuffer rendering pipeline has that kind of delay, the user will leave the app in frustration very fast.

It's not the competion that matters, not even playing against or defeating the #1 tennis player. Think of it as a tennis point being played. If both you and #1 play the point perfectly, a beautiful play that will remain in tennis history and create a sense of wonder in many people that watch that point, it does not even matter if you win or lose the point, what truly matters is being part of something great, greater than yourself, greater than the current #1 in the tennis. But to be able to do that, it requires a lot of work, a lot of dedication, and a mindset of playing for the game's sake, playing to feel good and have fun and make other people feel good watching, not trying to win a competition. Also, it doesn't mean that the point could not be played in a different way which is also perfect and beautiful in its own, so other people could potentially play that point and that doesn't mean they're lesser players that you, and it doesn't mean that somebody who can win all points and matches is also playing the most beautiful tennis ever.

I'm not a professional so what I'm saying could be stupid, but I don't see why anti-coagulant medication has to act globally in the organism for something that is a localized issue. I realize the circulatory system is not segmented, however couldn't there be something to be done with the time of action of the anti-coagulant? From my vague recollection, clot formation has something to do with turbulent flow post-valve as well, so improvements might be made in this area as well... try getting a fluid dynamics expert in the team that designs the valves, and I'm not joking. FWIW.

Sir — A. J. Tatem and colleagues calculate that women may out-sprint men by the middle of the twenty-second century (Nature 431,525; 2004). They omit to mention, however, that (according to their analysis) a far more interesting race should occur in about 2636, when times of less than zero seconds will be recorded.

This analysis fails to account for the prediction that in early 27th century FTL speeds will be achievable and a woman would invent a relativistic shoe that would allow here to wind the 100 meters dash.

The facts so far are that two new aircraft of the same model have crashed in a very short period of time, in the same stage of flight and exhibiting the same problem as evidenced by ATC recordings: loss of flight control. We should not focus only on the software aspect, even though a very questionable (and dangerous in my opinion) decision was made to not communicate to the pilots the existence and operation of the software with no additional pilot training.

The software relied on input from sensors at least in the Lion Air crash and the fact is the sensors failed on new aircraft.

I would trust the NTSB as much as the European counterparts. I have read some of their reports and they are very dilligent and fair.

We should avoid placing blame now on anyone whether it is Boeing, pilots, national agencies, until the full reports are available. The grounding of the aircraft was perfectly justified with the available data from a security point of view. The air industry has been focused on avoiding a blame culture. Even I, as a passenger sometimes look for the lowest price, so the pressure for cost cutting may come from us as well.

https://en.wikipedia.org/wiki/Russian_submarine_Kursk_(K-141...

Best decision: don't build it, if it's already built don't launch it, destroy it as soon as possible.

Why the need for actors? The ML could be trained on millions of hours of existing movies and produce fake, convincing personas. Why the need for spectators? The ML could analyse the movies and produce fake, convincing reviews.

Let's imagine a future where fully autonomous weapons exist. Advanced AI is driving them, and technological advances have enabled the weapons to have better sight (wide spectrum sensors), better range and faster reaction time than humans. They can go where humans can't and endure in environments where humans can't live even for a couple of minutes. Perhaps initially the weapons are simple, kind of like the "sword" from Second Variety (P. K. Dick), using radio emitters to identify friend from foe. They would also need a power supply, and because you can't put an advanced brain of huge computing power on a small platform (laws of physics still apply), the "brain" would be located somewhere shielded, deep underground, perhaps near a volcano to use the thermal energy, but also near water, because of cooling requirements. The brain would use a large capacity datalink to communicate with the weapons. Humans are still in the loop, of course, because the adversary is unfortunately quite adaptable and you need programmers to change the software as battle requirements demand. However, humans have this pesky thing called conscience, and sooner or later, if you make them fight, they will refuse to pull the trigger. So they need to be removed as far as possible from the decision to kill, left to the AI. So a team (quite large in fact) of programmers are working on small, disparate features (image recogniton, data communication, weapons delivery) but they never quite see the big picture themselves. Since what they do is quite important, they are well paid and enjoy a nice lifestyle. There are of course downsides. Refusing to do the work anymore or even talking about it could bring repercussions. So the best strategy is to keep quiet and mind your own business paycheck to paycheck. Meanwhile, old school soldiers become obsolete and the AI does all the messy work.

Sounds like fiction? Perhaps it is.

I've used recent enough Dell and Asus laptops, no issues whatsoever.

Tip: when X hangs, press Ctrl-Alt-F1 or F2 to switch to console mode, then Ctrl-Alt-F7 (or F8 on some distros) to go back to X. While in terminal mode you can investigate which process is reponsible for the X issue (high CPU? memory? disk I/O?) If that does not fix it, Ctrl-Alt-Backspace will kill X and every X application and you won't have to reboot.

Oh but we have them. Steve Jobs and Bill Gates were such people.

In US, if you say anything bad about US leaders, maybe you have trouble at the border when you go on holiday. In Russia, you can say anything about US leaders, and nobody will care.

I don't understand why this post is downvoted. You have a perfect example of an AI algorithm parsing text, determining feeling and responding with what it thinks are relevant words. It couldn't be more on-topic than this. AI is participating in HN discussions.

I'm sorry, but the quality of comments on that question is really low, apart from one. A malicious compiler can easily insert malicious code into you executable, and if you are not able to trust your compiler or read the code it generates, then you would be better off relying on the antivirus. Then again, with the prevailing mentality of most Windows users of installing packages from untrusted sources and running unknown binaries without understanding the risks, it is not surprising.

First question I would ask: what compiler are you using, and have you audited the binary it spits out. Sometimes it pays to know a little assembly and be able to use a debugger.

No, I'm sorry, you got this wrong. When you do that, you are not "calling" the cat, you are effectively controlling it with your mind eye. You need to be very careful with that, doing it long term can result in damage to the cat.

I think that it might end up looking more like this: https://www.youtube.com/watch?v=vl_zQ3TTejU

How about using electro-magnetic waves to alter the brain function temporarily and provoke it to lose consciousness? Sounds like a hard technical challenge, but we can already deliver effective tranquilisants remotely and use electrical discharge to disable the central nervous system. Just find a more efficient way of doing that.

So it seems the author has identified a real issue here, but I will go meta on this and identify issues with his demonstration. In my organization this would count as a bug report, so I wondered why this issue was not communicated privately to the operators of Github so they can have a chance to fix it before some un-educated person does some damage. Then I realized this issue might affect other git content hosters, so going public might alert them as well as forcing Github to fix it. Regardless, would the best approach not be to communicate privately first and allow Github to fix it before going public? If this was raised privately and not acted upon, then why are Github's internal processes so slow? So many questions, so little time...