Pavel Lang
@langpavel.bsky.social
Really great talk! I enjoyed the demo a lot!
January 28, 2026 at 6:41 PM
Really great talk! I enjoyed the demo a lot!
What a weird. Did you ask HTML and ECMA262?
January 19, 2026 at 11:04 PM
What a weird. Did you ask HTML and ECMA262?
Part two is having all the previous puzzles done. Leaderboard may be late by few minutes.
December 12, 2025 at 7:27 PM
Part two is having all the previous puzzles done. Leaderboard may be late by few minutes.
Try at first to filter out obvious edge cases. You will be surprised ;-)
December 12, 2025 at 9:40 AM
Try at first to filter out obvious edge cases. You will be surprised ;-)
Runes are compiler hints, fake functions replaced at compile time.
December 1, 2025 at 2:40 PM
Runes are compiler hints, fake functions replaced at compile time.
It's not about Java or any OOP.
It's about factory function.
It's perfectly functional ;-)
It's about factory function.
It's perfectly functional ;-)
December 1, 2025 at 2:38 PM
It's not about Java or any OOP.
It's about factory function.
It's perfectly functional ;-)
It's about factory function.
It's perfectly functional ;-)
```
const {createForm} = createFormFactory(...);
const formState = createForm(...);
```
const {createForm} = createFormFactory(...);
const formState = createForm(...);
```
December 1, 2025 at 2:35 PM
```
const {createForm} = createFormFactory(...);
const formState = createForm(...);
```
const {createForm} = createFormFactory(...);
const formState = createForm(...);
```
But runes are not runtime construct. it's a compile time marker. You cannot create your own runes without modifying the compiler. So state or store is a better word for what your function returns.
December 1, 2025 at 2:30 PM
But runes are not runtime construct. it's a compile time marker. You cannot create your own runes without modifying the compiler. So state or store is a better word for what your function returns.
Yeah, but in large projects with many people interested there is always one who doesn't care and actually it's easy to spot this bad pattern early I guess
November 3, 2025 at 11:23 PM
Yeah, but in large projects with many people interested there is always one who doesn't care and actually it's easy to spot this bad pattern early I guess
This is actually a good thing. Mixing server->client->server flow is bad thing IMO
November 3, 2025 at 7:13 PM
This is actually a good thing. Mixing server->client->server flow is bad thing IMO
And isolation is clearly declared with .remote midfix.
A huge bonus is API design with schema validation.
IMHO great design
A huge bonus is API design with schema validation.
IMHO great design
November 3, 2025 at 7:08 PM
And isolation is clearly declared with .remote midfix.
A huge bonus is API design with schema validation.
IMHO great design
A huge bonus is API design with schema validation.
IMHO great design
Derived stores can be really madness. Every structure needs vision and the right source of thought.
No framework can protect you from doing things in the wrong way.
No framework can protect you from doing things in the wrong way.
October 23, 2025 at 12:00 AM
Derived stores can be really madness. Every structure needs vision and the right source of thought.
No framework can protect you from doing things in the wrong way.
No framework can protect you from doing things in the wrong way.
You never loss with gathering experience ;-)
October 12, 2025 at 2:54 AM
You never loss with gathering experience ;-)
XML have misery with attribute or value, forever because this two overlaps on the way of interpreting.
JSON is simply evolution of possibilities of JavaScript. XML is dead on the web, SGML evolved to HTML and XHTML was rejected.
Web is mostly only the presentation layer. Internet is this for many.
JSON is simply evolution of possibilities of JavaScript. XML is dead on the web, SGML evolved to HTML and XHTML was rejected.
Web is mostly only the presentation layer. Internet is this for many.
October 12, 2025 at 2:50 AM
XML have misery with attribute or value, forever because this two overlaps on the way of interpreting.
JSON is simply evolution of possibilities of JavaScript. XML is dead on the web, SGML evolved to HTML and XHTML was rejected.
Web is mostly only the presentation layer. Internet is this for many.
JSON is simply evolution of possibilities of JavaScript. XML is dead on the web, SGML evolved to HTML and XHTML was rejected.
Web is mostly only the presentation layer. Internet is this for many.
That's simply not true.
I wish it was, but this is not the reality nor the near future.
Hypermedia are about shareable data. Web had that vision at first, you know and you stay, brave.
Today needs are different BTW.
If you have pure data, you can use XML, XSLT+FOP->PDF or HTML..
but XLS? CSV? yay.
I wish it was, but this is not the reality nor the near future.
Hypermedia are about shareable data. Web had that vision at first, you know and you stay, brave.
Today needs are different BTW.
If you have pure data, you can use XML, XSLT+FOP->PDF or HTML..
but XLS? CSV? yay.
October 12, 2025 at 2:35 AM
That's simply not true.
I wish it was, but this is not the reality nor the near future.
Hypermedia are about shareable data. Web had that vision at first, you know and you stay, brave.
Today needs are different BTW.
If you have pure data, you can use XML, XSLT+FOP->PDF or HTML..
but XLS? CSV? yay.
I wish it was, but this is not the reality nor the near future.
Hypermedia are about shareable data. Web had that vision at first, you know and you stay, brave.
Today needs are different BTW.
If you have pure data, you can use XML, XSLT+FOP->PDF or HTML..
but XLS? CSV? yay.
LLMs does not have soul, but soul is inprinted. Sure? Or it's about some unexpected factor?
October 12, 2025 at 2:17 AM
LLMs does not have soul, but soul is inprinted. Sure? Or it's about some unexpected factor?
It's all about your bravery and risk. When you have hundreds of users, go with. When you have proper E2E tests, go with. Do best for DX.
You may pin the version of Svelte and tooling for sake when something breaks. Do feedback.
Follow your company culture and nature if unsure but play and explore!
You may pin the version of Svelte and tooling for sake when something breaks. Do feedback.
Follow your company culture and nature if unsure but play and explore!
October 12, 2025 at 2:04 AM
It's all about your bravery and risk. When you have hundreds of users, go with. When you have proper E2E tests, go with. Do best for DX.
You may pin the version of Svelte and tooling for sake when something breaks. Do feedback.
Follow your company culture and nature if unsure but play and explore!
You may pin the version of Svelte and tooling for sake when something breaks. Do feedback.
Follow your company culture and nature if unsure but play and explore!
You just trolling me and others IMHO.
I perfectly know what the ideas are about. You just lost the point.
Data and presentation are two different things.
I perfectly know what the ideas are about. You just lost the point.
Data and presentation are two different things.
October 10, 2025 at 7:41 AM
You just trolling me and others IMHO.
I perfectly know what the ideas are about. You just lost the point.
Data and presentation are two different things.
I perfectly know what the ideas are about. You just lost the point.
Data and presentation are two different things.
Content hashing can solve this, sure?
If you don't upgrade packages, don't modify layout or generic packages but your content only, you should benefit from caching even after rebuild, don't you?
BTW are you using HTTPS? Do you properly use ETag, caching headers? If nobody cares, it's nonsense
If you don't upgrade packages, don't modify layout or generic packages but your content only, you should benefit from caching even after rebuild, don't you?
BTW are you using HTTPS? Do you properly use ETag, caching headers? If nobody cares, it's nonsense
October 10, 2025 at 7:31 AM
Content hashing can solve this, sure?
If you don't upgrade packages, don't modify layout or generic packages but your content only, you should benefit from caching even after rebuild, don't you?
BTW are you using HTTPS? Do you properly use ETag, caching headers? If nobody cares, it's nonsense
If you don't upgrade packages, don't modify layout or generic packages but your content only, you should benefit from caching even after rebuild, don't you?
BTW are you using HTTPS? Do you properly use ETag, caching headers? If nobody cares, it's nonsense
What (compiled) language syntax have common with (runtime) performance? Take a nap, please, so I will do too.
October 10, 2025 at 6:19 AM
What (compiled) language syntax have common with (runtime) performance? Take a nap, please, so I will do too.