Remove explanatory comment

That no longer vitally pertains.

1 files changed, 0 insertions, 14 deletions

diff --git a/ui/lib/store/channels.svelte.js b/ui/lib/store/channels.svelte.js
index 86d924e..31e9098 100644
--- a/ui/lib/store/channels.svelte.js
+++ b/ui/lib/store/channels.svelte.js
@@ -2,20 +2,6 @@ import { DateTime } from 'luxon';
 import { get } from 'svelte/store'
 import { STORE_KEY_CHANNELS_DATA, EPOCH_STRING } from '$lib/constants';
 
-// # Why we don't have a Channel object
-//
-// For reasons unclear to me, a straight up class definition with a constructor
-// doesn't seem to work, reactively. So we resort to this.
-//
-// Owen suggests that this sentence in the Svelte docs should make the reason
-// clear:
-//
-// > If $state is used with an array or a simple object, the result is a deeply
-// > reactive state proxy.
-//
-// Emphasis on "simple object".
-//
-// --Kit
 
 export class Channels {
   channels = $state([]);