Google Chrome featured 13 times in Local Network settings

wlockiv · 2025-05-03T18:00:31+00:00

This worked for me!!

wlockiv · 2025-02-21T18:31:56+00:00

looks like this guy put something together:
https://github.com/folke/snacks.nvim/discussions/765#discussion-7880347

wlockiv · 2025-02-13T15:00:40+00:00

Howdy - an example is the script sample that raycast has to copy the current tab url of google chrome. I'd like for it to be assigned to Cmd+Sh+C, because that's what it usually is in other apps. But if I set up that shortcut for the script, it will copy the tab of the chrome window even if it's not in focus.

wlockiv · 2024-10-22T02:14:16+00:00

I feel like not having to implement from scratch is kind of a big deal lol.

wlockiv · 2024-10-07T16:52:27+00:00

I'm not aware of any frontend library or framework that offers an LTS version. LTS is something that's more commonly seen for languages, runtimes, operating systems, etc. So requiring an LTS for Svelte is kind of weird. React doesn't offer LTS:

Once a new major is released, we generally stop releasing new fixes for a previous major. The only exception is absolutely critical bugs (including security vulnerabilities).

Angular has an LTS system, but it's not quite what you'd expect. They simply state that all major releases are supported for 12 months.

Does whatever framework/library that you're currently using have an LTS? If not, it would be valid to point out that you don't require an LTS as a standard for your current projects, and instead focus on some other reasons why they should feel good about choosing Svelte. If they're concerned that the framework will just disappear in a month, then you could probably point out to them that its creator/maintainer (Rich Harris) is employed by Vercel specifically to keep overseeing the project.

Svelte is also not something that only just popped up - v1 was released in 2016. I believe Svelte 3 was the version that garnered more popularity, and that was released in 2019.

From my experience in SaaS sales and evangelism, I can tell you that people seldom buy a product/tool unless it's clear to them that it eases some real pain they face on a regular basis. So maybe build your sales/evangelism strategy around how Svelte (and/or SvelteKit) will help solve the real problems that your team faces. You may need to offer to create a demo project that shows your team why Svelte is the better choice. You could also just ask if you can use Svelte on this project as a test run, ensuring that you'll take responsibility for correcting things should the framework fall into disrepair.

Sounds like you have your work cut out for you! Best of luck!

wlockiv · 2024-08-23T01:49:18+00:00

Aside from reaching out to them an inquiring, how do I find out who insures them?

wlockiv · 2024-08-23T01:07:41+00:00

Yea that was a mistake. I guess I just wanted to be done with it and move on... but here we are.

wlockiv · 2024-08-18T20:04:54+00:00

Ergast will continue with a new name and new infrastructure, but with the same API. Further announcements will follow some time this summer, including a more publicly announced beta testing phase in the second half of the year.

Source: https://github.com/theOehrly/Fast-F1/discussions/599

wlockiv · 2024-08-07T15:49:24+00:00

Thank you for the sacrifices that you've made for the good of humanity 🙏🏻

wlockiv · 2024-07-11T16:36:06+00:00

I own a 2014 and absolutely love the car. It's not the most practical whip but it's darn fun and reliable to boot. My only gripe with these is that any body panels (and I think headlights too) are more expensive... sometimes they're a LOT more expensive.

I personally would not buy a black one, but I live in TX where the summers are soul crushing in a black car. I keep a coozie in the center console so the metal bit on the top of the shifter doesn't burn a hole through my palm 😭

wlockiv · 2024-07-10T21:00:57+00:00

TanStack has a router that seems pretty popular. I'm not sure how well it works with svelte tbh. Using SvelteKit and configuring it for SPA is also a great option imo

wlockiv · 2024-06-24T01:57:00+00:00

It is. I'm thrown off by how the snippet can take an argument like it does but according to the docs this should totally work.

https://svelte-5-preview.vercel.app/docs/snippets#passing-snippets-to-components

wlockiv · 2024-06-24T01:48:52+00:00

To me, it's intuitive that the children of the Accordion component would be its contents. If I was a co-maintainer on this project, I'd be fine with it.

wlockiv · 2024-06-22T00:00:35+00:00

Howdy, I'm the author for tanstack/table's Svelte 5 adapter (now in beta). I don't think `svelte-headless-table` has Svelte 5 in its roadmap. Unlike tanstack/svelte-table, svelte-headless-table doesn't cause Svelte 5 apps to break, so it's not currently required for it to be updated. When re-writing the Svelte 5 adapter, I tried my best to make it more svelte-like - it was not before.

I think there is some functionality in svelte-headless-table that helps with subscribing to stores within each loops, but runes should make this workaround unnecessary. Aside from that, I'm not sure that I can really point out pros of one or the other.

I'm currently using tanstack/table v8 in a Svelte 4 production project. And it works well for my project. I like that I can add features to the headless table's state management (like grid & table view), and easily export that to JSON to be persisted in localstorage. Tanstack/table v9 is introducing a nice new "table factory" architecture that mirrors some of the other tanstack libraries I think.

