Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 internet speed test! ×

Comment Re:porting...what exactly? to what? WINE? VS CODE? (Score 2) 159

Are they porting compiler and build system or the entire IDE?

If they are porting IDE than with what? Isn't VS IDE done with WPF these days? Perhaps they target...ehem...WINE?

Or are they rebuilding it around Visual Studio Code?

As usual, the Slashdot article title is misleading. What they are describing is not really the porting of Visual Studio to Linux, although MS has been hinting at that for awhile. What the article is describing is the integration of the IDE (running on Windows) with a Linux tool chain (running on Linux). Which per my earlier post, has been possible before with third-party Visual Studio add-ons. For some use cases it is a win.

If you are not already a Visual Studio user and are developing exclusively for Linux, then you are not the target audience.

Comment Re:Sounds clunky (Score 2) 159

This, exactly.

Since I'm developing for a Linux platform, I already have one of these here. So explain again why I have to drag another platform (Windows with Visual C++) into my toolchain when perfectly good IDEs are available for the native Linux environment.

Explain who, exactly, is putting a gun to your head to switch to a different tool chain when what you are using now is perfectly fine?

Comment Sounds like VisualGDB... (Score 2) 159

...I wonder if they licensed any of that technology. I bought a copy of VisualGDB a few years ago and it was slick as hell. I had to port a bootloader written in C that was Windows-only, turning it into a simple command-line program on Linux. It was easy as using a native toolchain (easier, in fact, if you have Visual Studio muscle-memory), and so seamless that it was easy to forget that this was all over-the-wire interaction between a Linux box and Windows.

In my case I was porting it over to a Raspberry Pi to prototype a portable diagnostic device for a hardware project. Came out swimmingly, was one of the highest-impact things I did for them. I was starting with all Windows code, both C and C#. Between VisualGDB and Mono, the porting was extremely easy to do.

Comment Re:I'll believe it when I see it (Score 1) 119

I'd have chosen Voice of America as the foil there, given how Trump just turned it over to some breitbartish characters.

Wouldn't argue with that. The difficulty is that there are so many jaw-droppers to choose from you may as well just throw a dart at the wall. Which should be another clue that this isn't politics-as-usual.

If Obama was performing hostile takeover of this scope and magnitude in the first seven days of office, not only would conservatives be calling for blood, I truly believe that people who supported him would be having their share of WTF? moments.

Comment Re:I'll believe it when I see it (Score 1, Insightful) 119

...we haven't gotten to the point of State Run Media or Ministry of Information...

CNN, MSNBC, Bloomberg, and nearly everyone came awfully close for the Obama Administration.

Media bias (on some spectrum between real and perceived) is an entirely different thing than placing gag orders on in-the-public-interest government agencies and publicy-funded scientific work. But go ahead, keep treating this as a game show, because obviously this is just politics-as-usual and nothing could possibly go wrong in such an exceptional place as the US... (/sarcasm)

Comment Re:Main reasons. (Score 1) 181

Just wait until hackers find way to spoof update source, and use it as a way to install their shit on your IoT gadget (e.g.: that's a vulnerability that's been found on Philips Smart LED light bulbs).

This.

While auto-updates circumvent one problem, it introduces another attack vector. And a failure mode. (yay! none of the lights turn on because auto-update bricked them) Not to mention the "appliance" suddenly becoming unresponsive at exactly the wrong time while it decides to update itself on its schedule, not yours.

This just all get back to the fact that internet connectivity is being taken too far, and by people who's skillset (embedded devs) usually has no overlap with a security skillset. Been there, rubbed elbows with both.

Comment Re:Do older programmers even need help? (Score 4, Informative) 435

If you are over 50 and you are trying to get a job by going through HR, then there is something wrong with you.

Someone with decades of experience should have a deep network, and plenty of ex-coworkers to tap for opportunities. If they don't, that is because those co-workers don't want to work with them again. So why should I hire them?

Unless they've spent a large chunk of their later career keeping their small startup venture alive and generating revenue, effectively keeping them cloistered while they apply their skill set. Yeah, I've got a small network from when things were more robust and I had to hire out some of the engineering work, but most was done by yours truly. The one thing I could have done better was keep more of those contacts alive, as a lot of them are pretty stale. But that time period coincided with kids showing up on the scene, which triaged that pretty far down the list.

