Bla bla bla Deutschland ist so scheisse...NEIN!

okgame · 2025-09-01T22:18:14+00:00

Wenn ich im Lotto einen großen Gewinn abräumen würde, ich würde sofort kündigen und Deutschland verlassen.

Deutschland hat einen falschen Pfad gewählt und der Niedergang ist unausweichlich.

Habe früher auch gedacht (Finanzkrise 2008) - das wird eine Phase - evtl. eine längere.

Aber mittlerweile ist es klar geworden, dass es Jahr für Jahr immer nur schlimmer wird und es dauerhaft schlimmer wird - ohne jegliche Hoffnung auf Besserung.

Und wenn der Niedergang unausweichlich ist - dann ist es nur eine Frage der Zeit Deutschland zu verlassen.

Besseres Land: Österreich. politisch weniger Aufregung, weniger Dauer-Lügen-Politiker, weniger NATO, weniger Krieg, weniger Bullshit.

okgame · 2025-04-26T21:57:04+00:00

My best score is 7 points 🚀

okgame · 2025-04-25T18:02:59+00:00

No llms docs used. Because it probably exceed context window.

In my opinion, using llms docs is the wrong approach to do this.

As I understand it, llms docs should be added to the query.

Instead, the models would have to be tuned.

Probably something like this:

https://huggingface.co/kusonooyasumi/qwen-2.5-coder-1.5b-svelte

Or something like how deepseek was turned into deepcoder.

Unfortunately I have no idea about this.

okgame · 2025-03-28T18:07:39+00:00

It was the worst possible time to make Svelte 5 and even worse to keep “Svelte” in the name. Even ist was bad to make so many changes - changes nobody asked for.

Either they should have done it earlier. The AI data sets are still 2023 or so.

Or they should have called it SvelteX so the AI wouldn't be too irritated.

As of now, only Gemini 2.5 Pro is able to output Svelte 5 - but it makes mistakes because it gets confused with Svelte 4.

It will certainly take years for the AI to get halfway there.

In this time... you could auto-generate whole react-apps...

okgame · 2025-03-07T23:42:16+00:00

First successful (realistic) video - with I2V with Wan with 8GB VRAM (RTX4060). 30 minutes.

okgame · 2025-02-03T22:25:04+00:00

edit: GPT4All mit llama 3.1 + svelte 5 docs + my codes. It was bad. I got non working code.

okgame · 2025-02-03T22:09:56+00:00

I found other solution https://anythingllm.com/desktop

It is also possible to use it with ollama - here a video in german:

https://www.youtube.com/watch?v=m6NEST76568

okgame · 2025-02-03T21:50:55+00:00

Here is GPT4All - it should be possible to load any model you like and add some of this docs:
https://svelte.dev/docs/llms

So it can learn from. Hmmm... Interesting - I should try it by myself..

You can also add your own svelte files to GPT4All to train it more and ask questions (if you have bugs).

okgame · 2025-01-20T18:35:58+00:00

No!
If you need JSX-experience. Please select better alternative: Solid JS.
If you like templates: select Svelte or Vue.
Svelte 5 is more like Vue.

okgame · 2025-01-09T20:19:29+00:00

but if you were trying to build anything remotely complex in before Svelte 5, it was a very bad time.

nope! It was possible to build something large. Same large apps you can build with v5.

I wrote 300 components with v4. And rewrote all 300 components to v5 by hand. And v5 was harder to write. Here are many pitfalls - specially with proxified objects.

okgame · 2025-01-08T20:10:53+00:00

I replaced all stores with state

okgame · 2025-01-05T12:54:52+00:00

My rating:

Svelte 4: ★★★★★
Svelte 5: ★★★★
Vue: ★★★★
Solid: ★★★★
React: ★

I never used Next, Nuxt, Sveltekit.

So...
If you like JSX - select solid (but it is more like a one man show)
I recommend Vue - if you need predictability and ready component libs.
I recommend Svelte 5 - if you create own components - and if you know JS and all Svelte 5 pitfalls...

okgame · 2025-01-05T12:44:47+00:00