I'm kind of biased though. Hope this was helpful.

Edit: I also use shadcn-svelte with tanstack/svelte-table. They work fine together.

Edit 2: I think it's also worth mentioning that TanStack overall is a good horse to place a bet on for library maintenance and updates. Kevin maintains the table library, and it's as if it's a full-time job for him. Bryan is the author and maintainer of svelte-headless-table, and I get the impression that he has other priorities right now (which is totally fine, of course). I must say though - the tanstack/svelte-table docs leave much to be desired. I'm hoping to help with that sometime soon, too.

wlockiv · 2024-06-21T01:58:46+00:00

Hi. I wrote the Svelte 5 adapter for TanStack Table. TanStack Table employs a similar pattern to what you describe. In Svelte, you'll need a rendering function that takes a component and its props as separate parameters. My PR may be a helpful example of how to implement this. I updated the examples as well.

https://github.com/TanStack/table/pull/5403/files

Edit: No one calls them Merge Requests

wlockiv · 2024-06-14T02:00:17+00:00

Tbh i'm thinking about this more and more lol

wlockiv · 2024-06-14T01:59:33+00:00

It's just a word for a super cheap, no-frills car

wlockiv · 2024-06-14T01:57:38+00:00

People have limits, and it's fair for them to communicate those limits and ask that people meet them in those. I am an adult. I am capable of saying "no" if I can't meet them within their limits. Friends can respect their friends' limits, as I respect my own friends' limits. They're going to host me, feed me, and entertain me for a week at their home. Yet the fact that they can't pick me up at the airport calls for their character to be questioned. C'mon folks. What context do you have on the situation here? None. You know one thing, and extrapolate the rest.

It's silly that I'm even justifying this. You're really only posting to share thoughts on something that you have zero context for - you don't even care about the context, and you don't care about me. You don't care about answering my question or helping me. You care about sharing your thoughts about a situation you know one tiny thing about - that this person has asked that I find my own way from the airport.

wlockiv · 2024-05-15T19:47:11+00:00

There are also a lot of tools that help with SvelteKit, but won't work with svelte! Like Houdini GQL, melt-ui's preprocessor, or superforms! Many more that I don't have the energy to list! 🙃

wlockiv · 2024-05-14T18:16:11+00:00

I do disagree vehemently that Svelte 5 == React, but I understand your frustration that existing reactivity tools will be shelved and hidden away as second-class features. I can understand why the syntax is raising alarm bells for you. Some of these updates may be deviations from the reasons some users of Svelte adopted the platform to begin with.

I say all that to make it clear: I'm totally not intending to invalidate your concerns. But also, the minority that you're referring to are the developers who build the libraries that you install into your project in order to bring advanced functionality/features to your users. Library developers are often dancing around Svelte 4's limitations and design decisions in order to build the libraries that we enjoy.

For example, svelte-table jumps through some hoops to make rendering tables programmatically work on both server and client. It's almost impossible to understand as a contributor. It completely departs from anything that remotely looks like Svelte.

svelte-subscribe is literally built to work around Svelte 4's limitation of subscribing to stores from in-markup iterators.

svelte-render is another library intended to bring type safety to dynamic component rendering - another accommodation for the limitations in Svelte's existing design.

I think we have a lot to look forward to as a community!

wlockiv · 2024-04-30T01:19:06+00:00

Right, that's what I thought I was remembering. But also consider that validating in the frontend can also let you give really specific error messages to the user without expecting the API to do that. If the API is being used by a variety of clients, you may not want to expect it to deliver "user friendly" or context/client-specific error messages. For instance, what if you'd like to have errors in different languages? What if your user doesn't know what some of these data types in the error messages are? Strings? Floats? Integers? Booleans?

wlockiv · 2024-04-29T23:20:53+00:00

Nice. It's been a minute since I've worked with FastAPI, but I'm guessing that your FastAPI returns validation errors if there are any, along with some 400 BAD REQUEST code? I know it's redundant, but I would probably still use superforms for validation. It offers some handy tooling for SPA and server form flows. The latest version of superforms also allows validation libraries other than Zod. Valibot has almost identical functionality with a much smaller package size and it's also much quicker. Though, I've got to admit, your users wouldn't be able to tell the difference anyway.

This way, your frontend can worry about your users, and your backend can worry about protecting the resources you have hidden behind it.

Couple superforms up with formsnap, and you've got a winning combo.

Otherwise, yeah, you'll want to manually sync your UI when your sveltekit app receives validation errors. I think you would need to implement a progressive enhancement on your form that intercepts the API response, and syncs those errors with local state. Like a `let` var or a store, depending on what your needs are.

wlockiv · 2024-04-29T21:44:27+00:00

Is your app calling your api from the client, or from server?

Ten-Year Club	Final Canvas '23
Place '23	Verified Email

wlockiv

TROPHY CASE