So sure, the side-gigs I've gotten over the past 5-6 years have been solely through my small network, that's a good thing. But as the startup slowly winds down, my small network is not as lucrative as I'd like it to be. I haven't had to go the head-hunter route yet, but that's probably the next stop on this train.

All that said, when/if I'm to the point where I'm considering opportunities that involve an HR dept, then I'd say things would be in a pretty desperate state

Comment Re:So what? (Score 1) 437

Well now you know, Facebook is left/liberal biased (which was kind of obvvious before this stunning revalation) much like the overwhming majority of the tech sector. Get over it. They are doing nothing the right wing media and players like the Koch brothers haven't been doing for years.

With the acknowledgement that the above may well be completely true, recently I've been flooded with unhinged Trump posts. From FB friends I'd never expect to see it from. So much so that for the first time I've had to unfollow somebody.

For a long time prior to that I was seeing posts/shares from my left-leaning friends from high-school oh-so-long-ago. Which made sense since I came of age in the 70's in a very liberal part of the Northeast. So seeing liberal/progressive messages from my former classmates wasn't so much an indictment of the medium as much as the demographic with which I was affiliated.

Comment This is a big deal, but not the Apocalypse (Score 3, Informative) 440

https://blogs.msdn.microsoft.com/windows_hardware_certification/2016/07/26/driver-signing-changes-in-windows-10-version-1607

Trust me, as a driver developer, this has been causing me an immense amount of headaches, and Windows 10 is only part of the story.

But the blog entry has a key detail which nobody here seems to understand. Existing Drivers signed by a certificate that was issued prior to July 2015 will still be accepted by the kernel. What this means is that the new rollout is not going to cause the entire ecosystem of Windows legacy drivers to implode. If they were signed correctly for 64-bit Windows before, they will continue to work on Windows 10. Really, truly, I've tested this myself on preview editions of the Windows 10 AE

Where you get screwed is when a vendor needs to update a driver going forward. Then things get to be hairy. Logistically, signing became much harder, everything from obtaining a certificate to performing the actual signing. Pain. In. The. Ass.

Our company just released an update of our product just under the wire of when our legacy "get's a free pass" certificate expired so that we'd have some runway to incorporate the new driver signing nightmare into our tool chain. So we're good up until the next showstopper bug comes along, which fortunately is rare. You'll be able to use our latest release just fine on AE, even though it didn't get signed by Microsoft.

Comment Re:My PCP has a "scribe!" (Score 1) 326

Fair enough, but it seems like all that gets focused on is the cost without weighing in the (lower than for specialists, but non-zero) benefits. Even if it isn't a zero-sum outcome, I would think at this point that most near-the-brink-of-burnout doctors would seriously consider absorbing some of this load.

It's not a given mind you, as when I witnessed controversy over what should have been the no-brainer of adding a Hospitalist staff into the mix. That meant there was an inpatient-specific doctor staff to offload torturous middle-of-the-night admissions, among other things. Most of the doctors were fine with the tradeoff of losing some of the billings associated with the admissions, as it turned "on call" in being a telephone-only affair, rather than a Russian Roulette game of "am I going to get any sleep tonight this time?". There was a small but vocal contingent that balked, but in the end the Hospitalists were hired, which was a win for both doctors and patients alike.

Comment Re:Burnt out doc here: (Score 1) 326

From my view into what my spouse and the other doctors in the practice go through, this is spot on. Right down to the "I'll just go part time", which actually translates into 40 hours (in our case, 25 patient-hours easily is a 50-hour week, and more when an inevitable heavily-loaded week comes along). The only solutions I see are to either get out altogether, utilize the MD for something that's not patient care, or find one of those rare institutions that's enlightened enough to understand how bad this problem is and takes it seriously enough to keep it under control.

Sadly, the last option is probably all but impossible right now, though there are promising signs that the industry is slowly waking up to just how unsustainable the situation is.

Comment Re:Slow data entry (Score 1) 326

Yes. The UI's I've seen suck to high heaven. It's not hard to be five levels deep in nested dialog boxes as they have to navigate checkboxes and codes that are spread all over the place. The visual context-switching that has to be done to enter the information for a single visit is staggering. Not only is it slow as hell, but mentally taxing. A huge waste of the physician's mental bandwidth.

Slashdot Top Deals

Mathematicians practice absolute freedom. -- Henry Adams

Working...