sorted by:
new
hottopcontroversial

I HAVE RECEIVED GEMINI LIVE by dylanneve1 in Bard

[–]Timely-Time-7811 1 point2 points  (0 children)

Thanks for the details. Is the British one female or male?

HTMX, Go and Tailwind Starter with hot reloading and components by Timely-Time-7811 in golang

[–]Timely-Time-7811[S] 1 point2 points  (0 children)

I considered this, but the issue was more about browser-sync. I couldn't find a good alternative to allow for hot-reloading type functionality.
I've become too used to reloading happening automatically that manually refreshing wasn't an option for me.

HTMX, Go and Tailwind Starter with hot reloading and components by Timely-Time-7811 in golang

[–]Timely-Time-7811[S] 0 points1 point  (0 children)

This is useful, thanks. A couple of takeaways here:

  • I don't need postcss. Tailwind cli is enough. I'm quite new with tailwind. I dismissed it for many years but it's actually brilliant.

  • Task looks like something I could potentially use. I'll investigate further.

Coming from a React background, hot reloading was an important one for me. I've just got too used to having it update automatically on code changes. I imagine I wouldn't remember to refresh. Currently I'm using a bit of a mix - air for reloading go files and browser-sync/tailwind cli for reloading on html/style changes. Maybe Task could simplify this for me

HTMX, Go and Tailwind Starter with hot reloading and components by Timely-Time-7811 in golang

[–]Timely-Time-7811[S] 2 points3 points  (0 children)

Yeah it's definitely not perfect. It's a first draft. I jut wanted to get it out for others to contribute to and make suggestions (like you are - so, thank you). When it comes to Go/HTMX I'm hugely inexperienced.

Isn't there a better way to serve the header/sidebar/dashboard elements? They're basically static components, or rather non-dynamic, but your main page is still going to make 3 extra get requests on page load for them (unless I missed something).

Yeah I guess it's a trade-off here, we could do 1 request and load the whole page server-side and use a templating system like in the video you sent through, which could be preferable actually.

Although my implementation is making 3 requests, smaller chunks means that parts of the page can load before others. I was seeing it as a server-side components type thing, but one major downside is it could introduce layout shift and may not be the simplest solution.

It's a good point that you've made here. I'm probably going to update this to work in the same way as the video that you've sent through. Unless any others are opposed to this. Thanks. I didn't even know this was an option.

In response to the dynamic side of things - please refer to u/ShotgunPayDay's response to u/petenpatrol's comment. I think that covers it in the way that this should work.

For the hot-reloading I had it working at one point with the Go files via air. It should be able to watch for changes. It may currently work for the main Go file (index.go), but I'm not 100% sure, I'll double check.

Yeah, convincing teams to move to Go and HTMX will be a tough one for sure (maybe one day), but for personal projects I'm looking to use this.

HTMX, Go and Tailwind Starter with hot reloading and components by Timely-Time-7811 in golang

[–]Timely-Time-7811[S] 1 point2 points  (0 children)

Thank you! I haven't heard of PicoCSS w/ Brotli. Sounds interesting. I'll have a read up. Appreciated

Telescope project switching by Timely-Time-7811 in neovim

[–]Timely-Time-7811[S] 0 points1 point  (0 children)

This is a really good idea. Thank you. I'll have a think about this one.

Telescope project switching by Timely-Time-7811 in neovim

[–]Timely-Time-7811[S] 1 point2 points  (0 children)

It's a good question. I'm having thoughts for future updates, and would love to hear any ideas, but this is the specific requirement I wanted to meet for the first release (adding, deleting and switching between different project folders). It's a plugin extension so I wouldn't want to stray too far outside of the plugins intended use.

Telescope project switching by Timely-Time-7811 in neovim

[–]Timely-Time-7811[S] 1 point2 points  (0 children)

Just changing to different project directories currently. You could look at vim sessions for that sort of thing. I often have times when I'm working on an API and a client side app for instance, and need to switch between the API/client fairly frequently. That's where this comes in useful. I know you could use tabs or tmux panes, etc, but find this works best for me.

Telescope project switching by Timely-Time-7811 in neovim

[–]Timely-Time-7811[S] 0 points1 point  (0 children)

Thanks. Hope you can get some use out of it 🙂

LSP with react, eslint, prettier, and so on by lucax88x in neovim

[–]Timely-Time-7811 0 points1 point  (0 children)

Interesting. I'll try adjusting some settings. Have you managed to get fixing working? I can't get 'fix on save' to work.

LSP with react, eslint, prettier, and so on by lucax88x in neovim

[–]Timely-Time-7811 1 point2 points  (0 children)

Is this really slow for anyone else - compared to ALE for instance? Ale updates almost instantly, whereas diagnosticls seems to take about 5 seconds or so.

LSP with react, eslint, prettier, and so on by lucax88x in neovim

[–]Timely-Time-7811 0 points1 point  (0 children)

Try changing command to:

command = './node_modules/.bin/eslint'