vapourismo's comments

vapourismo | 7 years ago | on: Learn You a Haskell for Great Good

I wouldn't really consider stack to be a great tool. There is Stackage which may be useful but the tool itself falls apart quickly when used to compile more than a single package executable.

That being said, one should have looked at these:

  - cabal Nix-style builds
  - ghicd for continuous type-checking
  - stylish-haskell for light code formatting
  - brittany for slightly more invasive code formatting
  - hlint for linting

vapourismo | 7 years ago | on: If Haskell is so great, why hasn't it taken over the world? (2017)

I don't see how that is a big problem.

vapourismo | 7 years ago | on: If Haskell is so great, why hasn't it taken over the world? (2017)

Certainly it isn't the most attractive solution - still it is possible and works well.

When it comes to moving things across FFI barrier, that is also very possible as there are all kinds of types (including stable pointers) in the Foreign.* modules that map onto C types.

vapourismo | 7 years ago | on: If Haskell is so great, why hasn't it taken over the world? (2017)

You'd be surprise how much weirder it gets when everything is evaluated eagerly.

vapourismo | 7 years ago | on: If Haskell is so great, why hasn't it taken over the world? (2017)

GHC can produce native libraries just like C or Rust.

vapourismo | 9 years ago | on: Why Deutsche Bundesbank had to promise to leave 1200 tons of gold in New York

How do airplanes work?

vapourismo | 9 years ago | on: Seven years of Go

What is your argument?

vapourismo | 9 years ago | on: Seven years of Go

So, Go with a more expressive type system is a worse Go?

vapourismo | 10 years ago | on: Germany's Wi-Fi Shortage Set to Ease as Merkel Backs New Bill

https://de.m.wikipedia.org/wiki/Unterlassungserklärung

I think that is what you need.

vapourismo | 10 years ago | on: Show HN: Another C++ Lua Wrapper

I've found that most libraries implement the wrapper around C++ functions in the most terrible way. It ranges from userdata types wrapping std::function objects to wrapping the lua_State, which the users have to interact with themselfs.

Luwra uses inlinable functions and templates almost exclusively. That way (best-case scenario), each wrapped field/method/constructor/function implies only one generated lua_CFunction, which invokes the Lua API to retrieve the values and finally call the wrapped function with them. And all that, during compile-time, which in my opinion is the best part about it.

vapourismo | 10 years ago | on: Show HN: Another C++ Lua Wrapper

Also variable templates, which are crucial to generating the metatable name for user types.

vapourismo | 10 years ago | on: Show HN: Another C++ Lua Wrapper

Hope it works for you - love to hear some additional feedback.

vapourismo | 11 years ago | on: Germany’s great tuition fees U-turn

400€ per year or per semester? Where? I am at the Institute of Technology in Berlin and I payed 290.37€ this semester, which includes 179.40€ for public transport.

vapourismo | 12 years ago | on: The Best Programming Language (or How to Stop Worrying and Love the Code)

May I have fries with that?