Noway. Is this pure HTML? Some of every browser?
In Svelte sure, that code will run before rendering.
In the browser something similar may happen too, let's try timeout, tick, ready event.. defer script tag..
Please write back if you know what happened.
Thanks
What???
Pure hacks of the era. Needs vs compatibility.
Love the Unicode. It's almost the same. 🪲🦕 ❤️
Really great talk! I enjoyed the demo a lot!
Deno v2.6.6 just shipped with 11 bug fixes for Node compatibility, OTEL for cron, better `@types` handling, improvements to `deno task` and more.
Check out full changelog at github.com/denoland/den...
Don't wake me up after midnight.
I'm rude, after all.
Shout, tell, open to all, but rude.
Wake me up, talk to me down, let me sleep a pile of the clouds. Please
HTTP GET thing://
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.
Try at first to filter out obvious edge cases. You will be surprised ;-)
I just completed all 12 days of Advent of Code 2025 in #Deno @deno.land!
github.com/langpavel/ao...
#AdventOfCode adventofcode.com
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 ;-)
```
const {createForm} = createFormFactory(...);
const formState = createForm(...);
```
createFormFactory?
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
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
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.
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.
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.
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 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.
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
What (compiled) language syntax have common with (runtime) performance? Take a nap, please, so I will do too.
How does file upload works?
For example multiple images?
Go ahead to TS only! 🤣 With JSR!
There is Deno 🦕 ready for this natively at this time, but go forward!
Node will be ready soon, they are preparing with flags!
Ten years and NPM & browsers will be capable of (omitting) types too
Just kidding but go with modules now
