Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
For the out-of-band Slashdot experience (mostly headlines), follow us on Twitter, or Facebook. ×

Comment: Re:Who the hell still uses Silverlight (Score 1) 55 55

I can't speak for AqD, but quite often, yes. When I was developing business apps using .NET, desktop was my first choice. Unfortunately, most clients were adamant about a web UI, so Silverlight was my first fallback since it let me reuse a lot of the same code. Only if they resisted that did I go with HTML/JS and ASP.NET. Web app development sucks so I rarely do anything of the sort anymore, but Silverlight made it more tolerable.

Comment: Sorry... (Score 0) 186 186

Sorry, but merely being acquainted with the CLI does not make you a "FOSS expert", nor does it provide any degree of security assurance when running tools compiled from code you are unable to reason about. Unless you can actually read and reason about code at a level that enables you to discover vulnerabilities, backdoors, etc., you do not have the expertise necessary to stay safe, and you should be careful about saying things that imply otherwise.

Comment: Re:Lol don't (Score 0) 452 452

You don't get me, huh? Perhaps I need to be a bit more explicit: I don't give a shit what you use, but if start spewing vitriolic claims about a given technology, you'd best be adequately informed so that you can defend said claims. In this instance, your unsubstantiated, shallow assertions attracted the attention of a Powershell user, who challenged them. You failed to provide anything of substance indicating that "Powershell is a joke", making you look like yet another zealot who disregarded it for religious reasons. To reiterate: your choice didn't bother me, it was your attempt to position yourself as some sort of expert.

Comment: Re:Lol don't (Score 0) 452 452

You haven't provided a single concrete example of what you can easily achieve with the Linux CLI that can't be done with PS. Both have their obvious strengths and weaknesses, so doing so shouldn't be hard. It makes me question your competency, you know? In fact, the only example you've given makes me want to vomit. You think that is elegant or intuitive? Fuck man. But yeah, I actually do work with servers, being that I do a lot of work with distributed computing. In fact, I specialize in distributed test automation, so I'm getting a laugh out of your lone, pitiable example.

Comment: Re:Lol don't (Score 0) 452 452

IPC is possible, albeit differently than Linux. Is this alone enough to discount Powershell entirely? Perhaps if you're a zealot. Personally, I prefer the object oriented nature of PS to the hacky string parsing of the Linux CLI. I write enough string processing code as it is, I'd rather not write anymore performing menial tasks. Taking a dependency on a blob of text is generally a bad idea, and that's precisely why PS' approach is so elegant.

Anyway, if you genuinely recommend WSH over PS, you can be safely disregarded.

Comment: Re:ASLR anyone? hype? (Score 1) 303 303

I think you're confusing read overruns with more general read access violations. If you're trying to predict valid addresses, sure, you're probably going to crash the program with a read AV. However, a read overrun implies that the read begins in valid memory, so unless you hit a guard page or something while reading off the end of the buffer, you're probably in the clear.

Comment: Re:What? (Score 1) 303 303

Competent programmer here. Exploits are programs developed to take advantage of flaws and vulnerabilities, so most software is not "stuffed" with them. Anyway, the post I was responding to seemed to be insinuating that bugs like this go unfixed in proprietary software simply because it is proprietary. I can tell you that is not that case. There are researchers out there combing through everything, open or closed.

Unix: Some say the learning curve is steep, but you only have to climb it once. -- Karl Lehenbauer

Working...