Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. General talk
  3. The Lounge
  4. Google Code Jam 2018 stopped supporting Qt...
Forum Updated to NodeBB v4.3 + New Features

Google Code Jam 2018 stopped supporting Qt...

Scheduled Pinned Locked Moved The Lounge
4 Posts 4 Posters 1.7k Views 5 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • JKSHJ Offline
    JKSHJ Offline
    JKSH
    Moderators
    wrote on last edited by JKSH
    #1

    Has anyone taken part in Google Code Jam before? I have, using Qt and C++ to implement my solutions.

    Google is taking a new approach this year: Instead of building and running your code on our own PC, participants submit code to be compiled/interpreted directly on Google's servers. This means that Qt can no longer be used.

    This was a stark reminder of much value Qt adds to C++. For years, I've been taking functions like QString::split() and QString::endsWith() for granted. This morning, when I tried to solve Google Code Jam puzzles using C++ STL, I found myself handicapped: A standard split() function had been a mere proposal since 2013; ends_with() is becoming official, but only around the year 2020.

    Anyway, I've started implementing my solutions using JavaScript (Node.js). So far so good! I'm glad I got plenty of JavaScript practice through QML (and some outside web programming).

    Just wanted to say: Long live Qt!

    P.S. If anyone is interested in the contest, the Qualification Round for 2018 is still open for over 13 hours -- that's enough time to score enough points to qualify for the actual contest. Sample code exists for all supported languages.

    Qt Doc Search for browsers: forum.qt.io/topic/35616/web-browser-extension-for-improved-doc-searches

    kshegunovK 1 Reply Last reply
    6
    • JKSHJ JKSH

      Has anyone taken part in Google Code Jam before? I have, using Qt and C++ to implement my solutions.

      Google is taking a new approach this year: Instead of building and running your code on our own PC, participants submit code to be compiled/interpreted directly on Google's servers. This means that Qt can no longer be used.

      This was a stark reminder of much value Qt adds to C++. For years, I've been taking functions like QString::split() and QString::endsWith() for granted. This morning, when I tried to solve Google Code Jam puzzles using C++ STL, I found myself handicapped: A standard split() function had been a mere proposal since 2013; ends_with() is becoming official, but only around the year 2020.

      Anyway, I've started implementing my solutions using JavaScript (Node.js). So far so good! I'm glad I got plenty of JavaScript practice through QML (and some outside web programming).

      Just wanted to say: Long live Qt!

      P.S. If anyone is interested in the contest, the Qualification Round for 2018 is still open for over 13 hours -- that's enough time to score enough points to qualify for the actual contest. Sample code exists for all supported languages.

      kshegunovK Offline
      kshegunovK Offline
      kshegunov
      Moderators
      wrote on last edited by kshegunov
      #2

      @JKSH said in Google Code Jam 2018 stopped supporting Qt... :-(:

      This means that Qt can no longer be used.

      As you mentioned, this is a loss for the event itself.

      Just wanted to say: Long live Qt!

      I'm not religious, but here it fits perfectly: amen, brother!

      PS.

      An observation: the tasks seem to focus on NP-hard to NP-complete problems

      Read and abide by the Qt Code of Conduct

      1 Reply Last reply
      2
      • A Offline
        A Offline
        ambershark
        wrote on last edited by
        #3

        Yea I hate using just raw STL now. I haven't gotten to use Qt in the last 3 years on my official work. It's pretty annoying to go back to std::string that's for sure.

        My L-GPL'd C++ Logger github.com/ambershark-mike/sharklog

        1 Reply Last reply
        2
        • mrjjM Offline
          mrjjM Offline
          mrjj
          Lifetime Qt Champion
          wrote on last edited by
          #4

          Yeah after sitting in the GUI part all day and come back to the embedded ARM.
          std::string is just such a B! compared to QString. ;)

          1 Reply Last reply
          3

          • Login

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Users
          • Groups
          • Search
          • Get Qt Extensions
          • Unsolved