Skip to content
TheChatArchiveThe Chat Archive
Claudeclaude-opus-4-20250514-thinking-16k· AnthropicHugging Face LMArena Human Preference 140K

is there an easier oneliner to get 3 computed properties of current time? (current hour,…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with o3-2025-04-16’s answer.
  1. User

    is there an easier oneliner to get 3 computed properties of current time? (current hour, minute, and second). Here's what i've got now: const seconds = computed(() => new Date().getSeconds()) const minutes = computed(() => new Date().getMinutes()) const hours = computed(() => new Date.getHours())

  2. Claude Assistant

    You can create a single computed property that returns an object with all three values:

    const time = computed(() => {
      const d = new Date()
      return { hours: d.getHours(), minutes: d.getMinutes(), seconds: d.getSeconds() }
    })
    

    Then access them as time.value.hours, time.value.minutes, and time.value.seconds.

    If you want individual computed refs, you could also do:

    const { hours, minutes, seconds } = (() => {
      const time = computed(() => new Date())
      return {
        hours: computed(() => time.value.getHours()),
        minutes: computed(() => time.value.getMinutes()),
        seconds: computed(() => time.value.getSeconds())
      }
    })()
    

    The first approach is more efficient since it creates only one Date object per update instead of three.

    Also, note that your original code has a typo: new Date.getHours() should be new Date().getHours().

  3. User

    How do i make an arrow out of a div?

  4. Claude Assistant

    You can create arrows using CSS borders. Here are the most common approaches:

    Basic arrow using borders:

    .arrow-right {
      width: 0;
      height: 0;
      border-top: 10px solid transparent;
      border-bottom: 10px solid transparent;
      border-left: 15px solid black;
    }
    
    .arrow-left {
      width: 0;
      height: 0;
      border-top: 10px solid transparent;
      border-bottom: 10px solid transparent;
      border-right: 15px solid black;
    }
    
    .arrow-up {
      width: 0;
      height: 0;
      border-left: 10px solid transparent;
      border-right: 10px solid transparent;
      border-bottom: 15px solid black;
    }
    
    .arrow-down {
      width: 0;
      height: 0;
      border-left: 10px solid transparent;
      border-right: 10px solid transparent;
      border-top: 15px solid black;
    }
    

    Arrow with rotation (chevron style):

    .chevron-right {
      width: 10px;
      height: 10px;
      border-top: 2px solid black;
      border-right: 2px solid black;
      transform: rotate(45deg);
    }
    
    .chevron-left {
      width: 10px;
      height: 10px;
      border-top: 2px solid black;
      border-left: 2px solid black;
      transform: rotate(-45deg);
    }
    

    Arrow with pseudo-element (for arrows with tails):

    .arrow-with-tail {
      position: relative;
      width: 50px;
      height: 2px;
      background: black;
    }
    
    .arrow-with-tail::after {
      content: '';
      position: absolute;
      right: 0;
      top: -4px;
      width: 0;
      height: 0;
      border-top: 5px solid transparent;
      border-bottom: 5px solid transparent;
      border-left: 10px solid black;
    }
    

    The border technique works by setting the element's width and height to 0, then using transparent borders on three sides and a colored border on the fourth side to create the triangle shape.

  5. User

    Is there a way to set a border width to a percentage of a container div?

  6. Claude Assistant

    No, the CSS border-width property doesn't accept percentage values - it only accepts fixed units like px, em, rem, etc.

    However, here are some workarounds to achieve a percentage-based border effect:

    1. Using pseudo-elements:

    .container {
      position: relative;
      width: 200px;
      height: 100px;
      background: white;
    }
    
    .container::before {
      content: '';
      position: absolute;
      top: 0;
      left: 0;
      right: 0;
      bottom: 0;
      border: 5% solid black; /* This won't work */
      /* Instead, use padding or margin */
      padding: 5%; /* This creates the border effect */
      background: black;
    }
    
    .container::after {
      content: '';
      position: absolute;
      top: 5%;
      left: 5%;
      right: 5%;
      bottom: 5%;
      background: white;
    }
    

    2. Using box-shadow inset:

    .container {
      width: 200px;
      height: 100px;
      background: white;
      box-shadow: inset 0 0 0 calc(5% * 1vw) black;
      /* Or use min() for responsive sizing */
      box-shadow: inset 0 0 0 min(10px, 5vw) black;
    }
    

    3. Using outline with calc() (limited browser support for percentage calc):

    .container {
      width: 200px;
      height: 100px;
      outline: min(10px, 5vw) solid black;
      outline-offset: -min(10px, 5vw);
    }
    

    4. Using a wrapper div:

    .border-wrapper {
      background: black;
      padding: 5%; /* This creates the border */
    }
    
    .content {
      background: white;
      height: 100%;
    }
    

    The wrapper div approach is often the most reliable and cross-browser compatible solution for percentage-based borders.

  7. User

    about the computed date - your previous answer does not update automatically - seconds never change, i assume neither do minutes and hours

  8. Claude Assistant

    You're absolutely right! The computed property won't update automatically because new Date() isn't a reactive dependency. For a clock that updates, you need a timer to trigger reactivity:

    const now = ref(new Date())
    
    // Update the time every second
    setInterval(() => {
      now.value = new Date()
    }, 1000)
    
    // Now these will update automatically
    const seconds = computed(() => now.value.getSeconds())
    const minutes = computed(() => now.value.getMinutes())
    const hours = computed(() => now.value.getHours())
    

    Or as a cleaner solution with cleanup:

    const useTime = () => {
      const now = ref(new Date())
      
      const intervalId = setInterval(() => {
        now.value = new Date()
      }, 1000)
      
      onUnmounted(() => {
        clearInterval(intervalId)
      })
      
      return {
        hours: computed(() => now.value.getHours()),
        minutes: computed(() => now.value.getMinutes()),
        seconds: computed(() => now.value.getSeconds())
      }
    }
    
    // Usage
    const { hours, minutes, seconds } = useTime()
    

    The key is that Vue needs a reactive value (now.value) that changes to trigger the computed properties to recalculate.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.