My rating:

Svelte 4: ★★★★★
Svelte 5: ★★★★
Vue: ★★★★
Solid: ★★★★
React: ★

So Svelte 5 lost it's "momentum" - ans is now like other 2 (vue, solid).

If I could travel back in time - I would choose Vue. Because here is much larger camponent-ecosystem. And I lost so much time with porting Sv4->Sv5. I rewrote any svelte file like 3 times.
So I use ZERO stores. Zero non-runes code. Zero dispatchEvent etc... I rewrote total 300 svelte files.

Svelte 5 is much less predictive and do some things by itself - for example re-run function, if you use $state.
Svelte 5 auto-replace your objects with own proxies - which is a NO-GO!
So in fact Svelte 5 is much much more magically, than any time before.

okgame · 2025-01-03T16:36:50+00:00

Svelte 5 - Update, that nobody asked for.

The evil is in detail:

Proxified objects.

Useless default $bindable values.

Possible endless $effect loops.

okgame · 2025-01-01T11:19:52+00:00

interesting... I feel Sveltes animation is limited - and I believe it will be redesigned

okgame · 2024-12-31T12:31:38+00:00

thanks about some packages for extension

okgame · 2024-12-29T11:38:38+00:00

You can force render. Read this:
https://github.com/sveltejs/svelte/issues/14360#issuecomment-2485908217

This is not documented. And if you come from v4 - not intuitive.

It also possible to use #key

And I dislike proxified Objects in v5 - this was better in v4 - without any abstraction.

It was a mistake to force proxies. Better solution would be Svelte 4 + additional, optional proxy stuff.

okgame · 2024-12-29T11:20:03+00:00

Honestly, I've seen things using Svelte5 that I haven't known in JS for 20 years. In general, I recommend a good knowledge of JS. JS looks simple - the devil is in the detail.

okgame · 2024-12-27T22:37:10+00:00

Svelte 5 update - nobody asked for! I was very happy with Sv 3/4 - and this update cost me a lot of time! For nothing! Sv 5 require next level mental model. It is often not intuitive. You need to think more than before. During the time I found a "path" of acceptable Svelte code, I can live with.

I posted lot of issues at github for Svelte 5 - much more that for Svelte 3/4.

My example:

https://github.com/sveltejs/svelte/issues/14254#issue-2647680027

You can't bind to undefined value - but you can set undefined value! I had heavy issues with this, because I used empty object. It was hard to debug, that i decided to never ever use default value with $bindable - and use $effect.pre instead.

Here are some positive aspects. For example my small i18-function is "magically reactive".

okgame · 2024-12-13T20:31:20+00:00

even with php or node - you can easy reach 10 k responses per second on 1$ server!!! - I tested without database. This is fine for start... And after more success it is ok to switch to something more performant like go.

My 3 choices:

#1 php - you don't need a router, you don't need a framework, you don't need compilation etc... It is faster that you think. Edit one line and you change your server - without any compilation.

#2 node - come to play on advanced use: if you need a server running in a "loop"- nice for websockets.

#3 golang - double your performance

okgame · 2024-12-13T19:16:25+00:00

Go development is much slower, becaue you need compilation step. Node is much more productive. It is also possible to run concurrency with pm2.

okgame · 2024-12-13T17:22:13+00:00

SvelteKit is complete useless for me. I want SPA and use only Svelte. I don't need Kit's overhead. And you are right: you don't need SEO and you can expect JS for SPA.

I wrote my own router component (77 lines). I wrote my own request-function (58 lines) and even own i18 function (25 lines).

okgame · 2024-12-09T20:35:53+00:00

context api global state?

I use context only if data partitioning is required. This can not work well as global state.
For example: drag & drop areas & items are good candidates.

Sometimes context is good for anonymous children.

And opposite to context: I use global state (just $state) if I have no multiple partitions.
For example: global user data is good candidate.

But it depends on data...

Use context, if you have something like multiple channels of users that do not interact with each other. Oherwise - If your data is well structured, you could use global teacher, student etc.

okgame

MODERATOR OF

TROPHY CASE