Comments URL: https://news.ycombinator.com/item?id=44845397

Points: 2

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=44796187

Points: 3

# Comments: 0

[1]: https://www.cnet.com/home/electric-vehicles/this-donut-shape...

Comments URL: https://news.ycombinator.com/item?id=42631876

Points: 70

# Comments: 39

The [VS Code] WSL back-end has access to things in WSL PATH, like compilers and language servers. I don't duplicate them in Windows, and would like to avoid having double installs. It's also nice to be able to open integrated terminal and use `fish` and other unix-only CLI utilities.

Though many games have been built with Elm, I've had to implement lots of "game engine" code myself. For example, the collision system, physics (acceleration etc.), and path finding are custom code. It's worth mentioning that this is my fist gamedev project, and I've had to read up a quite a bit on the topic. Still the difficult was not in Elm itself, but in math and data structures, as it would be on any language.

Elm's lack of runtime exceptions and mutable state makes any game quite robust. Most of the bugs in Liikennematto have been of omissions (forgot to update something) and in math formulas. 3rd party Elm libraries are often excellent with great docs and have helped along the way.

Lastly Elm is quite performant (pure functions can be inlined and easily optimized) and I can create a single .js file that contains the game code, UI and the assets (which are still SVG in Elm). The whole game is still about 1 megabyte minimized! I think that's amazing, despite not shipping the runtime enviroment (the browser).

This has been a fun (and rather long) project. I craved for a simple city builder that a toddler could play and understand. You might want to start from the first devlog entry to see where Liikennematto came from.

You can play Liikennematto in your browser on itch.io[1] (the link is buried at the end of the article).

[1] https://yourmagicisworking.itch.io/liikennematto

I want to share with you this tiny tool that I recently hacked together.

It's trivial in nature - a web version of the Greenwich Time Signal that's often played when a news broadcast starts.

Though you can reset the seconds on your digital watch by visual means (like another synced clock), I think that a sound indicator helps with the timing. With that in mind, this tool fills a very small niche.

The original time signal is slowly being phased out from linear broadcasts, and other official sources are being discontinued [1]. I want to help preserve this part of analogue history in a digital format and provide a fallback.

https://matiasklemola.com/time-signal

[1]: https://www.theguardian.com/world/2023/oct/12/canada-officia...

Comments URL: https://news.ycombinator.com/item?id=38923188

Points: 3

# Comments: 1

https://package.elm-lang.org/packages/ianmackenzie/elm-units...

...which is used in other packages where unit type safety is important, such as elm-geometry:

https://package.elm-lang.org/packages/ianmackenzie/elm-geome...

Comments URL: https://news.ycombinator.com/item?id=25217793

Points: 6

# Comments: 2

Comments URL: https://news.ycombinator.com/item?id=24381781

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=23320045

Points: 4

# Comments: 0

I found that the examples showed individual features well, but when you combine features you are on your own. The "Kitchen Sink" example is far from having all features enabled at once.

The reason why I couldn't stay with v6 was that the virtualization examples used a deprecated API from an old minor version. I would have had to support a solution on a non-supported version (v6 has been pretty much abandoned).

So, I had to get these features to coexist peacefully:

- expanded rows

- virtualization

- sorting

- custom cell rendering

- click actions inside the cells (open a dialog, add the row entity to comparison)

Mirroring the GP, I had to use react-window and deal with the complexity from the library. I think that virtualization should be a first-class citizen inside react-table, like sorting.

On top of all of this the TypeScript support/typings are tricky to work with (IIRC you have to maintain a .d.ts file in your codebase and remember to update it when you update react-table). I literally had a headache for hours on while going through the refactoring.

In the end I managed to get everything to work without any bugs or weird behavior. I really was enthusiastic about v7, but was left with a bad feel of it.

I'm sure that things will get better, and luckily most folks don't beed all of these features. It's really the virtualization that makes things complicated. The thing is, pagination is not always a viable solution.

To save other people trouble, I should update the Codesandbox that I originally built (https://codesandbox.io/s/react-table-virtualized-subcomponen...).

Comments URL: https://news.ycombinator.com/item?id=22234414

Points: 2

# Comments: 0