pjmq

It was pretty cool to hear the broadcast reference this. 100% think it should be more concise and have a greater depth of personality.

Rad.FM maker here. Thanks for at least trying it. A) the web app is still in alpha. B) Rad needs your location to make what it says to the listener relevant to where you are and your current time. Also, news & weather need your location.

Thanks for the feedback though, I'll delay the location request to later in the flow + add a popover which explains why it's needed when we get to beta.

Pretty much everyone who was not a sub-postmaster involved in the Horizon mess needs to be sentenced. The sheer malice on display here is inescapable.

These people killed people and hid their mess. Plain and simple.

Are you looking to get a job with your framework of choice? Or are you looking to build stuff for yourself?

If it's the former: React

If it's the latter: Svelte (Especially with Svelte 5 around the corner)

Congrats on making it to the front page of The Verge! https://www.theverge.com/2023/10/24/23930133/paclear-c-yello...

Hey there! Just FYI your APIs are reporting address not found: Error: getaddrinfo ENOTFOUND app.fluxon.dev

Have they alluded to what they're using for that voice? It's Bark/ElevenLabs levels of good. Please god, let them release this voice model at current pricing....

I've been a paying subscriber to Kagi for over a year and I'm sad to say it just gets in my way and I often find myself just wishing I was using Google.

I've kept it thus far because I believe in the mission but man... I get why other promising search engines have fallen to Google.

If you follow Youtubers like Jim Browning that tackle this sort of scam-based cybercrime operations then this will come as absolutely no surprise to you.

I just want to write Svelte and get native apps out the other end. I know we have SvelteNative but that's not great and is a big abstraction. React here is a bit of a bummer i'm not going to lie.

Recently re-discovered him due to a Business Wars podcast episode on him. The dude deserves his own movie. Not a nice way to go but he'll surely be remembered.

Human curation does not scale or cater for individual tastes sadly!

Apple Music has so few 3rd party apps in fairness. Spotify has basically shafted the developer community who built their platform and fan base for them (Soundwave, Greenroom, and all the other services that have been built on top of them that Spotify have cannibalised and killed) so they deserve a mass migration even of 3rd parties. Here's hoping this is it.

I have absolutely 0 problems with them forking Rust off under a new moniker but "Crab lang" is an abomination of a name.

To my eye, this makes vanilla JS more like React rather than making vanilla JS reactive. I'm basically looking for an even lighter Svelte if I can get it. Maybe this just isn't for me!

With all the love in the world, that's probably down to the sunk-cost fallacy. You've invested a chunk of time into understanding the idiosyncrasies and non-standard methodologies that React has pushed at you over the years.

Svelte's pattern for data binding (with the exception of the $: reactivity) is exceptionally idiomatic and as close to standard web as 2-way reactivity will ever be. Easy to get to grips with as a newbie and a breath of fresh air for someone with years of fe experience under their belt.

Svelte embodies the KISS principle and long may that last.

The more I see it the more I'm certain that Rich and the team screwed the pooch with the whole '+page.server.ts' stuff.

They should really be using the existing <script context="module"> syntax to have a context="server" portion instead of splitting the file out.

Heck, it could even just be an import for a server.ts file in the same root directory if people really liked the +whatever style of having the server code separated.

It feels especially redundant when you're building a static app or SPA. The sort of overly opinionated nonsense that put me off React and on to Svelte in the first place.

I've decided against making the switch to SvelteKit and instead rely on good old Svelte because I can have a /pages/Whatever.svelte encapsulates the structure and core logic of each view/page. It's clean, it's HTML-like, it works and more importantly, I can immediately wrap my head around it when coming back to the project after a period away.

I deeply love the guy, but I really think Rich should walk back this decision and default to the "whats the cleanest pattern that people can easily wrap their head around" approach.

His comp should have been negative the salaries of those he over-hired and subsequently had to fire. Like that comp is roughly 1000 employees worth...

BTW you can also follow along on Reddit if you'd prefer doing it that way -> https://www.reddit.com/r/RadiantApp/

If you head over to our Discord which you can find here -> https://discord.gg/4YgkhAgfJ5 and it'll be announced there :)

You can also follow updates on Reddit -> https://www.reddit.com/r/RadiantApp/

This is absolutely on the roadmap!

Thank you so much to everyone for the points and really nice words of encouragement. Real shot in the arm and means a great deal.

This looks (or sounds, rather) exceptional.

Long term I'm going to go with something self-hosted using Tortoise TTS etc but I also want to break away from Google's Cloud Speech as that can cost me hundreds a month when the user base has a peak so this looks great, thank you!

oh wow thanks!

Is there like a link to a JackFM broadcast on Youtube or something? I'm super curious to learn what their formatting was like and maybe use it as a case study!

Short-form podcasts are being looked at as sort of a syndicated content. Like there'd be a list of interesting shows like 'The Daily', 'Business Wars Daily' etc that you could subscribe to and have injected into the stream when appropriate!

Obviously, I'd expand this with more full-fledged shows if people liked the format. You could even configure it with "I listen to my podcasts in the morning / after noon / when I'm driving" etc in settings and Rad would factor that in when choosing when to play em.

It was a native iOS app originally but now it's pure web (straight Svelte SPA, no UI framework) with native plugins.

I did it because I don't have the time to maintain for 3 platforms in parallel without one falling behind and I'm not a fan of React native personally. I spent a good chunk of time testing with much older hardware as a target to make sure performance wouldn't be a noticeable distraction for users and I'm happy with how it turned out :)

If you want something like this for a shop or store etc, ping me via rad@getradiant.app, we might be able to build something cool to fit that need (I've been toying with this idea for a while so it'd be nice to have a first user for it)

Radiant launched with a paid subscription model (like a dollar a month) Spotify shut it down, took away our API creds and left us in the lurch. Had to set it up again, with the subscription removed. That hurt because we had a good number of paying customers at that point.

But we moved to be compliant with their guidelines after that and I carried it on as a labour of love.

Now I'm actively looking at moving away from Spotify and on to my own data set and APIs that can match what Spotify has. I've built something like it before using the Cover Art Archive for the artwork, Acoustic/MusicBrainz for the metadata and custom logic built atop so I know it's possible.

Once I've done that I can start looking for sponsors.

There is always the possibility that if the userbase really scales up, Spotify would grant me a commercial license and allow me to commoditise the platform but I don't need that to happen really.

Rad literally says this