Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×

Comment Re:Discussion is outdated (Score 2) 492

If you want to play with research languages and esoteric forms of programming, then don't get a job in industry, and stick to academia. No one in industry uses Pascal, D, Go, or any of these languages du-jour on Slashdot, because they lack some combination of robust libraries, performance, online knowledge bases, or all 3.

Almost all business applications and consumer-facing applications written in industry today are done in 5 languages

- Java, because of it's incredibly rich library set under the Apache project.
- Python, for anything that does not need to be compiled
- JavaScript, for Web development and Node.JS development
- C/C++, for performance oriented applications, or used with a cross-platform toolkit for Windows/OSX applications
- C# Applications that are Windows platform exclusive
- Objective C (and now Swift) Applications that are OSX/iOS exclusive

Before you villify me, yes I am not retarded and I know that you can compile and run C# applications on OSX and can compile and run Objective C applications on Windows. The truth however is, no one in industry actually does this. If you write an application you want cross platform, you do it using a cross-platform toolkit.

Comment This. SO MUCH This. (Score 5, Insightful) 492

I often feel like everyone on Slashdot is a mix of two people

- Old 50+ year olds used to the good 'ol days when you would write your own stack from scratch whenever writing an application

- 20 year olds fresh out of (or still in) college who yell "squirrel!" at everything new and shiny

The truth is, that 75% - 90% of the business applications that make the world go 'round, and make nearly every startup today go 'round, are based on Java or some complimentary technology like Node.js with Java bindings. The reason for this is simple: The Apache foundation. There are SO MANY amazing enterprise-class Java libraries available via the Apache project that there is little to no reason to ever write your own. The mantra where I work, and it should be where EVERYONE works, is before you write any plumbing code at all, check Apache first. People who roll their own plumbing code INVARIABLY end up with subtle errors they did not think of or subtle problems that will manifest themselves in 2 or 3 year when they try to scale.. and all these problems were likely already figure out long ago.

When building a woodsheed, do you cut down the trees, mill the lumber, and forge the nails? Of course not, you take advantage of modern economies of scale so you can focus on the REAL building project, not the building blocks. The same is true for any halfway competent software developer.. The days of people writing their own libraries for DB MVC, for configuration management, for network access, for parsing libraries, for thread pools.. these days are gone, and thank god. The less you have to worry about the low-level plumbing, the more you can focus on the real business problem. And furthermore, the more people that make use of a low level plumbing libary, the better and more secure and stable it becomes, for everyone.

Comment Re:Are browsers so much better? (Score 1) 95

The risk of the "potential danger" of someone cracking into Chrome's update mechanism and pushing out a rogue update, is exponentially over-weighed by forcing client endpoints to always have the latest security patches - so I totally disagree with the premise of your post. It is far, far, far better for the security of the web as a whole to ensure browsers always have the latest security updates. The near-forced auto-update mechanisms of Firefox and Chrome are some of the best things to have ever happened to web browsers from the point of view of security.

Finally, Chrome *DOES* provide a way for administrators to lock down to specific Chrome versions, so your post doesn't even have a leg to stand on.

Comment Re:History Channel (Score 1) 166

The difference here is all the attempts at Oak Island, including the first discovery of the pit in the early 1795 had multiple witnesses and were fully documented thereafter. And it is not as simple as "well someone found it earlier and filled it back in", because if that was the case then all of the depth marker platforms would not be there.

Sorry if I seem a bit passionate but I have been fascinated by Oak Island ever since I read a book about it as a teenager. The most interesting thing I find is even with all the technology and engineering prowess available today, there is still not a way to just dig this hole up. For example, these guys on this show have literally spend millions of dollars on this - and they are engineers trained in deep well drilling - and they are still no further ahead. Tens of millions have been spent over the past 100 years trying to dig up this hole and deal with the spillway booby-trap.

Comment Re:History Channel (Score 1) 166

Oak Island is actually very interesting. The more you read into the history and find all the weird stuff going on, the more it seems like there has to be SOMETHING down there. The intricacies of what has been found to date preclude it being some sort of prank.

Slashdot Top Deals

"A car is just a big purse on wheels." -- Johanna Reynolds

Working...