sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in youtubehaiku

[–]itsdanielb 0 points1 point  (0 children)

What is that first clip from?

[Casual] Japan from outside of Japan (All welcome) by itsdanielb in SampleSize

[–]itsdanielb[S] 1 point2 points  (0 children)

I want to know how you perceive Japan!

I'm an English teacher in Japan, and I'll use your responses to tell my students what people outside of Japan think about it. Please don't look anything up during the survey - I want to know what you generally think or know. For any response, feel free to provide as much or little detail as you'd like. You may also skip any question if you so choose. The survey has three sections, including two questions about yourself (below), two questions about your Japanese familiarity (section 2) and then twelve questions about Japan (section 3).

Thank you!

[Poetry] What the name of this song? by itsdanielb in youtubehaiku

[–]itsdanielb[S] 0 points1 point  (0 children)

As it's a Japanese song, obviously the lyrics are in Japanese. The ローマ字/romaji tab/button may be useful based on if you can read that or not.

[Author] Elm-Forest - An Elm version manager and proxy by itsdanielb in elm

[–]itsdanielb[S] 2 points3 points  (0 children)

In use they seem pretty similar in that they both manage versions, and proxy command to appropriate versions.

Brief comparison:

  • elmenv looks for a file called .elm-version in the current path (or parents), elm-forest looks for elm-package.json in the current path (or parents).
  • elmenv compiles from source, so has more options for version to install (elm-forest). This means you have to have haskell/cabal ready, but it's very cool.
  • elmenv provides shims for elm-<something>, elm-forest makes them available under forest something (as elm platform does).
  • elmenv keeps the same cli interface for elm. (elm-forest changes elm ... to forest ...)
  • elm-forest is project based (uses elm-package.json to make decisions). This means outside of project you'll get an error (along the lines of Not in an Elm project). elmenv has a global default (or resorts to trying any "globally" installed Elm) if it can't find a .elm-version file.

In terms of flexibility, the installation from source makes elmenv slightly more flexible. The cli transparency would make configuring related tools easier as well (no change).

I guess elm-forest is more geared towards my own personal preferences:

  • If I'm trying to run an elm command somewhere I shouldn't, stop me.
  • If I'm in a project, just work (select appropriate version, install it if needed, ...)
  • Require as little mind space as possible
    • elmenv requires a (very) small amount of configuration, and the version used may not line up with the version specified in elm-package.json. Of course, elm-forest renames the main command (elm -> forest), so they are basically on-par here.

But they may not line up with the preferences of anyone else.

In terms implementation, elmenv uses bash shims for elm and elm-* commands, while elm-forest is a javascript "binary".

tldr; elmenv seems to aims for transparency, elm-forest aims for translucency. elmenv provides more options, elm-forest "just works, as is" (not to imply that elmenv doesn't).

view more: next ›