Besides that, no type signatures without parameters and other things just produce a lot more code than you'd have in a nicer type system.
232 karma · joined May 10, 2019
Besides that, no type signatures without parameters and other things just produce a lot more code than you'd have in a nicer type system.
My issues with it are that it's just an extremely verbose language. Just like all Microsoft languages. All the while lacking advanced type system features like algebraic data types, pattern matching etc.
This is a good list of how to use common React patterns in Typescript.
Meanwhile, the Chinese PLA certainly doesn't suffer from any manpower shortages to contain the situation when they eventually want to.
That said, myself I still write Flutter too, having jumped ship from React Native.
I don't know what you are trying to build on mobile but I'd definitely learn Flutter instead of RN, which I have. Others here have said you should just go full native instead, and they're probably right.
So I'm also interested in hearing more elaboration on how Flutter has been a struggle for you.
That would put you close to the 1% of the top earners in Finland. Even most mid-sized company CEOs don't make nearly that much.
Which is of course a fair point. A language by itself is probably not even in the top 3 considerations when choosing new tech. Stuff like runtime, ecosystem and the amount of available developers would probably be more important in most cases.
An effective use of a type system such as Haskell's Hindley-Milner can result in a vastly smaller surface area for possible problems and thus can cut a big number of otherwise mandatory unit tests off your todo list.
Much of this surely can be abstracted away to 3rd party libraries/frameworks. Haskell, even though a higher level language than most out there, lacks the ecosystem support for a lot of things that are handled by some library in lower level languages.
But since Elm is a DSL it can afford to cap the abstraction somewhere whereas Haskell is perhaps built for more complex problems than just a client facing web UI.
Having learned both, I feel the abstraction level is capped too low on Elm, sadly.
But since Haskell's ecosystem is small by comparison a lot of that logic leaks to your own application code. Especially when dealing with something like stateful websocket applications.
I think you guys should set up a website to explain and promote this a bit better. Basically how you introduced it here but just on a website.