bradenb

Maybe I'm off-base, but I feel like at this point the question of "who can see my data if it's stored in China?" is a bit silly. I--for one--will just always assume that any data stored in China might as well be public.

You are right, of course. But I think it's disingenuous to call all hyperbole clickbait.

This has been posted several times. It’s annoying, but just add a shortcut from lowercase “i“ to uppercase “I” and wait for the inevitable update.

I'm curious what you consider examining the entire code base to find similar problems. If this is more than a 5-10 minute search then I would feel like it's a significant waste of time. And if it is more than that amount of time and you are continuing to find bugs then I would ask what is the problem that allows the same bug to surface in multiple places where it is easy to identify but hard to search for?

Aren't the use cases are the same as for any SSH server?

This comes across as extremely petty. As someone that owns a 6S and no desire to get an X, I see why it might appeal to people. It's a huge UX shift which is enough to intrigue and excite a lot of people. Ultimately what it offers may not work, but you can't dismiss it immediately as being for "fanboys" or "rich people" (especially given there are other $1000 phones on the market).

I have found Paint.NET to be my go-to middle-ground image editor. I think it is more than simple enough for your 4-year-old son.

In January I had every intention of picking up one of these. They are beautiful and seemed to have everything I wanted. But I took a moment to look again at alternatives and I'm glad I did. After doing some research it seemed clear that the HP Spectre x360 was actually the ultrabook to have.

I'm not sure how good Linux support is, but with a 512gb M.2 SSD, 16GB, a U series Kaby Lake processor, and better battery life than the XPS, it felt like a non issue. I have no problems running VS and my CentOS VMs.

I'm not always for regulation but in this instance I absolutely think it is necessary.

"The people who buy this are probably the ones who can't afford real medicine"

This is the reason. If they can't afford real medicine I am doubly-supportive of labeling that prevents them from wasting that money entirely. I'm also not sure how often real medicine is more expensive... I've seen some expensive homeopathic treatments.

It would be nice if you could dry-run each execution of the contract and verify it passes a series of tests. It seems to me that regardless of how these contracts are written, you should be able to verify the behavior.

I would agree that lacking either of those things would cause the problem I described, but in this case we have both of those.

Most recently, I was the one joining a project after its incipient stage, so I was not the big picture guy, but the big picture guy chose not to establish any kind of patterns or standards so when others started joining the project--even with an understanding of how it should work--suddenly the app had a lot more functionality but it all performed terribly because of a lack of uniformity in design. Code review helps, but ultimately because there are no established patterns there is no justification for telling someone a task should be implemented differently, right? The only solution I can see is to establish that justification by trying to get the big picture guy on board with a massive refactor to establish some standards.

> In other words, if you ever find yourself thinking, "I know, I'll use a design pattern" before writing any code, you're doing it wrong.

I completely disagree... if I'm working with a team. I've spent far too many hours trying to fix fragile code that comes about as a result of different devs with different methodologies trying to tie their code together.

Over the last few days at Build, Red Hat had been making a big deal about "loving .NET." I wonder if this move is driven entirely by the desire to be the go-to destination for .NET Core on Linux.

EDIT: I saw this announced by Red Hat during a .NET session and they were giving out flash drives with the image.

I had a chance to play with HoloLens for a few hours yesterday and it was a really incredible experience. Yes, the FOV is noticeable and I hope they can address it, but I felt like I was able to easily compensate for that with the visual and audio cues the device can show you.

And speaking of audio cues... I found the sound to be a truly magnificent aspect of the hardware. There are two orange speakers that sit above your ears that are somehow able to produce some really great special sound effects. If something wasn't immediately in my FOV but it made a sound, my mind was actually tricked into thinking it was part of the ambient sound in the room. It was almost disconcerting to remove the headset at that point and have the sound disappear.

Our entire company uses Slack for most communication since everyone works 100% remotely. It has been fantastic. Finding a good tool for screen sharing has been difficult, though. I pair almost every day, so I need a tool that is stable and has a good quality-to-speed ratio.

For people with good connections, Screenhero works well; only downsides are that we get a lot of crashes in the beta app and sometimes the mouse sharing changes window focus or mouse position for the other user, but in general it is the best tool we've found. For those without good connections, we have to use GoTo since it sacrifices refresh rates for quality.

Overall, I'm excited to see how this works out. Right now it's a small subset of people in our company that use Screenhero, but I expect to see that number jump with this announcement.

Working for a small company that does a lot of parallel combustion CFD modeling and simulation, I'd love to see our engineers try out Julia and see how it much easier it could be on them.

But, from my experience trying to establish rules for using version control, I also realize that they're unlikely to ever rewrite (or even modularlize) their codebase to take advantage of any other language.

If it's a simple 5 minute change, why not implement it and use DI for a single instance? I imagine you would save a good amount of time by being able to run automated tests now rather than the manual tests you described in your other reply.

It's relativity; internal lighting will look the same because light in your ship will still be traveling at the speed of light relative to you (if I'm not mistaken).

Looking back at previous years, this seems like a pretty fun contest. I wish I had seen it earlier (deadline is in 2 days). I'd love to try it out next year.

For the most part this all made sense to me, but it also seemed to contradict experiences I've had. For example, whenever I have work days that consist of the same type of meaningless coding it seems to drag on forever, but give me an interesting or complex (or new) problem that I can really sink my teeth into and the day goes by in a flash.

Also, National Geographic's show Brain Games did an episode about our perception of time. It had a lot of this info in it; it even showed the experiment of displaying familiar pictures with the occasional unfamiliar picture mixed in. http://braingames.nationalgeographic.com/episode/2/

I am painfully aware of how much energy I expend trying to prop myself up above others. Whether I am delicately explaining how I would have done it differently or just fidgeting with my clothes to make myself look better in that place's light, I end up feeling like I'm acting fake. Maybe I am.

Regardless, I think there's little we can do about it. Anytime I overcome the urge to make myself look better to the strangers around me, it is done through no small amount of conscious effort. It is so much easier to just give in to my genetic encoding and try to appear more fit than to make my existence easier.

Here's where I get depressed about this whole thing: how will we know change has occurred? I mean, say in the best case scenario the government admits it was wrong and promises to stop the monitoring programs. How exactly are we supposed to know it has happened? I don't see why they couldn't simply start up a new secret program using the exact same resources and keep it from the public eye.

March 24? I feel like customers should have been notified much more quickly than this. Although they claim passwords were "encrypted," giving the perpetrators over 2 weeks is giving them more than enough time to try and access accounts.