teekoiv

5 ms·

1.
by teekoiv 8mo ago
https://teemukoivisto.xyz/
2.
by teekoiv 8mo ago
https://teemukoivisto.xyz
3.
Nokia launches new defense smartphone(nokia.com)
2 points by teekoiv 1y ago|0 comments
4.
An AI-Powered MTG Set Generator(wingedsheep.com)
3 points by teekoiv 1y ago|0 comments
5.
by teekoiv 1y ago
Right. So a custom build system which changes the built pages from dynamic path folders to named folders in a day. No bugs. Sure. Also I serve rich-text content with links so those gotta be rewritten as well.
6.
by teekoiv 1y ago
That's cool but I fail to see how this results in 100% static bundle.
7.
by teekoiv 1y ago
It doesn't really matter from user's point of view if the response is 200 or 404 if the end result is the same. This is just a rendered web page after all. But yeah, you can get stuck in the semantics of it but I personally just u
8.
by teekoiv 1y ago
No. I disagree, you have to refactor all the pages from using [pathId] folder pattern and change all the links including switching to useSearchParams. It's just a huge change, especially if I want to keep the old routes in my web app.
9.
by teekoiv 1y ago
Interesting. You can set up the server to respond with 200.html as the catch-all so the requests would return 200. There was some issue with it—can't remember what—which is why I switched to 404.html. After the initial load though the
10.
by teekoiv 1y ago
It doesn't. Those are executed build-time and you can't just set a wildcard so anything outside the given set results in 404. As background, I wanted to make a PoC with NextJS bundled into a static CapacitorJS app somewhat recentl
11.
by teekoiv 1y ago
Yeah, what the other commenter said. getStaticPaths still requires you to define the rendered routes build-time
12.
by teekoiv 1y ago
It's baffling to me why more SSR frameworks, Astro and NextJS namely, can't adopt static pages with dynamic paths like SvelteKit. So for example, if you have a page /todos/[todoId] you can't serve those in your stat
13.
by teekoiv 2y ago
I very much agree with the overall thesis of the post. Runes are just irksome in subtle ways. One big point that the post misses, is that the Class escape hatch for runes is incompatible with constructor-set parameters. Say you have a class
14.
by teekoiv 2y ago
Runes annoy me because they ruined the use of Svelte components as rendered widgets outside a Svelte site. I like using them in rich-text as rendered views but when Svelte 5 came out, the old way of simply setting the component props direct
15.
by teekoiv 2y ago
Well I'd say this is rather clumsy attempt with no real upside on my side. 10% of imaginary profits for giving access to my computer, IP, Upwork—not even taking into consideration the illegality—with zero guarantees I'll see a sin
16.
Ask HN: Is Upwork contracting through other people's accounts a thing?
1 points by teekoiv 2y ago|4 comments
17.
by teekoiv 2y ago
Damn. I did use webmidi to wrap the access but apparently there's something missing. Works with my MPK3. Thanks for the feedback.
18.
by teekoiv 2y ago
Great job on launching! It sure does feel good to ship something and get a positive reaction. I don't want to steal your thunder but I did something similar a year ago and posted it here with a fresh HN account without much fanfare. h
19.
Show HN: Music notation training app with Web MIDI(midi-note-trainer.teemukoivisto.xyz)
5 points by teekoiv 2y ago|0 comments
20.
by teekoiv 2y ago
Location: Helsinki Remote: Yes Willing to relocate: No Technologies: JS/TS, HTML/CSS, NodeJS, Svelte, React, Vue, ProseMirror, Tailwind, AWS, Terraform, Postgres Résumé/CV: https://teemukoivisto.xyz&#x
21.
by teekoiv 3y ago
Location: Helsinki Remote: Yes Willing to relocate: No Technologies: Rust, TS/JS, NodeJS, Svelte, React, Terraform, Ansible, ProseMirror, HTML/CSS, Tailwind Résumé/CV: https://teemukoivisto.xyz/cv