Slashdot Mirror


Something For (Almost) Every Developer

First up, reader martinjlogan sends along a tutorial for setting up a workable Erlang/OTP development environment on a Mac. Next, reader acid06 notes news of Perl 5.12, including what may be the first delivered fix for the Y2K38 bug. (Hit the Read More link below for some details on Perl's new release strategy.) "After two years of development, the new major version of Perl is now available. Notable new features are: better Unicode support, proper support for time after the Y2038 barrier, new APIs to allow developers to extend Perl with 'pluggable' keywords and syntax, warnings for deprecated features and more. From the linked post: You can get it from the CPAN right now or wait for a platform-specific release (such as Strawberry Perl for Windows)." Finally, from reader snydeq: "InfoWorld's Martin Heller provides an in-depth review of Visual Studio 2010 and finds Microsoft taking several large steps away from its legacy IDE code. 'Visual Studio 2010 is a major upgrade in functionality and capability from its predecessor. Developers, architects, and testers will all find areas where the new version makes their jobs easier. Despite the higher pricing for this version, most serious Microsoft-oriented shops will upgrade to Visual Studio 2010 and never look back,' Heller writes. Chief among the improvements are Microsoft's revamping the core editing and designer views to use WPF, its overhaul of IntelliSense and support for test-driven development, and its intelligent support for multiple versions of the .Net Framework."
Re: Perl. This release cycle marks a change to a time-based release process. Beginning with version 5.11.0, we make a new development release of Perl available on the 20th of each month. Each spring, we will release a new stable version of Perl. One month later, we will make a minor update to deal with any issues discovered after the initial ".0" release. Future releases in the stable series will follow quarterly. In contrast to releases of Perl, maintenance releases will contain fixes for issues discovered after the .0 release, but will not include new features or behavior.

50 of 263 comments (clear)

  1. VS upgrade cycle by QuantumG · · Score: 4, Insightful

    most serious Microsoft-oriented shops will upgrade to Visual Studio 2010 and never look back

    Of course, implying that you're not a serious Microsoft-oriented shop if you don't upgrade. This is the exact opposite of the case. As Microsoft regularly changes stuff in VS that no-one wants, most people don't upgrade until necessity forces it on them. It's entirely network effects. If you're using precompiled third party libraries and they upgrade, chances are you'll be forced to upgrade. If Microsoft made it easier to use the new IDE without upgrading the compilers, the standard lib, the header install, etc, I imagine more people would accept the feature improvements (and the bug fixes!) to the IDE without trepidation.

    --
    How we know is more important than what we know.
    1. Re:VS upgrade cycle by AndrewStephens · · Score: 4, Informative

      Agreed. I work in a "serious Microsoft shop" and we have just migrated our projects to VS2008. Experience has taught us that although the Microsoft Dev environments are of high quality, for the first 12 months there will be service packs and patches. We do not want to have to migrate our whole team and our projects every 3 months just to keep up.

      That said, I am looking forward to using VS2010 eventually. I couldn't care less about .NET but the new C++ language features are neat.

      --
      sheep.horse - does not contain information on sheep or horses.
    2. Re:VS upgrade cycle by QuantumG · · Score: 5, Insightful

      Bad, bad, bad, bad, bad idea.

      I think its a great idea.. there's no reason why the IDE release cycle has to be tied to the compiler release cycle.. except that Microsoft likes the lockin.

      --
      How we know is more important than what we know.
    3. Re:VS upgrade cycle by Sponge+Bath · · Score: 2, Insightful

      ...we have just migrated our projects to VS2008.

      They can have my MSVC 6 when they pry it from my cold dead GLURK, gaaasssspp...

      One problem I've had is the new redistributable requirements of each release. Not insurmountable, but a real concern when considering an upgrade.

    4. Re:VS upgrade cycle by yuriks · · Score: 5, Informative

      Actually, one of the features of 2010 is that you can target old compiler versions (starting with VS2008) with the new IDE.

    5. Re:VS upgrade cycle by jellomizer · · Score: 2, Interesting

      I think CPAN is there to make you go nuts trying to get a downloaded Perl Script to work as you dig around trying to find the right libraries to make the freakin program work... But I am not a fan of Perl so I digress...

      The 3rd party problem isn't a case of reinventing the wheel. But getting new wheels that already exist just because they are slightly different, eg a grid control that automaticly populates from the database vs. Loading it from 3 other commands...

      But... Sometimes for programming reinventing the wheel is a good thing. Why...

      1. Maintenance. A 3rd party control means code you probably wont touch... Even if it is open source you will not probably spend to much time reworking it unless you really have to
      2. Portability. Just as the Grand Parent mentioned moving to the next version of you developer system may break the third party tool, while you own version can be upgraded much easier, also if you were say moving from a windows form based app to a web app you already have the logic there to port you app over.
      3. Knowlege. Black Boxes in your knowledge and your product can be a bad thing. If you do it yourself you know how it works, if you don't and you find a problem you look and feel stupid
      4. Your License. If you get a GNU 3rd party license you have to follow the GNU. If you get a closed source license you need to follow their rules... You make it yourself you can license it any way you choose, as well as the rest of your app.
      5. Optimal Solution. Your code will do just as you need it to do. No more, No Less 3rd party tools either have you taking out a feature you would like. Or just do a lot more then you need causing issue later on.
      6. Easier for others to follow. If someone else is tracing you code and you get a 3rd party tool, it is either a black box application that you are referencing where you need to break your trace to see what the heck it is for. Or there is source and you go in there and it being code by a different person it is like you are in Wonderland were all coding styles have changed.
      7. Deployment. If possible you can get that app to run as a single unit deploying it is much easier as say for windows no registering a bunch of crap.
      8. Cleaning. If you have 3rd party tools that have been there for a while, you really don't want to get rid of them without knowing how it will effect your other program. Your own code it is a bit easier
      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    6. Re:VS upgrade cycle by h4rr4r · · Score: 2, Insightful

      CPAN installs everything you need, that is why the tool cpan exists. If it takes extra work, you are doing it wrong.

      1. if it does not do what you want, don't use it
      2. just fix the code like you would fix your own, or replace it.
      3. if you don't have source don't use it. No blackboxes that way.
      4. So long as code is all internal who cares.
      5. Use the features you need.
      6. Again if you don't have source you are a fool to use it.
      7. No, this is wrong. This is why every damn windows apps brings along it's own copy of everything. Get a fucking package manager you dolts.
      8. same issue when you have more than 1 developer internal or external.

    7. Re:VS upgrade cycle by Blakey+Rat · · Score: 3, Insightful

      there's no reason why the IDE release cycle has to be tied to the compiler release cycle..

      There's Intellisense which, you may have heard, is kind of a big deal about Visual Studio. If the language adds new constructs (which is does), and the IDE isn't updated to cope with that, then you end up with useless, or even worse-than-useless, Intellisense.

      What they could do is have the language team produce and release a patch for Intellisense to correspond to their language releases, but then you get into the nasty situation where the language team has to build and QA patches for 3 or 4 versions of Visual Studio-- bugs would creep in, undoubtedly.

    8. Re:VS upgrade cycle by GoatEnigma · · Score: 4, Interesting

      If no one ever reinvented the wheel, we'd all be running around on stone wheels.

    9. Re:VS upgrade cycle by grcumb · · Score: 2, Interesting

      There's Intellisense which, you may have heard, is kind of a big deal about Visual Studio. If the language adds new constructs (which is does), and the IDE isn't updated to cope with that, then you end up with useless, or even worse-than-useless, Intellisense.

      It's interesting to contrast this with bash TAB-completion, which operates in a very similar fashion (albeit in a somewhat different context). The basic capability has been around for a long time, but increasing numbers of utilities are taking advantage of it.

      These days, for example, you can use TAB-completion to see a list of available packages to install based on a given string; you can find the available options and arguments for countless different utilities, even when there are hundreds of available choices.

      All of these improvements have arrived piecemeal, without requiring any particular effort from the bash developers themselves.

      So why should Intellisense language bindings be limited to a particular version of Visual Studio? Surely one should be able add/update/change a language and have the bindings Just Work...?

      I risk inciting a flamewar for saying this, but both vi and emacs can integrate new language/version modes without any fuss or bother. Why would it be an issue for VS?

      --
      Crumb's Corollary: Never bring a knife to a bun fight.
    10. Re:VS upgrade cycle by YttriumOxide · · Score: 2, Informative

      most people don't upgrade until necessity forces it on them.

      My "day job" is C#, using Visual Studio, and yes, I'd agree with this in general. Not exactly for the reasons you mention, but close enough to it. My job is basically maintaining and extending an SDK that's handed down from our parent company and then handing it over further to third party development companies (plus a bit of in-house coding ourselves, using the same SDK) and providing code level support for them. The current release of our SDK is entirely .NET 2.0 with VS2005 solution files. We've only just very recently started releasing demo applications for the third parties with VS2008 solution files. It'll be a very long time before we even think about touching VS2010 outside of my "playground" Virtual Machines, since any upgrade we do, we're essentially forcing on several hundred other companies...

      --
      My book about LSD and Self-Discovery
      Also on facebook as: DroppingAcidDaleBewan
    11. Re:VS upgrade cycle by Com2Kid · · Score: 2, Insightful

      What do you mean by backwards compatibility?

      Lets say they allow you to open up solutions file unchanged from VS2005. When ever you load a VS2005 solution, any new VS2008 feature that has some aspect of it saved in the solution file would have to be disabled. That also means additional code paths all over the place checking if you have a VS2005 solution loaded up or a VS2008 solution loaded up, and the displaying of appropriate error messages whenever the user tries to use such a disabled feature.

      That is a messy solution, especially given that the most common imagined scenario is for a team of programers working together to all be using the same version of Visual Studio.

      For a product like Word it may be worth it to extend the extra engineering effort to enable backwards compatibility for years on end (IIRC Office 2000 files can interoperate with Office XP and 2003 files A-OK, so two major releases), but for a product used by technical users, one expects that the technical users would rather have other aspects of the product polished more (gated checkins! Holy cripes, TFS finally has gated checkins!) and for developers to just run a one time wizard and convert their project over.

      And actually it is possible to maintain a project across both VS2005 and VS2008. If you need a project to be used by both versions of VS, you only have to bother when changing project references or adding new source files, open the appropriate solution file up in both versions of VS and make the change to the project or the solution.

      Yes it sucks. I've hit this same issue when VS2008 first came out and not everyone on my team was using it, yes it is a PITA. The solution was to tell everyone that they had to just get around to installing VS2008 before the next time they pulled down the latest copy of the code.

      (And yah I see how it could suck if you have multiple teams and some team wants to stay with VS2005 for whatever reason)

      But really, VS2008 supported so many new types of solutions, and in some cases, completely brand new ways to have certain types of solutions organized, that the file format was going to change. Just thinking about it for 10 seconds or so and it seems like maintaining back compat would have involved a UI nightmare, telling users seemingly random features are disabled always sucks, and should be avoided whenever possible.

    12. Re:VS upgrade cycle by serviscope_minor · · Score: 2, Informative

      It's interesting to contrast this with bash TAB-completion, which operates in a very similar fashion (albeit in a somewhat different context). The basic capability has been around for a long time, but increasing numbers of utilities are taking advantage of it.

      I think you may musunderstand how BASH tab completon works. The completion has nothing to do with the utilities. BASH has programmable completion, and the program usually decides what to do based on the firstr token (i.e. the command name). It will then make finer grained decisions based on the argument before the cursor.

      This is all programmed in BASH, and the utility authors have no input. What has changed recently is that distributions have started shipping with a long and rather complete program for the command history.

      But as you have surmised correctly, the changes have arrived piecemeal. BASH scripts are easy to parse, and all my completion programs make use of only simple text maniuplation to figure out what to do. C++ on the other hand is very much harder to parse.

      Basically to make intellisense work, you need a C++ parser, and C++ is sadly one of the nastiest languages to parse. I would strongly suspect that they upgraded the compiler front end. To go with it, they updated the back end (the fron tnd has new features), the libraries (TR1 benefit from and C++0x libraries require C++0x support), and intellisense.

      By the time they've done that, they may as well upgrade the GUI.

      --
      SJW n. One who posts facts.
    13. Re:VS upgrade cycle by vivian · · Score: 2, Interesting

      My "day job" is C#

      Sorry to hear that. Mine used to be too - then I started using QT and QtCreator for my main project. Bliss! Finally I am able to easily write apps that will run on multiple platforms, but still has a rich library of UI controls ( widgets) and plenty of abstract data types.
      I really cant see me going back to C# - I just don't see a need for it any more, now it is so easy to write GUI intensive apps in C++. I have been working on my current project for a couple of years in C#, but it has only taken me a few months to get a C++/QT equivalent up and running - I was able to even ditch a lot of the code I had written in C# (eg. a docking panel interface, a MVC for treeviews, etc) because QT already provided those. In addition I have been able to completely ditch the third party control I was using for opengl too, since again, there's already an opengl widget in QT. (I'm writing a sort of Quantity surveying system / scriptable 3d CAD / quoting database thing for a construction company)
      Only down side I had initially to moving to QT was getting my head around how QT form designs and widget layouts work compared to how forms work in C# (ie. using anchoring/docking for sizable forms), but I have pretty much nailed that now.

      My biggest bitch with C# and Visual Studio Professional 2005 was the Complete lack of a profiler - I mean - WTF! I'm not forking out $15,000 for the team edition to get a profiler.

    14. Re:VS upgrade cycle by bondsbw · · Score: 2, Informative

      But the software couldn't be built anymore because it could only be built via Visual Studio and the current release of Visual Studio was incompatible with the version of VS that the app had been created under.

      That hasn't been the case in many years. Every .NET version of Visual Studio (2003, 2005, 2008, and 2010) are backwards compatible with the previous project files and solutions from prior .NET versions. Since I don't use VS for C++ or VB, I can't say whether compatibility goes back further.

      As far as the language and libraries go, Microsoft makes a point to keep things compatible unless there was a major bug with an API. C# 4.0 will compile C# 1.0 source code, and the libraries will still work, assuming you used them correctly and are not dependent on bugs in 1.0/1.1. (One major exception... ASP.NET 1.0/1.1 code is somewhat incompatible with later versions. I call this a feature, considering that the newer versions more strictly conform with the XHTML standard.)

      .NET 3.0+ features like WPF are not available on certain older operating systems, but that's a different subject. The 3.0 features are just additional libraries that run on CLR 2.0. If you don't use those libraries, compile your code for .NET 2.0 and you can use it on the older operating systems. 2.0 compilation has been provided since its introduction in VS 2005.

      --
      All my liberal friends think I'm a conservative, all my conservative friends think I'm a liberal.
  2. Whew! by Anonymous Coward · · Score: 2, Funny

    proper support for time after the Y2038 barrier

    Good to know that my time machine written in PERL will no longer malfunction due to improperly handled timestamps! Now to test this baby out. This knob here, this button here, and... %^$%^$%^$%^$%^ NO CARRIER

  3. Stereotyping? by kickme_hax0r · · Score: 2, Insightful

    So almost every developer either: a) Uses Erlang and a Mac b) Uses Perl or c) Uses VS2010? Is it just me, it would there still be a fair chunk of developers not included?

    1. Re:Stereotyping? by FooAtWFU · · Score: 3, Informative

      Well, almost every Unix developer uses Perl for glue code, and almost every Microsoft developer will use VS2010, and if you're programming a Mac, I don't see how you could be sufficiently non-erudite to use anything but Erlang.

      --
      The World Wide Web is dying. Soon, we shall have only the Internet.
    2. Re:Stereotyping? by Haxamanish · · Score: 2, Funny

      I really hoped there would be something in this thread for Prolog programmers who write their time-critical code in assembler, but I was disappointed again.

  4. So... by FlyingBishop · · Score: 5, Insightful

    We've started churning out pointless stories all day and then cramming four actual news posts into a single thread?

    1. Re:So... by crazycheetah · · Score: 4, Funny

      Welcome to Slashdot!

    2. Re:So... by Blakey+Rat · · Score: 2, Insightful

      At the very least, it could have been 4 actual entries so that the comments don't just become a huge clusterfuck.

      But... nobody running Slashdot gives a fuck. They don't even pretend, really.

  5. Erlang is an interesting language by msobkow · · Score: 4, Interesting

    I've been working with Erlang for about 9 months now. It's an interesting language, but prone to some of the most bizarre runtime problems because it doesn't do type checking (for example if you typo a "+" instead of "++" when concatenating strings it'll defer the error to runtime, when it reports an "arith error".)

    One thing that really impresses me about Erlang is how tight the code is. We've been working on a PBX application (with Freeswitch and PostgreSQL) and it's not even 30,000 lines of code in Erlang, including database I/Os and client/server GUI access. C++ would have weighed in at around 100,000 lines for the same functionality.

    --
    I do not fail; I succeed at finding out what does not work.
    1. Re:Erlang is an interesting language by Anonymous Coward · · Score: 2, Interesting

      In many languages ++ means concat the lists, so I assume that if a string is a list of characters then its a concat of the two lists? I'd guess that once you understand the underlying concepts and seen a few functional languages then its not too confusing to debug. It is frustrating to have to wait until runtime to find errors that a decent IDE would identify immediately..

      I always wondered how well Erlang handles caching. An LRU is generally a list crosscutting a hash-table and is done O(1) by reordering the entry. As Erlang uses persistent values, this would be O(n). Also, since an actor handles messages sequentially it couldn't handle a high load. Do Erlang folks do caching in the VM or is it purely externalized? I suspect that the common apporoach is to use memcached with a pool of actors that make the out-of-process calls? This would resolve the shared state issues, though how expensive is the serialization overhead?

    2. Re:Erlang is an interesting language by Algan · · Score: 2, Interesting

      I've been using Erlang as my primary language for the past 2 years and I have to say that you are essentially correct. My worst typo-leading-to-weird-bug situation was forgetting a comma in a list of strings. Apparently ["foo", "bar" "baz"] is interpreted as ["foo", "barbaz"]. That led to some subtle failures in a totally different part of the code.

      However, occasional weird issues aside, it does reduce the size of the code and the number of bugs by a factor of 4 or 5. I have been able to write non-trivial pieces of code in the range of 100 lines that ran fine the first time around. That never happened with C/C++/Java. And the way Erlang and the OTP environment handles product deployments and maintenance is really superb.

      --
      If con is the opposite of pro, is Congress the opposite of progress?
  6. 2K38? by the_humeister · · Score: 5, Insightful

    Would it hurt to just write 2038? No space is saved writing it the other way.

    1. Re:2K38? by moteyalpha · · Score: 5, Funny

      I think that 2K-10 is even better. 2K-10=(1024*2)-10=2048-10=2038=(2^11)-10

  7. Re:IDEs by badboy_tw2002 · · Score: 4, Interesting

    When your project size starts getting large and the number of classes/functions/types/etc starts heading to the thousands its pretty nice to have something that will quickly show you the organization of the code base and help you find things faster. Stuff like "I'm in a source file, open the corresponding header" or "show me all the places that call this function" or "rename this function everywhere it was used" or even "let me browse through the 10 versions of the function to see the right one without having to load the header file and stare at it". Also, when there's tight checkout integration its nice to click on another file, check it out, etc. without having to drop to the command line or move to something else. That's not to say that the command line isn't useful - I still find it easier to sometimes run makes or grep or whatever so there's always one handy, but personally I get a lot more done than with a plain old editor.

  8. Strawberry Perl will be out in a week or so by adamkennedy · · Score: 4, Informative

    Strawberry Perl has been doing betas all the way through the 5.12.0 RC process, so the production release should be out in a week or so.

    What the summary doesn't mention is that there's some stuff in 5.12 that allows Strawberry to add:

    GCC-based 64-bit support for Windows servers

    Strawberry Portable (flash drive) stuff finally works in a first-class manner (with separate core/vendor/site installation targets).

    1. Re:Strawberry Perl will be out in a week or so by Phroggy · · Score: 3, Informative

      In contrast to ActiveState's ActivePerl (a Windows port of Perl, sponsored by Microsoft, which works well but changes things enough that you generally can't just download some random CPAN module and compile it, you have to use one of the precompiled binary modules they make available), Strawberry Perl is a Windows port of Perl that tries to remain as close as possible to the original UNIX version, but tweaking just enough to get it to work well on the platform. I believe the goal is to move toward Vanilla Perl, which would be essentially taking the plain old normal Perl that runs on UNIX, and just running that on Windows without changing anything.

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  9. Re:IDEs by jellomizer · · Score: 3, Interesting

    I use IDE as a tool.

    The problem is some people use it as a crutch... "If the IDE doesn't handle it then it cant be done" mindset

    But it is a tool to keep in your cap. I know Visual Studio 2008 is good at showing me methods and properties I can access from the variables which is handy to let you know what is going on in a datatype/class you don't use much.
    However sometime I will take the file out of Visual Studios to do some additional coding because Visual Studios Expects you to code in Top Down in this order...
    IF (x == y)
    {
                msgbox("hello");
    }

    However real life has it more like this...

    msgbox("hello");

    run test...

    Up arrow Return
    if (x == y) {
    return down arrow to go past the msgbox command
    }

    For this case the IDE is a pain because it will try to close my if statments {} which if I am not paying attention it will give me an extra } that I need to dig around and find when I get a compile error.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  10. What, no ActiveState mention? by Anonymous Coward · · Score: 3, Informative

    While you're waiting for Strawberry Perl to put out a release, why not try a package from a company that has their stuff together? Activestate's ActivePerl 5.12.0 is free-for-non-commercial-use and already out. 32- and 64-bit builds for Windows, Mac, and select Linux distros are available.

  11. Re:IDEs by QuantumG · · Score: 4, Interesting

    Eclipse might be better than VS, but I've never been able to get it to run fast enough to be usable.

    Last time I installed it the person advocating it to me looked over my shoulder and said "yeah, I think you need to upgrade your video drivers".

    --
    How we know is more important than what we know.
  12. wtf? by MagicM · · Score: 5, Insightful

    Awesome. From now on, let's just post 1 story on Slashdot per day with all of the good stuff in it, so that we may discuss everything in it in one big unrelated clusterfsck of comments.

  13. Re: new major version of Perl is now available. by Sarten-X · · Score: 4, Insightful

    It's considered trolling because that's purely what it is.

    Perhaps you'd like to enlighten us with some examples of "byzantine syntax", since Greek and Latin aren't valid Perl. Perhaps you meant "British" syntax, since the language is based more off of English than other programming languages. Yes, I'm aware this places it in the same group as COBOL, but hear me out.

    Perl's syntax is based off natural language. You should be able to tell the computer what to do in the same way you'd tell another person, with some obvious extra clarity needed. In this regard, it is the opposite of INTERCAL. In Perl, when you want to run a function 'foo' if and only if 'bar' is true, the statement is very close to what I've just said.

    foo if bar;

    Sure, it's not like C, but why should we limit our thinking? Alternatively, just as in English you can say "If 'bar' is true, run 'foo'":

    if (bar) { foo }

    Perl is a language for people who use language. Even the more ugly syntax makes perfect sense with a bit of thought:

    s/foo/bar/g;

    That's a full statement, saying "substitute foo with bar globally". It applies to whatever you happen to be working on at the moment, just like how there are many statements in English that carry an implied 'you'.

    The syntax of the Perl language is only ugly if you try to forget that it is a language. Perhaps other languages should try to emulate Perl's features, and actually gain some readability. Sometimes, it just makes more sense to express things differently. Would COBOL be so bad if it allowed BASIC's syntax as well (and allowing non-computer people to write in it carried the death penalty)?

    --
    You do not have a moral or legal right to do absolutely anything you want.
  14. Re:IDEs by abigor · · Score: 4, Interesting

    I really hate Eclipse actually. I find it buggy, slow, and non-intuitive in a lot of ways. For Java stuff, IntelliJ IDEA is really great. For non-MS C and C++...I'm not really sure anymore. I mostly end up using Vim and the command line.

  15. Just to clarify... by Valdrax · · Score: 5, Funny

    %^$%^$%^$%^$%^ NO CARRIER

    Just to clarify, does that actually do something in Perl?

    --
    If it's for-profit but free, you're not the customer -- you're the product (e.g., the Slashdot Beta's "audience").
  16. Re:Perl 5.12? by mr_mischief · · Score: 4, Informative

    Perl 6 is mainly usable, and some form of it is being used in production at multiple sites. It's just not ready for public "launch" yet. If you really want it, you can get it. Perl6.org has it.

    Perl 5 hasn't exactly been sitting still the past decade. The changes between 5.6 and 5.8 or 5.8 and 5.10 are huge. I haven't looked over the full changes list for 5.12 yet, but it sure isn't the language Perl 5 was in 2000.

  17. no brainer? by thoughtsatthemoment · · Score: 4, Informative

    I've been using VC++ Express 2008 and was excited to get an upgrade. But instead I was surprised by a few seemingly "dumb" moves:

    1. The default fonts for the editor and tool windows have been changed to a font that looks very blurry on Windows XP. To change them back, you have to change them one by one for every window.

    2. The drag'n Drop capability to add buttons to the tool bars is gone. You have to find the button from another dialog and then click "MoveUp/Down" several times to move it to the place you want.

    3. The GUI I used the most in the Option Dialog, the directories of Exe/Include/Lib, is moved to a place that I haven't yet found.

    4. The startup time is much longer than that of 2008.

    5. The new GUI has a high contrast. Maybe it's just me, but after staring at it for a long time, I feel like I am starting to see ghost images.

  18. Is VS2010 still slow? by MrCrassic · · Score: 3, Informative

    A few days ago, I used a copy of Visual Studio 2010 that I got from my MSDN Academic Alliance account. It looks really nice, but it ran absolutely dog slow. And this was for debugging VBScript!

    I gave it another shot with Visual Studio 2010 Web Developer Express, which I heard can debug VBScript just like the full devenv can. It was a little faster (though still slower than VS2008), but it nor Visual Basic 2010 Express would debug my VBScript.

    I haven't tried coding on it for real (I also do C/C++ development; can't wait to port that script over to a REAL effin' language), but if it's as slow as I remember it being, I can see lots of companies turning back really quickly.

  19. Re:IDEs by ClosedSource · · Score: 2, Funny

    "It's always been very snappy on Windows"

    Hmm. And I always thought that "snappy" implied fast and responsive. I guess not.

  20. Bugs? Impossible! by AliasMarlowe · · Score: 5, Funny

    bugs would creep in, undoubtedly

    Impossible, if you follow Micosoft's guidelines, such as those published in the Microsoft Programming Series book by Steve Maguire: "Writing Solid Code: Microsoft Techniques for Developing Bug-free C" ISBN 978-1556155512
    Microsoft uses these very techniques themselves, in every single one of their bug-free programs. Uh, on second thoughts...

    --
    Those who can make you believe absurdities can make you commit atrocities. - Voltaire
  21. Re: new major version of Perl is now available. by ais523 · · Score: 2, Informative

    I'm offended by your statement that it's impossible to write valid Perl in Latin, and offer this counterexample. Arguably, a Latinised syntax fits it even better than an English-like one; in both Perl and Latin, there's often enough context to put things in a (relatively) arbitrary order. Of course, I'm someone whose signature is an INTERCAL statement, so you may want to take what I've said with that in mind.

    --
    (1)DOCOMEFROM!2~.2'~#1WHILE:1<-"'?.1$.2'~'"':1/.1$.2'~#0"$#65535'"$"'"'&.1$.2'~'#0$#65535'"$#0'~#32767$#1"
  22. Re:IDEs by JohnFluxx · · Score: 2, Interesting

    > This for instance is not something you do while the IDE is open

    Then that pretty much rules using an IDE. It's crazy to imagine opening and closing an IDE every few minutes just because I want to backport my fixes to a different branch, or bisect to find a bug, etc.

    Even plain old GDB lets you view raw types just by writing macros to display things however you want. Hell, it even has python scripting support, so you can go crazy with it.

  23. Re:IDEs by JohnFluxx · · Score: 2, Interesting

    grep is an interesting point actually.

    Okay, so the IDE lets you search all files. Just like doing:

        git grep someword

    How do I now use the IDE to search all the files.. in all of time? e.g. I remember that the code once had a certain string somewhere, but it seems to have been deleted. How do I find that?
    With git it's a single command.

  24. Re:IDEs by dkf · · Score: 2, Interesting

    Eclipse might be better than VS, but I've never been able to get it to run fast enough to be usable.

    I used to have a lot of problems with that, and then I moved it to a machine with more memory and the problems went away. IOW, it's a bloaty hog but otherwise OK.

    --
    "Little does he know, but there is no 'I' in 'Idiot'!"
  25. Re:IDEs by fredrik70 · · Score: 2, Interesting

    hear, hear, well, think Eclipse is alright, decent solid IDE once you get to know it. Jetbrains IntelliJ IDEA though rocks everything, best IDE ever.
    Coming back to VS, the best part with it is that you can install the Jetbrains Resharper, which makes VS behave (almost) like IntelliJ!!

    --
    if (!signature) { throw std::runtime_error("No sig!"); }
  26. Re:IDEs by moonbender · · Score: 2, Informative

    I don't know about "just opening it", but you can simply select Import -- Existing Project into Workspace and that's that. This has never been an issue for me with all kinds of projects (some of them rather large). A workspace is just a set of projects; I think many IDEs have a concept like that. If you don't want to bother with it, you can simply have one workspace for all projects with no real downside, that's what I do at home.

    That said, setting up the development environment for a legacy project can be anything but mundane. You need to have all the dependencies available, deal with version changes, have the compiler settings in place. Project files help a lot with that.

    --
    Switch back to Slashdot's D1 system.
  27. Re: new major version of Perl is now available. by jonadab · · Score: 2, Insightful

    > since Greek and Latin aren't valid Perl

    Well, there is Lingua::Romana::Perligata. Predictably, we have Damian to blame for that.

    --
    Cut that out, or I will ship you to Norilsk in a box.
  28. Re:Perl 5.12? by chromatic · · Score: 2, Interesting

    Perl 6 was also originally supposed to give us a pseudocode that would be shared with other languages.

    Parrot? It's out. It works.