未加星标

#code2016

字体大小 | |
[前端(javascript) 所属分类 前端(javascript) | 发布者 店小二04 | 时间 2017 | 作者 红领巾 ] 0人收藏点击收藏
Haskell

I started learning Haskell in the middle of 2015 with the help of this amazing Haskell book . But even after almost a year and a half I am still not at the level where I would feel comfortable when having to write something in Haskell.

I am not the smartest person, but also I am not the dumbest person. I am a busy person, but even after spending extra time with Haskell, I still can not find myself being productive with it.

Haskell makes me feel dumb, but not in a good way.

I will learn Haskell one way or the other, but I am hoping that there will be a language that will take most of the good ideas from Haskell and make it more approachable. I do not think being approachable is a priority for Haskell community. Which is OK, just not what I am looking for.

Rust

After a year of playing with Rust (once a month) I am slowly starting to become more confident with it. Still a long way to go, but it looks like this might be my next go to language .

At times Rust feels like Perl.

The only thing I really dislike (at times) is the syntax. I guess with age aesthetics is becoming less important.

I am yet to do any interesting with Rust , but 2017 might be the year this will change.

Elm

Giving Elm a try, was the best decision I ever made in a long time. Not only I gave it a try, but we ( Release Engineering team at Mozilla ) started to use it for some of our applications . Probably reasons why we went with Elm requires a separate blog post, but I am sure we will be using it more and more.

The most innovative thing with Elm is not the syntax or type system or anything technical, but the idea to focus on simplicity, while taking the best ideas from Haskell and functional world.

Learning Elm is easier then any javascript framework.

I see Elm actually already became my go to language for any front end work. I hope in the future this could be expanded to back end (e.g. elm-node ) or even different compilation targets then JavaScript. I wonder if I can teach my wife Elm.

JavaScript

I still write a bit JavaScript from time to time, but with Elm around, this is happening less and less. Yaaaay!

At work we created a simple bootstrapping library, called Neo . That should make bootstrapping a JavaScript (or Elm) project a problem of a past.

Another exiting thing that came out of 2016, was that finally people got sick of npm and developers at Facebook wrote yarn (a npm replacement). I am yet to try it out but from initial looks it seems like the right direction to go.

I might not be writing JavaScript myself, but I know many are. Having a sane package manager (like yarn) is then even more important for me.

In the future I don't see myself spending much time with JavaScript.

python

Everybody at work is mostly familiar with Flask , which meant it was time for me to look into it. Majority of things feel wrong since the framework doesn't guide you to best practices, but expects you to figure out best practices on your own, or you copy paste them from somewhere (they do document them nicely). It makes me miss the Pyramid framework quite a lot.

On the bright side I got introduced to connextion project (by Zalando ), since I am building quite some number of JSON API endpoints. What surprised me - in a positive way - is that having a language, swagger / openapi , that describes your JSON API a huge win for all the team.

early prototyping with the team without writing a single line of code. automatically documenting your APIs. easier to enforce best practices across all APIs. automatically generating API clients for different languages back end code now doesn't even look Flask specific, which should make it more future proof if new awesome framework comes along.

Another thing that I noticed this year is that the way I write python code this days is quite different from the code I was writing in the past. I almost stopped using class -es. I guess I got influenced by Elm , Haskell and Nix , to think in a more functional way.

Until I pick up my Rust knowledge Python is going to remain my go to language for back end. There are libraries I want to give a try in 2017: hypothesis (along with pytest ), effect , mypy , typo .

Nix

I work with Nix almost on a daily basis. Either for work or in my free time. I hope to promote Nix even more in 2017. I wont write much about Nix here because I mostly blog about things related to Nix and you can just checkmy blog for this.

Looks like 2017 is going to be the year of Nix.

If we only find a way and time to make more approachable :)

Misc

I am more and more convinced that programming should be a social experience and that programming in pairs or groups can not only be fun, but help improve everybody that participates.

I wish to do more pair programming in 2017.

Happy 2017.

本文前端(javascript)相关术语:javascript是什么意思 javascript下载 javascript权威指南 javascript基础教程 javascript 正则表达式 javascript设计模式 javascript高级程序设计 精通javascript javascript教程

主题: JavaScriptJavaRustFacebookPerlPython
分页:12
转载请注明
本文标题:#code2016
本站链接:http://www.codesec.net/view/519798.html
分享请点击:


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 前端(javascript) | 评论(0) | 阅读(45)